Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Won't Do
-
None
-
None
-
None
-
-
2
-
Firebird
Description
Purpose/Overview:
When the error occurs during the export of the item 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:
- Item UUID
- Item HRID
- Associated Holdings UUID
- Associated 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-259
Log errors for Holdings records export
-
- Closed
-
- defines
-
UXPROD-2493 Data Export - search existing mapping and job profiles
-
- Closed
-
- has to be done after
-
MDEXP-259
Log errors for Holdings records export
-
- Closed
-
-
MDEXP-261
Create API GET/data-export/logs/{jobExecutionID} for error log handling
-
- Closed
-
- relates to
-
GMU-1
POC - Detect which record exactly leads to the exception during the export to the error logs
-
- Closed
-
-
-
- Closed
-