-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Outputting issues with variables in every domain #128
Comments
This is a problem when the spec has column names in Snake case: It just assumes there's no domain in the spec, hence appearing multiple times. I have 3 suggestions:
edit: added the 3rd suggestion |
In addition to the column names case in metadata, we could check the mapping between the metadata and the expected metadata structure. The column names in the specifications file may differ depending on the template used for the specifications. It would be valuable to provide guidance to the user regarding which part of the metadata does not align with the expected metadata structure, what is the expected structure, and how to update the metadata to conform to the expected structure. For instance, in the P21C template, the column name is 'Data Type,' whereas the expected value is 'type.' |
I think |
…omain Closes #128 Add warning message when `xportr.*` column names don't match metadata
Look in 84-deepdive branch for data and specs
Should just be one
TRTSDT
If time given, then look into other xportr functions
The text was updated successfully, but these errors were encountered: