ORCID is a community effort. On these news pages we provide updates on policy, outreach, and technical developments. You may subscribe to our blog, follow us on Twitter @ORCID_Org, or check our Trello boards for the status of fixes and features.

We encourage community involvement. The success of ORCID depends upon it! You may enter and vote on ideas for development on our iDeas Forum, check our Knowledge Base for technical documentation, or contact us with questions.

Using RSS? Subscribe at https://orcid.org/blog/feed

Displaying 111 - 120 of 310 posts
  • Blog | ORCID Board Elections! Calling for Nominations


    Starting this year, ORCID will hold member elections for positions on next year’s Board. This follows a bylaws change made by the Board in November 2015, and recognizes that ORCID is maturing both as a platform and an organization.  Read on to learn who is on the Nominating Committee and how -- and when -- to submit recommendations.

  • Blog | User control over who sees what


    One of ORCID’s core principles is that individuals control their ORCID iD and the information attached to it. ORCID systems are designed so that nothing can be added to an individual’s ORCID record without his/her explicit consent. With an upcoming change to the ORCID API we will be strengthening user control, ensuring that individuals’ default visibility preferences apply to everything in their ORCID record. Read our post to understand how this change may affect you.

  • Blog | ORCID Workshops - Coming Your Way Soon…


    We are ramping up the ORCID workshop program in 2016, with plans to hold events in 15 countries - from Argentina to UAE - as part of our growing global outreach efforts. Thanks to the generous support of our sponsors, all workshops are free of charge to attendees. Find out more about in this post; and we hope to see you at one of our workshops in 2016!

  • Blog | What's in a Name? Internet2 Community Supports Unique Researcher Identifiers


    We are delighted to announce that eduPerson now includes the ORCID attribute. Read more in this guest post by Internet2's Emily Eisbruch, Work Group Lead, Trust and Identity (adapted from the original post on the Internet2 blog).

  • Blog | Meet ORCID Institutional Ambassador, Knowledge E


    Continuing our series of interviews with ORCID community members, this month you can learn more about one of our Institutional Ambassador organizations, Knowledge E, in this interview with their Director of Research Services, Philip Purnell.

  • Blog | Announcing the ORCID DE project to foster ORCID adoption in Germany


    We're delighted to announce a new project - ORCID DE - launched recently to foster and support ORCID adoption in Germany.

  • Blog | Organisations: the missing link?


    Persistent identifiers (PIDs) for people (researchers and other contributors), places (research institutions and organisations), and things (works and other contributions) are a vital element of the research infrastructure. Digital Object Identifiers (DOIs) are now clearly established as the industry standard identifier for works, and ORCID iDs are increasingly being adopted as a way of uniquely connecting researchers with other professional and personal identifiers, as well as with their works, affiliations, and awards. But what about persistent identifiers for organisations? Read how ORCID and THOR are joining forces with other organisations to help address this 'missing link" - and how you can get involved.

  • Blog | ORCID Trust


    Today we outline a program that we are calling ORCID Trust, and are opening an invitation to data security and privacy experts to help us vet the program before we formally roll it out.

  • Blog | Penguins, Patents, Pianos, and More - All About #ORCID16


    Highlights of our first Australian Outreach Meeting in Canberra (February 15-16, 2016) - including links to available presentations and videos!

  • Blog | ORCID Security Incident


    Yesterday (February 18) we experienced a security incident with the web interface of the ORCID Registry.  This post describes the issue and how it has been addressed.