Fees/Fines
(UXPROD-792)
|
|
| 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: |
|
||||||||||||
| Issue links: |
|
||||||||||||
| 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
This Comment from January 25, 2019 was moved from
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 When it should be this… Need to sort the letter(s) alphabetically, the number(s) numerically, then the rest alphabetically to get to this correct order… 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 ++ 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
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
|
| Comment by Holly Mistlebauer [ 18/Oct/19 ] |
|
From: Holly L. Mistlebauer 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. |
| Comment by Holly Mistlebauer [ 04/Nov/19 ] |
|
From: Laura Elisabeth Wright <lew235@cornell.edu> I think you can trust the parsing in the spreadsheet now. Best, |
| Comment by Holly Mistlebauer [ 04/Nov/19 ] |
|
From: Holly L. Mistlebauer 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. |
| Comment by Holly Mistlebauer [ 19/Mar/20 ] |
|
Notes from November 2019 Resource Access SIG meeting...added for historical purposes... |