Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
Concorde - Sprint 99
-
3
-
Concorde
Description
Purpose/Overview:
When the error occurs during the export of the holdings record, user would need to know what went wrong so that the issue could be addressed.
Requirements/Scope:
- Date, time, reason for the error, details of the affected record:
- Holdings UUID
- Holdings HRID
- Associated Instance UUID
- Associated Instance HRID
- Associated Instance Title
Note:
Due to limitation of the current implementation, when the error occurs during the export of the holding record, the logs will contain data from the related instance, all holdings and items. Originally planned functionality will be addressed once MDEXP-302 is completed
Acceptance criteria:
- The errors log can be accessed from UI
TestRail: Results
Attachments
Issue Links
- clones
-
MDEXP-257
Log errors for inventory Instance record exports
-
- Closed
-
- defines
-
UXPROD-2326 Export Manager - logs details
-
- Closed
-
- has to be done after
-
MDEXP-261
Create API GET/data-export/logs/{jobExecutionID} for error log handling
-
- Closed
-
- has to be done before
-
MDEXP-260
Log errors for Inventory Item records export
-
- Closed
-
- is cloned by
-
MDEXP-260
Log errors for Inventory Item records export
-
- Closed
-
- relates to
-
GMU-1
POC - Detect which record exactly leads to the exception during the export to the error logs
-
- Closed
-