Proposal D-Metadaten Management

Description

• It should be possible to assign multiple call numbers to a holdings/item record. At the moment this concerns the following fields:        
  • Call number type
  • Call number prefix
  • Call number
  • Call number suffix
  • Primary
• Levels: This refers to the call numbers on the levels:
  • Item
  • Holdings
• Primary call number:  It should be possible to mark the currently valid call number ("primary call number") by a function that includes the following properties:
  • At least one call number must be marked as "primary call number"
    • At least one call number must be marked as "primary call number" - ideally, the first call number is always marked as "primary call number" (regardless of whether it is added manually or automatically).
    • The field Primary is marked as a mandatory field with asterisk.
    • If no call number is marked as "primary call number", a message is displayed. This message should correspond to the existing concept (see draft) of mandatory field validation at item level.
      • Please select to continue
  • A subsequently added call number must be explicitly marked as "primary call number", if required.
    • This removes the mark of the previous "primary call number"
    • Only one call number can be marked as "primary call number"
  • Only one call number can be marked as "primary call number"
  • The primary call number is displayed in Folio for example in the tables, or in catalogs
    • e.g. the primary call number is displayed in the detail view of the instance in the list of holdings
    • e.g. the primary call number is used in circulation > patron notice templates:
  • (Suggestion) Label button inactive: Make call number primary
  • (Suggestion) Label button active: Primary
  • (Suggestion) Label of the field: Primary
• Delete: Each call number should can be deleted individually with all associated call number fields. For example by a bin icon. 
• Indexing: All call numbers should be included in the call number index so that it is possible to search for all call numbers.
• Filter/Search: A filter option should be implemented in order to enable the limitation of the results to records which match only values of the field "primary call number". 
• Exports: All call numbers should be included in exports, unless they are marked as "Suppress display in discovery".

Draft

Use cases

1. As a librarian I want to keep an old call number in the record after I assigned a new call number in order to be able to ensure traceability in the future. For example, items are moved from one location to another, and I want to capture the previous call number as well as the current one.
2. Certain reference works in the reading room (open collection) already have a stacks call number assigned. They'll be moved into the closed stacks some time in the future, e.g. as soon as they are outdated or no longer used on a regular basis.
3. The current issues of print journals are presented in the reading room, but the older volumes are placed in the stacks. The records of the new issues should already contain the stacks call number under which they will be placed in the future.

Data structure

Current: → String fields

"callNumber" : "PR6056.I4588 B749 2016",
"callNumberPrefix" : "PRE",
"callNumberSuffix" : "SUF",
"callNumberTypeId" : "512173a7-bd09-490e-b773-17d83f2b63fe"

Proposed: → Array with objects

  "callNumbers" : [ {
    "callNumber" : "PR6056.I4588 B749 2016",
    "callNumberPrefix" : "PRE",
    "callNumberSuffix" : "SUF",
    "callNumberTypeId" : "512173a7-bd09-490e-b773-17d83f2b63fe",
    "primary" : true
  }, {
    "callNumber" : "2023 A 3987",
    "callNumberPrefix" : "PRE",
    "callNumberSuffix" : "SUF",
    "callNumberTypeId" : "512173a7-bd09-490e-b773-17d83f2b63fe",
    "primary" : false
  } ]

Created Jira-Tickets

UXPROD-4334 - Getting issue details... STATUS

Relevant existing Jira-Tickets

...