-
Notifications
You must be signed in to change notification settings - Fork 0
Move EE data to intranet #123
Comments
|
@ballaschk: Lets talk on Monday to discuss the #124 approach. |
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 So we extend out person object with
|
"Positions" has beed finished Mar 2024. But now "Sonderfunktionen" and "Title" is also wanted. Added |
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:
These person fields should be managed by mpicms
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.
The text was updated successfully, but these errors were encountered: