Skip to end of banner
Go to start of banner

MARC records migration (authority)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Target releaseQuesnelia (R1 2024)
Epic


UXPROD-4082 - Getting issue details... STATUS
Document status
DRAFT

Feature Overview

Provide a brief introduction to the new feature, including its purpose and significance. Describe how it aligns with the project goals and any relevant user needs.

Requirements

List any technical or non-technical requirements for the feature. This could include hardware, software, dependencies, or any other prerequisites.

User Interface

Add any UI design elements or specifications related to the feature.

Technical Design

Architecture

Long term solution for migrating authority records

Database Schema

If the feature involves changes to the database, provide a schema or data model.

API Endpoints

MethodPathBodyResponseNote
POST/marc-migrations

{
"entityType": {
"type": "string",
"enum": ["AUTHORITY"]
},
"operationType": {
"type": "string",
"enum": ["REMAPPING"]
}
}

{
"id": {
"type": "uuid"
},
"entityType": {
"type": "string",
"enum": ["AUTHORITY"]
},
"operationType": {
"type": "string",
"enum": ["REMAPPING"]
}
}

Register new marc-migration operation
POST/marc-migrations/<id>

+ step



GET/marc-migrations/<id>

Return status of the marc-migration operation
GET/marc-migrations/<id>/chunks


Data Flow

Diagram or describe how data will flow within the feature.

Development Tasks

  1. folio-spring-support
    1. create a submodule which will provide support for minio/s3
  2. mod-marc-migrations?
    1. create repository and base structure of the module
    2. system-user creation
    3. create enpoints
      1. POST
      2. PUt
      3. ...
    4. async mapping
      1. prepare chunks
      2. mapping chunks
    5. data saving
  3. mod-entities-links
    1. new enpoint to process file-name and process it 

key summary type status
Refresh

Testing

Test Cases

  1. Test case 1
  2. Test case 2
  3. ...

Performance testing

Provide results of performance testing if needed.

Load testing

Provide results of load testing if needed.

Deployment

Deployment notes

Describe the deployment process.

Migration

Describe the migration process.

Documentation

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.

  • No labels