SPIKE: Figure out 999 Instance and SRS UUID handling
RCA Group
Description
Environment
Potential Workaround
defines
Checklist
hideTestRail: Results
Activity
Ann-Marie Breaux April 16, 2019 at 9:04 AM
Sounds good - and if it needs to move to a different project (like MODSOURCE or MODDICONV), we can do that too. I'll change it to a task and a spike. Let's plan to point it today. I'm no quite sure what you mean about dividing SRS and Instance UUIDs since they're already divided by subfield markers, but we can talk about it more at grooming.
Oleksii Kuzminov April 16, 2019 at 8:45 AM
Hello! It's clear enough as a requirement, but I propose to divide filling SRS and Instance ids in 999 field and add more technicals details. Maybe it will be a good idea to change this story to the spike and we will create mod stories and investigate the best way to implement this functionality
Ann-Marie Breaux April 16, 2019 at 8:22 AM
Hi Oleksii - I'm not quite sure how to write the MOD stories, but I decided that the number handling should be broken into a few different stories. This is this first piece, which will be to add a 999 field to any new SRS MARC Bib records as a spot for the Instance UUID and the SRS UUID. Please see details above. Is this complete enough and clear enough that we could change it to open and groom it? Is it blocked by any other MOD stories? Thank you!
Details
Details
Assignee
Igor GorchakovReporter
Ann-Marie BreauxLabels
Priority
P2
Spike to determine the best way to do the following:
When a new MARC Bib record is created in source record storage, create a MARC 999 field on the record with the following characteristics:
NOTE: Needed by Chalmers and OAI-PMH for SRS-EDS Integration and RTAC
Tag: 999
Indicator 1: f (lower-case letter f)
Indicator 2: f
Subfield i: associated Instance UUID
Subfield s: SRS UUID
So a fully created 999 field would look something like this (using $ as the subfield indicator):
999 ff$i5bec815c-72b9-452f-ac19-bc2793c94537$sffce08d4-c08d-4ff8-8ff8-060a5015aa2a
Outcome of this spike: Finalize how we will do this, and create a story or stories for doing the work.
Coverage for the MARCcat UUID will be added in a separate story (MODSOURMAN-96), when MARCcat is available to connect with.