Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
Firebird Sprint 131
-
5
-
Firebird
Description
Overview
To support exporting MFHD records, we need to support accepting UUIDs uploaded in a file and only export the holdings records.
Approach
- Change the ExportRequest.json to accept an additional field to specify if the UUIDs belong to Instance/holdings/items
- To avoid making it a breaking change it to use Instance as the default value, and support other values
- Change the ExportManagerImpl to call only holdings APIs to fetch the details to export based on the above parameter
- Create default mapping and job profile to support MFHD
Acceptance Criteria
- Logic is changed according to the approach above
- Export of MFHD works end-end and an export file is created according to the default rules created as part of
MDEXP-12 - Unit tests updated
- API tests updated
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1396 Generating simple MARC Holdings from Inventory holdings record
-
- Closed
-
- has to be done after
-
MDEXP-12 Create Inventory Holdings to MFHD record mapping rules
-
- Closed
-
- relates to
-
MDEXP-499 Existing holdings UUIDs are reported as invalid while exporting holdings record
-
- Closed
-
-
MDEXP-504 Exported holdings MARC records are combined with the records generated on the fly
-
- Closed
-
-
MDEXP-14 Export Inventory holdings records in MFHD based on provided UUIDs
-
- Closed
-
-
MDEXP-519 Holdings export: subfields for 866, 867 and 868 are entered separately
-
- Closed
-
-
MDEXP-584 Holdings cannot be exported with custom mapping profile
-
- Open
-
-
UIDEXP-177 Select UUIDs type before starting export
-
- Closed
-