Currently, the tool does not object to any placement of most fields, even if the placement would indicate a wrongly formatted dataset.
The fields DNA_sequence, scientificName, kingdom, phylum, class, order, family, genus can only logically be placed in the taxonomy table, but currently you can provide them in the Sample and Study table as well.
The fields eventDate, decimalLatitude, decimalLongitude, associatedSequences, materialSampleID can only logically be placed in the Sample (or in special cases in the Study) table, but currently you can provide them in the Taxonomy.
There are softer situations, but the above cases are almost always certainly wrong.
Can we make negative lists of fields that throws a warning if these are present in the (ir)relevant table upon upload?
Currently, the tool does not object to any placement of most fields, even if the placement would indicate a wrongly formatted dataset.
The fields
DNA_sequence, scientificName, kingdom, phylum, class, order, family, genuscan only logically be placed in the taxonomy table, but currently you can provide them in the Sample and Study table as well.The fields
eventDate, decimalLatitude, decimalLongitude, associatedSequences, materialSampleIDcan only logically be placed in the Sample (or in special cases in the Study) table, but currently you can provide them in the Taxonomy.There are softer situations, but the above cases are almost always certainly wrong.
Can we make negative lists of fields that throws a warning if these are present in the (ir)relevant table upon upload?