New Affiliation Manager Tool

[Rob Blackburn]

We are proud to announce the imminent arrival of the first of a new set of tools for ORCID Members, The Affiliation Manager. Conceived of as a way for consortia members to quickly add affiliation information to ORCID records, the Affiliation Manager will be launched as official beta on May 4th 2021. As a point of interest for API user group members, reading records with affiliations posted by an Affiliation Manager client with the 3.0 API will look different than regular clients because they show the origin and the source that pushes the assertion. Affiliations read by 2.0/2.1 API however will not show the assertion-origin even if the affiliation was pushed by the Affiliation Manager. This is because this functionality was introduced in the 3.0 API.

For further clarification please see the following examples:

1. Single employment item asserted by a standard API client and read with 3.0 API

Here you see only <common:source-client-id> and <common:source-name> because there is only one source

2. Single employment item asserted by the  Affiliation Manager and Read with 3.0 API

Here you see the <common:source-client-id>,  <common:source-name> as well as <common:assertion-origin-client-id> and <common:assertion-origin-name> because it is pushed by the source on behalf of the origin.

And for comparison:

3. Single employment item asserted by a standard API client and read with the 2.1 API

Here there is only <common:source-client-id>,  <common:source-name> .

4. Single employment item asserted by the Affiliation Manager and read with the 2.1 API

Here even though it was pushed by the Affiliation Manager it does not show the <common:assertion-origin-client-id> and <common:assertion-origin-name> because it was read by the 2.1 API which does not support it. 

 

As you can see the assertion origin is only shown in 3.0 API and only when asserted by the Affiliation Manager.