Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 111, eHoldings Sprint 112, eHoldings Sprint 116
-
3
-
Spitfire
-
R1 2021 Hot FIx #2
-
Yes
Description
Purpose/Overview:
To allow the user to search the data in MARC fields, subfields, and control fields.
Requirements/Scope:
- Allows the user to search for the presence or absence of a given field or subfield.
Approach:
Search is formatted like
{
"fieldsSearchExpression": "899.value is 'present'"
}
for a tag or
{
"fieldsSearchExpression": "899.a is 'present'"
}
for a subfield.
'present' can be changed to 'absent'.
Acceptance criteria:
- Evaluate if results are returned in under a minute against a collection of 10 million SRS records. If not create other tickets as needed.
- Results should be paginated
- Offset and limit parameters will determine pagination
- Results should contain a JSON response with keys: records (array of associated instance UUIDS), recordCount (integer)
- A search with no results should have an empty records array and count of 0
- When passing parameter suppressed=true then records that are suppressed from discovery will be included in the results
TestRail: Results
Attachments
Issue Links
- blocks
-
MODSOURCE-312 Release v5.0.5 (R1 Iris Hot Fix 2)
-
- Closed
-
- defines
-
UXPROD-2940 SRS MARC Query API part 2
-
- Closed
-
- is cloned by
-
MODSOURCE-269 Implement presence or absence searches for indicators
-
- Closed
-