sprint 53 demo - summary

[Jill Mellanby]

Sprint 53 showcase:

Sorry for the sound issues everyone, I’m sure this didn’t help with understanding what are complicated processes.

 

To help, these are the main points that we covered in this sprint:

 

The Hub’s API now no longer expires access tokens when a new token is issued.  This allows you to have multiple services/processes calling on the Hub, without them blocking each other.

 

A new feature is being worked on to give the option for all Hub API calls to be asynchronous, e.g., retrieving a user’s ORCID record as json.  With the asynchronous flag set, the Hub API responds with a task id instead of having to wait for ORCID's response.  If your app subsequently gives the task id back to the Hub, the stored ORCID response is returned.  NB this is still a work in progress and more details will come.

 

The Hub is becoming much more tolerant of inputs, and will now accept both lower/hyphenated and upper/underscored versions of ORCID categories, e.g., it should no longer matter whether you give an external identifier type as “PART_OF” or “part-of”.

 

And finally, a nice change which has been rolled out across all task types is the inclusion of the Is-active field as part of invitees.  We’re now respecting this field and if it is set to true in any record in an uploaded task, irrespective of whether it’s a csv file upload or a json api post, the Hub will immediately start processing the task without requiring any further action.