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

Inventory. Search call number (Core functional) - thin thread

    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:
      120
    • PO Rank:
      125
    • PO Ranking Note:
      CW: Aligned PO rank with Calculated Total rank
    • Rank: Chalmers (Impl Aut 2019):
      R2
    • 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: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      This feature capture the work planned for the Core functional team

      The elements Call number, and Call number type are implemented in the Holdings and Item records as of Q4 2018.

      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.

      Summary of requirements discussed with SMEs:
      So this would be the best solution for the searching of call numbers:

      1. String/phrase index for prefix and call number (no keyword index)
      2. Searching must be possible without spaces and/or special characters
      3. Additionally: exact search (with spaces and special characters)
        • could be customized (per tenant) with a selection list of special characters to be taken into account in a search.
      4. No automatically truncation
        • Wildcards
        • Wildcard for explicitely right truncation, e.g. “*”
        • Wildcard for exact one character, e.g. “!”
      5. Call numbers
        • geo 11
        • geo 12
        • geo 100
        • geo 123
      6. 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
      7. Wildcard for 0-n characters, e.g. “#”
      8. Character classes
        • germ 3[567]0* = germ 350* | germ 360* | germ 370*
      9. Boolean operators, also to combine different search criteria
        • AND
        • OR
        • NOT

      Documentation:

      • - - - - - - - - - - - - - - - - - - - - - - -

      Examples:
      tit=letters per=goethe,*
      (Title must contain “letters”, author is Goethe,* ‑ standard operator is AND)
      per=bach,j* NOT sgn=mus*
      (Author is bach,j*, call number does not start with “mus”)
      tit cookbook AND (sgn=math* OR sgn=comp*)
      (the cookbook series from O’Reilly)

      Some more complex examples from GBV libraries *before *normalization (added by Felix Hemme):

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

        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