- Getting Support
- Specific System Help
- Collect and Connect
- Making the business case
Where do I place my order?
How much would my institution pay?
Fees are Jisc banded. The current agreement runs until December 2018. The following prices are per calendar year in US Dollars:
- Jisc bands 1, 2 and 3 pay $3,500 per annum
- Bands 4, 5A & 5B pay $2,500 per annum
- Bands 6, 7, 8, 9 and 10 pay $1,500 per annum
Pro-rating of fees does not apply.
Are the fees fixed?
Yes. The fees shown above are those that will apply until December 2018. During 2018 Jisc will set the renewal fees for 2019 onwards.
Is there a discount if we pay for three years?
No. There is no discount available for paying all three years up front.
Are there any other charges besides the fees?
No further fees are due to Jisc for participating in the consortium.
Where can I view the licence?
You can view the licence here and sign electronically when placing your order.
Who should I contact if I have a question about my membership?
Please contact email@example.com who will cascade your query as appropriate.
What are the advantages of consortium membership through Jisc compared to the institution signing up individually?
- Access to full features of premium ORCID membership at heavily reduced prices
- Premium member APIs
- The use of ORCID integration across multiple enterprise systems
- Access to on-boarding webinars, online resources, technical documentation and training materials
- The use of ORCID in vendor-hosted systems as well as separate internal systems
- Notifications from ORCID when information is updated in an ORCID record connected to the organisation
- Unlimited integrated user acceptance testing in preparation for launches and releases for different enterprise systems
Based on: https://aaf.edu.au/media/2016/02/ORCID_WS_pre_v2_20151008.pdf (page 6).
Do I have premium membership?
All members who join ORCID through the Jisc UK consortium agreement acquire premium membership which is the highest level of membership available.
What are the advantages of a consortium model of membership?
- More cost effective together than alone
- Co-ordinated approach to implementation
- Strategic value in developing a community of practice
- Wide adoption to maximize benefits
- Build sustainability, long term commitment and investment
Based on: https://aaf.edu.au/media/2016/02/ORCID_WS_pre_v2_20151008.pdf (page 5).
Not much research is conducted at my institution. Should I join the UK ORCID consortium?
Membership of the UK ORCID Premium Consortium is relevant to:
- Organizations that will be integrating ORCID iDs in multiple systems
- Organizations that will be using ORCID iDs in vendor-hosted systems and separate internal systems
- Organizations that have high data needs, or require frequent data dumps
- Organizations interested in analytics of the interactions between their systems and ORCID
- Organizations that will interact with a relatively large number of researchers per month
- Organizations interested in enabling data synchronization between ORCID data and their own.
Institutions will also have access to the UK Support network which provides technical advice, webinars and hack days. If there are not many researchers within your institution this level of automation may not be required. It could be that just encouraging your researchers to register themselves for a free of charge ORCID is sufficient. I would refer you to ORCID’s website for further details about what individuals can get for free compared with membership. Also, the Jisc catalogue page provides information on the steps needed to complete your integration. If you do not have integration-ready vendor systems, or the technical skills and resources to develop your own integrations, it is unlikely that you will be able to take advantage of the full benefits of membership. You should consider whether you can achieve your aims using the public API. Please contact the helpdesk if you wish to discuss further.
Which contacts are required and why?
Contacts are required both by the Jisc support service and ORCID to represent the consortium member (the institution) and act on their behalf. There are different roles and types of communication. The three main contacts types are:
- Main contact
- Technical contact
- Subscription contact
Different people may need to be named for each role. The appropriate person may depend on your institution, how different support services are set up, and which services are contributing to ORCID implementation. Contacts can come from the library, research office or IT, for example. The following questions and answers are intended to explain what the contacts are used for, to help you choose the right person.
What is the role of the main contact?
A named contact is required as the key person who is able to handle and act on communications regarding ORCID at your institution and who can be relied on to respond. The main contact represents the consortium member (the institution) in matters relating to licensing responsibilities and membership privileges (like voting) and is able to act on behalf of the consortium member.
The main contact will receive official correspondence from ORCID and Jisc. This includes the monthly newsletter from ORCID (containing links to the institution’s statistics); any important announcements from ORCID e.g. relating to security or service issues; event invitations from Jisc; notifications of any new initiatives or service changes from both Jisc and ORCID.
In particular, the main contact will receive communication from ORCID for the purposes of voting rights associated with the institutional membership of ORCID. Although the voting contact is usually the main contact they can actually delegate this responsibility to another named contact if they wish to do so.
The main contact needs to be able to handle all questions regarding progress of ORCID implementation at your institution (either by answering directly, or by referring the query on). They need to be able to report which institutional systems are connecting to the ORCID API and the types of transactions allowed in the institution. They may be responsible for advocacy of ORCID to other staff, for business planning around ORCID, or reporting on ORCID use internally or to external bodies. They will be asked to engage with ORCID and Jisc regarding any initiatives (such as Collect and Connect) or any evaluation processes (e.g. surveys).
Types of communication that the main contact will receive:
- Monthly ORCID newsletter
- Emails from ORCID about voting
- Emails from Jisc about events run by Jisc for the consortium
- Requests or information on any new initiatives
- Information on onboarding on becoming a member
Example job titles for those who take on the role of main contact:
Research Data Manager, Content Delivery Manager, Head of Library Research Services, Library Digital Service Manager, Research Support Librarian, Library Systems Manager, Open Access & Research Repository Specialist, Senior Policy Advisor, Research & Innovation, Research Information Manager, Head of Scholarly Communications Management, Research Asset Management Project Lead, Head of Research Performance, Impact & Integrity
What is the role of the technical contact?
When an organisation joins ORCID, they build an integration to use the ORCID API, or connect using a vendor system (like a CRIS). To access the API, credentials are needed (an ID and ‘secret’/password). The technical contact will be in charge of requesting the credentials, managing the API keys for applications and describing the integration, as well as acting as main contact for any technical queries from ORCID. For example, they would be contacted about any downtime, changes to the API, suspicious activity or unusual patterns of activity if detected, etc.
The right technical contact will depend on the institutional set-up and infrastructure.
For institutions that are using the CRIS or repository to connect to ORCID, the person who has responsibility for those systems is sometimes named as the technical contact. Alternatively, institutions building a home-grown integration usually name the developer who is developing the integration. In both these cases it could instead be a senior person or IT manager who oversees the various IT systems who takes on the role.
The technical contact will be subscribed to the ORCID newsletter. It is strongly recommended that technical contacts should also subscribe to the ORCID-API users group, where announcements about changes and planned upgrades to the API are made and where assistance from others using the API can be requested. The main point of contact for any technical queries for members of the Jisc UK ORCID consortium should always be the Jisc helpdesk firstname.lastname@example.org as a starting point, and queries will be escalated as needed.
Example communications to technical contacts:
- Advance notice of changes or upgrades to the API
- Requests for information on the type and version of systems connecting to ORCID
- Any queries about credentials
What is the role of the subscription contact?
This is the person with access to the Jisc Collections ordering system. They will be the one to initiate the order, process payments and deal with invoices.
As the subscription is annual, the payment will need to be processed once a year, unless the institution chooses to pay upfront for the remainder of the agreement period. The ORCID membership commences once the order is completed.
The subscription contact therefore enables the membership to commence at the outset but then hands over to the main contact. They will be contacted by the Jisc support service on completion of the order and asked for the main contact details for ORCID at the institution. It is important that the subscription contact hands over promptly to the main contact who can handle further communications and actions that are needed. Some requirements and actions are part of the licence agreement, therefore there is an obligation to work with Jisc support to complete this step efficiently. The subscription contact will be added by ORCID as their invoicing contact.
Can we have additional contacts?
Additional contacts can be added on request as secondary contacts; they can also receive the ORCID newsletter (please state this specifically). Institutions occasionally choose to add an internal mailing list for a group who are jointly responsible for a system or process.
How do we inform Jisc and ORCID of the institutional contacts?
Once the order for membership through Jisc Collections is completed, the person who has placed the order will be contacted by Jisc support with a request for the named main contact. The named contact then receives a list of steps for new members. This includes a link to a survey form, where the technical contact can be added.
How do we keep our contacts updated?
Staff move jobs, change roles, or take leave; we would greatly appreciate it if you could notify us when these changes happen. This is in order to be able to communicate with the correct persons and avoid breaks in communications with your institution; otherwise your institution could miss out on important notifications. Please email the Jisc support desk email@example.com to let us know of any changes.
How are contacts shared?
Contacts are shared with ORCID through a private spreadsheet. ORCID then displays a list of member organisations on their web pages with a contact named on the individual institution’s page. For an example of how this requested information will appear on the ORCID website, refer to the entry for UCL.
The information to be displayed by ORCID is completed by the institution through the survey monkey link sent to the main contact on subscribing.
In the UK there is also a public spreadsheet facilitated by Jisc support and maintained by the community to help identify peers who are at a similar stage of development or identify those using the same institutional systems, to facilitate peer support and communication. The inclusion of an email address in this spreadsheet is optional, and you can choose which email address to add based on convenience.
We are still very early in our planning stages, and don’t have a technical contact to name. What do we do?
For some institutions that are still developing their ORCID strategy and where there is no obvious person yet to take on the role of technical contact, the JISC UK ORCID support co-ordinator has agreed to assist the main contact with answering any technical questions and communications and explaining them, until the institution determines that there is someone else more suitable for the role. Until such time as the institution requests credentials and starts to use them in an integration (home-grown or vendor), the technical contact is not critical.
I don’t know who the main and technical contacts for our institution are. What do I do?
Please email the Jisc support desk firstname.lastname@example.org
Who should I contact if I have a question about technical implementation?
Please contact the dedicated Jisc support desk in the first instance at email@example.com who will cascade your query as appropriate.
Once I place my order what are the next steps?
Before production credentials can be sent institutions will need to Register a client application: Production Member API – Trusted Party with the required information. Before production credentials are issued, Institutions will be asked to provide a demo of their integration. Items the ORCID team will be looking for in the demo are described at Member credential check list. ORCID will process the request right away. Note: This process is not fully automated – there may be a delay before ORCID respond to you with credentials or a demo request after you complete this form. The work-flow is described below.
At any point during the following process, Institutions building their own integration start work on the ORCID sandbox (see registering for sandbox credentials).
- Institution places order via the Jisc Collections’ catalogue pages .
- Institution provides additional confirmation of ORCID’s use of their name and logos as outlined on the following BOS survey link.
- Institutions who have built their own integration with ORCID set up a demo with ORCID team. It should be noted that additional contingency time should be allowed in the case of adjustments or bug fixes being required. NB this step can be skipped for institutions using a vendor provided system.
- Institutions apply for production credentials from ORCID.
- ORCID returns production credentials to be used in the Institution’s integration.
- Institution advises ORCID when they officially launch the integration. ORCID can assist with publicity if required.
How do I find members of my organisation who are already signed up to ORCID?
Institutions often would like to find out the researchers from their institution who already possess an ORCID ID. One of the reasons is to return ORCID IDs with HESA returns. Another reason is to target advocacy efforts. You can watch a recording made at one of our events where colleagues from UK universities discuss their information needs. Those institutions who are inviting their staff to connect to ORCID through systems like a CRIS would like to find out about the staff members who have an ORCID ID but have not yet made the connection through the CRIS.
This question is one of the top features requested from ORCID in their ideas forum. ORCID provides an answer in their knowledge base with two main methods to help you get an answer. First, there are suggestions for how to search the API, and second, ORCID provides a form to request the total number of users registered with an institutional email address. Do vote for this idea in the ideas forum if you would like to see the feature prioritised. Member institutions also receive monthly statistics and reports, which are accessed through the links in the monthly newsletter from ORCID. See next FAQ: What reports does ORCID provide on statistics of users from my institution signed up to ORCID?
What reports does ORCID provide on statistics of users from my institution signed up to ORCID?
ORCID made the following announcement in their newsletter of October 2016:
“New feature for premium integrators — email stats! We are pleased to announce a new feature in your premium member reports: email stats! Beginning this month, premium members with live integrations will find these new report sections:
- Records registered to your email domain(s)
Count of unique ORCID iDs that include an address within your institution’s email domain(s)
- Records registered to your email domain(s) AND associated with your client IDCount of unique ORCID iDs which include an address within your institution’s email domain(s) and which include your institution as a Trusted Party (i.e. records for which your institution has a valid access token)
How do we determine your email domains?
We don’t have a crystal ball that lets us know about all members’ email domains, so we’re starting out by including domains that match the website URL that we have on file for your organization. For example, if your website URL is www.universitycollege.edu, we’re searching emails such as firstname.lastname@example.org.
If we don’t have a website URL on file, you’ll see “No email domains provided” in the email count section.
If we didn’t get your email domain quite right, or if you’d like to add additional domains, let us know at email@example.com.”
For those that do not have a system integration with ORCID, statistics were added to the ORCID monthly report from December 2016. Premium members without live integrations receive a truncated premium member report which includes:
- Records registered to your email domain(s)
Count of unique ORCID iDs that include an address within your institution’s email domain(s)
- A link to the monthly general premium report, which reports analytics for all active member integrations
- Information on how to get started with building and testing your integration
For more details, see the ORCID documentation reading your premium member report.
If you have any questions regarding the recipients of the monthly newsletter, with links to your reports, at your institution, or require any further help, please do get in touch with the UK helpdesk firstname.lastname@example.org
What export formats can I get from ORCID? Is RIS supported for citations?
Links from ORCID:
- Citation format
- Record Export format
- Add support for RIS formatted citations (in ideas forum) – Do vote for this idea by following this third link if you would like to see the feature implemented.
What can you tell me about the move to 2.0 API (2017-2018)?
Check out the dedicated page Guidance on moving to 2.0 API.
Where do ORCID IDs appear in Crossref metadata?
The Crossref documentation describes how ORCID IDs appear in person metadata. In particular note that it is possible to use an attribute to indicate that the ORCID ID has been authenticated
<person_name sequence="first" contributor_role="author">
Can I share my experiences or ask questions of other institutions who are implementing ORCID?
Yes, there is a mailing list to share experiences and discuss best practice in the UK: ORCID-UK@JISCMAIL.AC.UK. Please sign yourself up.
Are there other institutions implementing a system like mine (e.g. eprints/CRIS)?
There is a spreadsheet showing the different systems that institutions are integrating with ORCID. If your own details need to be updated, please add comments with the correct information and the spreadsheet will be updated centrally by Jisc support staff. You can also contact the Jisc support desk email@example.com if you would like help facilitating a conversation with an institution on that list or any further information on stage of implementation.
What events are planned?
Please see the events page on this website. Events are also announced on the ORCID-UK Jiscmail list.
What other support is available?
Please see the support page on this website for a full list of support options.
Collect and Connect
What is the Collect and Connect initiative?
Collect and Connect is an initiative from ORCID that describes the types of interactions that a user can complete using integrations developed using the ORCID API. It provides a framework for institutions building integrations or using vendor systems that connect with ORCID. The underlying thread of the initiative is to improve communication.
Collect and connect provides badges to describe the capabilities that are available in a system integration – capabilities are cumulative (one level builds on the previous one) and are named authenticate, collect, display, connect and synchronise.
A key emphasis is placed on communicating with end users about their interactions with ORCID and what they are able to do with the institutional system, and why. Therefore to earn the badge, it is required not only to implement the capability and interactions that go with that badge; clear explanations must be provided to users alongside the implementation.
Where can I find out more about Collect and Connect?
See the overview on the ORCID website
This recorded presentation from ORCID is under 6 minutes long, and provides a comprehensive overview, whilst key messages about Collect and Connect are reiterated in the blog post which also links to resources.
Pages intended specifically for research organisations which go into more details about the badges and the requirements are also available.
How do I collect the badges for my institution?
Jisc will contact consortium members individually with information about the badges that your integration qualifies for, and suggesting other steps to qualify for the next badges. ORCID will then email you with the badges awarded. If you would like more information about Connect and Collect, and would like to understand how to qualify for badges please do email the Jisc help desk firstname.lastname@example.org, with ‘ORCID Collect and Connect’ in the subject title.
Specific system help
Where can I find the eprints plugin?
Information about eprints plugins is available on the eprints wiki page.
What does the eprints plugin do?
Details about eprints capabilities are described on our eprints page.
How much time and effort will be needed to integrate eprints?
The community has been working together towards a plugin for eprints that takes advantage of ORCID member benefits. For example see the blog post on this site regarding eprints. Until a plug and play solution becomes available, a solution for eprints requires technical knowledge to adapt, implement and maintain some of the open source software that has been made available. See the eprints wiki for approaches and suggestions made by others in the eprints community. Please be aware that until a community agreed solution becomes available, home-grown solutions will not be guaranteed to be compatible with future versions of community solutions that develop.
What web pages will I need to provide?
Where can I find examples of materials that I can use to promote ORCID to researchers?
- ORCID 5 minute introduction for researchers (video)
- ORCID outreach resources page
- PHD Comics The most important decision
- University of Kent advocacy toolkit
- Blog post from University of Reading on running a competition (includes interview with researcher)
- Customised mug idea from University of York
- Open University Blog post on keeping your ORCID record up to date
More resources provided by the community will be added.
Making the business case
What are the benefits of ORCID membership for the institution?
Our business case toolkit outlines the benefits of ORCID for researchers and institutions, and can help you present the benefits of ORCID adoption to key decision makers in your institution.
We don’t have systems that support ORCID or resource to implement them and are not sure if membership is right for us at this stage. How do we support ORCID at our institution?
Where else can people use their ORCID IDs?
Lots of places: On business cards, letter heads, email signatures, (don’t forget to update your corporate standards for all of these!), personal web pages, LinkedIn profiles, and on Wikipedia.
How can ORCID IDs be used on Wikipedia?
Here’s how: You probably have colleagues who are the subject of Wikipedia articles, and certainly some who edit Wikipedia. Their ORCID IDs can be included on the articles about them, or on their user pages. See the Wikipedia guidance for how to do this.