PubMan Func Spec Browse By

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

UC_PM_B_01 browse by organizational unit

The user browses by organizational unit.

Status/Schedule

• Status: implemented
• Schedule:6.1

Triggers

• The user wants to browse by organizational unit.

Actors

• User

Pre-Conditions

• None

Flow of Events

• 1. The user chooses to browse by organizational unit.
• 2. The system displays all organizational units, see 'Display' for details.
• 3. (Optionally) The user chooses to view the child organizational units of an organizational unit.
  • 3.1. The system displays all child organizational units of the selected organizational unit.
• 4. (Optionally) The user chooses to view the items of an organizational unit.
  • 4.1. The system searches for items where the organization is linked to the selected organizational unit or any child organizational unit in the structure and displays the result list. Include use case UC_PM_BD_02 view item list.
  • 4.2. (Optionally) The user chooses to view detailed information of the selected organizational unit.
• 5. The use case ends successfully.

Future development

• The user can choose to also include the history of affiliations (successors/predecessors) in the search of items of an organizational unit. (scenario for the history of affiliations in browsing)
• Display current number of publications behind each organisational unit member

Display

• Tree

UC_PM_B_02 browse by creator

Status/Schedule

• Status: in implementation
• Schedule:6.1

Triggers

The user wants to view all creators and corresponding items

Actors

User

Pre-Conditions

None

Flow of Events

• 1. The user chooses to browse by creator.
• 2. The system displays all creators who have a cone identifier, see 'Display' for details..
• 3. (Optionally) The user chooses to view the items of a creator.
  • 3.1. The system searches for items where the selected person is creator of, and displays the result list. Include use case UC_PM_BD_02 view item list.
  • 3.2. (Optionally) The user chooses to view the researcher portfolio of a creator.
    • 3.2.1. The researcher portfolio of the selected creator is displayed.
• 4. The use case ends successfully.

Display

• 2 Steps:
  • 1) Character (A-Z)
  • 2) Creator Names

Future Development

• Display current number of publications behind each creator.
• Give user the possibility to choose if only role 'author' or any role (currently any role).

UC_PM_B_03 browse by subject

Status/Schedule

• Status: in implementation
• Schedule:6.1

Triggers

The user wants to view all subjects and corresponding items

Actors

User

Pre-Conditions

None

Flow of Events

• 1. The user chooses to browse by subject.
• 2. The system displays all subjects who have been assigned to an item in the repository, see 'Display' for details..
• 3. (Optionally) The user chooses to view all items related to a specific subject.
  • 3.1. The system searches for items who are related to that specific subject and displays the result list. Include use case UC_PM_BD_02 view item list.
• 4. The use case ends successfully.

Display

• 2 Steps:
  • 1) Character (A-Z)
  • 2) Subject Name

Future Development

• Browse By Free Keywords
• Inclusion of Tag Cloud
• Change display style to hierarchical (instead of numerical) order, if it turns out that it is more appropriate for users (e.g. for ddc or pacs).
• Display current number of publications behind each subject

UC_PM_B_04 browse by journal

Status/Schedule

• Status: specified
• Schedule:6.1 Prio 2

Triggers

The user wants to view all journals and corresponding items

Actors

User

Pre-Conditions

None

Flow of Events

• 1. The user chooses to browse by journals.
• 2. The system displays all journals who are in cone, see 'Display' for details.
• 3. (Optionally) The user chooses to view the related items of a journal.
  • 3.1. The system searches for items with this journal and displays the result list. Include use case UC_PM_BD_02 view item list.
  • 3.2. (Optionally) The user chooses to view the details of this journal (all info available in cone, e.g. publisher, address).
    • 3.2.1. The details of the selected journal are displayed.
• 4. The use case ends successfully.

Display

• 2 Steps:
  • 1) Character (A-Z)
  • 2) Journal Names

Future Development

• Display current number of publications behind each journal

UC_PM_B_05 browse by year

Status/Schedule

• Status: in implmentation
• Schedule:6.1

Triggers

The user wants to view all years and corresponding items

Actors

User

Pre-Conditions

None

Flow of Events

• 1. The user chooses to browse by year.
• 2. The system displays all years, see 'Display' for details.
• 3. (Optionally) The user chooses to view the related items of a year (publication date).
  • 3.1. The system searches for items with this year as publication date and displays the result list. Include use case UC_PM_BD_02 view item list.
• 4. (Optionally) The user chooses to view the related items of a year (any date).
  • 4.1. The system searches for items with this year as any date and displays the result list. Include use case UC_PM_BD_02 view item list.
• 5. The use case ends successfully.

Display

• Chronological order, ascending from the oldest publication in the repository
• The user can choose if only searching for publication date or any date (publication date is default).

Future Development

• Display current number of publications behind each year
• As soon as we can know the number of entries we can also bundle the years to packages of 10/20 items or so.

UC_PM_B_06 browse by event

Status/Schedule

• Status: tbd
• Schedule:tbd

Triggers

The user wants to view all events and corresponding items

UC_PM_B_07 browse by language

Status/Schedule

• Status: tbd
• Schedule:tbd

Triggers

The user wants to view all languages and corresponding items

Comment

• Here we should only display languages which have actual items related to.

Publication Management

Use Case