Skip to content
This repository was archived by the owner on Sep 24, 2024. It is now read-only.
This repository was archived by the owner on Sep 24, 2024. It is now read-only.

Semi-automated Matching to Common Schema(2): Simple Matching from input to target schema  #10

@mjia8

Description

@mjia8

Team members: Aadit, Michael, Jaqueline
Sprint 5: 6/26-7/3

Overall goal:
Create a basic semi-automated system for writing crosswalks for new data sets. We want to use the existing crosswalk information as a blueprint on how to transform the data that we downloaded into the format we want it. The current crosswalk data is defined by the user so we want a faster/semi-automated way to do this.

What does success look like?

  • We want a function that takes in a dataset and returns a draft crosswalk mapping (as an Object in JS). When we integrate this into existing functionality, the user will be able to review this object and approve or modify it.
  • We will also need a json file called crosswalk_mappings.json that contains a mapping from each target header to an array of source headers and functions containing one or more source headers.
  • Start with 1:1 mappings between target data labels and the data labels we have. This is enough for success now.
  • Later we can consider adding mappings from target headers to functions of one or more source headers.

Comments:

  • Based on previous crosswalk data and seeing which input column names were associated with each target schema column name, we want to create a basic system where we can give in an input column name and generate the target schema column name that is associated with it.

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions