PubMan Func Spec History of affiliations

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)

Examples:

x, y and z are Organizational Units

Example 1: Replacement

• x replaces y
  • x haspredecessor:replacement y
    • This relation will be created
  • y hassuccessor:replacement x
    • This relation will be derived

Example 2: Fusion

• x + y fusion to z
  • z haspredecessor:fusion x and z haspredecessor:fusion y
    • these two relations will be created
  • z issuccessorof:fusion x and z issuccessorof:fusion y
    • these two relations will be derived

Example 3: Spin-off

• x is spin-off of y
  • x haspredecessor:spin-off y (y still exists)
    • this relation will be created
  • y hassuccessor:spin-off x (y still exists)
    • this relation will be derived

Example 4: Splitting

• x is split into y + z
  • z haspredecessor:split x and y haspredecessor:split x
    • these two relations will be created
  • x hassuccessor:split z and x hassuccessor:split y
    • these two relations will be derived

Scenarios

Status/Schedule

• Status: in design
• Schedule:R5.5

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

Status/Schedule

Status: implemented Schedule:R5

• 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 selects one organizational unit for editing, 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. The selected organizational unit is therefore a successor of all in this manner related organizational units.
  • The information is shown in the organizational unit edit view and the organizational unit detail view.
  • See UC_PM_OUM_06 Add predecessor to organizational unit for more details.

History of affiliations in advanced search

• The user wants to search for items of a specific organizational unit. The user chooses an organizational unit from the browse tree (implemented)
  • Additionally user has the option to search for items of all predecessors or successors of this organizational unit additionally. See UC_PM_SR_03 Do advanced search
  • No tracking of history of affiliations in advanced search for R5
  • Future development: After choosing a organisational unit for the advanced search, the user can add single successors/predecessors or all successors/predecessors of the OU to the search

History of affiliations in browsing

• 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.
    • No tracking of history of affiliations in organisational browsing for R5

See UC_PM_BD_03 Browse by organizational unit

History of affiliations linked from item view

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

Publication Management

Organizational Unit