What you get for your UK ORCID consortium membership

UK ORCID consortium lead.

The key responsibilities of the consortium lead are defined by ORCID but in summary are:

  • Manage and support the on-boarding of new consortium members
  • Engage with members collectively and individually to understand, help prioritize, and support integration plans
  • Act as first point of contact for UK consortium members
  • Provide helpdesk support for outreach, technical and membership queries, by email and phone:
    • Requests acknowledged: Within 1 working day. (This is an automated response)
    • Requests Resolved: We aim to resolve most queries within 7 working days and almost all queries within 20 working days.
    • Support hours: Monday – Friday (09:00 – 17:00) excluding UK public holidays and Jisc closure days between Christmas and New Year
  • Escalate queries to ORCID, where support queries cannot be resolved by consortium lead
  • Provide UK-focused guidance materials and resources for new and existing ORCID users, as well as signposting useful resources elsewhere
  • Ensure members are kept up to date with ORCID technical and community developments, such as new functionality, API upgrades, new resources, etc
  • Regular check-ins with ORCID support staff
  • Act as liaison between ORCID and consortium members, and keep ORCID up to date with consortium news.
  • Monitor the ORCID API mailing list and contribute where required
  • Facilitate community engagement and collaboration and drive benefits for institutions and individual researchers
  • Coordinate implementation activities among group members
  • Monitor and promote the growth of ORCID integration
  • Gather technical interoperability requirements across UK universities
  • Help to implement or guide integration developments, where appropriate
  • Run user community events: hackdays, webinars, meetings, workshops etc (min 2 events a year)
  • Facilitate knowledge sharing nationally and feeding into international developments
  • Participate in ORCID International Consortia activities
  • Support the wider adoption of ORCID as a global initiative

Administrative support for consortium membership:

  • Jisc negotiation and establishment of the licence including full legal review of the licence which includes due diligence around data protection.
  • The initial establishment of the licensing agreement
  • Subsequent renewal of licences
  • Management of the billing cycle for the collection of fees from members and the payment of licensing fees

ORCID community forum:

The consortium lead has set up a community forum. This is made up of representatives drawn from the consortium membership to represent different university systems and the diversity of our membership, and ORCID representatives.

The aim of the community forum is to ensure that ORCID UK engagement and development activities meet the community’s needs.

The role of this group includes:

  • Comment on outputs and support materials created by the consortium lead, including the web site
  • Suggest new activities, highlight gaps in existing information
  • Help consortium lead to reach end users (researchers and contributors) or those taking policy and strategy decisions
  • Advise on how best the service should communicate with various audiences and stakeholders;
  • Advise on the programme for planned events e.g. workshops and hackdays to support integration and uptake
  • Suggest new contacts and key organisations who have not yet engaged with ORCID
  • Promote and publicise ORCID and the efforts of the service to local and national contacts, where appropriate.

Premium API Access:

As part of a consortium, all member institutions will have access to full features of premium ORCID membership at a reduced cost. Premium membership is the highest level of ORCID membership. The membership pricing is based on Jisc banding.

The main features of consortium premium membership include:

  • access to dedicated, ORCID trained, technical and community support staff from the consortium lead
  • access to on boarding webinars and other online resources such as FAQs, technical documentation, and training materials provided by the consortium lead in collaboration with ORCID;
  • access to, and participation in, a growing national and international community in the development of best practices, knowledge and skills in research management, including
    • engagement with the ORCID organisation to ensure that consortium ORCID integrations are in accordance with ORCID guidance and stated good practice;
    • sharing of plans and coordination of implementation activities among consortium members;
    • contribution to consortium liaison between the UK ORCID user community and the ORCID organisation ensuring that the UK community’s interests are represented and that feedback is provided via appropriate channels to fuel improvement and innovation;
  • access to 5 sets of Member API credentials to use across multiple systems (e.g. Institutional Repository, CRIS, HR and Identity management systems etc.). This supports the use of ORCID across the entire spectrum of research management processes and activitie
  • register of webhooks via API for notifications from ORCID when information is updated in an ORCID record connected to the organisation (e.g. receiving notice when a new publication is added to an ORCID record)
  • review of member integrations before applying for member API credentials from ORCID
  • customised analytics report from ORCID and ORCID monthly newsletter
  • exclusive use of ORCID tools such as affiliation manager

Responsibilities of member institutions

  • Familiarise themselves with and follow the terms of licence including ORCID trademark and display guidelines
  • Complete consortium onboarding procedures including agreement to licence terms and providing contact details
  • Keep contact details up to date by informing consortium lead following staff changes
  • Be active participants in mailing lists, events, workgroups and knowledge sharing activities
  • Follow good practice requirements as set out by ORCID
  • Communicate issues to consortium lead
  • Keep abreast of notifications from ORCID as communicated through the monthly newsletter or direct mailings
  • Technical contacts are strongly encouraged to join the ORCID API user group