Replies: 1 comment
-
|
Thanks for the question (and your patience), so each sample in your metadata has a property ( If this is the case then the current limitation is that song is only concerned with ensuring the files listed within any given analysis object exist in object storage. This is a requirement of publication (every analysis with state For the specific validation you're describing (checking FASTA headers against metadata), you'd likely need to implement custom validation logic. This could parse the uploaded FASTA files and verify that all fasta_header values from your samples object exist in the files. @joneubank Does this track am I missing anything? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
My metadata will be an array of objects under the
sampleskey. Each object will have a fasta_header field, although this name can change if needed.My files will be one or more FASTA files to an Analysis.
Is it possible for overture (score, or something else) to verify whether there is a FASTA record for each metadata record? Or is there a standard way to build such validation on top of finalising an upload or something?
Beta Was this translation helpful? Give feedback.
All reactions