Skip to content

Add data validation and missing data handling practices#11

Open
nick-gorman wants to merge 1 commit intomainfrom
data-validation
Open

Add data validation and missing data handling practices#11
nick-gorman wants to merge 1 commit intomainfrom
data-validation

Conversation

@nick-gorman
Copy link
Member

@nick-gorman nick-gorman commented Jan 29, 2026

A write-up of the proposed data validation practices we discussed at the 2026 planning workshop.

My notes on this session were a little light, so I mostly went off memory, and have added extra details where I thought they were warranted. As always please treat as draft and let me know what you think, or if you want to add details from your notes.

Addresses #5

Documents schema-based approach for handling missing data in templater
and translator modules, including schema enforcement at module boundaries,
testing requirements, and documentation standards.
@nick-gorman
Copy link
Member Author

Another thought for consideration. In the schemas, should we either allow additional columns which aren't required or optional, but get dropped at enforcement time? I'm thinking of columns like "status" in the ecaa_generators table. It seems strange to make the status column required or even create it and fill it with NaNs if not included. But we could either specify a set of metadata columns that are allowed but dropped (silently) on schema enforcement or just drop (silently) all columns which aren't either required or optional.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant