Difference between revisions of "PubMan Func Spec Collection Administration"

From MPDLMediaWiki
Jump to navigation Jump to search
(New page: =UC_PM_CA_01 create a collection= Category:PubMan)
 
Line 1: Line 1:
=UC_PM_CA_01 create a collection=
==UC_PM_CA_01 create a collection==
One or more organizational units need a new collection as an administrative container for managing their items.
===Triggers===
• The user wants to create a new collection for one or more organizational units.
===Actors===
• Local Administrator
===Pre-Conditions===
• .At least one publication workflow and one modification workflow are available.
===Flow of Events===
*1. The user chooses to create a collection.
*2. The system displays a list of all open organizational units and subunits for which the user has the privileges as local administrator.
*3. (Optionally) The user chooses to view the organizational unit description.
**3.1. The system displays the organizational unit description
*4. The user selects one or more organizational units and confirms the choice.
*5. The system creates a collection in the state “created” with the selected organizational unit(s) and the standard workflows predefined. By default all available genres are selected as “allowed genres”, all available submission methods are selected as “allowed submission methods”.
''Comment Natasa: According the set-up of the context in the core services: we first define the content types allowed in the context and only then we define the allowed genres for the metadata profile associated as a default with the content type (i.e. in case the metadata profile in use is genre specific).''
*6. Continue with use case UC_PM_CA_02 edit collection with the created collection as selected collection. The use case ends successfully.
===Post-Conditions / Results===
• A new collection in the state “created” has been created.






[[Category:PubMan]]
[[Category:PubMan]]

Revision as of 09:59, 22 November 2007

UC_PM_CA_01 create a collection[edit]

One or more organizational units need a new collection as an administrative container for managing their items.

Triggers[edit]

• The user wants to create a new collection for one or more organizational units.

Actors[edit]

• Local Administrator

Pre-Conditions[edit]

• .At least one publication workflow and one modification workflow are available.

Flow of Events[edit]

  • 1. The user chooses to create a collection.
  • 2. The system displays a list of all open organizational units and subunits for which the user has the privileges as local administrator.
  • 3. (Optionally) The user chooses to view the organizational unit description.
    • 3.1. The system displays the organizational unit description
  • 4. The user selects one or more organizational units and confirms the choice.
  • 5. The system creates a collection in the state “created” with the selected organizational unit(s) and the standard workflows predefined. By default all available genres are selected as “allowed genres”, all available submission methods are selected as “allowed submission methods”.

Comment Natasa: According the set-up of the context in the core services: we first define the content types allowed in the context and only then we define the allowed genres for the metadata profile associated as a default with the content type (i.e. in case the metadata profile in use is genre specific).

  • 6. Continue with use case UC_PM_CA_02 edit collection with the created collection as selected collection. The use case ends successfully.

Post-Conditions / Results[edit]

• A new collection in the state “created” has been created.