Statistical code facet for instances, holdings and items
Description
Environment
Potential Workaround
CSP Request Details
CSP Rejection Details
CSP Approved
defines
has to be done before
is cloned by
Checklist
hideTestRail: Results
Activity
Magda Zacharska February 14, 2022 at 2:46 PM
@Charlotte Whitt the spelling changes will be addressed in scope of https://folio-org.atlassian.net/browse/MSEARCH-284#icft=MSEARCH-284. However since there was no information provided which properties can be safely renamed without impacting UI, Pavel implemented aliases on the mod-search side so that both spellings will be supported. Please see https://folio-org.atlassian.net/browse/MSEARCH-294#icft=MSEARCH-294 for more details.
Charlotte Whitt February 14, 2022 at 11:53 AMEdited
Hi @Magda Zacharska
See @Pavel Filippov's comment:
Facets have been implemented in https://folio-org.atlassian.net/browse/MSEARCH-193#icft=MSEARCH-193, so you can retrieve facets separately for instance, items and holding-records using the following names:
Resource | Facet name |
|---|---|
instance | statisticalCodeIds |
items | items.statisticalCodeIds |
holdings | holdings.statisticalCodeIds |
Please notice that the prefix to be used for item will be: item and not items ... This is a conversation we had last week.
Michal Kuklis January 31, 2022 at 6:21 PMEdited
@Magda Zacharska thanks for your clarification. I think I have everything I need to improve it on the UI side now.
Magda Zacharska January 31, 2022 at 6:18 PM
@Oleksii Kuzminov could you please follow up with @Michal Kuklis to determine if there are any changes on the mod-search side needed.
Charlotte Whitt January 31, 2022 at 3:59 PM
@Magda Zacharska - we need to have all three values returned from mod-search - if I have understood @Michal Kuklis correct.
Who from the Falcon team should @Michal Kuklis reach out to if needed?
Details
Assignee
Oleksii KuzminovOleksii KuzminovReporter
Magda ZacharskaMagda ZacharskaPriority
P3Story Points
2Sprint
NoneDevelopment Team
FalconFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Oleksii KuzminovReporter
Magda ZacharskaPriority
P3
Purpose/Overview:
The purpose of this story is to create a facet that will provide a quick way to narrow down search results by selecting values for statistical codes coming from the reference data but filtering by keys stored in inventory instance, holdings and item records.
Requirements/Scope:
Support statistical codes for instances holdings and items:
Filter/Facet
Reference data
Instance field
Statistical codes
/statistical-codes
statisticalCodeIds (array of strings)
Approach:
Acceptance criteria:
Query returns accurate hit count
Query returns only instances that fulfill selected facet
Filter can be combined and represent logical conjunction
Filters are part of the cql query and the fields which are filtered should be configured in mappings