Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Instance-level classification requirements

Classification (all)
#

Requirement

Description

Functionality

Feature / Related tickets

Req statusImplementation status
1

Generate a shelving order for the classification 

  • Classification (instance-level data, resembles the structure of call numbers) has a Classification type, which are similar to the Call number types; for the first iteration of this work, we should generate shelving orders for the following types:

    • LC
    • Dewey
Other scheme -  still confirming what "Other" means  Add new inventory
  • LC and Dewey classification numbers should be sorted using the same normalization rules we applied for item-level call numbers

  • Like call number types, classification types can be configured in Inventory settings - however, I believe a user can only create Local types and cannot edit types with source = "folio". The others are assigned the "folio" source and can be assigned by the user manually in FOLIO source Instance records, or derived from mapping of the MARC bibliographic record (see: Default MARC Bibliographic-to-Inventory Instance Mappings
  • LC mapping: 
    • 050$ab AND/OR 090$ab
    • $a and $b go on the same line, with a space between them
    • If multiple $a in the same field, put them in separate classification fields with first $a and its $b if present in first classification field, and second $a (and its $b, if it has one) in second classification field
  • Dewey mapping:
    • 082$ab
    • $a (which may repeat) and $b all go on the same line, with a space between each subfield
    • If there is a slash in $a, remove it and close up the space
    • If there is a $b between two $a's within one 082 field, put the first $a and $b in one classification field, and the second $a in second classification field
Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-4120

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

2Add new inventory browse option for Classification (all)
3
For this option, since we don't know the shelving order to use, we can sort alphabetically 

Status
colourGreen
titleverified


3Add new inventory browse options for Instance classification
  • We should support the following for the first iteration:
    • Classification (all) - the first iteration should
    • LC
    • Dewey
  • If the classification type is not LC or Dewey, then that classification is only included in the "Classification (all)" option
Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2624

Status
colourGreen
titleverified

Status
colour

Red

Grey
title

deffered

not started

4Add Inventory tenant-level setting to configure whether Classification or item-level call numbers should be available as a browse option
(still need to verify this requirement)

Deferred at this time, tenant level configuration will be investigated in the future

  • This option should allow libraries to specify whether they'd like Item-level call number browse options OR instance-level classification browse options
  • Depending on which option is selected, those browse options would be available
Browse


Status
colourRed
titledeffered

5Populate browse results with Instance-level classification
  • Instances can have MULTIPLE classifications with different classification types
  • Unlike item-level call numbers, Instance classification numbers are stored in a single field (no separate fields for prefix or suffix, etc.)
    • Therefore, the browse results only contain a single property: Classification
  • These call numbers should be included REGARDLESS of the presence of holdings/items
Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2625

Status
colour

Grey

Green
title

not started

verified

Status
colourGrey
titlenot started

6

Sort by calculated effective shelving order

  • For classification (all) option, search alphabetically
Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2625

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

7

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

  • Preceding call numbers should include five records

Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2625

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

8

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


Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2625

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

9The results should indicate a match when the entered browse query matches the full value of the Classification field
Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2625

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

10If no exact match is found, the browse query should be placed in proper order (with preceding and succeeding classification numbers) as a placeholder (“x would be here)
Browse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2625

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

11Do not show effective location facet for instance classification browse*Because this is instance levelBrowse
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-2624

Status
colourGreen
titleverified

Status
colourGrey
titlenot started

12Users should be able to search Instances in Inventory by classification
  • Assumption is that this may be required in order to navigate from browse results to related Instances in search
Search


Status
colourGrey
titlenot started