{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","results":{"codes":[]},"settings":"","params":[]},"next":{"description":"","pages":[]},"title":"Metadata manifest file format","type":"basic","slug":"format-of-a-manifest-file","excerpt":"","body":"Two different metadata manifest file formats are used on CAVATICA. Which metadata manifest file you should use depends on the functionality that you're using the manifest for.\n\n  * [Command Line Uploader ](doc:set-metadata-using-the-command-line-uploader) - use this format of metadata manifest file in order to apply metadata when uploading files to CAVATICA.\n  * [Editing metadata via the visual interface](doc:edit-metadata-using-the-visual-interface) - use this format of the metadata manifest file in order to edit metadata for the files that are already in one of your projects on CAVATICA. \n\n##Metadata manifest format for the Command Line Uploader\n\nWhen uploading files to CAVATICA using the [Command Line Uploader](doc:set-metadata-using-the-command-line-uploader#section-set-metadata-for-multiple-files-using-a-manifest-file), a metadata manifest file can be used to define metadata values for those files. The supported file format for this manifest file is CSV, i.e. comma separated values. A CSV file contains a number of rows with columns which are separated with a comma.\n\nThe following rules apply:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Rule\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Line separation\",\n    \"0-1\": \"The lines are separated with a line break, while the columns are separated using a comma.\",\n    \"1-0\": \"First row\",\n    \"1-1\": \"The first row (manifest file header) has to contain column names which are treated as metadata keys (e.g. “sample”, “library”). Within the header, the first column must be `File` name, while the remaining columns are metadata keys. Also, please have in mind that metadata keys might be metadata schema or custom metadata keys.\",\n    \"2-0\": \"Must include File name\",\n    \"2-1\": \"It's mandatory to have `File` name as the first column in the header.\",\n    \"3-0\": \"First column\",\n    \"3-1\": \"The first column has to contain the names of the files which will be uploaded. In case the files are not in the same directory as the metadata manifest file, you should also include a path to the files (e.g. `../filename.fastq`).\",\n    \"4-0\": \"Subsequent columns\",\n    \"4-1\": \"All subsequent columns should contain metadata fields which will be assigned to the specified files.\",\n    \"5-0\": \"Case sensitivity\",\n    \"5-1\": \"Keys and values are case sensitive.\",\n    \"6-0\": \"Escape character\",\n    \"6-1\": \"To escape comma character in metadata key or value, enclose that field within double quotation marks (e.g. for setting specific key to md_value1,2 use \\\"md_value 1,2\\\"). Furthermore, to use double quote character in metadata key or value, enclose that field within double quotation marks and use two double quotation marks (e.g. for setting specific key to md_value\\\"1\\\" use \\\"md_value\\\"\\\"1\\\"\\\"\\\").\",\n    \"7-0\": \"Maximum size\",\n    \"7-1\": \"The maximum size for the metadata manifest file is 5 GiB.\",\n    \"8-0\": \"Maximum number of key-value pairs\",\n    \"8-1\": \"Maximum number of key-value pairs per file is 1000, including null-value keys.\",\n    \"9-0\": \"Keys and values encoding\",\n    \"9-1\": \"Keys and values are UTF-8 encoded strings.\",\n    \"10-0\": \"Maximum key length\",\n    \"10-1\": \"100 bytes (UTF-8 encoding)\",\n    \"11-0\": \"Maximum value length\",\n    \"11-1\": \"300 bytes (UTF-8 encoding)\",\n    \"12-0\": \"Metadata for files only\",\n    \"12-1\": \"There is no metadata for folders on CAVATICA. Any folder specified in the manifest file will be skipped and the metadata will not be set for a folder.\"\n  },\n  \"cols\": 2,\n  \"rows\": 13\n}\n[/block]\nThe following example shows the content of the metadata manifest for three files with three metadata fields.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"File name\",\n    \"h-1\": \"sample\",\n    \"h-2\": \"library\",\n    \"h-3\": \"paired_end\",\n    \"0-0\": \"file1.fastq\",\n    \"0-1\": \"sample1\",\n    \"0-2\": \"examplelibrary1\",\n    \"0-3\": \"1\",\n    \"1-0\": \"file2.fastq\",\n    \"1-1\": \"sample1\",\n    \"1-2\": \"examplelibrary1\",\n    \"1-3\": \"2\",\n    \"2-0\": \"file3.fastq\",\n    \"2-1\": \"sample2\",\n    \"2-2\": \"examplelibrary2\",\n    \"2-3\": \"1\"\n  },\n  \"cols\": 4,\n  \"rows\": 3\n}\n[/block]\nBelow is the same example in a comma separated format.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"File name,sample,library,paired_end\\nfile1.fastq,sample1,examplelibrary1,1\\nfile2.fastq,sample1,examplelibrary1,2\\nfile3.fastq,sample2,examplelibrary2,1\\n\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\n\n\n##Metadata manifest format for modifying metadata via the visual interface\n\nThis manifest file is used In case you are modifying metadata for your project files via the visual interface.\n\nThe supported file formats for this manifest file are CSV and TSV. A CSV file contains a number of rows with columns which are separated with a comma, while the TSV file separates them with a tab.\n\nThe following rules apply:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Rule\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"Line separation\",\n    \"0-1\": \"The lines are separated with a line break, while the columns are separated using a comma.\",\n    \"1-0\": \"Columns separator\",\n    \"1-1\": \"The columns are separated using a comma (CSV) or a tab (TSV) while the lines are separated with a line break.\",\n    \"2-0\": \"First row\",\n    \"2-1\": \"The first row (manifest file header) has to contain column names which are treated as metadata keys (e.g. “sample”, “library”). Within the header, the first column must be either `id` or `name`, Next, there can be project and size columns which are system metadata fields and are treated as read-only (these fields are present if manifest file is generated using Export metadata to a manifest action). The remaining columns are metadata keys, which can be metadata schema or custom metadata keys. Please have in mind that the order of columns is important, e.g. id column (if present) must be the first one.\",\n    \"3-0\": \"Must include id or name (along with project path)\",\n    \"3-1\": \"1. It’s mandatory to have either id or name column, and it’s allowed to have both of them.\\n2. If both id and name columns are present, then id will be used for identifying file, while the name will be omitted.\",\n    \"4-0\": \"Name field\",\n    \"4-1\": \"This field should also include file path within the project for files which are not in the project root, so it’s actually path + name. If \\\"id\\\" column is not present in the metadata manifest file, then this field will be used for identifying files whose metadata should be edited. If \\\"id\\\" is present in the metadata manifest file, then this field will be ignored, meaning it's not possible to change file name or file path using \\\"Import metadata manifest\\\" feature (situation which is the same as currently, although it might change in the future). This way, it's possible to edit metadata using manifest file without providing file IDs and providing only file names (along with path, in case when files are stored in folder instead of project root) instead of having to fetch file IDs.\",\n    \"5-0\": \"Project field\",\n    \"5-1\": \"It’s possible to have “project” column (e.g. if you have used the Export metadata manifest feature, then edited generated metadata manifest file and submitted it for import). If present it is treated as read-only field (i.e. it is not possible to either move or copy files from one project to the other using this feature), but validation should take place - if the specified “project” value is different than the current project (i.e. the project in which the Import metadata manifest feature has been used) then this file shouldn’t be edited and it should be counted towards files which are failed as part of this action. Have in mind that the “project” field is non-mandatory field in the manifest file.\",\n    \"6-0\": \"Size field\",\n    \"6-1\": \"It is possible to have the “size” column (e.g. you have used the Export metadata manifest feature, edited the generated metadata manifest file and submitted it for import). If present, it is treated as read-only field (i.e. it is not possible to change the file size using this feature, or any other feature). In addition, there should not be any validations including this field.\",\n    \"7-0\": \"Metadata schema fields and custom metadata fields\",\n    \"7-1\": \"Following the aforementioned fields (there can be at a minimum one, and at the maximum four read-only fields) you can specify the metadata fields which should be edited. There must be at least one metadata column specified in the manifest file (otherwise the action will fail because there is no metadata field to be edited). The metadata schema fields are specified according to the documented metadata schema.\",\n    \"8-0\": \"Empty rows\",\n    \"8-1\": \"It's allowed to have an empty row in the manifest file. Empty row will be skipped during manifest file processing.\",\n    \"9-0\": \"Case sensitivity\",\n    \"9-1\": \"The manifest file is case-sensitive.\",\n    \"10-0\": \"Escape character\",\n    \"10-1\": \"To escape comma character in metadata key or value, enclose that field within double quotation marks (e.g. for setting specific key to md_value1,2 use \\\"md_value 1,2\\\"). Furthermore, to use double quote character in metadata key or value, enclose that field within double quotation marks and use two double quotation marks (e.g. for setting specific key to md_value\\\"1\\\" use \\\"md_value\\\"\\\"1\\\"\\\"\\\").\",\n    \"11-0\": \"Maximum size\",\n    \"11-1\": \"The maximum size for the metadata manifest file is 5 GiB.\",\n    \"12-0\": \"Maximum number of rows\",\n    \"12-1\": \"The maximum number of rows for the metadata manifest file is 40,001, which corresponds to maximum number of files in the single project on the Platform (plus header row).\",\n    \"13-0\": \"Maximum number of key-value pairs\",\n    \"13-1\": \"Maximum number of key-value pairs per file is 1000, including null-value keys.\",\n    \"14-0\": \"Keys and values encoding\",\n    \"14-1\": \"Keys and values are UTF-8 encoded strings.\",\n    \"15-0\": \"Maximum key length\",\n    \"15-1\": \"100 bytes (UTF-8 encoding)\",\n    \"16-0\": \"Maximum value length\",\n    \"16-1\": \"300 bytes (UTF-8 encoding)\"\n  },\n  \"cols\": 2,\n  \"rows\": 17\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Columns which are specified after id, name, size and project will be treated as metadata fields.\"\n}\n[/block]\nThe following example shows a metadata manifest file which contains both id and name columns along with one metadata schema field (quality_scale, paired_end) and one custom metadata field (Read length). Please note that in this case the id field will be used to uniquely identify file within the project, while the name field will be ignored.\n\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"id\",\n    \"h-1\": \"name\",\n    \"h-2\": \"quality_scale\",\n    \"h-3\": \"paired_end\",\n    \"h-4\": \"Read length\",\n    \"0-0\": \"581b298d20946e087b2ce503\",\n    \"0-1\": \"file1.fastq\",\n    \"0-2\": \"illumina18\",\n    \"0-3\": \"1\",\n    \"0-4\": \"26\",\n    \"1-0\": \"581b298d20946e087b2ce51f\",\n    \"1-1\": \"file2.fastq\",\n    \"1-2\": \"illumina18\",\n    \"1-3\": \"2\",\n    \"1-4\": \"26\",\n    \"2-0\": \"581b298d20946e087b2ce50b\",\n    \"2-1\": \"file3.fastq\",\n    \"2-2\": \"solexa\",\n    \"2-3\": \"1\",\n    \"2-4\": \"98\"\n  },\n  \"cols\": 5,\n  \"rows\": 3\n}\n[/block]\nBelow is the same example in a comma separated format.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"id,name,quality_scale,paired_end,Read length\\n581b298d20946e087b2ce503,file1.fastq,illumina18,1,26\\n581b298d20946e087b2ce503,file2.fastq,illumina18,2,26\\n581b298d20946e087b2ce503,file3.fastq,solexa,1,98\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\nThe following example shows a metadata manifest file which contains the name column, one metadata schema field (case_id) and one custom metadata field (Donor ID). Please note that in this case the name field (containing file path along with the name of the file) will be used to uniquely identify the file within the project.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"name\",\n    \"h-1\": \"case_id\",\n    \"h-2\": \"Donor ID\",\n    \"0-0\": \"StudyYYZ/file1.bam\",\n    \"0-1\": \"cid173\",\n    \"0-2\": \"1197\",\n    \"1-0\": \"StudyYYZ/file2.bam\",\n    \"1-1\": \"cid365\",\n    \"1-2\": \"1198\",\n    \"2-0\": \"StudyYYZ/file3.bam\",\n    \"2-1\": \"cid882\",\n    \"2-2\": \"1199\"\n  },\n  \"cols\": 3,\n  \"rows\": 3\n}\n[/block]\n\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"name,case_id,Donor ID\\nStudyYYZ/file1.bam,cid173,1197\\nStudyXYZ/file2.bam,cid365,1198\\nStudyXYZ/file3.bam,cid882,1199\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]","updates":[],"order":8,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"5cd581b26ea1040056ec1f61","project":"5773dcfc255e820e00e1cd4d","version":{"version":"1.0","version_clean":"1.0.0","codename":"","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["5773dcfc255e820e00e1cd51","5773df36904b0c0e00ef05ff","577baf92451b1e0e006075ac","577bb183b7ee4a0e007c4e8d","577ce77a1cf3cb0e0048e5ea","577d11865fd4de0e00cc3dab","578e62792c3c790e00937597","578f4fd98335ca0e006d5c84","578f5e5c3d04570e00976ebb","57bc35f7531e000e0075d118","57f801b3760f3a1700219ebb","5804d55d1642890f00803623","581c8d55c0dc651900aa9350","589dcf8ba8c63b3b00c3704f","594cebadd8a2f7001b0b53b2","59a562f46a5d8c00238e309a","5a2aa096e25025003c582b58","5a2e79566c771d003ca0acd4","5a3a5166142db90026f24007","5a3a52b5bcc254001c4bf152","5a3a574a2be213002675c6d2","5a3a66bb2be213002675cb73","5a3a6e4854faf60030b63159","5c8a68278e883901341de571","5cb9971e57bf020024523c7b","5cbf1683e2a36d01d5012ecd","5dc15666a4f788004c5fd7d7","5eaff69e844d67003642a020","5eb00899b36ba5002d35b0c1","5eb0172be179b70073dc936e","5eb01b42b36ba5002d35ebba","5eb01f202654a20136813093","5eb918ef149186021c9a76c8","5f0839d3f4b24e005ebbbc29","5f893e508c9862002d0614a9","6024033e2b2f6f004dfe994c","60a7a12f9a06c70052b7c4db","60a7ab97266a4700161507c4","60b0c84babba720010a8b0b5"],"_id":"5773dcfc255e820e00e1cd50","__v":39,"createdAt":"2016-06-29T14:36:44.812Z","releaseDate":"2016-06-29T14:36:44.812Z","project":"5773dcfc255e820e00e1cd4d"},"category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Set metadata associated with a file","slug":"set-metadata-associated-with-a-file","order":7,"from_sync":false,"reference":false,"_id":"5cb9971e57bf020024523c7b","project":"5773dcfc255e820e00e1cd4d","version":"5773dcfc255e820e00e1cd50","createdAt":"2019-04-19T09:38:38.103Z","__v":0},"user":"566590c83889610d0008a253","createdAt":"2019-05-10T13:50:42.059Z","__v":0,"parentDoc":null}

Metadata manifest file format


Two different metadata manifest file formats are used on CAVATICA. Which metadata manifest file you should use depends on the functionality that you're using the manifest for. * [Command Line Uploader ](doc:set-metadata-using-the-command-line-uploader) - use this format of metadata manifest file in order to apply metadata when uploading files to CAVATICA. * [Editing metadata via the visual interface](doc:edit-metadata-using-the-visual-interface) - use this format of the metadata manifest file in order to edit metadata for the files that are already in one of your projects on CAVATICA. ##Metadata manifest format for the Command Line Uploader When uploading files to CAVATICA using the [Command Line Uploader](doc:set-metadata-using-the-command-line-uploader#section-set-metadata-for-multiple-files-using-a-manifest-file), a metadata manifest file can be used to define metadata values for those files. The supported file format for this manifest file is CSV, i.e. comma separated values. A CSV file contains a number of rows with columns which are separated with a comma. The following rules apply: [block:parameters] { "data": { "h-0": "Rule", "h-1": "Description", "0-0": "Line separation", "0-1": "The lines are separated with a line break, while the columns are separated using a comma.", "1-0": "First row", "1-1": "The first row (manifest file header) has to contain column names which are treated as metadata keys (e.g. “sample”, “library”). Within the header, the first column must be `File` name, while the remaining columns are metadata keys. Also, please have in mind that metadata keys might be metadata schema or custom metadata keys.", "2-0": "Must include File name", "2-1": "It's mandatory to have `File` name as the first column in the header.", "3-0": "First column", "3-1": "The first column has to contain the names of the files which will be uploaded. In case the files are not in the same directory as the metadata manifest file, you should also include a path to the files (e.g. `../filename.fastq`).", "4-0": "Subsequent columns", "4-1": "All subsequent columns should contain metadata fields which will be assigned to the specified files.", "5-0": "Case sensitivity", "5-1": "Keys and values are case sensitive.", "6-0": "Escape character", "6-1": "To escape comma character in metadata key or value, enclose that field within double quotation marks (e.g. for setting specific key to md_value1,2 use \"md_value 1,2\"). Furthermore, to use double quote character in metadata key or value, enclose that field within double quotation marks and use two double quotation marks (e.g. for setting specific key to md_value\"1\" use \"md_value\"\"1\"\"\").", "7-0": "Maximum size", "7-1": "The maximum size for the metadata manifest file is 5 GiB.", "8-0": "Maximum number of key-value pairs", "8-1": "Maximum number of key-value pairs per file is 1000, including null-value keys.", "9-0": "Keys and values encoding", "9-1": "Keys and values are UTF-8 encoded strings.", "10-0": "Maximum key length", "10-1": "100 bytes (UTF-8 encoding)", "11-0": "Maximum value length", "11-1": "300 bytes (UTF-8 encoding)", "12-0": "Metadata for files only", "12-1": "There is no metadata for folders on CAVATICA. Any folder specified in the manifest file will be skipped and the metadata will not be set for a folder." }, "cols": 2, "rows": 13 } [/block] The following example shows the content of the metadata manifest for three files with three metadata fields. [block:parameters] { "data": { "h-0": "File name", "h-1": "sample", "h-2": "library", "h-3": "paired_end", "0-0": "file1.fastq", "0-1": "sample1", "0-2": "examplelibrary1", "0-3": "1", "1-0": "file2.fastq", "1-1": "sample1", "1-2": "examplelibrary1", "1-3": "2", "2-0": "file3.fastq", "2-1": "sample2", "2-2": "examplelibrary2", "2-3": "1" }, "cols": 4, "rows": 3 } [/block] Below is the same example in a comma separated format. [block:code] { "codes": [ { "code": "File name,sample,library,paired_end\nfile1.fastq,sample1,examplelibrary1,1\nfile2.fastq,sample1,examplelibrary1,2\nfile3.fastq,sample2,examplelibrary2,1\n", "language": "text" } ] } [/block] ##Metadata manifest format for modifying metadata via the visual interface This manifest file is used In case you are modifying metadata for your project files via the visual interface. The supported file formats for this manifest file are CSV and TSV. A CSV file contains a number of rows with columns which are separated with a comma, while the TSV file separates them with a tab. The following rules apply: [block:parameters] { "data": { "h-0": "Rule", "h-1": "Description", "0-0": "Line separation", "0-1": "The lines are separated with a line break, while the columns are separated using a comma.", "1-0": "Columns separator", "1-1": "The columns are separated using a comma (CSV) or a tab (TSV) while the lines are separated with a line break.", "2-0": "First row", "2-1": "The first row (manifest file header) has to contain column names which are treated as metadata keys (e.g. “sample”, “library”). Within the header, the first column must be either `id` or `name`, Next, there can be project and size columns which are system metadata fields and are treated as read-only (these fields are present if manifest file is generated using Export metadata to a manifest action). The remaining columns are metadata keys, which can be metadata schema or custom metadata keys. Please have in mind that the order of columns is important, e.g. id column (if present) must be the first one.", "3-0": "Must include id or name (along with project path)", "3-1": "1. It’s mandatory to have either id or name column, and it’s allowed to have both of them.\n2. If both id and name columns are present, then id will be used for identifying file, while the name will be omitted.", "4-0": "Name field", "4-1": "This field should also include file path within the project for files which are not in the project root, so it’s actually path + name. If \"id\" column is not present in the metadata manifest file, then this field will be used for identifying files whose metadata should be edited. If \"id\" is present in the metadata manifest file, then this field will be ignored, meaning it's not possible to change file name or file path using \"Import metadata manifest\" feature (situation which is the same as currently, although it might change in the future). This way, it's possible to edit metadata using manifest file without providing file IDs and providing only file names (along with path, in case when files are stored in folder instead of project root) instead of having to fetch file IDs.", "5-0": "Project field", "5-1": "It’s possible to have “project” column (e.g. if you have used the Export metadata manifest feature, then edited generated metadata manifest file and submitted it for import). If present it is treated as read-only field (i.e. it is not possible to either move or copy files from one project to the other using this feature), but validation should take place - if the specified “project” value is different than the current project (i.e. the project in which the Import metadata manifest feature has been used) then this file shouldn’t be edited and it should be counted towards files which are failed as part of this action. Have in mind that the “project” field is non-mandatory field in the manifest file.", "6-0": "Size field", "6-1": "It is possible to have the “size” column (e.g. you have used the Export metadata manifest feature, edited the generated metadata manifest file and submitted it for import). If present, it is treated as read-only field (i.e. it is not possible to change the file size using this feature, or any other feature). In addition, there should not be any validations including this field.", "7-0": "Metadata schema fields and custom metadata fields", "7-1": "Following the aforementioned fields (there can be at a minimum one, and at the maximum four read-only fields) you can specify the metadata fields which should be edited. There must be at least one metadata column specified in the manifest file (otherwise the action will fail because there is no metadata field to be edited). The metadata schema fields are specified according to the documented metadata schema.", "8-0": "Empty rows", "8-1": "It's allowed to have an empty row in the manifest file. Empty row will be skipped during manifest file processing.", "9-0": "Case sensitivity", "9-1": "The manifest file is case-sensitive.", "10-0": "Escape character", "10-1": "To escape comma character in metadata key or value, enclose that field within double quotation marks (e.g. for setting specific key to md_value1,2 use \"md_value 1,2\"). Furthermore, to use double quote character in metadata key or value, enclose that field within double quotation marks and use two double quotation marks (e.g. for setting specific key to md_value\"1\" use \"md_value\"\"1\"\"\").", "11-0": "Maximum size", "11-1": "The maximum size for the metadata manifest file is 5 GiB.", "12-0": "Maximum number of rows", "12-1": "The maximum number of rows for the metadata manifest file is 40,001, which corresponds to maximum number of files in the single project on the Platform (plus header row).", "13-0": "Maximum number of key-value pairs", "13-1": "Maximum number of key-value pairs per file is 1000, including null-value keys.", "14-0": "Keys and values encoding", "14-1": "Keys and values are UTF-8 encoded strings.", "15-0": "Maximum key length", "15-1": "100 bytes (UTF-8 encoding)", "16-0": "Maximum value length", "16-1": "300 bytes (UTF-8 encoding)" }, "cols": 2, "rows": 17 } [/block] [block:callout] { "type": "info", "body": "Columns which are specified after id, name, size and project will be treated as metadata fields." } [/block] The following example shows a metadata manifest file which contains both id and name columns along with one metadata schema field (quality_scale, paired_end) and one custom metadata field (Read length). Please note that in this case the id field will be used to uniquely identify file within the project, while the name field will be ignored. [block:parameters] { "data": { "h-0": "id", "h-1": "name", "h-2": "quality_scale", "h-3": "paired_end", "h-4": "Read length", "0-0": "581b298d20946e087b2ce503", "0-1": "file1.fastq", "0-2": "illumina18", "0-3": "1", "0-4": "26", "1-0": "581b298d20946e087b2ce51f", "1-1": "file2.fastq", "1-2": "illumina18", "1-3": "2", "1-4": "26", "2-0": "581b298d20946e087b2ce50b", "2-1": "file3.fastq", "2-2": "solexa", "2-3": "1", "2-4": "98" }, "cols": 5, "rows": 3 } [/block] Below is the same example in a comma separated format. [block:code] { "codes": [ { "code": "id,name,quality_scale,paired_end,Read length\n581b298d20946e087b2ce503,file1.fastq,illumina18,1,26\n581b298d20946e087b2ce503,file2.fastq,illumina18,2,26\n581b298d20946e087b2ce503,file3.fastq,solexa,1,98", "language": "text" } ] } [/block] The following example shows a metadata manifest file which contains the name column, one metadata schema field (case_id) and one custom metadata field (Donor ID). Please note that in this case the name field (containing file path along with the name of the file) will be used to uniquely identify the file within the project. [block:parameters] { "data": { "h-0": "name", "h-1": "case_id", "h-2": "Donor ID", "0-0": "StudyYYZ/file1.bam", "0-1": "cid173", "0-2": "1197", "1-0": "StudyYYZ/file2.bam", "1-1": "cid365", "1-2": "1198", "2-0": "StudyYYZ/file3.bam", "2-1": "cid882", "2-2": "1199" }, "cols": 3, "rows": 3 } [/block] [block:code] { "codes": [ { "code": "name,case_id,Donor ID\nStudyYYZ/file1.bam,cid173,1197\nStudyXYZ/file2.bam,cid365,1198\nStudyXYZ/file3.bam,cid882,1199", "language": "text" } ] } [/block]