Add all missing BIBFRAME 2.0 Instance fields into ETL transformation to BIBFRAME Lite
Description
Environment
Potential Workaround
Attachments
- 06 Oct 2023, 05:39 AM
Checklist
hideTestRail: Results
Activity
Punnoose Kutty Jacob PullolickalOctober 16, 2023 at 1:07 PM
HI @Gloria Gonzalez , Unfortunately, the graph got deleted from our DB. So, the links in your comment are not opening.
It looks like the comments are regarding the properties that are not in scope of thin thread. Is it ok to create a separate ticket for addressing these and may be do it after thin thread?
Gloria GonzalezOctober 6, 2023 at 5:52 AMEdited
All BF Lite Instance fields look great! Especially's PK's work around Titles, ParallelTitle, etc.
I have a few requests and topics that came up during my review:
Translate Update
Update conference-publication to bfMarc:ConferencePublication (Conference Publication)
This Class is using lower case, but it should be proper (like other types)
Web Viewer Update
Replace http://sg.ebsco.link/resource/JYEIIo4l1xA with http://loc.folio.link/resource/JYEIIo4l1xA across all Resource pages
Topics to discuss with the LCAP / NetDev teams
Question - is there a better way to handle the Instance labels created from 776?
Work Fingerprints (include contributors and subjects)
2 Batmans
Question - Are these the same Work? What pros/cons do you see of tighter fingerprinting rules?
National Bibliograpic Control Numbers - Would they like to search on these like other bf:Identifiers?
nationalBibliographyControlNumber-
https://web-viewer-oml.int.folio.ebsco.com/graph/pk_kevin_1k_001/resource/dpJlApLMh7M
uk:019244700
bnb:gbb925294
Anuar NurmakanovOctober 3, 2023 at 12:10 PM
@Gloria Gonzalez here is the link to the graph - https://web-viewer-oml.int.folio.ebsco.com/graph/pk_kevin_1k_001. Thanks to @Punnoose Kutty Jacob Pullolickal for the help
Giorgi NinuaSeptember 29, 2023 at 12:35 PM
@Gloria Gonzalez PLS review ticket in this sprint if you have time
Problem statement:
When the ETL fields conversion is tested for the current ETL implementation and when we can display those fields in MARVA Editor, we still might not have some fields
Some of the fields can be present in BIBFRAME 2.0 Monograph, but we don't have them in the ETL
What we need:
We must extend the ETL in our FOLIO EIS repositories to convert all BIBFRAME 2.0 Monograph fields
The fields must be saved in the Linked Data Storage for further usage
Acceptance Criteria:
We run the ETL, and the ETL works without errors
All BIBFRAME 2.0 Instance fields are saved in the DB but in BIBFRAME Lite format