Inventory (UXPROD-785)

[UXPROD-2170] Store Effective Copy Number Created: 02/Dec/19  Updated: 06/Dec/23

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

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: cap-mvp-split, epam-folijet, inventory, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png    
Issue links:
Blocks
blocks UXPROD-393 Finalize display format of Call Numbe... Closed
blocks UXPROD-2271 Use effective copy number in loans an... Blocked
Cloners
is cloned by UXPROD-2171 Store Effective Call Number Type Closed
Defines
defines UXPROD-785 Inventory In Progress
is defined by CIRC-570 Provide effective copy number for req... Open
is defined by MODINVSTOR-362 Store effective copy number on item r... Open
Relates
relates to UXPROD-1626 Store Effective Call Number Prefix, C... Closed
Release: Not Scheduled
Epic Link: Inventory
Front End Estimate: Large < 10 days
Front End Estimator: Michal Kuklis
Back End Estimate: Large < 10 days
Back End Estimator: Bohdan Suprun (Inactive)
Development Team: Folijet
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 41
PO Ranking Note: 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 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.

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 copy number. Please note that:

  • Effective copy 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 )
  • 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.

Use Cases:
Use cases for when the item would need to inherit copy number from the holding record (more to be added):

  1. One scenario would be multi-volume sets, which could include serial runs. Usually a copy of a multi-volume set will all shelve together, have the same copy number, and would be collected under one holding record. Let's say we have "My Magnum Opus" in three volumes, copy 1 shelves in the Main Library and copy 2 shelves in the Science Library. So there would be one holding record for copy 1 with item records for the three volumes, and another holding record for copy 2, also with three item records. For manual operations, assigning the copy number at the holding level might be less error-prone than duplicating at the item level. (from Tod Olson, University of Chicago)
  2. One institution (Chicago?) has Chinese language materials that are very large multi-volume sets (300 volumes). They are all the same copy, just 300 different volumes. In this case, putting the copy on the holdings record saves a huge amount of data entry.
  3. Conceptually you want to group issues with the set that makes up copy 2
  4. See MM SIG discussion here 56:59 to hear full discussion https://drive.google.com/file/d/1NP190uh_M9XCQjGcxV_y5owx4wqUnBjJ/view?usp=sharing

Overall: At the broadest level, keeping the same inheritance logic for all the elements of the effective call number simply makes the most sense, both because it is consistent and because it provides the greatest flexibility for institutions to use copy number in different ways depending on their needs. (from David Bottorff, University of Chicago)

Stories Needed:

  • Store effective copy number on item record - MODINVSTOR-362 Open
  • Make it possible to display effective copy number on item record - MODINV-TBD
  • Provide effective copy number for requests and loans - CIRC-570 Open
  • Update Effective call number string wherever it displays (Request details, Item details etc) - Stories TBD
  • Update Call number data in CSV exports (Hold shelf clearance report etc) - Stories TBD


 Comments   
Comment by Cate Boerema (Inactive) [ 10/Dec/19 ]

Hi Bohdan Suprun I need to get updated feature estimates on all my remaining MVP features. Could you please add a high-level backend estimate to this feature? Please consider these two stories in scope:

  • Store effective copy number on item record - MODINVSTOR-362 Open
  • Make it possible to display effective copy number on item record - MODINV-TBD
  • Provide effective copy number for requests and loans - CIRC-570 Open

This is where you enter the estimates:

Michal Kuklis could you please estimate the frontend work for this UXPROD? I haven't created the stories yet, but this is the idea:

  • Update Effective call number string wherever it displays (Request details, Item details etc - probably about 5 pages) - Stories TBD
  • Update Call number data in CSV exports (Hold shelf clearance report etc - probably about 5 CSV exports) - Stories TBD

Let me know if you have any questions. When it comes to estimating at the feature level, please err on the side of being conservative. Thanks!

Comment by Bohdan Suprun (Inactive) [ 11/Dec/19 ]

Hi Cate Boerema,

It is about 7-10 days work for all three stories.

Also, I'm assuming that MODINVSTOR-332 Closed and MODINV-151 Closed will be resolved separately before starting working on this feature.

Comment by Cate Boerema (Inactive) [ 11/Dec/19 ]

Yes - thank you Bohdan Suprun! This is exactly what I needed.

Comment by Michal Kuklis [ 11/Dec/19 ]

Cate Boerema I estimated the same (7 - 10 days) just because we have multiple places to do this.

Comment by Charlotte Whitt [ 10/Jul/20 ]

Cate Boerema - at yesterday's Data Export meeting Magda Zacharska demonstrated that when doing data export of the effective call number item data it do not include the item copy number. Magda explained that this bug was due to item copy number not being part of the item effective call number component.

Based on the descriptions above I'm not 100% sure if UXPROD-2170 Open would solve this problem for Data Export, but if it do, then maybe we could consider to move the work to Q3 2020 or Q4 2020 - alternatively the Data Export dev team might need to rethink a interim way to work around this.

Other observations:
The item effective call number string is displaying properly in the top of item record.

Comment by Cate Boerema (Inactive) [ 10/Jul/20 ]

Hi Charlotte Whitt. We have implemented inheritance for all of the call number bits (prefix, call no, suffix) except for copy. Given that, we are currently just using the copy number specified in the item record in the Effective call number string throughout FOLIO. This means that, if the copy number is empty in the item record, the Effective call number string displays nothing for the copy number (even if there is a copy number specified in the holding). This UXPROD feature, when implemented, would calculate an Effective copy number so we could use that instead.

I don't know enough about the data export needs to understand if effective copy number is a higher priority for them or if they can also just include the Item copy number (or the holding copy number or both).

Maybe Magda Zacharska can shed some light on that?

Comment by Magda Zacharska [ 10/Jul/20 ]

I don't think the copy number is required from the data-export point of view. When the data export subgroup prioritized fields supported in mapping profile item's copy number was not listed as a priority: https://drive.google.com/file/d/1XvHmToGQwhzmMNlQ5-l1QTEDyUtDpdn_/view?usp=sharing

What we we saw yesterday that the way Effective call number string is displayed in UI might suggest that the copy number is a part of the Effective call number string:

when in fact it is not (copyNumber property is outside the effectiveCallNumberComponets):

{
      "id": "7212ba6a-8dcf-45a1-be9a-ffaa847c4423",
      "hrid": "item000000000014",
      "holdingsRecordId": "e3ff6133-b9a2-4d4c-a1c9-dc1867d4df19",
      "formerIds": [],
      "barcode": "10101",
      "itemLevelCallNumber": "TK5105.88815 . A58 2004 FT MEADE",
      "effectiveCallNumberComponents": {
        "callNumber": "TK5105.88815 . A58 2004 FT MEADE",
        "typeId": "512173a7-bd09-490e-b773-17d83f2b63fe"
      },
      "enumeration": "",
      "chronology": "",
      "yearCaption": [],
      "copyNumber": "Copy 2",
      "notes": [],
      "circulationNotes": [],
      "status": {
        "name": "Available"
      },
      "materialTypeId": "1a54b431-2e4f-452d-9cae-9cee66c9a892",
      "permanentLoanTypeId": "2b94c631-fca9-4892-a730-03ee529ffe27",
      "permanentLocationId": "fcd64ce1-6995-48f0-840e-89ffa2288371",
      "effectiveLocationId": "fcd64ce1-6995-48f0-840e-89ffa2288371",
      "electronicAccess": [
        {
          "uri": "http://www.loc.gov/catdir/toc/ecip0718/2007020429.html",
          "linkText": "Links available",
          "materialsSpecification": "Table of contents",
          "publicNote": "Table of contents only",
          "relationshipId": "3b430592-2e09-4b48-9a0c-0636d66b9fb3"
        }
      ],
      "statisticalCodeIds": [
        "b5968c9e-cddc-4576-99e3-8e60aed8b0dd"
      ],
      "tags": {
        "tagList": []
      },
      "metadata": {
        "createdDate": "2020-07-09T09:52:02.048+0000",
        "updatedDate": "2020-07-09T19:29:22.606+0000",
        "updatedByUserId": "16b854e4-cabd-52be-83c0-4a4814210045"
      }
    }
Comment by Ann-Marie Breaux (Inactive) [ 06/Dec/23 ]

Moved from Prokopovych backlog to Folijet Backlog cc: Ryan Taylor

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