Page Comparison

Generate a shelving order for call numbers

• Initial implementation focused on implementing type-based shelving orders for LC and Dewey call numbers, based on the marc4j library, as well as Other scheme

• Added normalized shelving orders based on NLM and SuDoc types (Poppy release)

• The sorting mechanism should consider the call number, volume, enumeration, chronology, copy number, and suffix data

Allow users to select which specific call number type they'd like to browse

• Current implementation of the following call number type options:
  • Call numbers (all)
  • Call numbers, Dewey Decimal classification
  • Call numbers, Library of Congress classification
  • Call numbers, Local
    • *where "Local" includes any call numbers with a type of source: Local
  • Call numbers, National Library of Medicine classification
  • Call numbers, Other scheme
  • Call numbers, Superintendent of Documents classification
• These call number types have been made uneditable (with source: system)

POTENTIALLY: Change this implementation to use a filter instead of a facet

Populate browse results list with all item-level call numbers

• Item call numbers can either be specified in the Item record, or inherited from the Holdings record

• Browse results will contain ALL item-level call numbers (see below for navigating forward and backward through the list)

• A single Instance can have multiple items with call numbers of different types

Sort by calculated effective shelving order

Browse results should contain preceding and succeeding call numbers per shelving order

• Preceding call numbers should include five records

Users should be able to navigate forward and backward through the list

Call numbers on the browse results list should display the Prefix, Call number, and Suffix values, if applicable

• Currently, since the shelving key does not contain the prefix, when the user browses the call number with the prefix value, it will not find a match, but will show the visually matching call number directly below the “X would be here” message. It is confusing to some users. But it is expected behavior.

If no exact match is found, the browse query should be placed in proper order (with preceding and succeeding call numbers) as a placeholder (“x would be here)

• If no exact match is found, display this placeholder, do not display a "No results found" message

If there are multiple copies with the same call number (with a value in the Copy field) and the user browses with the copy number, any copy number should return a match

When browsing typed call numbers, the effective location facet should only contain the locations of the specific call numbers types on the Instance

• Should ignore characters & spacing and be case insensitive

• Should ignore characters & spacing and be case insensitive

• I think this facilitates the ability to navigate from a result in the call number browse list to the Instance in Inventory

Similar implementation to Classification browse in order to resolve ID and reference data issues

• For ECS, this should be configurable on the central tenant only
• Likely need new permission for call number browse configuration (similar to classification browse config)