[UXPROD-3253] Data Export - Transformation form populated dynamically Created: 26/Aug/21  Updated: 18/Jan/22

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Magda Zacharska Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Development Team: Firebird
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem:
When setting up a custom mapping profile, the user need to specify transformations for the fields that will be included in the export. This is being done on the mapping profile transformation form.

The current implementation supports only subset of fields for each record type as specified in https://docs.google.com/spreadsheets/d/1XvHmToGQwhzmMNlQ5-l1QTEDyUtDpdn_/edit#gid=1869895650

To avoid the need to revisit the form each time new fields are being added to the inventory records or to avoid time consuming prioritizing of the fields, the transformation form should be populated dynamically with all properties for each inventory record type.

In scope
The list of fields is populated dynamically instead of using pre-defined enum: https://github.com/folio-org/mod-data-export/blob/3bef6dc2ae5ecc7bc48d0f41de0ee607fbbe7376/src/main/java/org/folio/service/transformationfields/TransformationConfigConstants.java

Out of scope

Use case(s)
When a new field is added to the record, no changes in the code are required

Proposed solution/stories
GET /data-export/transformation-fields returns all fields for each inventory record type
The labels for the fields displayed on the form are generated dynamically as well


Generated at Fri Feb 09 00:30:39 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.