Make Inventory Instance rely on SRS MARC Bib (Part 1 of Connecting SRS, Inventory, and MARCCat for Bibs/Instances)
Description
Priority
P2Fix versions
Development Team
Assignee
Solution Architect
Parent Field Value
Parent Status
Attachments
- 22 May 2019, 09:11 AM
- 12 Mar 2019, 04:48 AM
- 28 Aug 2018, 10:36 AM
- 29 Jun 2018, 02:46 PM
defines
is defined by
is duplicated by
relates to
Checklist
hideTestRail: Results
Activity
Ann-Marie BreauxJune 26, 2019 at 5:06 AM
Remaining stories moved to https://folio-org.atlassian.net/browse/UXPROD-1805#icft=UXPROD-1805
Cate BoeremaMarch 13, 2019 at 10:59 AM
Your proposed breakdown sounds sensible. The only questions I would have are whether #4 is really a thin thread as it doesn't seem to support an end-to-end workflow. Or would the workflow for #4 be something along the lines of "view FOLIO-created instance in MARC"?
Ann-Marie BreauxMarch 13, 2019 at 8:06 AM
Hi @Cate Boerema Yes, we could potentially break them out . I'm nervous to end this feature with the SRS MARC Bib record out of synch with the Inventory Instance record.
Another way to break it up might be:
1, 2, 3, 5: make Inventory Instance rely on SRS and get the standard mappings from SRS to Instance straightened out
4: Implement Instance-to-MARC mapping
6-8: SRS-MARCcat integration (reduces risk too, since we're not clear on the delivery timeframe for MARCcat)
9: Spike that can be addressed by the DI small group or ACT; then a separate add-on feature if Inventory needs to make changes to SRS
How does that sound? And yes, I agree that having the Inventory work here (and me coordinating it with @Charlotte Whitt allows for coordinating pieces to fit together better, plus maybe gives us an option of 2 different dev teams (core-fxn and Folijet) depending on capacity.
Cate BoeremaMarch 12, 2019 at 11:12 AM
@Ann-Marie Breaux, same comment as on the the holdings feature. This looks great but we might be able to create smaller, thin-thread features for numbers 5,6,7 above. Thoughts?
CRUD of MARC Bib records in SRS should result in the corresponding mapped changes in the Inventory Instance records
CRUD of MARC Bib records in SRS should result in the corresponding changes in the MARCcat MARC Bib records
CRUD of MARC Bib records in MARCcat should result in the corresponding changes in the SRS MARC Bib records
BTW, I like the idea of organizing the inventory work as stories under these features
Ann-Marie BreauxMarch 12, 2019 at 4:48 AMEdited
@Cate Boerema and @Charlotte Whitt Please review the description above, and see if this sounds OK to you.
Question: Should these highlighted features be turned into stories under this https://folio-org.atlassian.net/browse/UXPROD-1577#icft=UXPROD-1577 feature?
Q2 2019 Data Import Priority 2 of 8, Continued by UXPROD-1805
NOTE: During Q2 2019 planning, decided this will be handled by Folijet, consulting with Core-Fxn if needed for Inventory-related aspects
This is Part 1 of Connecting MARCcat, Source Record Storage, and Inventory for MARC Bibs/Instances: Make Inventory Instance rely on SRS and update the standard mappings from SRS to Instance (UXPROD-1577)
See Part 2: Block edit of Instance Elements maintained in the underlying MARC Bib record (UXPROD-1447)
See Part 3: Implement Instance-to-MARC Mapping, including spike for whether whether Inventory Instance influences SRS MARC Bibs in any way other than creating a brief SRS MARC Bib when one does not exist (UXPROD-1397)
See Part 4: SRS-MARCcat Integration (UXPROD-1595)
Goal is to have the corresponding Inventory Instance, SRS MARC Bib, and MARCcat MARC Bib linked to each other and interacting with each other.
Requirements:
When an Inventory Instance is based on a MARC record stored in SRS
The Instance's "view source" button opens a new window with a MARC display of the SRS MARC Bib (UIIN-518, UIIN-459, MODSOURCE-34)
The fields of the MARC record are surfaced in the Inventory Instance based on a standard MARC-to-Instance map
The current MARC-to-Instance map is old and needs to be updated/refined (https://folio-org.atlassian.net/browse/UXPROD-149#icft=UXPROD-149)
Instance from MARC mapping: https://docs.google.com/spreadsheets/d/11lGBiPoetHuC3u-onVVLN4Mj5KtVHqJaQe4RqCxgGzo/edit#gid=1704497781
The standard MARC-to-Instance map needs to be editable at the tenant level, at a CLI level to start, and via a UI in the future. We need to cover the CLI portion in this feature
Instance fields that surface from the underlying SRS data should not be editable (UXPROD-1447)
CRUD of MARC Bib records in SRS should result in the corresponding mapped changes in the Inventory Instance records
Update all older documentation that describes loading MARC records directly to Inventory Storage via CLI, e.g. the instructions of Wayne Schneider at https://github.com/folio-org/folio-install/blob/master/single-server.md, and there "Load Sample Data"
NOTE: May have to extend the Inventory data structure a bit to include the proper reference, especially if Instance may have more than one SRS record in the future - this may be a future enhancement
====================================================
Older requirements:
Implement storage of batch loaded MARC records stored in blob store. The MARC blob of each record has a unique identifier.
Define linking to matching Inventory record:
Instance record: UUID= 5b1eb450-ff9f-412d-a9e7-887f6eaeb5b4
Storage address of instance: http://localhost:9130/inventory/instances/5b1eb450-ff9f-412d-a9e7-887f6eaeb5b4
Address of it's source record: http://localhost:9130/instance-storage/instances/5b1eb450-ff9f-412d-a9e7-887f6eaeb5b4/source-record/marc-json
Define eventually (very few) search criteria
Define linking to union catalogue records