...
Copy the "Identifier" to the end of the URL (e.g. /cp/researchobjects/<Identifier> ) and you'll see the full request. Within this request, click on the link listed as the "@id" of the "Aggregation". This URL will return the full OREMap JSON-LD file for your request. This file can be used by repositories to process the request - it contains a full list of all aggregated objects (Collections and Datasets for v1.5), their metadata, and their relationships (including the collection/dataset hierarchy). These objects are listed with an ORE:similarTo URL pointing at the live objects in the space - in content itself (for 1.5, adding a "/file" to the end of this URL will allow retrieval of the bytes for a given filethis is the restful endpoint to the live binary content for a dataset, which, since only metadata about a dataset can change, is also the content for the version being published).
A repository can find requests for it at /cp/repositories/<orgidentifier>/researchobjects and can again retrieve the full request and OREMap as above. As a repository processes the request, it should add status messages using a PUT to /cp/researchobjects/<Identifier>with a message of the form: { "reporter": "SEAD-CP", "stage": "Receipt Acknowledged", "message": "request recorded and processing will begin"} , replacing the values as appropriate. The status, with a timestamp generated by the service will be added. The full status chain for a request can be seen doing a GET to /cp/researchobjects/<Identifier> /status.
...