Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Applying mapping profile - Combination of record types - selected fields - missing transformation

Description

Purpose
This story addresses exporting multiple record types when the user wants to export only selected fields and each field but does not provide transformation.

Scenario 1:
Given: the mapping profile contains selected fields from the inventory instance and the fields don't have specified transformations
When: the fields have mappings in rules.json (used for generating records on the fly)
Then:

  1. Only fields selected in the mapping profile are part of the exported record

  2. The fields are populated with the data coming inventory instance record according the existing mapping rules

  3. LDR is re-generated based on the selected fields

  4. .mrc file is generated

  5. Unit and API tests are written

Scenario 2:
Given: the mapping profile contains selected fields from the inventory instance and the fields don't have specified transformations
When: the fields have don't have mappings in rules.json (used for generating records on the fly)
Then:

  1. the fields are being disregarded during the export

  2. the log is populated with the information that the transformation was not available

  3. .mrc file is generated and populated only with the fields that have transformations or mappings available

Scenario 3:
Given: the mapping profile contains selected fields from holdings or items records
When: and the fields don't have specified transformations
Then:

  1. the fields are being disregarded during the export

  2. the log is populated with the information that the transformation was not available

  3. .mrc file is generated and populated only with the fields that have transformations or mappings available

Environment

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Illia Borysenko September 24, 2020 at 2:07 PM

Attached logs from the rancher environment for missing default rules for instance. I also found an issue with logging for holdings and items transformation with empty values, I'll push fix together with changes for

Magda Zacharska September 21, 2020 at 5:47 PM

please provide examples of log entries for the fields that were not mapped and without default mappings.

Illia Borysenko September 21, 2020 at 4:43 PM

Attached downloaded .mrc file

Kruthi Vuppala September 21, 2020 at 1:09 PM

Please attach the downloaded .mrc file and a screenshot of the parsed file.It will help in verification Thanks!

Illia Borysenko September 21, 2020 at 12:25 PM
Edited

Steps to verify using CURL commands (for snapshot-load environment):

Header 'x-okapi-token' for each request should be replaced with real one value. All reference id values in 'data-row' body should also be replaced with real uuids received as responses of previous requests.

1) Create mappping profile for all instance fields with empty trasformations:

2) Create job profile with new mapping profile and use new generated uuid of mapping profile:

3) Create a new file defiition:

4) Upload .csv with record identifiers:

5) Run data export with certain file definition and job profile

6) Find necessary job execution to get job execution id and id of generated .mrc file:

7) Download generated file from S3 by certain job execution id and file id:

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Concorde

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 21, 2020 at 4:58 PM
Updated November 2, 2020 at 10:56 AM
Resolved September 30, 2020 at 12:37 AM
TestRail: Cases
TestRail: Runs