Don't create pmd:codesUsed for measures #88
Comments
lkitching
added a commit
that referenced
this issue
Jan 3, 2019
Issue #88 - Only create codesUsed collections for dimension and attribute columns. Add codes_used column to intermediate component specifications file. Update related metadata to include this new column. The column has a value (of "yes") to indicate if the component should have an associated pmd:codesUsed property relating it to a code list. Update the corresponding CSVW metadata to only output codesUsed codelists connected to the corresponding components for dimension and attribute columns. Fix failing test. Fix another test. Fix another test. Fix test. Add tests for pmd:codesUsed on dimensions and measures. Only declare skos:Collection statements for codelists that exist. Only generate codelists for dimension and attribute columns. Remove unused function. Add documentation.
lkitching
added a commit
that referenced
this issue
Jan 3, 2019
Issue #88 - Only create codesUsed collections for dimension and attribute columns. Add codes_used column to intermediate component specifications file. Update related metadata to include this new column. The column has a value (of "yes") to indicate if the component should have an associated pmd:codesUsed property relating it to a code list. Update the corresponding CSVW metadata to only output codesUsed codelists connected to the corresponding components for dimension and attribute columns.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Measures don't need
pmd:codesUsedcollections. The measureType dimension should still have one of course.The text was updated successfully, but these errors were encountered: