Move EE data to intranet

[donald]

We want more data, which is now maintained in the Fiona Employee-Editor, to be edited from the intranet and transferred to the Fiona site via ldap:

These special collections should be managed by mpicms:

• position_* (already editable, but EE should be loaded from mpicms)
• status_*
• sf_*

These person fields should be managed by mpicms

• membership to status_* and sf_* collections
• title

Maybe use a special status for inactive/deleted contacts to be used as a filter for the people lists instead of a fake organizational unit. Currently there is "Aktiver/r Mitarbeiter/in", "Alumni", "externe/r Kooperationspartner/in", "Gast")

Or use sc_status ("Wissenschafterliche/r Mitarbeiter/in", "Nichtwissenschaftliche/r Mitarbeiter/in") ?

Or maybe even feed show_contact from mpicms. But we need to make sure, only the maintainer of the written agreements can change that flag.

[donald]

• 2DO: Review Helpdesk thread "Neue Position im Employee Editor" and collect everything from there into this issue.

[donald]

@ballaschk: Lets talk on Monday to discuss the #124 approach.

[donald]

[donald]

FTR: Positions (the set of available positions and their German and English names) are now managed in the intranet. However the assignment of Persons to Positions is not (yet). This is next.

Important: Following the helpdesk-thread "Import LDAP-->Employee-Editor" from 6.1.2022ff, we should not add Positions and other collections to the collectionId LDAP attribute. This would require a previous change in Employee-Editor to ignore these patterns. It is better to define a new LDAP attribute for each independent collection.

So we extend out person object with eePositionId: position_whatever, the same for other new collections.

collectionId: service
collectionId: AllgBereich
collectionId: service_it
eeStatusId: status_active
eeScStatusId: sc_status_niwimi
eePositionId: position_Leit_Servicegruppe
eeShowContact: TRUE
eeTitle: Dr.
eeAcademicSuffix: PhD