ORCID FAQs

Why are there two fees to join the Australian ORCID Consortium, but only one fee if you join ORCID directly?

The Australian ORCID Consortium provides cheaper ORCID licensing fees as well as local technical support and consultation services. Hence there are two fees:

  • CONSORTIUM MEMBER FEE: Which is collected in US dollars and paid directly to ORCID for the licenses and use of ORCID registry.
  • CONSORTIUM LEADER FEE: Which is an administrative fee charged by the consortium to help manage the consortium, provide personalised local level 1 and level 2 technical support as well as consultations for consortium members. This fee is charged in AUD and is cost recovered in nature.

Joining ORCID directly means organisations will only pay one fee, however that fee is quite high compared to paying the consortium fees. Also, organisations may not have access to the local technical support with knowledge of ORCID within the Australian Research sector.

What benefits does my organisation get from joining the consortium?

Joining the consortium means that your organisation is an ORCID member and includes all the benefits a premium ORCID member gets, plus access to local technical support as well as the chance to be a part of the community. The benefits include but are not limited to

  • 5 member APIs to integrate 5 systems with the ORCID registry
  • update notification via member API using webhooks
  • ability to add/update/delete information from ORCID records (provided initial consent is obtained)
  • personalised local technical support, consultations as well as integrated application user acceptance testing.

Where can I get the ORCID Outreach Resources?

The best place to get up to date and most recent ORCID outreach resources is at ORCID communications and outreach.

Where do I go to get technical information about the ORCID API?

Technical information about the ORCID API can be found in the following places:

If your organisation is an Australian ORCID Consortium member and you have questions on ORCID, you can direct them to [email protected].

Using statistics from ORCID integration in reporting

Staff at organisations that have implemented an ORCID integration can obtain insights into how ORCID is being used at the institution. For example:

  • Number of researchers that have connected their ORCID ID using the ORCID integration
  • Number of ORCID records that have been updated
  • A timeline of ORCID IDs connected over time.

Organisations can gain a high-level overview of how their ORCID integration is performing and demonstrate the value of their ORCID integration.

If your organisation is an ORCID consortium member, you will have access to the ORCID Member Portal – Reporting Dashboard tool which will provide you with customised reports to your ORCID integration. ORCID have detailed more information on how to use the Reporting Dashboard here.

If you are a member of the Australian ORCID Consortium and have questions regarding the ORCID Member portal – Reporting Dashboard, please reach out to us on [email protected]

Upgrading to ORCID APi v3.0

ORCID released v3.0 of the ORCID API in May 2019. This is a major release of the ORCID API and several new sections like research resources can be added to the ORCID record via API v3.0.

Why should I upgrade to API v3.0?

If ORCID integrations are using previous versions of the ORCID API, they will no longer receive data, that cannot be modelled in that version of the API.  For example: The introduction of the CREDIT contributor role taxonomy into the v3.0 API.  Once live, v2.x integrations will slowly lose visibility of contributor roles as more and more researchers and integrations adopt CREDIT.  v2.x users wont break, but they will receive less rich metadata as time passes.

API v3.0 also has a new expanded “affiliation type” section, the ability to add “research resources” as well as newer work types. For more information on API v3.0 please refer to the ORCID website.

Displaying the ORCID Member Badge

The full ORCID Logo should not be changed or altered in anyways. ORCID have a special member logo for ORCID Members to indicate their membership status with ORCID. Using the ORCID logo according to ORCID’s usage policy along with the ORCID Member Logo allows for researchers to experience a seamless user-experience with the look and feel of an organisations ORCID page, irrespective of their organisation.

When researchers move between organisations, they will find the familiarity and user-experience of the ORCID page easy to navigate, making the transition of moving their research outputs between organisations easier.

If you are an Australian ORCID Consortium member and do not have the necessary ORCID Member logo, send us an email to [email protected] . If you are an ORCID member who requires the ORCID Member logo, please send an email to [email protected].
https://aaf.edu.au/orcid/faq/
aaf.edu.au
crawl=CC-MAIN-2022-40
85332
application/http; msgtype=response
sha1:I7SKTHUSFXDS6C5LVOV6BCPLYIGPQYXD
<urn:uuid:c2bd245d-2791-4fb5-9ad2-8f6ab6eebcb0>
2022-09-25T12:09:18Z
141.193.213.20
text/html
sha1:GZQDQUSY4PXAY7XKMLURCMYJNR6VVF4W
<urn:uuid:5a0bc990-8097-4f0b-8945-7790143064f6>
https://aaf.edu.au/orcid/faq/
response
<urn:uuid:5fee1b68-9c86-48be-865d-fe76141d514a>
isPartOf: CC-MAIN-2022-40
publisher: Common Crawl
description: Wide crawl of the web for September/October 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-215
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/