Call number browse notes

Summary of issues found in Poppy release and required actions to resolve

Issue

What was changed

Outcome of change

Action

Action Status

Issue

What was changed

Outcome of change

Action

Action Status

1

No shelving order generated

  1. Original purpose: The existing logic did not utilize the call number type, so there needed to be a mechanism to determine how to generate the shelving order. Therefore, validation was used to determine how to process each call number

  2. Poppy changes: When creating the functionality for browsing by type, we now use the type to tell the system which rules to use for generating the shelving order. However, this validation remained in place. As we spoke about in last week's meeting, this is causing shelving orders to not be generated if the call number does not pass this "validation".

  3.  

Shelving orders were not being generated if the call number didn’t pass validation for any call number types

Remove validation; No negative impact was identified - this will allow the shelving order to be generated making the call numbers browsable.

CSP 3

complete

2

Call number types showing in other type browse option

N/A

N/A

Run reindex before second step of call number migration script

complete

3

Call numbers not showing in expected order in Call numbers (all) option

Call number type is involved in a numeric algorithm for shelving order. We always generate a numeric representation, but when there is a type, the numeric representation begins with the type.

This algorithm places call numbers together by type. Without an exact match, it is treated as a call number without a type

Determine:

  • Alternative ways to approach Call numbers (all) option to sort call numbers as in previous releases, even without exact matches

  •  

 

in progress