Details
-
Umbrella
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
Folijet Sprint 91, Folijet Sprint 92
-
0
-
Folijet
-
Q2 2020
Description
Overview
A lot of FOLIO modules are requesting MARC records from SRS. However current API https://s3.amazonaws.com/foliodocs/api/mod-source-record-storage/source-record-storage.html# doesn’t cover some query cases, which causes additional filtering on the program code level or extra requests that might have been avoided.
Cases
There are a couple of cases for OAI-PMH, that are nice to be able filtering on the SRS level:
- Retrieve SRS records by the input list of UUIDs. When the set of instances was received from Inventory and their MARC records are required, it'd be more convenient to pass the whole list of their UUIDs instead of getting SRS records one by one. Use POST method with a list of UUIDS in the body. What kind of records it should be(source records\ plain records)?
https://issues.folio.org/browse/MODSOURCE-156
- Get deleted records along with created/updated records for the defined period, so that EDS could have updates and be aware of deletes: at the moment there is no possibility to retrieve both active and deleted records by one request, thus two requests are being made as a workaround. Use state field.
https://issues.folio.org/browse/MODSOURCE-157
- Consider MARC Leader 05 - Record status in “d”, "s", "x" as a sign of deleted record as per https://www.loc.gov/marc/authority/adleader.html. See details in
MODOAIPMH-108ticket. It will be either convenient to- synchronize “deleted” parameter of SRS record with its MARC Leader or
- take out MARC Leader 05 - Record status in additional parameter, so that Leader itself shouldn’t be parsed.
Steps:
- Add leaderRecordStatus column char(1)
- Add trigger to fill this value from parsedRecord->content->leader(5)
- Add this field to query params
- change parsedRecord content column type to jsonb
https://issues.folio.org/browse/MODSOURCE-155
- Make different combinations of the deleted parameter (mind Leader 05 - Record status) with other SRS record parameters, e.g. suppressDiscovery, so that the next request example was available:
(so that the records with suppressDiscovery = true AND deleted = “false” parameters were eliminated) - see details inMODOAIPMH-126ticket
TestRail: Results
Attachments
Issue Links
- blocks
-
MODOAIPMH-156 Flow control doesn't work correctly without deleted records support
-
- Closed
-
-
MODSOURCE-151 Release v4.0.0
-
- Closed
-
- defines
-
MODSOURCE-121 Improve performance for receiving records from SRS
-
- Closed
-
-
UXPROD-2363 SRS Performance Improvements
-
- Closed
-
- earliest end is start of
-
MODOAIPMH-136 Move filtering deleted by leader records to the SRS level
-
- Closed
-
- has to be done after
-
MODSOURCE-134 SPIKE: investigate request from all apps to SRS and design new endpoints
-
- Closed
-
- is blocked by
-
MODSOURCE-155 MARC Leader Status
-
- Closed
-
-
MODSOURCE-156 Get Source Records By List of UUIDs
-
- Closed
-
- relates to
-
MODOAIPMH-175 Update dependency on SRS v4.0.0
-
- Closed
-
-
MODSOURCE-157 Filter by record state instead of delete query parameter
-
- Closed
-