A subset of the MIxS specification that's self-documenting and DataHarmonizer compatible. Comes with valid and invalid data examples. Subset = all checklists and all environmental packages, but partial combinations.
Usage of terms in Checklist classes would be completely redundant. In the output of XXX, we informally model these usages? assignments? in terms of a "core" grouping
Already have
checklist oriented class-slot assignment and requirement sheet: data/core_requirements_recommended_required_curated.tsv
Starting on
environmental package usage sheet, based on data/mixs_v6_environmental_packages.tsv
Usage of terms in Checklist classes would be completely redundant. In the output of XXX, we informally model these usages? assignments? in terms of a "core" grouping
Already have
Starting on
47