Difference between revisions of "PubMan Func Spec History of affiliations"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 16: Line 16:


==History of affiliation in organizational unit management==
==History of affiliation in organizational unit management==
The service administrator wants to specify how an organizational unit has been created (e.g. as a replacement, fusion, spin-off or splitting of another organizational unit). The user chooses an edit view of the selected organizational unit, adds one or more organizational units from the organizational unit structure and specifies the exact form of the event. See [[PubMan_Func_Spec_Organizational_Unit_Management#UC_PM_OUM_06_Add_predecessor.2Fsuccessor_to_organizational_unit|UC_PM_OUM_06 Add predecessor/successor]]
The service administrator wants to specify how an organizational unit has been created (e.g. as a replacement, fusion, spin-off or splitting of another organizational unit). The user chooses an edit view of the selected organizational unit, adds one or more organizational units from the organizational unit structure and specifies the exact form of the event. Added organizational units are related as predecessors of the selected organizational unit. See [[PubMan_Func_Spec_Organizational_Unit_Management#UC_PM_OUM_06_Add_predecessor_to_organizational_unit|UC_PM_OUM_06 Add predecessor to organizational unit]]


==History of affiliations in advanced search==
==History of affiliations in advanced search==

Revision as of 10:06, 27 March 2009

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


Authors of items in PubMan are affiliated to one or more organizational units. These organizational units can merge into other organizational units, i.e. an organizational unit can have one or more predecessors and/or one or more successors.

Following types of relations are maintained:

  • An OU(1) has one direct successor OU(2) and not exists anymore in reality. The OU(1) is set in status closed (replacement).
  • An OU is founded as fusion from two or more other OUs (fusion). The new OU has multiple predecessors.
  • A part of an OU(1) is created as spin-off. The OU(1) exists beside the new OU(2) (spin-off).
  • An OU(1) is split-up into multiple new OUs (OU(3), OU(4), …) and has therefore multiple successors. OU(1) not exist in reality any longer and is therefore set to status ‘closed’. (splitting)


Scenarios[edit]

The user wants to track the history of an organizational unit. This affects browsing, search and organizational unit management.

History of affiliation in organizational unit management[edit]

The service administrator wants to specify how an organizational unit has been created (e.g. as a replacement, fusion, spin-off or splitting of another organizational unit). The user chooses an edit view of the selected organizational unit, adds one or more organizational units from the organizational unit structure and specifies the exact form of the event. Added organizational units are related as predecessors of the selected organizational unit. See UC_PM_OUM_06 Add predecessor to organizational unit

History of affiliations in advanced search[edit]

  • The user wants to search for items of a specific organizational unit. The user chooses an organizational unit from the browse tree (implemented)

History of affiliations in browsing[edit]

  • The user wants to browse by organizational unit. In the organizational unit structure the user can choose an organizational unit detail view to view a description. (implemented)
    • Information on all predecessors/successors of the selected organizational unit is also provided in the detailed view.
  • The user wants to see all items of an organizational unit. Choosing an organizational unit in the organizational unit structure, a search result list is displayed showing all items of the selected organizational unit and its children. (implemented)
    • Optionally the user can now choose to view all items of the predecessors/successors additionally.
  • The user wants to view detailed information of the selected organizational unit in the search result list. The user can go to "show affiliations" and view the description (implemented)
    • The description also includes information of all predecessors/successors of the selected organizational unit.

See UC_PM_BD_03 Browse by organizational unit

History of affiliations linked from item view[edit]

The user wants to view detailed information on an organizational unit that is linked to an author of an item in the item view. A link shows the organizational unit detail view of the selected organizational unit. See UC_PM_BD_04 View item version