...
The design document presented below outlines a complete redesign of the Data Export module, aimed at supporting the export of various record types, such as Instances, Holdings, and Authorities, in different environments, including Single tenant, Multi-tenant, and Consortia. The primary goal is to handle the export of shared and local instances while ensuring that holdings and item data are correctly attached. The redesigned solution is intended to be scalable, extensible, and reliable, catering to various functional and non-functional requirements.
Requirements
Following features provide source for requirements:
provides source for requirements.Jira Legacy server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key UXPROD-4254 System Jira columnIds issuekey,summary,status columns key,summary,status maximumIssues 20 jqlQuery key = UXPROD-4254 serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
Functional requirements
- Ability to export shared instance records from a tenant.
- Support for exporting with both default and custom mapping profiles.
- Generation of simplified MARC records for local and shared instances.
- Correct attachment of holdings and item data to instances during export with custom profiles.
- Ability to handle significant volumes of data (> 1,000,000 records) and export them into multiple files.
- Configurable maximum number of records per file.
- Parallel processing of multiple files of the same Data Export job.
- Retrieval of MARC records from local or central SRS storage based on the source.
- Storage of result files in AWS S3 buckets.
...