Inventory (UXPROD-785)

[UXPROD-1626] Store Effective Call Number Prefix, Call Number and Suffix in the Item Record Created: 25/Mar/19  Updated: 16/Sep/20  Resolved: 10/Dec/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: call_number, cap-mvp, inventory, metadatamanagement, po-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-393 Finalize display format of Call Numbe... Closed
blocks UXPROD-2002 Implement Normalized Call Number for ... Closed
blocks CIRC-520 BE: In transit report: call number fi... Closed
blocks UIIN-842 FE: In transit report: call number fi... Closed
blocks UXPROD-86 Loans list: Display effective call nu... Closed
blocks UXPROD-1655 Inventory. Search call number (Core f... Closed
blocks UXPROD-2185 Inventory. Search call number (Core p... Closed
blocks UIU-1171 Display call number: Create shared m... Closed
Defines
is defined by CIRC-544 Provide effective call number, suffix... Closed
is defined by MODINVSTOR-357 Store effective call number on item r... Closed
is defined by MODINVSTOR-358 Store effective call number prefix on... Closed
is defined by MODINVSTOR-360 Store effective call number suffix on... Closed
is defined by UIIN-750 Display effective call number string ... Closed
is defined by UIIN-863 Display effective location for item a... Closed
Relates
relates to UXPROD-2170 Store Effective Copy Number Open
relates to UXPROD-2172 Call Number Accordion on Item Record Open
relates to UXPROD-2171 Store Effective Call Number Type Closed
relates to MODRTAC-18 PO Verification: Implement "OR" logic... Closed
relates to UXPROD-2173 Display Effective Call Number Through... Closed
relates to CIRC-501 Call number suffix not returned in re... Closed
relates to UIIN-884 Holdings call number prefix and suffi... Closed
relates to CHAL-40 Call number suffix not returned in re... Closed
relates to CHAL-136 Call number suffix not displayed in h... Closed
Epic Link: Inventory
Analysis Estimate: Small < 3 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Small < 3 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Medium
Back End Estimate: Small < 3 days
Back End Estimator: Niels Erik Nielsen
Development Team: Prokopovych
PO Rank: 104
PO Ranking Note: CW: Small task.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R5

 Description   

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

  • Call number type - split off to UXPROD-2171 Closed
  • Call number prefix - In scope for this feature
  • Call number - In scope for this feature
  • Call number suffix - In scope for this feature
  • Copy number - split off to UXPROD-2170 Open

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 prefix, Effective call number and Effective suffix. Please note that:

  • All 3 data elements are needed for Call number searching (see UIIN-858 Closed )
  • Effective call number is also needed for Call number sorting (see UXPROD-2002 Closed )
  • This data is also valuable to display in the "Effective call number string" throughout FOLIO Agreed upon format = <EffectiveCallNumberPrefix> <EffectiveCallNumber> <EffectiveCallNumberSuffix> <Volume> <Enumeration> <Chronology> <EffectiveCopy> <ItemCopy> (ideally we'd have <EffectiveCopy>, but that hasn't been implemented yet (see UXPROD-2170 Open )
  • Finally, it is valuable to store this data so it is readily available for reporting (in-FOLIO and external)

This feature had to be split, as it was not completed in time for the Q4 release. Spin-off features:

Call number notes document: I drafted a document which covers how call number is working today which may be a good starting point for discussion: https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit


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