Deleted OAI/PMH record identifier should be configurable (HRID or UUID)
Description
Environment
None
Potential Workaround
None
has to be done after
Checklist
hideTestRail: Results
Activity
Show:
Magda Zacharska July 1, 2022 at 9:07 PM
- this story is not related to deleting inventory instances. This story describes possible improvements on how the records are identified in the OAI-PMH response. Currently, the identifier contains edge module, tenant and record UUID, for example:
Once this story is implemented, the libraries can decide if the OAI-PMH identifier should use HRID instead of UUID.
Details
Details
Assignee
Unassigned
UnassignedReporter
Michelle SuranofskyPriority
P3Sprint
Development Team
Firebird
Release
Umbrellaleaf (R3 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created December 10, 2020 at 5:11 PM
Updated February 6, 2025 at 9:55 PM
TestRail: Cases
TestRail: Runs
Purpose/Overview:
Currently the OAI/PMH response for a deleted record only includes the UUID. Discovery systems may be using (in Lehigh's case we are using) the HRID as the 'key' for each record which makes the delete step not possible (without the proper key).
Requirements/Scope:
Could the identifier in the OAI/PMH response (every record - not just the deleted records) be configurable to either return the HRID or the UUID? In the interest of getting this story developed in the near future, returning 'both' ids in the response would be usable also.
The configuration should be on the tenant level
Out of scope: UI approach - this story covers only backend configuration and implementation
Approach:
Acceptance criteria:
The library can specify what data element is a part of the deleted record identifier : UUID or HRID
Once the value is configured it is being used when reporting deleted records
Additional information:
FOLIO does not support deleting inventory instances but SRS records can be marked as deleted using quickMarc.