{
"name": "sequenceExperiment",
"version": 2,
"createdAt": "2026-03-10T20:12:09.922808",
"options": {
"fileTypes": [
"BAM",
"FASTQ"
],
"externalValidations": [...]
},
"schema": {
"$schema": "http://json-schema.org/draft-07/schema#",
"id": "analysisPayload",
"type": "object",
"definitions": {
"common": {...},
"file": {
"fileType": {
"type": "string"
},
"fileData": {
"type": "object",
"required": [
"dataType",
"fileName",
"fileSize",
"fileType",
"fileAccess",
"fileMd5sum"
],
"properties": {
"dataType": {
"type": "string"
},
"fileName": {...},
"fileSize": {...},
"fileAccess": {...},
"fileType": {...},
"fileMd5sum": {...},
"info": {...}
}
}
},
"analysisType": {...}
}
A) is to account instances where files contain multiple file types. For example a single VCF could contain SNVs and InDels type.
B) a controlled list is preferable but recognize the list of datatypes could grow. An implementation similar to fileTypes where dataTypes can be updated via options would be good.
Below is an example of a schema
where
dataTypeis defined as astring. We'd like to :A) Modify
dataTypefromstringto anarrayofstringsB) Allow for dynamic schema defined list of enum values
A) is to account instances where files contain multiple file types. For example a single VCF could contain
SNVsandInDelstype.B) a controlled list is preferable but recognize the list of datatypes could grow. An implementation similar to
fileTypeswheredataTypescan be updated viaoptionswould be good.