Fees/Fines (UXPROD-792)

[UXPROD-2128] Future Fees/Fines: Address Call Number sorting issue on Fees/Fines History Created: 15/Oct/19  Updated: 12/Jan/23

Status: Draft
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: None
Parent: Fees/Fines

Type: New Feature Priority: TBD
Reporter: Holly Mistlebauer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Unassigned-from-Holly, feesfines, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Blocks
is blocked by UXPROD-393 Finalize display format of Call Numbe... Closed
is blocked by UXPROD-2002 Implement Normalized Call Number for ... Closed
Epic Link: Fees/Fines
Front End Estimate: Small < 3 days
Front End Estimator: Holly Mistlebauer
Front-End Confidence factor: Medium
Back End Estimate: Medium < 5 days
Back End Estimator: Holly Mistlebauer
Development Team: Vega
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 Closed . This issue ( UXPROD-2128 Draft ) is for just the sorting issue.

This Comment from January 25, 2019 was moved from UXPROD-393 Closed 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.



 Comments   
Comment by Holly Mistlebauer [ 15/Oct/19 ]

This Comment from Anya Arnold on March 29, 2019 was copied from UXPROD-393 Closed to this issue:

Comment from the March Meeting : call number sort needs to work

Comment by Holly Mistlebauer [ 15/Oct/19 ]

Holly removed the Rank values because they were for the old issue UXPROD-393 Closed and we can't be sure that everyone feels the same about sorting the call number as they do about displaying the call number properly.

Comment by Holly Mistlebauer [ 18/Oct/19 ]

From: Holly L. Mistlebauer
Sent: Friday, October 18, 2019 3:25 PM
To: Laura Wright (lew235@cornell.edu) <lew235@cornell.edu>
Subject: Call Number Examples

Hi Laura. I am starting to work on the user story for sorting call numbers. Cornell has a process that I am going to “borrow”, but first I need to understand the parts of the FOLIO call number. I have placed some real Duke and Cornell call numbers in a spreadsheet at https://docs.google.com/spreadsheets/d/1qSFwyeQG5msmrqQFfU3VQ2EZlm_oWCnG1P1K0G1Af90/edit?usp=sharing Would you mind taking a look and letting me know if I have broken them down properly? If not, please make corrections. There are only 13 so it shouldn’t take you too long. Please feel free to add more examples so I can see how all of the pieces might be used.
Thanks much,
Holly

Comment by Holly Mistlebauer [ 04/Nov/19 ]

From: Laura Elisabeth Wright <lew235@cornell.edu>
Sent: Thursday, October 24, 2019 1:19 PM
To: Holly L. Mistlebauer <hlm7@cornell.edu>
Subject: call number examples

I think you can trust the parsing in the spreadsheet now.
Whether a year is part of the call number itself, the enumeration, or the chronology can be idiosyncratic and depends on the type of resource and sometimes on local decisions or needs. The most important thing I think with these is the order of elements and that blank elements are simply not displayed.
Do you need more sample data for us to test the order?

Best,
Laura

Comment by Holly Mistlebauer [ 04/Nov/19 ]

From: Holly L. Mistlebauer
Sent: Monday, November 4, 2019 10:41 AM
To: Laura Elisabeth Wright <lew235@cornell.edu>
Subject: RE: call number examples

Hi Laura. Sorry for the delay in getting back to you. I took a look at the spreadsheet—it’s fine for now. I thought that it would be easier to build a call number for sorting using the parts of the call number, but given how idiosyncratic the data can be I am not sure about that. I think I will contact the libraries that are implementing between now and summer 2020 and try to get a batch of call numbers from them after they have run a test migration from their current system to FOLIO. Thanks for your help with this.
Best,
Holly

Comment by Holly Mistlebauer [ 19/Mar/20 ]

Notes from November 2019 Resource Access SIG meeting...added for historical purposes...

Generated at Fri Feb 09 00:21:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.