Stage the metadata document
PUT/deposit/:id/metadata
Optional core — provided when deposit.supported is true. See the Deposits guide.
Stage the RO-Crate metadata document for this deposit. This is a full replace — staging a new metadata document discards the previously staged one; there is no metadata PATCH and no metadata DELETE. The metadata document and files may be staged in any order; metadata–file association is checked at finalise.
At finalise the staged metadata document becomes the RO-Crate's authoritative file manifest: each file entity in the metadata document resolves to bytes staged in this deposit, else (for update deposits) to the file carried forward by @id from the baseline version, else remains an unresolved reference. Unresolved references are not protocol errors — they simply 404 when followed — but implementations MAY reject them at finalise via validation. Files present in the baseline but absent from the new metadata document drop out of the new version.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 409
- 429
- 500
Metadata document staged
Bad Request - the body is not a JSON-LD document
Not authenticated
Access token does not have the required scope
Deposit not found - unknown, or expired and cleaned up
Conflict - the deposit is not in the open state
Rate limit exceeded
Response Headers
Request limit per time window
Requests remaining in current time window
Unix timestamp when the rate limit resets
Number of seconds to wait before retrying
Internal Server Error