[GMU-3] Fix class cast exception during fields mapping Created: 16/Dec/20 Updated: 10/Mar/21 Resolved: 18/Dec/20 |
|
| Status: | Closed |
| Project: | generate-marc-utils |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 1.1.0 |
| Type: | Bug | Priority: | P2 |
| Reporter: | Andrii Novytskyi | Assignee: | Igor Gorchakov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Sprint: | Concorde - Sprint 104 | ||||||||
| Story Points: | 1 | ||||||||
| Development Team: | Concorde | ||||||||
| Description |
|
Purpose: For holdings and items, during the mapping process, the class cast exception occurs during creating RecordInfo, for simple fields when their jsonPath contains array (for example "$.holdings[*].hrid") Acceptance criteria:
|
| Comments |
| Comment by Magda Zacharska [ 17/Dec/20 ] |
|
Igor Gorchakov and Andrii Novytskyi - is there a way to validate the fix? |
| Comment by Andrii Novytskyi [ 18/Dec/20 ] |
|
Magda Zacharska create a mapping profile with holdings or items, with selected hrId field, and start export, and check that hrId is present is the marc file |
| Comment by Andrii Novytskyi [ 18/Dec/20 ] |
|
verified on local with the latest changes from gmu. Exported with default MFH rules, as a result, no exceptions, and fields are present in marc file: |