DR-000008 - Data export by using Spring Batch (aka Export Manager)
Overrides/Supersedes
This decision was migrated from the Tech Leads Decision Log as part of a consolidation process. The original decision record can be found here.
RFC
N/A
Stakeholders
Vasily GancharovVBar Taras SpashchenkoMikhail Fokanov
Contributors
Approvers
This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.
Background/Context
The new Data export approach was designed for the following features:
- Export orders in bulk via delimited file format: https://folio-org.atlassian.net/browse/UXPROD-2318
- Build a report with rollover errors and store in CSV file: https://folio-org.atlassian.net/browse/MODFISTO-173
- Circulation log export to CSV: https://folio-org.atlassian.net/browse/UXPROD-2691
- Cornell Library's go-live requirements to transfer fees/fines to the Cornell bursar system: https://folio-org.atlassian.net/browse/UXPROD-2862
- The ability to import/export fund updates via CSV file in order to bulk edit funds: https://folio-org.atlassian.net/browse/UXPROD-199
There is no intent to replace any existing data export solution for now. If later there will be a requirement to significantly extend any existing Data export solution, the new approach should be applied.
Assumptions
N/A
Constraints
N/A
Rationale
N/A
Decision
All the new Data export features should be implemented by using this approach
Implications
- Pros
- N/A
- Cons
- N/A
Other Related Resources