{"_id":"5774eb77e719e01900625a86","version":{"_id":"5773dcfc255e820e00e1cd50","__v":26,"project":"5773dcfc255e820e00e1cd4d","createdAt":"2016-06-29T14:36:44.812Z","releaseDate":"2016-06-29T14:36:44.812Z","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"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"user":"575e85ac41c8ba0e00259a44","__v":4,"githubsync":"","parentDoc":null,"project":"5773dcfc255e820e00e1cd4d","category":{"_id":"5773df36904b0c0e00ef05ff","version":"5773dcfc255e820e00e1cd50","__v":0,"project":"5773dcfc255e820e00e1cd4d","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-06-29T14:46:14.277Z","from_sync":false,"order":12,"slug":"api","title":"Cavatica API"},"metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-06-30T09:50:47.763Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","examples":{"codes":[]},"method":"patch","auth":"required","params":[],"url":""},"isReference":false,"order":41,"body":"This call modifies the metadata values for the specified file. \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Metadata on the Platform\",\n  \"body\": \"Learn more about [metadata fields and their values](metadata-on-the-seven-bridges-platform) on Cavatica.\"\n}\n[/block]\nFiles are specified by their IDs, which you can obtain by making the API call to [list files in a project ](doc:list-files-primary-method).\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"https://cavatica-api.sbgenomics.com/v2/files/{file_id}/metadata\",\n      \"language\": \"text\",\n      \"name\": \"API path\"\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"PUT and PATCH\",\n  \"body\": \"The API has two method to modify file metadata. This method uses the HTTP verb `PATCH`, and the other uses the HTTP verb `PUT`. \\n\\nThe difference between the two concerns the way that they update the information stored about the user. `PATCH` allows you to update just one metadata field. On the other hand, a `PUT` request will fully overwrite the values for all metadata fields. This means that when issuing a `PUT` request you must enter values for every key required to specify the metadata, even if the values for some keys are unchanged. If you don't specify a value for a given metadata field when making the `PUT` request, then any existing value for that field will be reset.\"\n}\n[/block]\n##Request\n\n###Example request\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"PATCH /v2/files/562e449060b274321afb6091/metadata HTTP/1.1\\nHost: cavatica-api.sbgenomics.com\\nX-SBG-Auth-Token: 565357a1e4b09c884b29334a\\n\",\n      \"language\": \"http\",\n      \"name\": null\n    },\n    {\n      \"code\": \"curl --data '{\\\"foo\\\": \\\"bar\\\"}'  -s -H \\\"X-SBG-Auth-Token: 7942f56901534434a054dafc3813bc96\\\" -H \\\"content-type: application/json\\\" -X PATCH \\\"https://cavatica-api.sbgenomics.com/v2/files/5657152ee4b0298dd2cdf724/metadata\\\"\",\n      \"language\": \"curl\",\n      \"name\": \"cURL\"\n    }\n  ],\n  \"sidebar\": true\n}\n[/block]\n###Header Fields\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"`X-SBG-Auth-Token`\\n_required_\",\n    \"0-1\": \"Your Cavatica [authentication token](doc:get-your-authentication-token).\",\n    \"h-2\": \"\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n###Path parameters\n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"`file_id`\",\n    \"h-0\": \"Name\",\n    \"h-1\": \"Description\",\n    \"0-1\": \"The ID of the file whose metadata you want to update.\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n###Query parameters\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Name\",\n    \"h-1\": \"Data type\",\n    \"h-2\": \"Description\",\n    \"0-0\": \"`fields`\",\n    \"0-1\": \"string\",\n    \"0-2\": \"Selector specifying a subset of fields to include in the response.\"\n  },\n  \"cols\": 3,\n  \"rows\": 1\n}\n[/block]\n##Request body\nEnter a dictionary of key-value pairs to the request body. \n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Key\",\n    \"h-1\": \"Datatype of value\",\n    \"h-2\": \"Description of value\",\n    \"0-0\": \"Freeform -- enter any key.\",\n    \"0-1\": \"string\",\n    \"0-2\": \"The value for the corresponding key\"\n  },\n  \"cols\": 3,\n  \"rows\": 1\n}\n[/block]\n###Example request body\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"foo\\\": \\\"bar\\\"\\n}\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n##Response\n\n[See a list of Cavatica-specific response codes that may be contained in the body of the response.](doc:api-status-codes) \n\n###Example response body\nThe response contains the full metadata specification for the file, including the values that you just added with the request.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"library_id\\\": \\\"12345\\\",\\n  \\\"platform\\\": \\\"my_platform\\\",\\n  \\\"foo\\\": \\\"bar\\\",\\n  \\\"my_key_1\\\": \\\"my_value_1\\\",\\n  \\\"my_key_2\\\": \\\"my_value_2\\\"\\n}\",\n      \"language\": \"json\"\n    }\n  ],\n  \"sidebar\": true\n}\n[/block]\n<div align=\"right\"><a href=\"#top\">top</a></div>\n\n<hr>","excerpt":"/files/{file_id}/metadata\n\nFor general information on the API, including formatting, parameters, and pagination, please see the [API Overview](the-api).","slug":"modify-a-files-metadata","type":"endpoint","title":"Modify a file's metadata"}

patchModify a file's metadata

/files/{file_id}/metadata For general information on the API, including formatting, parameters, and pagination, please see the [API Overview](the-api).

This call modifies the metadata values for the specified file. [block:callout] { "type": "warning", "title": "Metadata on the Platform", "body": "Learn more about [metadata fields and their values](metadata-on-the-seven-bridges-platform) on Cavatica." } [/block] Files are specified by their IDs, which you can obtain by making the API call to [list files in a project ](doc:list-files-primary-method). [block:code] { "codes": [ { "code": "https://cavatica-api.sbgenomics.com/v2/files/{file_id}/metadata", "language": "text", "name": "API path" } ] } [/block] [block:callout] { "type": "success", "title": "PUT and PATCH", "body": "The API has two method to modify file metadata. This method uses the HTTP verb `PATCH`, and the other uses the HTTP verb `PUT`. \n\nThe difference between the two concerns the way that they update the information stored about the user. `PATCH` allows you to update just one metadata field. On the other hand, a `PUT` request will fully overwrite the values for all metadata fields. This means that when issuing a `PUT` request you must enter values for every key required to specify the metadata, even if the values for some keys are unchanged. If you don't specify a value for a given metadata field when making the `PUT` request, then any existing value for that field will be reset." } [/block] ##Request ###Example request [block:code] { "codes": [ { "code": "PATCH /v2/files/562e449060b274321afb6091/metadata HTTP/1.1\nHost: cavatica-api.sbgenomics.com\nX-SBG-Auth-Token: 565357a1e4b09c884b29334a\n", "language": "http", "name": null }, { "code": "curl --data '{\"foo\": \"bar\"}' -s -H \"X-SBG-Auth-Token: 7942f56901534434a054dafc3813bc96\" -H \"content-type: application/json\" -X PATCH \"https://cavatica-api.sbgenomics.com/v2/files/5657152ee4b0298dd2cdf724/metadata\"", "language": "curl", "name": "cURL" } ], "sidebar": true } [/block] ###Header Fields [block:parameters] { "data": { "h-0": "Name", "h-1": "Description", "0-0": "`X-SBG-Auth-Token`\n_required_", "0-1": "Your Cavatica [authentication token](doc:get-your-authentication-token).", "h-2": "" }, "cols": 2, "rows": 1 } [/block] ###Path parameters [block:parameters] { "data": { "0-0": "`file_id`", "h-0": "Name", "h-1": "Description", "0-1": "The ID of the file whose metadata you want to update." }, "cols": 2, "rows": 1 } [/block] ###Query parameters [block:parameters] { "data": { "h-0": "Name", "h-1": "Data type", "h-2": "Description", "0-0": "`fields`", "0-1": "string", "0-2": "Selector specifying a subset of fields to include in the response." }, "cols": 3, "rows": 1 } [/block] ##Request body Enter a dictionary of key-value pairs to the request body. [block:parameters] { "data": { "h-0": "Key", "h-1": "Datatype of value", "h-2": "Description of value", "0-0": "Freeform -- enter any key.", "0-1": "string", "0-2": "The value for the corresponding key" }, "cols": 3, "rows": 1 } [/block] ###Example request body [block:code] { "codes": [ { "code": "{\n \"foo\": \"bar\"\n}", "language": "json" } ] } [/block] ##Response [See a list of Cavatica-specific response codes that may be contained in the body of the response.](doc:api-status-codes) ###Example response body The response contains the full metadata specification for the file, including the values that you just added with the request. [block:code] { "codes": [ { "code": "{\n \"library_id\": \"12345\",\n \"platform\": \"my_platform\",\n \"foo\": \"bar\",\n \"my_key_1\": \"my_value_1\",\n \"my_key_2\": \"my_value_2\"\n}", "language": "json" } ], "sidebar": true } [/block] <div align="right"><a href="#top">top</a></div> <hr>