You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When rewriting the ETL script, many issues with spelling between the ETL and the dataset column names were identified. Those spelling issues will affect harmonization which could result in resources generated with missing Interoperability pieces in place.
While it should be safe to assume that the data we get is consistent from one version to the next, we've seen that it isn't always the case. Having play's extractor component halt on values that don't match the current data-dictionary would lead to catching these inconsistencies earlier.
The text was updated successfully, but these errors were encountered:
When rewriting the ETL script, many issues with spelling between the ETL and the dataset column names were identified. Those spelling issues will affect harmonization which could result in resources generated with missing Interoperability pieces in place.
While it should be safe to assume that the data we get is consistent from one version to the next, we've seen that it isn't always the case. Having play's extractor component halt on values that don't match the current data-dictionary would lead to catching these inconsistencies earlier.
The text was updated successfully, but these errors were encountered: