When the optional Content-MD5 header is included, the final checksum of the stored file is compared against the MD5 value included in the header to ensure that the file was stored correctly. If the header is not included, an MD5 checksum is computed as the file is transferred to storage, and that value is used in the final comparison.
All properties to be set must be included as a request header with the prefix "x-dura-meta-". Any header using the "x-dura-meta-" prefix will be stored as a content property, with a few exceptions, which are used for specific other purposes:
Headers used as part of the Set Space ACLs call (the * is replaced by the user or group name)
Code Block
x-dura-meta-acl-*
x-dura-meta-acl-group-*
Headers used internal to DuraCloud
Code Block
x-dura-meta-content-mimetype (set Content-Type header instead)
x-dura-meta-content-size (automatically written as Content-Length header)
x-dura-meta-content-checksum (automatically written as Content-MD5 header)
x-dura-meta-content-modified (automatically written as Last-Modified header)
Headers used by the DuraCloud SyncTool to automatically capture file details
The properties associated with the source content item are copied to the destination content item.
The source and destination spaces may be the same.
Including the optional header indicates that the copy action should retrieve the source file from a space in the specified storage provider. This allows for copying a file from one storage provider to another.
Set Content Properties
Purpose: Updates the properties associated with a piece of content. Note: You must include ALL properties you would like associated with the given content item in this call. Any properties that exist before this call but are not included in the call itself will be removed. This is to allow for both adding and removing properties.