Inventory (UXPROD-785)

[UXPROD-2219] DRAFT: Implement Type-Based Parsing for Call Number Sorting by Dewey and LC Created: 02/Jan/20  Updated: 14/Sep/23  Resolved: 14/Sep/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: call_number, metadatamanagement, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-2002 Implement Normalized Call Number for ... Closed
Epic Link: Inventory
Development Team: Prokopovych
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

------- DRAFT - DO NOT RANK -----------

Raw call number data does not sort well. UXPROD-2002 Closed will generate and store a machine-sortable call number but, for simplicity, it will use LC parsing for all call numbers, regardless of type. The purpose of this feature is to introduce type-based call number sorting which will use different parsers for different call number types. Since we have access to a Dewey parser, extending to Dewey will be the focus of this feature. That said, the design should support additional parsers when/if additional they become available. This feature will likely require:

  • The ability to map available parsers to call number types in Settings
  • Tod Olson's utility supports both Dewey and LC, so we would start with those parsers
  • A plan for how this change would affect sorting of item lists (e.g. Loans, Fees/Fines) when listed items have different call number types/parsers

Call number searching, both with and without punctuation & spacing, is addressed in a separate feature UXPROD-1655 Closed .

---------------------------------------

Call Number Sub-group membership:

  • Laura Wright (leader)
  • Charlotte Whitt
  • Christie Thomas
  • Felix or Martina
  • Andrea Loigman?
  • Lisa McColl
  • David Bottorff
  • Darcy Branchini
  • Cate Boerema

Call number notes document: https://docs.google.com/document/d/1FMl-_oNR6k-wVDQrZeMT_V9-ZDDaZBzdiipx0OQii9E/edit



 Comments   
Comment by Cate Boerema (Inactive) [ 02/Jan/20 ]

Hi lew235 and Charlotte Whitt. Per Laura's comment on UXPROD-2002 Closed (https://folio-org.atlassian.net/browse/UXPROD-2002?focusedCommentId=11781&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel) I restructured that feature to focus on LC parsing as a first step. I drafted this feature to represent the next step of call number sorting work. Can you please review and fix as-needed so we can remove all the "Draft" indicators and begin gathering rankings? Thanks much!

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: Provided we have a normalized call number sort, we could go live without separate indexes for LC and Dewey.We think that part of the work is already being done for Goldenrod. -Tod Olson

Comment by Khalilah Gambrell [ 03/Dec/21 ]

Magda Zacharska and Charlotte Whitt is this still needed.

Comment by Magda Zacharska [ 03/Dec/21 ]

I believe only LC call numbers are supported right now. Charlotte Whitt is this correct?

Comment by Christine Schultz-Richert [ 14/Sep/23 ]

This work has been addressed:

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