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

Implement Normalized Call Number for Sorting (LoC Parsing Only)

    XMLWordPrintable

Details

    • Large < 10 days
    • Low
    • XL < 15 days
    • Best guess given we haven't defined this yet!
    • Prokopovych
    • 98
    • R5
    • R1
    • R1
    • R2
    • R1
    • R1
    • R4
    • R1
    • R1
    • R2
    • R1
    • R2

    Description

      Raw LC call number data does not sort well. The purpose of this feature is to generate and store a machine-sortable call number for the purposes of sorting lists such as Loans and Fees/fines. The machine sortable call number will also be available for inclusion in reports (both in-FOLIO and external to FOLIO). The scope of this feature is implementing Library of Congress parsing to all FOLIO call numbers. Call number display and sort in the FOLIO UI is out of scope. Separate feature(s) will also be written as needed to cover type-based parsing (e.g. Dewey parsing for Dewey call numbers etc).

      Per discussion with the Call number sub-group, the machine sortable call number will be based on the <Effective call number> data element on the item record. We will leverage Tod Olsen's SolrMarc code for generating the machine sortable call number.

      Call number searching, both with and without punctuation & spacing, is addressed in a separate feature UXPROD-1655.

      ---------------------------------------

      Call Number Sub-group membership:

      • Laura Wright (leader)
      • Charlotte Whitt
      • Christie Thomas
      • Felix or Martina
      • Andrea Loigman?
      • Lisa McColl
      • David Bottorff
      • Darcy Branchini
      • Cate Boerema

      CB: 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

      NOTE (for those who may be looking) Agreed upon format for Call number string = <EffectiveCallNumberPrefix> <EffectiveCallNumber> <EffectiveCallNumberSuffix> <Volume> <Enumeration> <Chronology> <EffectiveCopy> <ItemCopy> (ideally we'd have <EffectiveCopy>, but that hasn't been implemented yet (see UXPROD-2170)

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1389 Add call number sorting to user's open loans and closed loans

            • 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. UIU-1390 Export normalized, sortable call number with loans exports

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1395 Add shelving order to loans exports

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

            New Feature - New feature requests UXPROD-2128 Future Fees/Fines: Address Call Number sorting issue on Fees/Fines History

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-2174 Loans: sort by normalized call number

            • P2 - normal priority level, must be included in the current development cycle
            • Open
            has to be done before

            New Feature - New feature requests UXPROD-2683 Display Call Number Sort Code in Requests

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-2920 For In Transit Items Report, add normalized call number field for the item

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-3496 Sort & Browse by Holdings Level Call Number

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

            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
            is cloned by

            New Feature - New feature requests UXPROD-2219 DRAFT: Implement Type-Based Parsing for Call Number Sorting by Dewey and LC

            • 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. MODINV-155 Map shelving order property for items

            • 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. MODINVSTOR-381 Store Shelving Order in item (LC call numbers only)

            • 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. MODINVSTOR-521 Determine shelving order for existing items during upgrade

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

            Task - A task that needs to be done. MODINVSTOR-679 Comply with the MARC4J licence

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-816 Display Shelving order on the item record

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

            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-1714 FOLIO wide search by call number for any item search functionality

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

            New Feature - New feature requests UXPROD-1854 Create Call number generator

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

            New Feature - New feature requests UXPROD-3255 Call Number browse - Back-end

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

            New Feature - New feature requests UXPROD-3447 Subject browse - back-end

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

            New Feature - New feature requests UXPROD-3459 Call Number browse - Front-end

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

            New Feature - New feature requests UXPROD-3460 Subject browse - front-end

            • 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-1066 Implement normalized call number for sorting NLM call numbers

            • 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. MSEARCH-527 Implement normalized call number for sorting NLM call numbers

            • 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
            • Closed
            mentioned in

            Page Loading...

            Activity

              People

                charlotte Charlotte Whitt
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                19 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases