Skip to content

chore: 🏗️ add variable-resource map for adverse events - #220

Open
lwjohnst86 wants to merge 1 commit into
docs/add-a-design-for-flowfrom
chore/mapping-variables-to-resource-ae
Open

lwjohnst86 wants to merge 1 commit into
docs/add-a-design-for-flowfrom
chore/mapping-variables-to-resource-ae

Conversation

@lwjohnst86

Copy link
Copy Markdown
Member

Description

First part of this mapping. Will make PRs as I add mappings.

Needs a quick review.

@lwjohnst86
lwjohnst86 requested a review from a team as a code owner September 7, 2026 10:18
@lwjohnst86 lwjohnst86 moved this from Todo to In Review in Data development Sep 7, 2026
@lwjohnst86
lwjohnst86 force-pushed the chore/mapping-variables-to-resource-ae branch from a1879a8 to 56a1b69 Compare September 8, 2026 13:17

@martonvago martonvago Sep 9, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To make sure I understand, this is a table that for each raw field gives:

  • the resource it will go in
  • its name in the raw data
  • its name in the staged data
  • the abbreviation of the raw form it is from
  • the name of the raw form it is from

I don’t understand the new_form_name column — why would a form ever be renamed? Aren’t forms the raw thing and resources the processed thing?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those are a remnant of the work Signe and I did with noting down what the new name should be in Main. You can ignore those I think.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah okay! But then should that column be removed / moved to a separate table?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, for sure, good catch. We don't actually need that column anymore. Will remove 👍

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll remove those after all the other stacked PRs have been reviewed, approved and merged.

@K-Beicher K-Beicher left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy with these, the entire form may be dropped in main.

@K-Beicher K-Beicher left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, agree on that last one.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

3 participants