The preservation Gateway functions as an aggregating cache for preservation requests originating with a repository and destined for a DDP via the OTM Bridge. This allows repositories to synchronously send content preservation in an asynchronous deep archive.
Create a gateway object for preservation of a Bag Object from the repository
Request: PUT /ObjectId HTTP/1.1
Content-TypeResponse Code: 201 Created (on success)
Holy Bags? For large file deposit. - i don't want to push this content over the network and/or - i don't want to store it on a Gateway accessible disk |
Bag profiles? |
Write up something about ObjectID semantics and repository reconstruction. |
Retrieve audit metadata for the object.
Request: GET /ObjectId/audit HTTP/1.1
200 OKResponse Body:
{
ddp_name: {
preserved: true
destroy_requested: true
}
} |
Request removal of a Bag Object and all its contents
Request: DELETE /ObjectId HTTP/1.1
204 No Content
Request restore of a Bag Object and all its contents for later retrieval
Request: POST /ObjectId?restore HTTP/1.1
202 Accepted (if the object is not already restored)200 OK (if the object is already restored and available for retrieval)Can HTTP Range requests be used to retrieve individual files (e.g. metadata) |
Retrieve a restored object.
Request: GET /ObjectId HTTP/1.1
200 OK (if the object is restored available)403 Forbidden (if the object has not been restored)
Can HTTP Range requests be used to retrieve individual files (e.g. metadata) |