Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1626

Store Effective Call Number Prefix, Call Number and Suffix in the Item Record

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      Small < 3 days
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Small < 3 days
    • Front-End Confidence factor:
      Medium
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
    • 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
      • 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

      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)
      • Effective call number is also needed for Call number sorting (see UXPROD-2002)
      • 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)
      • 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

        TestRail: Results

          Attachments

            Issue Links

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-520 BE: In transit report: call number fields

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-842 FE: In transit report: call number fields

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1171 Display call number: Create shared module to format display call number

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-86 Loans list: Display effective call number and related fields

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-393 Finalize display format of Call Number within Fees/Fines

            • P2 - normal priority level, must be included in the current development cycle
            • Analysis Complete

            New Feature - New feature requests UXPROD-1655 Inventory. Search call number (Core functional) - thin thread

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2002 Implement Normalized Call Number for Sorting (LoC Parsing Only)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2185 Inventory. Search call number (Core platform, normalized 2nd phase)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-544 Provide effective call number, suffix and prefix for requests and loans

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-357 Store effective call number on item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-358 Store effective call number prefix on item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-360 Store effective call number suffix on item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-750 Display effective call number string at the top of the item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-863 Display effective location for item at the top of the item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODRTAC-18 PO Verification: Implement "OR" logic for item or holding call number and location name

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2170 Store Effective Copy Number

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            New Feature - New feature requests UXPROD-2171 Store Effective Call Number Type

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-2172 Call Number Accordion on Item Record

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            New Feature - New feature requests UXPROD-2173 Display Effective Call Number Throughout Requests App

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests CHAL-40 Call number suffix not returned in responses from GET /circulation/requests

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CHAL-136 Call number suffix not displayed in holdings accordion on Instance detailed record

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-501 Call number suffix not returned in responses from GET /circulation/requests

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-884 Holdings call number prefix and suffix not displayed in holdings accordion on Instance detailed record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                charlotte Charlotte Whitt
                Analysis Estimator:
                Charlotte Whitt Charlotte Whitt
                Front End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Back End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases