Hi Kenny. Nice post. Particularly interested in the sentence "The schemas link this metadata directly to both raw sequencing files and processed results, like gene counts and downstream reports". I know how with latch the metadata can be linked to the raw sequencing data but am unsure how a row can be linked to results, particularly when you could have multiple executions for one sample. Be keen to know more
You can create a nullable column for each anticipated execution and link the report directly as a file. If a sample has less executions, you would simply leave the value as null.
It would be a nice feature to be able to import these by pointing at a folder and linking to sample name and in addition have the column header be a clickable item linking to the execution
Hi Kenny. Nice post. Particularly interested in the sentence "The schemas link this metadata directly to both raw sequencing files and processed results, like gene counts and downstream reports". I know how with latch the metadata can be linked to the raw sequencing data but am unsure how a row can be linked to results, particularly when you could have multiple executions for one sample. Be keen to know more
You can create a nullable column for each anticipated execution and link the report directly as a file. If a sample has less executions, you would simply leave the value as null.
It would be a nice feature to be able to import these by pointing at a folder and linking to sample name and in addition have the column header be a clickable item linking to the execution
Totally, passed on to Hannah