Recap of the showcase from sprint #56
Jason Gush
By request (and because the #55 sprint crashed) we reran the showcase showing assertion of complex research resource items via json (or yaml) upload.
As a reminder, ORCID’s model of a research resource is a complex beast:
It’s best thought of as a specialised form of project/proposal(*) having between one and ten proposal hosts(*) and utilizing from one to one hundred research resources(*), and where each resource has from one-to-ten resource hosts(*). Each of the asterisk shows where at least one identifier is required (e.g. proposal-id, grid, ringgold, etc) for ORCID to accept the message as valid.
1/ Fields in bold are required, and 2/ the External ID block is comprised of: external-id-type; external-id-value; external-id-url; and external-id-relationship.
While the Hub has been accepting research resources in csv/tsv format for a few weeks (by imposing the restriction of one each for proposal host, resource, resource host, and the needed identifiers), this was the first demo for asserting the complete research resource model through the upload of the Hub’s formats for complex items.
The rest of the demo (trimmed and cut where I made an error in the model structure, and the waits for ORCID sandbox to load) can be viewed here:
https://drive.google.com/open?id=10ex7YFO1UzGxTwpNyT-6FEHZAYzp1P2n
With the run list:
- 00:00 Uploading Research Resources task as json.
- 03:45 Seeing the result in one of the invitees' records.
- 04:10 Editing the resource message in place via the UI.
- 05:00 Seeing the changed content propagated to ORCID.
- 05:37 Quick run-through of the Hub's API for managing research resource tasks including creation of a new resource task.
- 08:10 Retrieving the newly created task by its task_id with a GET command.
- 08:55 Using the PATCH verb to amend the task, e.g., to set the task's status to active.
- 10:45 Seeing the new content propagated to ORCID.
- 12:00 Showing Hub Admin view of mail logs for troubleshooting.
- 12:50 Wrap up