Import Updates

import updates

(javadoc)

Discovers updates to existing local CRIS productions in an ORCID profile.

Each returned work results from a work group at ORCID (merged into as a single work) whose external identifiers match a local productions but that introduces new external identifiers not known locally, referring to the local production that is to be updated. To import works without shared external identifiers, the import works procedure should be used instead.

These works contain only the meta-data that needs to be updated locally. Currently, only the introduction of newly found external identifiers is considered (i.e., those that were already present in the local productions that is being updated are removed from the returned updates).

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, since the found updates must refer to the existing local production that must be updated.

Ensures

• The procedure returns every work group, merged as a single group, whose external identifiers match an input local production and contains additional unknown external identifiers.

• The returned works assign to a matching local production the fields which need be updated. Currently, only newly found external identifiers are returned, the remainder meta-data fields being set to null.

• Since only external identifiers are being collected from the ORCID works, the quality criteria is not enforced on remote ORCID works.

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

Performance

This procedure simply performs a GET call to the API to obtain the summaries, since the remainder meta-data is irrelevant.