Issues
- Refinements to Inventory Statistical CodesUXPROD-5237
- NFR: Data Import/Inventory Support Bug work (Trillium)UXPROD-5199Ryan Taylor
- NFR: Data Import/Inventory Technical, NFR, & Misc work (Trillium)UXPROD-5198Ryan Taylor
- NFR: Data Import/Inventory Technical, NFR, & Misc work (Sunflower R1 2025)UXPROD-5007Ryan Taylor
- NFR: Data Import/Inventory Support Bug work (Sunflower R1 2025)UXPROD-4966Ryan Taylor
- Alternate graphic representations - UI updatesUXPROD-4856Ryan Taylor
- Allow user to "unshare" or demote a shared Instance to be a local instanceUXPROD-4839Ryan Taylor
- ECS - Allow user to navigate Inventory holdings and items without changing affiliationUXPROD-4715Ryan Taylor
- Review Inventory UI permissions - Phase 2UXPROD-4701Resolved issue: UXPROD-4701Ryan Taylor
- ECS - Allow user to update "ownership" of Inventory Holdings and Items within ECS systemUXPROD-4573Resolved issue: UXPROD-4573Ryan Taylor
- Merge duplicate instances (ECS and non-ECS)UXPROD-4570Ryan Taylor
- LC Tenants Structure support >Data import (Folijet)UXPROD-4563Resolved issue: UXPROD-4563Ryan Taylor
- Linked Data - FOLIO integration (Folijet development)UXPROD-4552Resolved issue: UXPROD-4552Ryan Taylor
- UIIN test tech debtUXPROD-4540Ryan Taylor
- Review Inventory UI permissions - Phase 1UXPROD-4531Resolved issue: UXPROD-4531Ryan Taylor
- Miscellaneous Inventory enhancements (not in current release)UXPROD-4515Ryan Taylor
- Electronic Access Block--New Elements (Instance, Holdings, Items)UXPROD-4467Ryan Taylor
- Subject Heading Granularity Updates - Instance schema changes (Folijet)UXPROD-4445Resolved issue: UXPROD-4445Ryan Taylor
- MARC-Instance default mapping changes: Canceled LCCN -- 010 $z (Ramsons)UXPROD-4444Resolved issue: UXPROD-4444Ryan Taylor
- Save Item UUIDs in FOLIO Inventory from Action MenuUXPROD-4441Ryan Taylor
- Instance edit form: Add component for multi-field lookup that populates a single propertyUXPROD-4392
- Improve user experience of purchase order re-encumber fieldUXPROD-4391Dennis Bridges
- Possible Phase 2 ECS Inventory and Data Import workUXPROD-4374Ryan Taylor
- Prevent user from deleting a Holding that is referenced by an order lineUXPROD-4366Ryan Taylor
- Addition of Flags to Quickly Identify Requests and POLs Connected to Instance/holdings/itemsUXPROD-4343Ryan Taylor
- Dependency check and move. Analytical records; bound with - part 2: link multiple bibs to the same itemUXPROD-4341Charlotte Whitt
- Inventory: Capture additional repeatable call numbersUXPROD-4334Khalilah Gambrell
- Duplicate a local Instance as a shared consortial or local InstanceUXPROD-4329Resolved issue: UXPROD-4329Ann-Marie Breaux
- Export landing page - pausing and resuming running jobsUXPROD-4309Magda Zacharska
- Export MARC Bib Records Marked for Deletion via API in ECSUXPROD-4306Resolved issue: UXPROD-4306Magda Zacharska
- Set instance/bib record for deletionUXPROD-4303Resolved issue: UXPROD-4303Ryan Taylor
- Sharing & Linking MARC authority recordsUXPROD-4278Resolved issue: UXPROD-4278Christine Schultz-Richert
- quickMARC & MARC authority UI changes needed for ECSUXPROD-4265Resolved issue: UXPROD-4265Christine Schultz-Richert
- Folijet NFR: Data Import/Inventory Support Bug work (Ramsons R2 2024)UXPROD-4235Resolved issue: UXPROD-4235Ryan Taylor
- NFR: Data Import/Inventory Technical, NFR, & Misc work (Ramsons R2 2024)UXPROD-4234Resolved issue: UXPROD-4234Ryan Taylor
- Duplicate a shared or local Instance (BE work)UXPROD-4210Resolved issue: UXPROD-4210Ann-Marie Breaux
- Inventory UI changes needed for ECSUXPROD-4209Resolved issue: UXPROD-4209Ann-Marie Breaux
- Allow user to promote a local Instance to be a shared consortial instance, plus shared/shadow instance logic (BE work)UXPROD-4140Resolved issue: UXPROD-4140Ann-Marie Breaux
- CDL (Controlled Digital Lending)UXPROD-3977Charlotte Whitt
- Configure Fast Add Suppressed by Default according to the app where Fast Add is opened fromUXPROD-3958
- Inventory Elastic Search (Poppy): Timebox for Priority Inventory Search and Filter EnhancementsUXPROD-3946Resolved issue: UXPROD-3946Khalilah Gambrell
- Settings page. Inventory > Instances > Related instancesUXPROD-3905Ryan Taylor
- In the Inventory app, allow items with a status of Order closed to be marked missing or withdrawnUXPROD-3868Ryan Taylor
- NFR: Data Import & Inventory Support Bug work (Poppy R2 2023)UXPROD-3838Resolved issue: UXPROD-3838Ryan Taylor
- Do not allow item deletion if an open order status is tied to the item recordUXPROD-3799Ryan Taylor
- Mark instance for deletion. 2nd iteration. Enable the user to mark an instance for deletionUXPROD-3742Ryan Taylor
- Inventory Elastic Search (Orchid): Timebox for Priority Inventory Search and Filter EnhancementsUXPROD-3709Resolved issue: UXPROD-3709Charlotte Whitt
- Create API endpoint to get the current maximum assigned HRIDUXPROD-3703Ryan Taylor
- Create/edit. Analytical records; bound with - part 2: link multiple bibs to the same itemUXPROD-3655Resolved issue: UXPROD-3655Charlotte Whitt
- Item Status: Recently ReturnedUXPROD-3652Ryan Taylor
50 of 958
Refinements to Inventory Statistical Codes
Description
Priority
Fix versions
None
Development Team
None
Assignee
Unassigned
UnassignedSolution Architect
None
NoneParent
None
Parent Field Value
None
Parent Status
None
Attachments
2
Checklist
hideDetails
Reporter
Laura E DanielsLaura E DanielsPotential Workaround
Continue to use statistical codes with current functionality.
Templates would also alleviate some of the challenges.PO Rank
0TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Laura E Daniels
Laura E DanielsPotential 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 agoNone
This issue links to "Page (FOLIO Wiki)"
Laura E Daniels
made 2 changesMarch 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 PMContinue 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
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)
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.