Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Duplicate
-
None
-
None
-
-
Spitfire
Description
- Note that this logic only applies to new SRS records created after initial migration, and includes the following assumptions:
- Initial migration will not be handled via Data Import
- Any pre-existing HRIDs will be mapped and handled during initial data migration
- When the Data import action = Modify or Update
- 001 may be used for matching purposes, e.g. extract records for authority vendor, then re-load the updated records
- If there is field mapping to move the incoming 001 to a different field (e.g. move 001 to 035), then move it
- The incoming record should always be matching to an existing SRS record. In the event of a conflict between incoming 001 and SRS 001, and the 001 is not being used as the matchpoint, the incoming 001 should be ignored in favor of retaining the existing SRS record’s 001
- Once assigned, the HRID in existing SRS records is not editable
Notes
- HRID handling for MARC Bib records when action is Create is described in
MODSOURMAN-207 - Separate stories for HRID handling for MARC Holdings in MARCcat (
MODCAT-137) and for Holdings in Inventory (MODINV-161)
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2858 Define human readable identifiers (HRIDs) and UUIDs for SRS MARC Holdings records
-
- Closed
-
- is blocked by
-
MODINVSTOR-374 Generate HRID for holdings record
-
- Closed
-
- relates to
-
UIIN-741 Create Inventory settings page for HRID handling
-
- Closed
-