Talk:Func Spec Admin

User Management[edit]

User accounts:
- for both create/edit account user, it should be stated that these are the use cases that are valid only for local user management.
- it should also be stated, that in case of identity provider e.g. LDAP, these are externally implemented.
- there is the concept of the user-attributes that needs to be provided with the newest core-service. However it is not fully clear how the implementation would happen. Would be known after stable 1.2 core-service release.

Integrated in UC --Friederike 09:47, 4 November 2009 (UTC)

User groups:
- maybe a bit clearer description on editing of the user group.
- it's cumbersome to state that user would like to change "affiliated persons in the user group". When editing a user group, user is modifying the selectors of the user group (thus implicitly users that are members of the user group).

Integrated in UC --Friederike 09:47, 4 November 2009 (UTC)

it is wrong to have one publication or one modification workflow available
- these settings are part of the admin descriptor (depending on the type of the context i.e. PubMan, Faces etc..) - admin descriptors may have different settings

Changed in UC --Friederike 09:55, 4 November 2009 (UTC)

When creating or changing a user account, the corresponding user gets a information message. It would be verry good, if this messages are easily changeable by the local admin and also by us (e.g. via static html pages) as the requirements for these texts can change from institution to institution (and also from solution to solution). --Kristina 10:51, 29 October 2009 (UTC)

Integrated in Preference Management UC --Friederike 09:29, 3 November 2009 (UTC)

It would be nice that all lists that occur in the admin interface are sorted alphabetically (perhaps the sorting can be changed to last created/edited, too). --Kristina 10:51, 29 October 2009 (UTC)
Will CoNE be of any importance in this scenario, or is this independent from Admin Solution? --Friederike 16:22, 3 November 2009 (UTC)