Create a deposit to update an RO-Crate
POST/ro-crate/:id/deposits
Optional core — provided when deposit.supported is true. See the Deposits guide.
Open a deposit session against an existing RO-Crate. The deposit starts logically empty; the client stages a new metadata document plus only the files that changed. At finalise the new metadata document is the authoritative file manifest — unchanged files are carried forward from the baseline by @id, and files absent from the new metadata document drop out. A metadata-only fix is therefore just PUT /deposit/{id}/metadata followed by finalise.
The baseline for carry-forward is the RO-Crate's current version at the moment this deposit is created. Concurrent open deposits against one RO-Crate are allowed; each finalise replaces the RO-Crate wholesale, so the last finalise wins as a unit.
Request
Responses
- 201
- 401
- 403
- 404
- 410
- 429
- 500
Deposit created
Response Headers
The URL of the created deposit
Not authenticated
Access token does not have the required scope
RO-Crate not found
Gone - the resource has been deleted. Returned in place of 404 when the implementation declares a tombstonePolicy of "410"; the body is a tombstone describing the deletion. Under a tombstonePolicy of "404", deleted resources return 404 instead.
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