...
Research objects have a lifecycle that, from a curation and preservation service perspective, begins with a request for the object to be published, proceeds through a series of processing steps that result in status updates, and ends with successful publication, failure at some step, or revocation of the request. A request is made by POSTing to the /cp/researchobjects endpoint. The object sent is a compound JSON-LD object consisting of an object describing the top level item (an ORE Aggregation) to be published, the list of user preferences (i.e. from the staging area), and the repository the request is for. A GET at /cp/researchobjects shows the list of requests, and doing a GET on /cp/researchobjects/<Identifier> will show the full request. Within the full request is a URL from which the OREMap for the Aggregation can be retrieved. The Map includes a list of all subobjects, their metadata, and their relationships in an ORE-compliant JSON-LD structure.
A DELETE to /cp/researchobjects/<Identifier> causes the request to be revoked/deleted .
A PUT to PUT to /cp/researchobjects/<Identifier> can <Identifier>/status can be used to send a Status message to update the request and a request can be revoked/deleted by using DELETE.
A GET to /cp/researchobjects/<Identifier>/status willl retrieve just the status information known about a request.
...