Description Daniel Tröder 2018-03-26 13:21:16 CEST

* Add section to UCS@school manual on how to retrieve LDAP objects using the new objectClasses or attribute.

* Add section about how to migrate existing objects.

+++ This bug was initially created as a clone of Bug #45379 +++

It would be very useful to provide all UCS@school objects with a unique object class / attribute (e.g.: ucsschoolObjectType=...). Based on already existing object class on the user objects:
Users: ucsschoolStudent / ucsschoolTeacher / ucsschoolAdministrator / ucsschoolStaff

I would like to see this also for groups:
Groups: ucsschoolWorkingGroup / ucsschoolClass / ucsschoolCompuerRoom


Why is this necessary?
At the moment it is really hard to find and identify all classes or all working groups. At the end they are all ldap groups. There are no difference between the objects, only the location in the ldap make a group to a class or a working group. Also, the objects do not differ from the default built-in groups.

Our claim is that the LDAP is the leading data source, so it must also be easy to find the data (e.g. for sync to external services).

I would suggest, that these unique object classes / attributes should be set during the import. Also, there must be an option to edit these options (like the user options).