Export Instances with Custom Export Profile from Member Tenant
Description
Environment
None
Potential Workaround
None
defines
Checklist
hideActivity
Show:

Magda Zacharska May 17, 2024 at 8:41 PM
Functionality delivered in scope of the Quesnelia release meets this scenario.

Viachaslau Khandramai April 10, 2024 at 11:39 AM
, please, review - this should be already implemented.
Done
Details
Details
Assignee
Unassigned
UnassignedReporter

Priority
Story Points
0
Development Team
Firebird
Release
Ramsons (R2 2024)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 26, 2024 at 9:08 PM
Updated November 1, 2024 at 10:57 PM
Resolved May 17, 2024 at 8:41 PM
TestRail: Cases
TestRail: Runs
Purpose/Overview:
A member tenant should be able to export records using a custom export profile that will include instance records (shared and local) enriched with holdings and items data .
Requirements/Scope:
User can trigger the export by uploading the file with list of identifiers or by cql statement.
User can export with a custom mapping profile that has been defined for this member tenant.
A custom export profile will export all matching instances that are shared or local for the member tenant and will include relevant holdings and items data stored in member tenants according to the custom profile settings.
If the record does not have an underlying MARC bib record (SRS instance record), then the abbreviate record based on the default mappings is generated and holdings/ items data is appended to it.
If the record does have an underlying MARC bib record (SRS instance record), then that record is used in the exportand holdings/ items data is appended to it.
If the instance does not have any holdings associated with this member tenant but it matches the requested instance (UUID or CQL), it is also included in the export without providing holdings and item data.
If the list of submitted identifiers contains duplicate, the instance is exported only once.
Approach:
Acceptance criteria:
All requirements are met
Migration scripts are provided (if required)
API tests are written/updated and tests passed successfully (screenshot added)