NF Schema v2.1.0

Version	Date	Author	Decision	Rationale
2.1.0	9/16/2021	RJA	Added MRIAssay template	To provide a simplified template for data contributors of MRI data.
2.1.0	9/16/2021	RJA	Added parent "MRISequence" attribute with definition and source.	Bugfix for missing parent attribute.
2.1.0	9/16/2021	RJA	Added Conventional MRI, Functional MRI, Magnetic Resonance Spectroscopy to assay valid values	Bugfix for missing valid values

NF Schema v2.0.0

Version	Date	Author	Decision	Rationale
2.0.0	8/25/2021	RJA	Update milestoneReport definition.	To clarify that our "milestones" = GFF "progress reports".
2.0.0	9/16/2021	RJA	Added more granular assay terms for MRI (Magnetic Resonance Spectroscopy, Functional MRI, Conventional MRI). Conventional MRI replaces the previous term "MRI", thus this is a "major" update and is not backwards compatible. This will require remapping all "MRI" terms in the portal.	At data contributor request.
2.0.0	9/16/2021	RJA	Added "MRISequence" attribute with T1, T2, PD, and STIR sequences.	Help clarify conventional MRI data modalities.
2.0.0	9/16/2021	RJA	Changed "milestoneReport" to "progressReportNumber". Will need to remap term in main fileview.	At request of funding partner for clarity with their grantees.

NF Schema v1.0.1

This release contains the following logged changes:

Version	Date	Author	Decision	Rationale
1.0.1	8/24/2021	RJA	Corrected fileFormat valid values	Was missing 'nii' in valid values, even though we had previously defined this attribute

NF Schema v1.0.0

This release contains the initial NF schema with all historical changes and the following logged changes:

Version	Date	Author	Decision	Rationale
1.0.0	8/18/2021	RJA	Add nii file format.	Needed for new dataset, no existing sufficient term
1.0.0	8/18/2021	RJA	Added image mask dataType.	Needed for new dataset, no existing sufficient term
1.0.0	8/18/2021	RJA	Enhanced "dataType" definition.	Was not very clear definition, and was confusing (previously referred to only bioinformatics data types, which is not how this term is being used).
1.0.0	8/18/2021	RJA	Added cellLine values from prototype Neurofibromatosis Tools and Resources database.	Ensure parity in canonical cell line names between these two resources.
1.0.0	8/18/2021	RJA	Added animal model values from prototype Neurofibromatosis Tools and Resources database.	Ensure parity in canonical animal model names between these two resources.
1.0.0	8/18/2021	RJA	Combined modelSystemName and modelSystemStrainNomenclature (removing the latter term)	They are becoming redundant; most mouse model "names" we are using are model system strain nomenclatures.
1.0.0	8/18/2021	RJA	Shortened definition for Prss56Cre;R26mT	It was overly detailed, source link can be used for more information.
1.0.0	8/20/2021	RJA	added definitions and sources for Male, Female, Unknown attributes	To help clarify usage
1.0.0	8/20/2021	RJA	added "Sporadic Schwannoma" term for diagnosis	To accomodate situations in which patients have non-schwannomatosis schwannomas
1.0.0	8/20/2021	RJA	Changed tumorType definition to "The type of tumor that the biospecimen used to generate the data were collected from."	To clarify that this attribute refers to the biospecimen, not the patient.
1.0.0	8/20/2021	RJA	added "comments" attribute and added to all manifest types	To collect unstructured information that may not be captured by schema.
1.0.0	8/20/2021	RJA	Added additional values to NF1/NF2 genotype	To account for situations in which somatic or germline hits might not be known. Long term, this could be split into more attributes (e.g. 22q LOH, NF2 somatic mutation, LZTR1 somatic mutation, etc..) but that might be burdensome to annotate. For now, keep terms simple for exploration, and rely on additional project-specific metadata.
1.0.0	8/20/2021	RJA	Changed all lowercase "unknown" values to "Unknown"	There was previously a mixture, harmonizing will allow us to have one single attribute (TODO). This will require remapping some values currently on the portal.
1.0.0	8/20/2021	RJA	Found and removed duplicate values for "sex" attribute	Was causing validation errors ('unknown' treated as canonical value rather than 'Unknown')