F1 - Data Mapping

[VRagulina]

As a NAD administrator, I want map provided fields from the record to NAD required/defined fields, so I can process record.

AC:

Tasks

Preview Give feedback

1. Add UI component
2. Integrate UI with the backend

[VRagulina]

Explore technical complexity for P3 and possible solutions.

[sb-2011]

PR has been merged with the Initial design of the crosswalk/column mapping logic which uses yaml configuration files. To complete this work, we want to consider the points below. The points labeled (Minor) are not required for the MVP, however, (Major) labeled points are.

1. Need some UI components to allow the user to upload a config or create a config visually. (Major)
2. Decide on how many configs will we allow a data producer to create to serve different source data schemas and do we want to allow the application to store historical updates of a config. (Minor)
3. As of today, we are storing the configs locally within the application but do we want to store them in an external storage system such as S3 instead. (Minor)

[emilylordahl]

Hi @akuny @JuliaCardis @VRagulina @seckb: I added the flows for the data mapping UX in this prototype. As mentioned in slack, I'd love to walk through this with the team to discuss, answer any questions and discuss a concern about the proposed flow. I'll grab us time next week!

Thanks!