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

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

NOTE: Class: Classification browse requirements have been moved to separate page: Classification Browse Requirements

Differences between item call numbers and instance classification numbers in FOLIO

...

under review

Mostly implemented, but current search is case sensitive

not started

#

Requirement

Description

Functionality

Related tickets

Implementation StatusRequirement status

1

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

Browse

LC:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MODINVSTOR-381
Dewey:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MODINVSTOR-876
Other scheme:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MODINVSTOR-877
NLM:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MODINVSTOR-1066
SuDoc:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MODINVSTOR-1069

Status

colour	Green
title	Complete

2

Add a new Inventory browse option for call numbersAllow 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

Browse

FE -initial:

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3459

BE - initial:

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3255

FE - browsing by type:

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-4327

BE - browsing by type:

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3569

Status

colour	YellowGreen
title	in progressComplete

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

Browse

Status

colour	Green
title	Complete

4

Sort by calculated effective shelving order

Browse

Status

colour	Green
title	Complete

5

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

Preceding call numbers should include five records

Browse

Status

colour	Green
title	Complete

6

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

Browse

Status

colour	Green
title	Complete

7

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

Browse

Status

colour	Green
title	Complete

8

The results should indicate a match if:

The browse query matches the Prefix + Call number + Suffix (the call number components that are visible on the results pane) -
Status
subtle true
colour Red
title under review
- as noted in the description, it is confusing when the browsed query indicates that a match is not found but to the user, it looks to match the succeeding call numberOR the components of the shelving key (call number, volume, enumeration, chronology, copy number, and suffix data)

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.

Browse

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-558

Status

colour	RedGreen
title	under reviewComplete

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

Browse

Status

colour	Green
title	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

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:

Browse

Status

colour	GreyGreen
title	not startedComplete

11

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

Browse

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-600

Status

colour	GreyGreen
title	not startedComplete

12

Users 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

Status

subtle

true

colour

Red

title

Search

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MODINVSTOR-444
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key MSEARCH-507
(case insensitivity)

Status

colour	RedGreen
title	under reviewComplete

13

Users should be able to search Items in Inventory by the Effective call number (item), normalized

Should ignore characters & spacing and be case insensitive

Search

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UIIN-857

Status

colour	Green
title	Complete

14

Users 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

Search

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UIIN-858

Status

colour	Green
title	Complete

15

Users should be able to search Holdings in Inventory by the normalized call number (holdings)

Should ignore characters & spacing and be case insensitive

Search

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UIIN-1918

Status

colour	Green
title	Complete

16

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

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

Search

Status

colour	Green
title	Complete

17

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

Search

Status

colour	Green
title	Complete

18

In Call numbers (all) option, sort call numbers alphabetically

Browse

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-713

Status

colour	Green
title	Complete

19

Effective location facet should only include the locations for the specific call number type

Browse

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-600

Status

colour

Grey

title

	Green
title	Complete

20There should be no validation of format per call number typeSort by algorithm per assigned type, regardless of format of call numberBrowse

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MODINVSTOR-1177

Status

colour	Green
title	Complete

21In ECS central tenant, there should be no Shared facetAll call numbers included are only on items on shared instancesBrowse

Status

colour	Green
title	Complete

22In ECS, effective location facet should only include item locations on the instances based on the Shared and Held by facets
Browse

Status

colour	Green
title	Complete

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

Status

colour	Green
title	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 selectionBrowse

Status

colour	Green
title	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)

Browse

Status

colour	Green
title	Complete

26Preceding call numbers should be displayed regardless of the number of characters that are shared between different call numbers
Browse

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-705

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-641

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	MSEARCH-614

Status

colour	Green
title	Complete

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

Status

colour	Green
title	Complete

Versions Compared

Old Version 14

New Version Current

Key

Differences between item call numbers and instance classification numbers in FOLIO

Page Comparison

Versions Compared

Old Version 14

New Version Current

Key

Differences between item call numbers and instance classification numbers in FOLIO