You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many users are now involved in projects where multiple tissues may be sampled from a single specimen. The tissues will be used for different purposes (stable isotopes, whole genomes, population genetics) by different lab groups, and will be housed in various institutions.
Currently, the Samples tab of a Biocode Team workbook records both material samples (materialSampleID and associated fields) as well as tissues (tissueID and related fields). In order for a user to create multiple tissues for one specimen, the materialSampleID row must be exactly duplicated, then tissue-specific metadata adjusted as needed.
Since GEOME stores Sample and Tissue data as separate tables, could we also design data ingestion and export to mirror this structure? E.g. The Events tab in the workbook has eventID and associated fields; Samples tab maps materialSampleIDs to an eventID and has associated sample fields; and a Tissues tab could map a tissueID to a materialSampleID and have tissue fields. This would greatly reduce errors and make recording, uploading, and updating data much more efficient.
The text was updated successfully, but these errors were encountered:
Many users are now involved in projects where multiple tissues may be sampled from a single specimen. The tissues will be used for different purposes (stable isotopes, whole genomes, population genetics) by different lab groups, and will be housed in various institutions.
Currently, the Samples tab of a Biocode Team workbook records both material samples (materialSampleID and associated fields) as well as tissues (tissueID and related fields). In order for a user to create multiple tissues for one specimen, the materialSampleID row must be exactly duplicated, then tissue-specific metadata adjusted as needed.
Since GEOME stores Sample and Tissue data as separate tables, could we also design data ingestion and export to mirror this structure? E.g. The Events tab in the workbook has eventID and associated fields; Samples tab maps materialSampleIDs to an eventID and has associated sample fields; and a Tissues tab could map a tissueID to a materialSampleID and have tissue fields. This would greatly reduce errors and make recording, uploading, and updating data much more efficient.
The text was updated successfully, but these errors were encountered: