Talk:Func Spec Admin

User Management

• 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)

UC_LA_UM_01 Create account user

• Somewhere the predefined subject, text and link for the confirmation request should be specified --Kristina 10:54, 4 November 2009 (UTC)
• That means that one user can only belong to one organizational unit. Perhaps sometimes a user belongs to more than one? --Kristina 11:02, 4 November 2009 (UTC)
• This use case should be extended by the use case Assign priviledges to the user, because without priviledges, the user can not work. --Kristina 11:04, 4 November 2009 (UTC)

UC_LA_UM_02 Edit account user

• in UC_LA_UM_05 Activate user you say, that edit account user can be used as extension point --Kristina 10:54, 4 November 2009 (UTC)

• this has to be listed in this use case as possible trigger
• the user himself can also be an actor, not only the local admin

• That means that the local admin can change the password for each of "his" users. Is that what we want? --Kristina 11:01, 4 November 2009 (UTC)

UC_LA_UM_04 Delete/inactivate account user

• Step 2-3: Hier ist irgendwie der Wurm drinn --Kristina 11:10, 4 November 2009 (UTC)

• 2.1 Wenn nur items in state pending existieren, dann step 5 (account user wird deleted). Sollte hier nicht erst die Liste mit allen pending alben gezeigt werden (step 3)
• 2.2 Wenn es auch items in anderen stati als pending gibt, sollte der user nur inactive gesetzt werden (step 6)

UC_LA_UM_06 Create user group

• Step 5: The user defines the group selectors by choosing --Kristina 11:15, 4 November 2009 (UTC)

• Shall the system display a list of all available organizational units or users?

Context Management

• 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)

UC_LA_CM_02 Edit context

• Extension point to UC_LA_CM_07 Assign validation rules to a context is missing --Kristina 11:27, 4 November 2009 (UTC)

UC_LA_CM_05 Delete a context

• Post-Conditions / Results: The context and all items in state “pending” are deleted and no longer available for any system action.

• Which items in the state pending? I thought when a context is still in the state pending, no corresponding items can be created? --Kristina 11:25, 4 November 2009 (UTC)

Organizational Unit Management

UC_LA_OUM_01 Create organizational unit

• A lot of aspects within this UC are also part of the edit UC. Wouldn't it be nicer yust to mention the create functionalities here and then continue with UC Edit Organizational Unit? --Kristina 12:45, 4 November 2009 (UTC)

UC_LA_OUM_02 Open organizational unit

• In this UC, some functionalities from edit OU are integrated, but not all. Wouldn't it be nicer to make an extension point to edit? --Kristina 12:44, 4 November 2009 (UTC)

General Feedback

• 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)
• What is the difference between a publication and a modification workflow? --Friederike 10:50, 4 November 2009 (UTC)

Lightweight Directory Access Protocol

Use Case

Coordinated Universal Time

Publication Management

Organizational Unit

Control of Named Entities