...
That investigations is the entity that creates an automatic DP/DOI
There is no current provision to approve DOI requests
That ROR is used to search for institutes
That the API will be called as part of a script to automatically mint DOIs (not provided)
That the user can only see open datasets that they are allowed to seedata or their own data.
The API can take up to 10 seconds to mint a DOI, due to the calls needed to pythonICAT, and that this is ok.
A set of Investigations / datasets and datafiles are allowed for user-defined DOIs
Request Rules:
At least one Investigations / datasets or data files has to be provided
creator
is mandatory and all its subfields:Code Block "name": "James T Kirk", "givenName": "James", "familyName": "Kirk", "nameType": "Personal", "email": "jtk@starfleet.org",
...
Code Block "affiliation": "Starfleet Academy"
relatedIdentifiers
are optional but each must be unique if providedtitle
anddescription
are mandatoryfull details can be found at /docs
🔒 Authentication
Point 5 above has the following implications:
The user (datagateway) front end must provide a valid user ICAT session token which the API checks is valid. This means that theoretically, it would be possible for a user to create a DOI for guessed Investigation, datasets or datafile entities, as long as they are logged in and have a valid session token.
As there is no direct user authentication in the API, there is no way of knowing exactly who the user is. A user does not have to list themselves as a creator, nor does the API add any users related to the icat entities. This means:
a user could take sole credit for work which involved others
a user could create a doi given a fake name
A new user
doiminter
was created to assign to the DataPublication to