Find out what the responsibilities are of Consortia and ORCID after signing the agreement
The process of forming a new consortium requires considerable commitment and effort, but don’t worry; we are here to work with you every step of the way. If your organization already collaborates with other organizations on research infrastructure and scholarly communications topics and has a general perspective of what they can do, you may be a good candidate to form a consortium.
This document outlines the expectation, roles, and responsibilities of both the Consortium Lead Organization and ORCID after the Consortium Agreement is signed. Be sure to visit our other pages, Building a Successful Consortium, and Onboarding Checklist, for more information.
For the Consortium Lead Organization
| Alignment with ORCID Strategy | – Understand and commit to ORCID’s Vision and Mission |
| Communicate with ORCID | – Participate in regularly scheduled calls with your assigned ORCID Engagement Lead, providing ample advance notice of any schedule changes or necessary cancellation. – Respond to communiques from ORCID within three (3) business days. |
| Provide administrative support for the consortium | – Manage the ORCID licensing agreement and annual renewal on behalf of the consortium members – Manage annual billing cycle for consortium membership fees and licensing fees (Member Fee) – Provide accurate contact information to ORCID for each consortium member —including voting contacts for ORCID annual Board elections—and proactively ensure that ORCID has new information as it changes – Provide regular updates to ORCID about activities such as consortium governance, consortium member activities, and other activities as needed by your particular consortium |
| Actively grow the consortium in alignment with objectives | – Promote the value of ORCID, the consortium, and integrations by – Developing collateral and resources – Coordinating activities and events for the national or regional community – Conduct marketing campaigns to drive consortium targets and objectives – Other activities as appropriate |
| Manage and support the on-boarding of new consortium members | Act as the primary contact between ORCID and the members for all membership enquiries – Manage consortium membership process as outlined in the consortium license agreement – Provide relevant resources to assist new members |
| Provide central community support for all consortium members | Catalyze ORCID adoption among consortium members, ensuring that they understand the value of ORCID to their organizations and how to make the most of ORCID tools and services – Engage with members collectively and individually to understand, help prioritize, and support their integration plans – Provide an online support process for consortium members, including: — Availability during local working hours Monday—Friday — Providing resolution of basic (Tier 1) technical support incidents, such as errors described in the documentation, information about service providers, or guidance in the understanding of ORCID tools and functionalities — Managing the escalation of Tier 2 and 3 support incidents to ORCID’s dedicated Support Team, such as complex API errors or institutional sign-in issues – Manage onboarding and training of any additional or new replacement consortium support staff, including general understanding of ORCID as well as the responsibilities of providing support for ORCID users. – Provide guidance to consortium members aligned with ORCID standards and requirements: — Engage with ORCID to ensure that member ORCID integrations are consistent with ORCID guidance and best practices. — Actively promote new developments in ORCID services providers and systems that are used in the consortium — Ensure members are kept up to date with ORCID technical and community developments, such as new functionality, API upgrades, new resources, etc. – Provide technical feedback to ORCID: — Act as liaison between the consortium member organizations and ORCID, ensuring that members’ technical interests are represented and that feedback is provided via appropriate channels to fuel improvement and innovation — Manage the consortium issues register — Execute the consortium escalation process — Ensure all consortium member contacts are registered in the Member Portal and have activated their account. |
| Maintain consortium technical and non-technical documentation | Provide relevant local online resources to help consortium members: — Integrate with the ORCID Registry — Promote ORCID adoption within their own organizations, — Collaborate within their own organizations |
| Participate in the ORCID consortium community | – Join and contribute to the ORCID API User Group, Consortia Community Forum, Consortia Interest Group, and other groups as appropriate – Share experiences, user stories, and resources with other consortia – Attend ORCID virtual and/or in-person consortia meetings, including the annual consortium workshop |
| Develop and maintain consortium-specific communication and engagement resources | – Develop and contribute to/adapt resources developed by ORCID and (as appropriate) other consortia: — To educate members about ORCID and the services and tools that are available to them — To inform members about integration options — To promote ORCID to member organizations and researchers |
For ORCID
| Keep consortia leads up to date on ORCID’s strategic priorities | – Communicate ORCID’s vision, mission, current priorities, and plans with Consortium Lead Organization via: — Strategic Plan — Annual Report — Town Hall meetings — Consortia Interest Group meetings |
| Provide administrative support to the Consortium Lead Organization | – Manage the ORCID licensing agreement and the annual membership renewal with the Consortium Lead Organization – Manage the annual billing cycle for the collection of licensing fees – Coordinate and connect Consortium Lead Organizations through Consortia Interest Group meetings and other groups |
| Provide training and support for the Consortium Lead Organization | – Provide training within 90 days after the consortium formation, including: details about ORCID organization, technical integrations and APIs, and outreach strategies – Provide a point of contact within ORCID for each Consortium Lead Organization – Serve as the primary contact to support the consortium escalation process. Act as the problem manager for all escalated incidents/issues – Provide resources and support material for the Consortium Lead Organization’s Support staff to communicate, educate, and integrate ORCID technology with members |
| Provide Tier 2 and 3 Technical support for the Consortium Lead Organization and Members | – Manage the resolution of Tier 2 and 3 support incidents escalated by the Consortium Lead Organization – Provide guidance and advice to the Consortium Lead Organization to ensure that member ORCID integrations are consistent with ORCID’s standards and best practices |
| Provide and maintain resources for technical implementation, communication and engagement | – Provide resources for consortia to assist members with integrating and realizing the benefits of ORCID – Setup and manage a web interface/repository with resources for consortia to: — Assist with member integrations — Share vendor integration examples and resources — Share communication and engagement activities — Provide communication material and resources for consortia and members to use – Develop and maintain documentation, online resources, promotional material and collaboration tools for consortia – Host various training events – Maintain a presence at relevant conferences and events |
Ready to start the conversation with us?
If, after you’ve reviewed this document, Building a Successful Consortium, and the Onboarding Checklist, you’re ready to start a conversation with us to explore the possibility of forming an ORCID Consortium, we encourage you to reach out to us at [email protected].