Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P2
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 19.0.0
-
Labels:None
-
Template:customfield_11100 32953
-
Sprint:Core: F - Sprint 82, Core: F - Sprint 83
-
Story Points:3
-
Development Team:Prokopovych
Description
We need 2 virtual indexes for call number searching on the "holdings" table and 2 on the "items" table. Example below only covers "holdings", "items" is similar.
- * callNumberAndSuffix* (call number + suffix) and * fullCallNumber* (prefix+callnumber+suffix) with lower-case and space normalization applied
Proposed schema.json (pseudo) configuration:
"index": [
{
"fieldName": "fullCallNumber",
"multiFieldNames": "callNumberPrefix,callNumber,callNumberSuffix",
"caseSensitive": false,
"normalizeWS" true, #does not exist [~charlotte] says this normalization can be skipped for Q1
},
{
"fieldName": "callNumberAndSuffix",
"multiFieldNames": "callNumber,callNumberSuffix",
"caseSensitive": false,
"normalizeWS" true, #does not exist [~charlotte] says this normalization can be skipped for Q1
}]
CQL
The following CQL should be used for the client/UI search:
fullCallNumber == "xxx" OR callNumberAndSuffix=="xxx"
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-858
Search. Holdings. Search option for Call numbers, eye readable (thin thread)
-
- Closed
-
-
UIIN-990
Search. Item. Search option for Call numbers, eye readable (thin thread)
-
- Closed
-
- defines
-
UXPROD-1655 Inventory. Search call number (Core functional) - thin thread
-
- Closed
-
- relates to
-
MODINVSTOR-446 add indexes for call number searching (normalized)
-
- Closed
-
-
-
- Draft
-