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

Future Fees/Fines: Address Call Number sorting issue on Fees/Fines History

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Medium < 5 days
    • Confidence factor:
      Medium
    • Development Team:
      None
    • Calculated Total Rank:
      22
    • Kiwi Planning Points (DO NOT CHANGE):
      1
    • PO Rank:
      0
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R2
    • Rank: Duke (Full Sum 2021):
      R4
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: hbz (TBD):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R4
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Update on November 22, 2019: At yesterday's RA SIG meeting it was agreed that this feature does not need to be in the MVP. For the MVP we will sort the Call Number column of FF History the same as the other columns.

      Update on November 18, 2019: Inventory is creating and saving a normalized call number. Fees/Fines will use that call number for sorting when it is available. We don't need to do our own normalizing.

      Update on October 15, 2019: Holly split the sorting issue from the formatting issue. The formatting issue remains at UXPROD-393. This issue (UXPROD-2128) is for just the sorting issue.

      This Comment from January 25, 2019 was moved from UXPROD-393 to this issue:

      Holly met with Frances Webb to discuss how Cornell Library has addressed the call number sorting issue. Here are Holly's notes from the meeting:

      The call number starts with a letter or letters, and then a number or numbers follow. Have to sort alphabetically due to the letters, but this messes up the numbers. For example, the sort results in this…

      D1
      D10
      D100
      D110
      D2
      D20
      D222

      When it should be this…
      D1
      D2
      D10
      D20
      D100
      D110
      D222

      Need to sort the letter(s) alphabetically, the number(s) numerically, then the rest alphabetically to get to this correct order…
      DE2.D48 R42
      DE2.D485 A12
      DE2.D49 M6

      Some fields needs to be ignored when sorting, like prefixes (Rare Books, Oversized, Archives, etc.). Frances has a file of prefixes to ignore. How will this work for FOLIO? Will we have to let tenet set what to ignore?

      Solr will make a normalized call number based on a customer sort filter Frances wrote. All punctuation is cleaned up except for decimal points (periods with a number right before it and right after it) and prefixes in the file mentioned above are excluded. For example...

      INPUT: Oversize ML410.1.M619 G56.1 2012 ++
      OUTPUT: ml 000000410.1 m 619 g 56.1 2012

      The output string is then simply sorted alphabetically.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                hollyolepm Holly Mistlebauer
                Front End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Back End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases