Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Core: F - Sprint 69, Core: F - Sprint 70, Core: F - Sprint 71, Core: F - Sprint 75, Core: F - Sprint 76, Core: F - Sprint 77
-
8
-
Prokopovych
Description
Purpose: The filter for Locations which we implemented for alpha was based on Permanent location in the Holdings record, and Temporary location in the Item record. For beta we'll follow the Effective Location logic described on wiki: https://wiki.folio.org/display/RA/Effective+Location+Logic
The Location filter will be derived of the effective location for the given item.
Proposed CQL to filter by effective location:
item.pL = x OR (item.pL = "" AND item.tL = x) OR (item.pL = "" AND item.tL = "" AND holding.pL = x) OR (item.pL = "" AND item.tL = "" AND holding.pL = "" AND holding.tL = x)
UX mock ups:
1) The Effective location filter will be an unfolded filter at all three segments Instance (UIIN-759), holdings (UIIN-760) and item (UIIN-761) . When no search has been entered it looks like this:
2) When start entering search it will be following display. If a library has many, maybe even 100s of locations, then the list should only display the first 5 location.
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-233 Holdings Record. Accordion Locations. Implement new elements and reorder data
-
- Closed
-
- defines
-
UXPROD-140 Q4 2019 Timebox for Priority Inventory Search and Filter Enhancements
-
- Closed
-
- is blocked by
-
CQLPG-41 Implement foreign key searches
-
- Closed
-
-
MODINVSTOR-61 Duplicate instance rows returned for cross-table filters
-
- Closed
-
-
MODINVSTOR-348 UIIN-199: Filter by Effective Location: Save Effective Location on Item Record
-
- Closed
-
-
RMB-178 parseQuery throws StackOverflowError for deeply nested SQL query
-
- Closed
-
-
RMB-179 net.sf.jsqlparser does not support "IS TRUE" and "a@>b"
-
- Closed
-
- relates to
-
MODINVSTOR-364 holdingsRecord.permanentLocationId is required field
-
- Closed
-
-
UIIN-1008 Inventory search. Relabel filter to be named Effective location (item) - in all three segments
-
- Closed
-
-
UXPROD-1432 Add new effective location attribute calculated at the time of check-out
-
- Open
-
-
CHAL-91 Infinite scroll breaks/freezes when you scroll using scroll bar
-
- Closed
-
-
CQLPG-41 Implement foreign key searches
-
- Closed
-
-
MODINV-56 Resolve location id overrides
-
- Closed
-
-
MSEARCH-3 Instance - hierarchical filter by item effective locations - inventory
-
- Open
-
-
MSEARCH-32 Holdings - hierarchical facet by permanent locations
-
- Open
-
-
MSEARCH-48 Instance - search by item's effective locations
-
- Closed
-
-
MSEARCH-55 Instance - filter/facet by item effective locations
-
- Closed
-
-
MSEARCH-56 Holdings - filter/facet by permanent locations
-
- Closed
-
-
UIIN-194 Add Temporary Location to Inventory Holdings Record
-
- Closed
-
-
UIIN-195 Add Locations Section to Inventory Item Record Incl Permanent Location
-
- Closed
-
-
UIIN-196 Add Effective Location to Inventory Item Record
-
- Closed
-
-
UIIN-679 Holdings and item segment. Filter by the Holdings permanent location (in addition to effective - UIIN-199)
-
- Closed
-
-
UIORG-86 Delete Location (Hierarchical)
-
- Closed
-