Uploaded image for project: 'mod-inventory-storage'
  1. mod-inventory-storage
  2. MODINVSTOR-360

Store effective call number suffix on item record

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 18.0.0
    • Core: F - Sprint 74, Core: F - Sprint 75, Core: F - Sprint 76, Core: F - Sprint 77
    • 5
    • Prokopovych

    Description

      Purpose: To store the effective call number suffix on the item record (uses item level call number prefix, if available, otherwise uses the holding level one). This will allow us to:

      • Support search of items on effective call number
      • Provide data to reporting (they prefer to get stored data than to have to calculate on the fly)
      • Store the data that needs to be further transformed into machine-sortable call number CB: This doesn't apply because current plan is to generate machine-sortable call number based on the call number data element only
      • Possibly: serve as a component of a derived "call number block" which would assemble various call number related data elements into a single "block" for display throughout FOLIO (Loans, Loan details, Check in, Check out, Requests etc.)

      Scenarios:

      1. Scenario
        • Given an item record
        • When displayed (UI mockup and story still in progress)
        • Then an Effective call number suffix should display from a stored value
      2. Scenario
        • Given the Effective call number suffix field
        • When displayed/stored
        • Then use item-level "Call number suffix", if available, otherwise, use holding-level "Call number suffix"

      NOTE: When developing this feature, please bear in mind that we will soon be implementing the ability to move items from one holding to another.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            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. CIRC-546 UIREQ-368: Backend for adding effective call number to Hold shelf clearance report

            • 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. CIRC-556 BE: In transit report: remaining 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. CIRC-592 Backend: Display effective call number prefix, call number, and call number suffix in loans contexts

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-593 Backend: Display enumeration, chronology, volume in loans contexts

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-861 BE: Add item level copy number to mod-circ for effective call number string FE work

            • 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. UICHKIN-127 Display effective call number prefix, call number, and call number suffix at check in

            • 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. UICHKIN-144 Display enumeration, volume, chronology, item-level copy number at check in

            • 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. UICHKIN-145 Display effective copy number at check in

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

            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-860 Call number accordion on Item record

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

            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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-925 FE: In transit report: remaining 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. UIREQ-366 Display effective call number string on the Request 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. UIREQ-367 Include effective call number elements in the Request CSV

            • 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. UIREQ-368 Include effective call number elements in the Hold shelf clearance report

            • 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. UIREQ-372 Display effective call number string on the Dedicated request queue page

            • 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. UIU-1347 Display effective call number prefix, call number, and call number suffix in loans contexts

            • 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-1358 Add more granular call number fields to loans exports

            • 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-1391 Display enumeration, chronology, volume in loans contexts

            • 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-1394 Display effective copy number in loans contexts

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1396 Add effective copy number to loans exports

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1482 Add chronology, copy number to loans exports

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

            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
            defines

            New Feature - New feature requests UXPROD-1626 Store Effective Call Number Prefix, Call Number and Suffix in the Item Record

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

            Activity

              People

                rladdusaw Ryan Laddusaw
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases