Inventory search. Create filter options for Instance segment
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
Environment
None
Potential Workaround
None
Attachments
1
defines
has to be done after
has to be done before
relates to
Checklist
hideTestRail: Results
Activity
Show:
Done
Details
Details
Assignee

Reporter

Tester Assignee

Priority
Development Team
Prokopovych
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 2, 2019 at 11:08 AM
Updated November 1, 2023 at 4:06 PM
Resolved November 1, 2023 at 4:06 PM
TestRail: Cases
TestRail: Runs
Overview: Until the Instance > Holdings > Item search results can be displayed in a hierarchical view - long term solution defined by @Filip Jakobsen (https://folio-org.atlassian.net/browse/UXPROD-491#icft=UXPROD-491) then we'll show the search result defined as is (MVP). A short term solution will be to improve the MCL Result list (https://folio-org.atlassian.net/browse/UXPROD-1634#icft=UXPROD-1634) - which didn't make it for `cap-mvp`.
Only the filters marked as bold it to be implemented for the MVP.
This story describes the filter options for Instance - and will be a refinement of the existing filters.
Usecase: Circulation staff, catalogers and other staff members need the ability to search and filter Instance records by a number of different field values. This will help them find exactly what they are looking for and what they should be working with.
Scenarios:
Scenario
Login to FOLIO Snapshot, go to the Inventory app landing page
When a user wants to filter within Instance records (the Instance record toggle is highlighted) - as defined in UIIN-758
Then they should see the following options in the filters area, in this order:
Effective location – implementation see: https://folio-org.atlassian.net/browse/UIIN-199#icft=UIIN-199
Permanent location – implementation see: UIIN-679
Language – implementation see: UIIN-735
Resource type – implemented as one long list. Refined implementation using render filters (same as the Orders App) see: https://folio-org.atlassian.net/browse/UIIN-193#icft=UIIN-193
Format – implementation using render filters (same as the Orders App) see: UIIN-820. Longterm we'll implement hierarchical display (https://folio-org.atlassian.net/browse/UXPROD-1632#icft=UXPROD-1632, https://folio-org.atlassian.net/browse/UX-198#icft=UX-198)
Mode of issuance
Nature of content
Classification type
Contributor type
Publication date (year range) – to be implemented later, see: https://folio-org.atlassian.net/browse/UXPROD-1984#icft=UXPROD-1984 (not MVP)
Previous held (yes) – implementation see: https://folio-org.atlassian.net/browse/UIIN-762#icft=UIIN-762
Staff suppress (yes) – only visible if you have the permission to view records marked as Staff suppress (UIIN-746) – implementation see: https://folio-org.atlassian.net/browse/UIIN-289#icft=UIIN-289
Suppress from discovery (yes) – implementation see: https://folio-org.atlassian.net/browse/UIIN-289#icft=UIIN-289
Mark for delete – implementation see: https://folio-org.atlassian.net/browse/UIIN-1094#icft=UIIN-1094
Date created (date range) – implementation see: UIIN-788
Date updated (date range) – implementation see: UIIN-790
Created by – to be implemented later (when we can ensure this to be suppressed from the UI by the European libraries according to GDPR, Employment agreement)
Updated by – to be implemented later (when we can ensure this to be suppressed from the UI by the European libraries according to GDPR, Employment agreement)
Statistical code – implementation see: UIIN-792
Instance status – implementation see: UIIN-1207
Source – implementation see: UIIN-1132
Tags – implementation see: https://folio-org.atlassian.net/browse/UXPROD-274#icft=UXPROD-274, https://folio-org.atlassian.net/browse/UIIN-307#icft=UIIN-307, UIIN-763
And all filter accordions should be closed except for Effective location (set in the Item record)
And results should be displayed as is for now until we can get this refined (https://folio-org.atlassian.net/browse/UXPROD-1634#icft=UXPROD-1634, and later https://folio-org.atlassian.net/browse/UXPROD-491#icft=UXPROD-491)
Scenario
Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot
NOTE Filtering by tags is also high priority for Chalmers, but cannot be implemented until assigning tags to instance records has been implemented. See separate stories https://folio-org.atlassian.net/browse/UIIN-307#icft=UIIN-307, and UIIN-763 for adding filtering by tags.