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

Holdings record. Call number, eye readable. Search on exact data in Call number data element

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: F - Sprint 93
    • Story Points:
      5
    • Development Team:
      Prokopovych

      Description

      Overview: When we implemented search on the Call number, eye readable, then right truncation is not set as a default - UIIN-858, but can be set explicit by the user by using *
      But that has lead to unintended behavior, which for a user seems confusing: When you search only on data in the call number data element, then you don't get all the expected results, if you do not use the right truncation. This unwanted behavior has been confirmed by MM-SIG SMEs.

      Scenarios
      Assume two instance records with following holdings records exist

      Example Concatenated call number Call number prefix Call number Call number suffix
      1 GE77 .F73 2014   GE77 .F73 2014  
      2 GE77 .F73 2014 Curriculum Materials Collection   GE77 .F73 2014 Curriculum Materials Collection
      1. Scenario
        • Login to FOLIO Snapshot, go to Inventory
        • When searching in the Holdings segment, using the search option Call number, eye readable,
        • and enter in the search box: GE77 .F73 2014 (with no asterisk)
        • Then both instance records will be found

        TestRail: Results

          Attachments

            Issue Links

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1040 Holdings record. Call number, eye readable. Search on exact data in Call number data element

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

            New Feature - New feature requests UXPROD-2298 Q2 2020 Timebox for Priority Inventory Search and Filter Enhancements

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

            New Feature - New feature requests UXPROD-2443 Q3 2020 Timebox for Priority Inventory Search and Filter Enhancements

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

            New Feature - New feature requests UXPROD-2712 Inventory Elastic Search: Timebox for Priority Inventory Search and Filter Enhancements

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-481 Item record. Effective call number (item), eye readable. Search on exact data in Call number data element

            • 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-1041 Item record. Effective call number (item), eye readable. Search on exact data in Call number data element

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

              Activity

                People

                Assignee:
                bohdan-suprun Bohdan Suprun
                Reporter:
                charlotte Charlotte Whitt
                Tester Assignee:
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases