Inventory (UXPROD-785)

[UXPROD-4334] Inventory: Make call number a repeatable element Created: 01/Jun/23  Updated: 09/Oct/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Inventory

Type: New Feature Priority: TBD
Reporter: Felix Hemme Assignee: Khalilah Gambrell
Resolution: Unresolved Votes: 0
Labels: inventory, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Inventory
Development Team: None
PO Rank: 0

 Description   

Current situation or problem:

The call number elements are available as non-repeatable fields in both the holdings and item record:

  • callNumber
  • callNumberPrefix
  • callNumberSuffix
  • callNumberTypeId

To support certain use cases, theses fields should become repeatable.

In scope

Out of scope

Use case(s)

  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.

Proposed solution/stories

See detailed description in the requirement analysis from d-MM: https://folio-org.atlassian.net/wiki/x/qg0b 

Links to additional info

Questions

  • Implications on call number browse?
  • Does it affect query search?
  • (from Ann-Marie Breaux) Rather than making the existing call number field (and its various component fields) repeatable, could we consider adding a new repeatable field called alternate or previous call number? Might that be less disruptive than changing the existing field to repeatable?
  • Implications for call number field mapping in holdings/item Data Import field mapping profiles?
  • Implications for exporting call number data for holdings/items?


 Comments   
Comment by André Hohmann [ 01/Sep/23 ]

Hi Ann-Marie Breaux , thanks a lot for the Question "Rather than making the existing call number field (and its various component fields) repeatable, could we consider adding a new repeatable field called alternate or previous call number? Might that be less disruptive than changing the existing field to repeatable?"

We discussed it with Felix Hemme in the German group for Resource Management and we agree that it is much better to add a new repeatable field  - called for example alternate call number.

It would be very helpful, if a function (e.g. by a button for each alternate call number) could be integrated to "exchange" values from alternate call number and call number. In case that an item is assigned a new call number, because it changed physically the location, as example. 
That would be a substitute for the function "primary call number" from our previous suggestion and is intended to prevent users from "exchanging" the values manually by copy and paste.

We have described our suggestions in the FOLIO-wiki: https://folio-org.atlassian.net/wiki/x/9xMb Unfortunately, the wiki is not available at the moment. 

We hope it will help you to understand our requirements. Please feel free to ask for further information, if our suggestions are not clear, or if you have any other ideas/suggestions to implement them. 

Comment by André Hohmann [ 09/Oct/23 ]

Hi Ann-Marie Breaux, sorry for bothering you, but do our suggestions help you for the assessment of adding repeatable alternate call numbers?
Please feel free to ask, if you need more information.   

Generated at Fri Feb 09 00:39:05 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.