Issues

Select view

Select search mode

 
50 of 958

Refinements to Inventory Statistical Codes

Description

Currently all statistical code types and statistical codes can be assigned to all record types (instance, holdings, items) in Inventory. This leads to several challenges: there can be very long drop-down lists that can be difficult to navigate and it is possible (easy) to assign a code to a type of record for which it was never intended to be used.

Changes to Settings for Inventory

Add an option for each statistical code type and each statistical code to indicate/restrict which record type(s) it can be assigned to. Settings for the statistical code type would be “inherited” by the codes with that type. So, for example, if a code type is restricted to instances, any code of that type can only be assigned to instances. If a code type can be applied to instances, holdings, and items, any code of that type may be assigned to all three record types unless additional restrictions are applied to the code itself. The default setting, if no restrictions are set, for all code types and codes would be unrestricted (can be applied to all record types).

Add a status for statistical code types and statistical codes to be assigned a as inactive. This should function in the same way that the status does for locations, that is, a warning is shown when an inactive value is selected and the user is prompted to either cancel or select the inactive value. The default would be for code types and codes to be active. (see screen shots)

image-20250318-153841.png
image-20250318-153816.png

Further refinements include the ability to sort statistical codes by code name (current default sort), code, type, and status.

When restrictions are applied to an existing code that has been assigned to a record type is is no longer valid for, a warning should first display (as with assigning an inactive value). A list of identifiers (UUIDs would be fine) should also be supplied, with the ability to print or export it, for all records with the value that would/will conflict with the restriction. The user changing settings should be allowed to choose whether to delete all these codes or to keep them, in which case they would remain in the records, but that value would no longer appear as an option in the drop-down menu.

Changes to Inventory UI

Add a filter by type option to the Statistical code selection interface. This filter should be optional, that is, if not selected, a code can still be selected by searching or scrolling through the complete drop-down list.

Only code types and codes that are valid for each record type should display in the drop-down menus for assigning statistical codes.

Other potential changes: need help from a UX expert on ways we could change the view of the drop-down list to make it easier to navigate. Indentation? Font changes? Right now it is flat and, if long, difficult to parse.

Priority

Fix versions

None

Development Team

None

Assignee

Solution Architect

Parent

None

Parent Field Value

None

Parent Status

None

Attachments

2
  • 18 Mar 2025, 03:50 PM
  • 18 Mar 2025, 03:50 PM

Confluence content

mentioned on

Checklist

hide

Details

Reporter

Potential Workaround

Continue to use statistical codes with current functionality. Templates would also alleviate some of the challenges.

PO Rank

0

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 18, 2025 at 3:50 PM
Updated 4 days ago

Activity

Show:
Laura E Daniels
updated the remoteissuelink4 days ago
None
This issue links to "Page (FOLIO Wiki)"
Laura E Daniels
made 2 changes
March 18, 2025 at 8:24 PM
Status
Open
Draft
Description
Currently all statistical code types and statistical codes can be assigned to all record types (instance, holdings, items) in Inventory. This leads to several challenges: there can be very long drop-down lists that can be difficult to navigate and it is possible (easy) to assign a code to a type of record for which it was never intended to be used. *Changes to Settings for Inventory* Add an option for each *statistical code type* and each *statistical code* to indicate/restrict which record type(s) it can be assigned to. Settings for the statistical code type would be “inherited” by the codes with that type. So, for example, if a code type is restricted to instances, any code of that type can only be assigned to instances. If a code type can be applied to instances, holdings, and items, any code of that type may be assigned to all three record types unless additional restrictions are applied to the code itself. The *default* setting, if no restrictions are set, for all code types and codes would be unrestricted (can be applied to all record types). Add a *status* for *statistical code types* and *statistical codes* to be assigned a as *inactive*. This should function in the same way that the status does for *locations*, that is, a warning is shown when an inactive value is selected and the user is prompted to either cancel or select the inactive value. The *default* would be for code types and codes to be active. (see screen shots) !image-20250318-153841.png|width=418,height=181,alt="image-20250318-153841.png"! !image-20250318-153816.png|width=50%,alt="image-20250318-153816.png"! Further refinements include the ability to *sort* *statistical codes* by code name (current default sort), code, type, and status. When *restrictions are applied to an existing code that has been assigned to a record type is is no longer valid for*, a warning should first display (as with assigning an inactive value). A list of identifiers (UUIDs would be fine) should also be supplied, with the ability to print or export it, for all records with the value that would/will conflict with the restriction. The user changing settings should be allowed to choose whether to delete all these codes or to keep them, in which case they would remain in the records, but that value would no longer appear as an option in the drop-down menu. *Changes to Inventory UI* Add a *filter by type* option to the Statistical code selection interface. This filter should be *optional*, that is, if not selected, a code can still be selected by searching or scrolling through the complete drop-down list. Only code types and codes that are valid for each record type should display in the drop-down menus for assigning statistical codes. Other potential changes: need help from a UX expert on ways we could change the view of the drop-down list to make it easier to navigate. Indentation? Font changes? Right now it is flat and, if long, difficult to parse.
Laura E Daniels
updated the Potential WorkaroundMarch 18, 2025 at 4:07 PM
Continue to use statistical codes with current functionality. Templates would also alleviate some of the challenges.
Laura E Daniels
created the IssueMarch 18, 2025 at 3:50 PM
TestRail: Cases
TestRail: Runs