The preservation gateway 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 for asynchronous preservation in a an asynchronous deep archive.
Repository Gateway API
Deposit Object
Destroy Object
Restore Object
...
PUT Object (deposit)
- Purpose: Request preservation a Bag Object from the repository
Request:
PUT /ObjectId HTTP/1.1- Request Body: Compressed Bag
- Request Headers:
- Content-Type
- Response Code:
202 Accepted(on success)
HEAD Object (audit)
- Purpose: Retrieve audit metadata
Request:
GET /ObjectId HTTP/1.1- Request Body: n/a
- Response Code:
200 OK
DELETE Object (destroy)
- Purpose: Request removal of a Bag Object and all its contents
Request:
DELETE /ObjectId HTTP/1.1- Request Body: n/a
- Response Code:
204
POST Object Restore
- Purpose: Request restore of a Bag Object and all its contents for later retrieval
Request:
Post /ObjectId?restore HTTP/1.1- Request Body: n/a
- Response Code:
202 Accepted(if the object is not already restored)200 OK(if the object is already restored and available for retrieval)
GET Object (retrieve)
- Purpose: Retrieve a restored object
Request:
GET /ObjectId HTTP/1.1- Request Body: n/a
- Response Code:
200 OK(if the object is restored available)403 Forbidden(if the object has not been restored)
Authentication
Repository Client Authorization
...