/
Call number browse requirements overview - DRAFT

Call number browse requirements overview - DRAFT

Jan 28, 2025

DRAFT

Contents:

Purpose

This document seeks to outline the full requirements of the Call number browse feature in FOLIO. It compiles the requirements from the original implementation of the feature (Call Numbers Browse), as well as the feature to browse by call number type (LC, Dewey, SuDOC, etc).

Use cases

The ability to browse by call number (and more specifically by type) facilitates the following use cases:

  • Aids in the classification of new materials by helping to control duplication and maintain symmetry in classification.

    • Identifies the next unused call number

    • Identifies where the searched call number would fall within the shelf list

    • Helps librarians manage multi-part and series materials by highlighting which volumes have been cataloged

  • Supports inventory management/auditing by providing a way to verify the presence or absence of materials on the physical shelves as well as the ability to analyze subject depth for acquisitions/weeding planning

  • Aids in data cleanup and record maintenance efforts by making it easier to identify incorrectly assigned call numbers

  • Aids in the discovery of sources related to known items

Item-level call number requirements

#

Requirement

Description

Related tickets

Requirement status
1

Generate a shelving order for call numbers

New implementation is not using the shelving order for sorting. This is only applicable for releases pre-Ramsons

  • 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

OBSOLETE

2

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

FE -initial: UXPROD-3459 - Getting issue details... STATUS

BE - initial: UXPROD-3255 - Getting issue details... STATUS

FE - browsing by type: UXPROD-4327 - Getting issue details... STATUS

BE - browsing by type: UXPROD-3569 - Getting issue details... STATUS

COMPLETE

3

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


COMPLETE

4

Sort by calculated effective shelving order

New implementation is not using the shelving order for sorting. This is only applicable for releases pre-Ramsons


OBSOLETE

5

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

  • Preceding call numbers should include five records


COMPLETE

6

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



COMPLETE

7

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



COMPLETE

8

The results should indicate a match on the call number and suffix

  • The components of the shelving key (call number, suffix, volume, enumeration, chronology, copy number, and data)

  • The components of the shelving key (call number, volume, enumeration, chronology, copy number, and suffix data)

  • In Ramsons, we will no longer require the copy number and enumeration data to produce an exact match.

  • 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.

MSEARCH-949 - Getting issue details... STATUS

UPDATED

9

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


COMPLETE

10

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

Only applicable for releases pre-Ramsons. In new implementation this results in exact matches regardless of copy number.

  • Currently, only a seemingly random copy will return a matching result if the Instance record has multiple items with the same call number but different copy numbers:


OBSOLETE

11

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


COMPLETE

12Users should be able to search Items in Inventory by the Effective call number (item), eye-readable
  • Should be exact in terms of characters & spacing, but it should be case insensitive

COMPLETE

13Users should be able to search Items in Inventory by the Effective call number (item), normalized
  • Should ignore characters & spacing and be case insensitive

COMPLETE

14Users should be able to search Holdings in Inventory by the eye readable call number (holdings)
  • Should be exact in terms of characters & spacing, but should be case insensitive 

COMPLETE

15Users should be able to search Holdings in Inventory by the normalized call number (holdings)
  • Should ignore characters & spacing and be case insensitive

COMPLETE

16Users should be able to search Instances in Inventory by the effective shelving order of the item call number

Shelving order is no longer being used in new implementation. We will potentially remove this search option, but that is TBD and if so, we would implement after refactor effort.

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

OBSOLETE

17Effective location facet selection should be retained when selecting a record in the browse results list for call number browse by type

COMPLETE

18In Call numbers (all) option, sort call numbers alphabetically
 MSEARCH-713 - Getting issue details... STATUS COMPLETE
19Effective location facet should only include the locations for the specific call number type
 MSEARCH-600 - Getting issue details... STATUS COMPLETE
20There should be no validation of format per call number typeSort by algorithm per assigned type, regardless of format of call number MODINVSTOR-1177 - Getting issue details... STATUS COMPLETE
21In ECS central tenant, there should be no Shared facetAll call numbers included are only on items on shared instances
COMPLETE
22In ECS, effective location facet should only include item locations on the instances based on the Shared and Held by facets

COMPLETE
23In ECS, held by facet results should only include item call numbers that are on holdings on either shared/local records

COMPLETE
24In ECS member tenants, there should be a shared facetCall numbers included are on items on either shared/local instances, based on Shared facet selection
COMPLETE
25Users should be able to configure which call number types should be sorted per sorting algorithm (call number type sort option)

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)
 UIIN-3116 - Getting issue details... STATUS COMPLETE
26Preceding call numbers should be displayed regardless of the number of characters that are shared between different call numbers

MSEARCH-705 - Getting issue details... STATUS

MSEARCH-641 - Getting issue details... STATUS

MSEARCH-614 - Getting issue details... STATUS

COMPLETE
27Item records should inherit call number type and call number components if neither is specified on the item record

COMPLETE
28When a call number is selected from the browse results list, redirect to Inventory Item tab to search for the prefix + call number + suffix in "Effective call number (item), normalized)See requirement about using query search
OBSOLETE
29

Title column should be populated with the title of the Instance on which the item call number appears

  • If the call number exists on more than one instance, level the title column blank

 MSEARCH-948 - Getting issue details... STATUS UPDATED
30Number of titles should be updated after a facet selection is madeDue to LOE and priorities of other work for refactor, this is being deferred and not included as part of the refactor feature. MSEARCH-943 - Getting issue details... STATUS DEFERRED
31

Create search query in Query search that includes criteria for both the call number selected as well as the call number type Ids.


 UIIN-3205 - Getting issue details... STATUS UPDATED