Log errors for Holdings records export

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:

  1. 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

Environment

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Magda ZacharskaOctober 9, 2020 at 8:57 PM

Thank you, for documenting this so well - it was very helpful while I validated it.

Andrii NovytskyiOctober 9, 2020 at 8:10 AM
Edited

Verified on https://folio-testing.dev.folio.org:
1 Create a mapping profile:


We have a bug with material type, that will be fixed tomorrow, so the export will be failed. The job profile name is Test log
2. Start the export process with this csv


3. The export is failed, query error logs by job execution id /data-export/logs?query=jobExecutionId=ec0329b8-9dc2-49f3-b02b-f9f3e34cb5a5;
The response is:

The second check is to export file with random uuid:
Start the export process with random uuid in csv file;
Get the error logs by created job execution id;
The response is:

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Concorde

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 3, 2020 at 7:31 PM
Updated November 2, 2020 at 10:56 AM
Resolved October 9, 2020 at 8:58 PM
TestRail: Cases
TestRail: Runs