Comment 1 Valentin Heidelberger 2018-12-03 15:18:45 CET

It would be nice to have an attribute for ImportUser similar to school_classes for workgroups

Comment 2 Sönke Schwardt-Krummrich 2018-12-03 15:24:17 CET

Another customer is using a special hook for advanced courses (Kurssystem für Oberstufe), which is a similar use case. Maybe we should add a generic solution here.

Comment 3 Daniel Tröder 2018-12-03 15:31:01 CET

(In reply to Johannes Kenkel from comment #0)
> UCS@School clients like to import/create workgroups by CSV import, besides
> the primary class/group.
Does the customer have
* a list of workgroups in a CSV file, or
* a list of students in a CSV file? (And the workgroups should be created on the fly?)

Comment 4 Johannes Kenkel 2018-12-04 18:45:43 CET

The client likes to import a list of students in a CSV file and the workgroups should be created on the fly!
But comparable requirements will appear from project Basel in the near future and they might have slightly different implementation requirements...

Comment 5 Daniel Tröder 2018-12-05 07:56:33 CET

In that case I think an attribute with the same syntax as "school_classes" (like Valentin suggested) would work.

In Python that would be: 

ImportUser.work_groups = {'OU1': ['name1', 'name2'], 'OU2': ['name1']}

It would be encoded in CSV like this: 'OU1-name1,OU1-name2,OU2-name1'

In LDAP work groups are groups like school_classes with a name '$OU-$NAME' →
cn=OU1-name1,cn=schueler,cn=groups,ou=OU1,$base

So the problem here is, that importers must take care not to create work groups and school_classes with the same name.

BTW: When trying to create a work group with a name for wich a school_class already exists, the UMC shows the error: "The workgroup 'SchuleEins-1a' already exists!", which is wrong in two ways: a) its not a work group and b) the name is "1a", the school should be displayed separately, the internal encoding should not be shown.

Comment 6 Jan-Luca Kiok 2023-06-23 13:15:50 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and UCS components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.