PubMan Func Spec Basket

PubMan Functional Specification View · Browse Full Submission · Easy Submission Import · Export Quality Assurance · Search Collaboration · Copyright Collection Administration Organizational Unit Management User Management Feeding local webpages History of affiliations edit

Add one or more item(s) to basket

Status/Schedule

• Status: implemented

Triggers

• User wants to combine results of several resources for common reuse, like export.
• User (librarian) wants to collect entered/modified items to create a list.

Actors

• User

Pre-Conditions

• Basket may be empty or filled with items.
• None of the items that should be added are in basket.
• Item can be in any status.

Flow of Events

• 1. The user chooses to view a list of items by executing one of the above mentioned use cases.
• 2. The system displays the number of items and the list of items. The defaults for the display type (see PubMan Display), the sorting order (see PubMan Sorting) and the number of hits per page are given by the system (= by default: 10 hits per page) or are taken from the users preferences if available.
• 3. (Optionally) The user changes the sorting order.
  • 3.1. The system displays the item list in the selected sorted order.
• 4. (Optionally) The user chooses another number of hits to be displayed per page.
  • 4.1.The system displays the item list containing the selected number of hits per page.
• 5. (Optionally) The user changes the display type.
  • 5.1. The system displays the item list in the selected display type.
• 6.(Optionally) The user changes the display type for one item.
  • 6.1.The system displays the item in the selected display type.
• 7. The use case ends successfully.

Post-Conditions / Results

• The item list is displayed in the selected sorting order containing the defined number of hits per page and the items are displayed in their selected display type.

Add several item versions to basket

Status/Schedule

• Status: implemented

Triggers

• The user wants to view the details of the item version.

Actors

• User

Flow of Events

• 1. The user chooses to view the selected item version.
• 2. The system displays the data of the item version and the files. The possibility for download is offered for all files the user has privileges to access (for details see PubMan Visibility). The possibility to view detailed information about each organization related to the item is offered, providing that information on this organization is stored in the system.
• 3. (Optionally) The user chooses to download a file.
  • 3.1. The system provides the file for download.
• 4. (Optionally) The user (only logged in users of the corresponding context) chooses to send an E-Mail to the moderator of the context, the item is administrated at.
  • 4.1 A Link from view item version is displayed. When the user clicks on the link, a new window opens with to prefilled with the contact address of the moderator of the responsible context and with the escidoc Id prefilled as subject. Further more the user can write a text and then send the Mail. Currently we took the pubman-support@gwdg.de mail address, as the contact address can't be defined per context yet.
• 4. (Optionally) The user chooses to view detailed information about an organization related to the item.
  • 4.1. The organizational unit detail view ("description") (see UC_PM_BD_03 Browse by organizational unit, step 4 ) is displayed, including the description and related affiliations (with Start_Date/End_Date) of the organizational unit. See scenario for history of affiliations linked from item view.
• 5. (Optionally) The user chooses to view the researcher profile of an author related to the item.
  • 5.1. The researcher profile, including a list of publications and person information stored in the CoNE service (see UC View researcher portfolio), is displayed, if the respective author has an authorized CONE person ID.
• 6. Extension point: view release history
  • 6.1. If the user wants to view all released versions of the item and there is at least one released version of the item, include use case UC_PM_BD_05 view release history.

• 7. Extension point: view item event log
  • 7.1. If the user is in any role defined in the workflows for the item’s collection and wants to view the log entries for the item versions, include use case UC_PM_BD_06 view item event log.

• 8. Extension point: view revisions of item
  • 8.1. If the user wants to view all related revisions of the item and if there is at least one related revision of the item, include use case UC_PM_BD_07 view revisions of item.

• 9. Extension point: view item statistics
  • 9.1. If the user wants to view the statistics for an item, include UC_PM_BD_08 view item statistics.

• 10. Extension point: create item from template
  • 10.1. If the user has the role “Depositor“ and wants to create a new item using the current item version as template, include UC_PM_SM_05 create item from template.

• 11. Extension point: create new revision of item
  • 11.1. If the user has the role “Depositor”, and the current item version is in state “released” and the user wants to create a new revision for that released version, include use case UC_PM_SM_11 create new revision of item.
• 12. Extension point: modify item
  • 12.1. If the user is allowed to start the modification workflow for the item, the last item version is selected and in state “released” and the user wants to modify that item version, include UC_PM_QA_11 modify item.
• 13. Extension point: withdraw item
  • 13.1. If the user is the owner of that item, the last item version is in state “released” and the user wants to withdraw that item, include use case UC_PM_QA_09 withdraw item.
• 14. Extension point: do simple export
  • 14.1 If the user wants to do a simple export of the item, include UC_PM_EX_02 Do simple export.
• 15. Extension point: grant or revoke audience privileges for files
  • 15.1 If the user as allowed to grant or revoke audience rights for files of an item , include UC_PM_UM_11_Grant_or_revoke_audience_privileges_for_files.
• 16. The use case ends successfully.

Alternatives

• 2a. The item is in state “withdrawn”.
  • 1. The system displays the withdrawal comment, the withdrawal date and the item data (see PubMan Display). The use case ends successfully.

Post-Conditions / Results

• The details of the item are displayed, including the information how to cite this item.

Publication Management

Control of Named Entities

Control of Named Entities

Identifier