Import Invalid

import invalid

(javadoc)

Discovers new invalid works (that do not pass the PTCRISync quality criteria) in an ORCID profile given a set of known local CRIS productions, as well as the causes for invalidity (which are defined here). Other than the criteria, the behavior is similar to that of the import works procedure. Note that currently group merging simply collects the meta-data (other than the external identifiers) from the work selected as preferred by the user, which is used in the quality assessment.

Requires

• The procedure expects the CRIS service to provide the local productions in the ORCID schema, in particular encoding productions as works. Since only the external identifiers of the local productions are used to search for ORCID matches, the remainder meta-data of the input local productions could be left null.

• The put-code of these local productions is expected to be used as local key identifiers, but these are actually disregarded by this procedure since the newly found works will not refer to any of the existing local productions.

Ensures

• The procedure returns every work group, merged as a single group, whose external identifiers do not match any of the input local productions.

• The merging algorithm collects the external identifiers of every grouped work, and the meta-data of the work of that group selected as preferred by the user.

• Only works that fail the PTCRISync quality criteria are returned by the procedure.

• Since the put-code attribute is used as a local key of each work, it is null for the returned works (and not the put-code of the remote ORCID works that gave origin to it).

Performance

This procedure performs a GET call to the API to obtain the summaries and an additional GET call for each work identified as invalid. The procedure only fails if the initial GET fails. Asynchronous workers are used for getting the full works.