ENA currently stores checklist fields and field groups as reusable components and assmeble these into checklists. Similarly we should store fields and field groups in Github and assemble them to JSON Schema at the publication time. First, study existing ENA checklist editor functionality and come up with a structure to store fields in the Github. The structure should be well documented and easily accessible programatically. Think about reusing, versioning, immutabiity of fields and groups.
Study existing ENA checklist format and identify shortcomings (fields, groups)
Develop file structure to store fields and field groups. These fields should be later accessed programatically.
Develop a strategy to assemble fields into schemas.
Create a script for assembling/publishing a checklist/schema from fields/groups
ENA currently stores checklist fields and field groups as reusable components and assmeble these into checklists. Similarly we should store fields and field groups in Github and assemble them to JSON Schema at the publication time. First, study existing ENA checklist editor functionality and come up with a structure to store fields in the Github. The structure should be well documented and easily accessible programatically. Think about reusing, versioning, immutabiity of fields and groups.