Authority remapping
Target release | Ramsons (R2 2024) |
|---|---|
Epic |
|
Document status | In ProgRESS |
Feature Overview
There exists significant difficulties with regards to the upgrading of a large set of MARC authority records when mapping rule changes have been applied, as well as migrating authority records from other systems to FOLIO. Updating authority records to apply mapping rules changes is a time-consuming process that takes multiple days, and using DI does not scale well when libraries are attempting to do other work with data import. Failure to update these records leads to data inconsistency. With the implementation of authority control/linking (manual) with Orchid, this issue may become even more problematic for libraries. As automated linking is introduced, this issue will become even more challenging.
The proposed solution addresses issues related to remapping and initial record migration in terms of data volumes and expected performance.
Requirements
User Interface
No user interface
Technical Design
Architecture
Tech Design: solution for migrating authority records
Database Schema
If the feature involves changes to the database, provide a schema or data model.
API Endpoints
Data Flow
Described in architecture design
Testing
Performance testing
https://folio-org.atlassian.net/browse/PERF-929
Load testing
https://folio-org.atlassian.net/browse/MODMARCMIG-11
Deployment
Deployment notes
Describe the deployment process.
Migration
Describe the migration process.
Documentation
NFR Scorecard: UXPROD-4082 NFR Scorecard
Provide links to or include any documentation related to the feature, such as API documentation or user guides.
Dependencies
List any external dependencies to other teams and features required for this feature.
Risks and Mitigations
Identify potential risks associated with the feature and describe mitigation strategies.