airr-standards
airr-standards copied to clipboard
airr-community
AIRR Community Data Standards
When we introduced `data_processing_id`, it was meant to allow for multiple data processings to exist side-by-side, and we included statements like this: > It is expected that typical Repertoires might...
The field name as plural suggests multiple, but the description is written as though single. Also the fact that it's a single text field suggests single. Though it seems like...
I reviewed the documentation and I have some questions, comments and suggestions on various sections of the document. ## Random comments Who is the target audience for the document? I...
The current `DataProcessing` object is a sub-object within `Repertoire` so it's `data_processing_id` only needs to be unique within a repertoire. If we want to make `DataProcessing` a top-level object, or...
Again, from Emily, sparked by our discussion at the Vocab/Ontology meeting... We have been treating it solely as case and control, but never actively defined "case" - generally the studies...
In the 1.5 docs (e.g. for pcr_target_locus) the enum values for controlled vocabularies are missing: https://docs.airr-community.org/en/stable/miairr/data_elements.html versus the 1.4 docs: https://docs.airr-community.org/en/v1.4.1/miairr/data_elements.html Something odd with the doc generation?
MiAIRR has 3 levels of compliance. ``` - essential - important - defined ``` And I would argue, implied is a 4th level which is `none`. I.e. the AIRR object...
Until now our focus has been on data sets that are in the public domain, i.e. have been deposited within the infrastructure of INSDC. However, when thinking about the a...
We need to sync up the various terminology sets: 1. AIRR-C Terminology document (internal link) 2. AIRR-C Glossary of Terms: https://zenodo.org/record/5095381#.YTJK7NNKjgE 3. `docs/appendix/terms.rst`: https://docs.airr-community.org/en/stable/appendix/terms.html The Zenodo link will be authoritative,...
