MARC Authority - Phase 1 Features
(UXPROD-2944)
|
|
| Status: | In Progress |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Quesnelia (R1 2024) | Parent: | MARC Authority - Phase 1 Features |
| Type: | New Feature | Priority: | P1 |
| Reporter: | Khalilah Gambrell | Assignee: | Khalilah Gambrell |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | LC-priority2, NFR, SolutionArchitecture, arlef-di, authority, back-end, cataloging, data-import, di-swat, loc, marc-authority, metadatamanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release: | Poppy (R2 2023) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | MARC Authority - Phase 1 Features | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Out of scope | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXXL: 30-45 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 100% | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Spitfire | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Problem: Tremendous difficulty to upgrade a large set of MARC authority records when mapping rules change (per release) have been applied. With the Nolana release, a short term solution was applied https://folio-org.atlassian.net/wiki/display/DD/ARCH-36+Provide+a+way+to+update+MARC+authority+records+when+mapping+rules+have+changed but has proven unreliable and not scalable. Until this issue is addressed, many libraries will not be able to use the MARC authority app and authority control effectively. Note Library of Congress has over 10 million authority records.
The proposed solution should
View migration numbers for several libraries : https://docs.google.com/spreadsheets/d/10GiFrfZee8aY8PcE0JJxf-lWtMkddFWnOYo_tiKYXrs/edit#gid=0
Definition of done
|
| Comments |
| Comment by Khalilah Gambrell [ 28/Mar/23 ] |
|
Hey Taras Spashchenko and Pavlo Smahin Here is a note from University of Missouri related to this feature Has anyone been working with authority control vendors, in terms of sending/reloading records, and have you used scripts to handle it in Data Import? The University of Missouri system has been trying to figure out how to navigate this based on DI functionality in Nolana and an efficient way to reload ~4-4.5M bib records isn't really clear to us. We're less concerned with the potential of quarterly updates but figuring out how to do the initial sync is causing us some headaches. |
| Comment by Lynne Fors [ 28/Mar/23 ] |
|
This is also something that Wellesley College is interested in. We are sending our bibliographic records to our authority control vendor in late May/early June for updating and creating our new base file with FOLIO identifiers. This will be the first time we have done authority control post-migration to FOLIO in June 2022. We need to be able to import and update our bibliographic records with the updates when they are returned to us. We are expecting over 674,000 bibliographic records to be returned. We will also get the authority files that go with those records. We are concerned about how to get these records back into FOLIO in a timely and accurate manner considering the limitations of Data Import. |
| Comment by Lloyd Chittenden [ 28/Mar/23 ] |
|
Regular quarterly updates from an authority vendor can also be very large. Last year Library of Congress changed the URLs in subfield $0 in authorized fields. This required all bib records in everyone's databases to be replaced. |
| Comment by Lloyd Chittenden [ 28/Mar/23 ] |
|
Authority vendors also sometimes send files of authority records that need to be deleted. There needs to be a mechanism to load a file of MARC authority records, and delete them in FOLIO. |
| Comment by Lloyd Chittenden [ 15/May/23 ] |
|
To be clear, this would need a lot of the features of DI. It would need field protection for example. In the case of getting new bib records from an authority vendor, I would want to replace the fields that the vendor updates without replacing other fields that might have local changes I don't want to overlay. Different vendors may update different fields and each vendor has many options for what fields they change and what they don't. It would really have to be very flexible. It's not just a total record replacement. |
| Comment by Ann-Marie Breaux (Inactive) [ 17/May/23 ] |
|
Hi Lloyd Chittenden for the locally-changed fields that need to be protected, how would those be identified? Would they have a certain subfield present, e.g. $4localcode? Would it be particular MARC fields that are protected? It would be really helpful to have a sample MARC Authority file with some of those locally-changed fields. Would it be possible to attach that to this Jira? Thank you! |
| Comment by Taras Spashchenko [ 31/May/23 ] |
|
Hello Khalilah Gambrell, I am reassigning this feature back to you. The design https://folio-org.atlassian.net/browse/ARCH-46 has been completed. |