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

Inventory. Search call number, normalized (Core functional)

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      Small < 3 days
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      Medium < 5 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Outstanding questions:
      * Implemented as a search index or as a persisted field containing the normalized version of the call number?
      * Hard-code normalization rules or configurable?
      Show
      Outstanding questions: * Implemented as a search index or as a persisted field containing the normalized version of the call number? * Hard-code normalization rules or configurable?
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      50
    • PO Rank:
      125
    • PO Ranking Note:
      CW: Aligned PO rank with Calculated Total rank
    • Rank: Chalmers (Impl Aut 2019):
      R2
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R1

      Description

      The elements Call number, and Call number type are implemented in the Holdings and Item records.

      Use cases:
      Multiple times daily catalogers and other library staff need to search by call number; system needs to search normalized version, not exact text string.

      Several libraries have expressed a requirement on being able to search by normalized call number - besides search on call number as an exact string, we'd also need search where we handle removing of misc. qualifiers, and more.

      Status on work being implemented in Inventory (thin thread) Q1 2020:

      1. Search across data elements (holdings and item):
        • Call number, prefix
        • Call number
        • Call number, suffix
      2. Implemented two indexes:
        • Call number, prefix
        • Call number and Call number, suffix
      3. Search option in the Holdings segment: Call number, eye readable (with no normalization)
        1. outstanding un-intended behavior - story: UIIN-1040
      4. Search option in the Item segment: Call number, eye readable (with no normalization)
        1. outstanding un-intended behavior - story: UIIN-1041

      Summary of normalization functionality:

      1. Search option in the Holdings segment: Call number, normalized
        • Normalization between lower casing and capitalized letters
        • Searching must be possible
          • with and without spaces
          • with and without hyphen
          • with and without period
          • with and without comma
          • with and without colon
          • with and without slash
          • with and without bracket
          • with and without parenthesis
      2. Search option in the Item segment: Effective Call number (item), normalized
        • Normalization between lower casing and capitalized letters
        • Searching must be possible
          • with and without spaces
          • with and without hyphen
          • with and without period
          • with and without comma
          • with and without colon
          • with and without slash
          • with and without bracket
          • with and without parenthesis

      Examples in scope:

      • 8 G.B.439 :6
      • JUR:R III:54:(1):Schm:1850
      • 94 NF 14/1:3792-3835
      • Z 557: 54.1961/62,7-12
      • Y 43839 (2017/18)
      • 1990/146 4°
      • 426/083 4° SH 34

      Out of scope - to be implemented post-mvp? - UXPROD-2360:

      1. Wildcard for exact one character, e.g. “!” - UIIN-1043
        • Search variants:
          • geo 1! → geo 11 and geo 12
          • geo 1!! → geo 100 and geo 123
          • geo 1* → geo 11 and geo 12 and geo 100 and geo 123
      2. Wildcard for 0-n characters, e.g. “#”

      Documentation:

        TestRail: Results

          Attachments

            Issue Links

              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:
                14 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases