This call changes the metadata values for the specified file.
If you are using Seven Bridges Platform EU, please use the following endpoint:
https://eu-api.sbgenomics.com/v2/files/{file_id}/metadata
Metadata on the Platform
Learn more about metadata fields and their values on the Seven Bridges Platform.
Files are specified by their IDs, which you can obtain by making the API call to list files in a project .
PUT and PATCH
The Seven Bridges Platform API has two method to modify file metadata. This method uses the HTTP verb
PUT
, and the other uses the HTTP verbPATCH
.The 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, aPUT
request will fully overwrite the values for all metadata fields. This means that when issuing aPUT
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 thePUT
request, then any existing value for that field will be reset.
Custom metadata fields
Apart from the standard set of metadata fields that can be seen through the visual interface, you are also able to add custom metadata for your files. Custom metadata fields are user-defined key-value pairs that allow you to provide additional metadata associated to files on the Platform. Custom metadata can be added via the command line uploader or via the API, but not through the visual interface.
The following rules apply to custom metadata fields:
- Keys and values are case sensitive unless explicitly treated differently by a tool or a part of the Platform.
- Maximum number of key-value pairs per file is 1000.
- Keys and values are UTF-8 encoded strings.
- Maximum length of a key is 100 bytes (UTF-8 encoding).
- Maximum length of a value is 300 bytes (UTF-8 encoding).
- Null values and keys are ignored and not counted towards the 1000 key-value pair limit.
Example request body
{
"foo": "bar",
"my_key_1": "my_value_1",
"my_key_2": "my_value_2",
"platform": "my_platform",
"library_id": "12345"
}