Inventory (UXPROD-785)

[UXPROD-2171] Store Effective Call Number Type Created: 02/Dec/19  Updated: 16/Sep/20  Resolved: 10/Jan/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2020
Parent: Inventory

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: cap-mvp-split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Blocks
blocks UXPROD-2174 Loans: sort by normalized call number Open
Cloners
clones UXPROD-2170 Store Effective Copy Number Open
is cloned by UXPROD-2172 Call Number Accordion on Item Record Open
Defines
is defined by MODINV-177 Forward effective call number typeId ... Closed
is defined by MODINVSTOR-361 Store effective call number type on i... Closed
Relates
relates to MODINVSTOR-458 EffecticeCallNumberComponents is not ... Closed
relates to UXPROD-1626 Store Effective Call Number Prefix, C... Closed
Epic Link: Inventory
Development Team: Prokopovych
Rank: Chicago (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1

 Description   

This was split off of UXPROD-1626 Closed (Implement effective logic for call number in Holdings record and inherited to Item records) as it was not completed in Q4 2019, as planned. (Effective) call number type is required for sorting by call number ( UXPROD-2174 Open ).

Context:
There are a number of data elements that exist on both the holding and item record in inventory:

For these elements, the item record should inherit the data from the holding record unless something different has been specified in the item record. This resulting "effective" data is, then, the data that actually matters for the item. This data needs to be stored, as opposed to being calculated on the fly if:
1. It will be used for searching
2. It will be used for sorting
3. It needs to be available in reporting

Scope:
The scope of this feature is to store Effective call number type. Please note that:

  • Effective call number type number is not needed for Call number searching (which will act on Effective prefix, Effective call number and Effective suffix only see UIIN-858 Closed )
  • Effective copy number is not needed for Call number sorting (which will act on Effective call number only see UXPROD-2002 Closed ) at least initially. Eventually we may want to allow for different sorting rules depending on the call number type, but that is down the road.
  • Effective call number type is not displayed in what we are calling the "Effective call number string" which is the assembled call number that displays throughout FOLIO (e.g. at the top of the item record, in the Request record, the Loan record etc). The Effective call number string is: <EffectivePrefix> <EffectiveCallNumber> <EffectiveSuffix> <Volume> <Enumeration> <Chronology> <EffectiveCopy> (until we have EffectiveCopy, we are using the ItemCopy).
  • The main reason for storing this data in the item record at this point would be so that it is easily available for external reporting and also for consistency with the other data elements that exist on both the holding and item records.

Stories Needed:

  • Provide effective call number type for requests and loans - Not sure this is actually needed as call number type wasn't seen as important to display as part of the Effective call number string in Circulation
  • Display effective call number type on item record - UIIN-903 CB: This will have to be part of the call number accordion feature, as we don't have that accordion yet.
  • Store effective call number type on item record - MODINVSTOR-361 Closed

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