Advance Notice: All ORCID websites, including the Registry (Public and Member APIs and the user interface), and, will be unavailable from 2pm UTC on December 15 for up to eight hours for a scheduled hardware upgrade. We apologize for any inconvenience.


Subscribe to ORCID News feed
Updated: 29 min 29 sec ago

Announcing the Results of our 2019 Board Elections

Fri, 07 Dec 2018 - 15:19 UTC

ORCID holds Board member elections every year, following an open recommendation and nominations process. ORCID Board members serve for three years; each year about a third of the Board seats are up for election. The Nominating Committee was chaired this year by Karin Wulf, a researcher member of the ORCID Board. The committee reviewed 25 applications.

The committee must balance a number of objectives when developing the slate. Their overarching aim is to recommend candidates who are driven by the ORCID mission and are able to contribute to ORCID’s development, through their personal and organizational knowledge and networks of influence. Diversity is also an important factor - in terms of skills, geographic location, organizational representation, and gender -- and the committee must also ensure that the Board, as per our bylaws, remains majority non-profit.

The Nominating Committee’s slate of candidates was reviewed by the Board at its September 2018 meeting, announced in this blog post by Karin Wulf, and sent directly to ORCID members via our newsletter and an email to all voting contacts in member organizations.

This year, for the first time, we also held regional Town Hall meetings after the slate was announced for members in the Americas, Asia Pacific, and Europe, Middle East & Africa, to provide an overview of the process, share information about the slate, and answer questions.

Of the 832 members eligible to vote in the 2019 Board elections, 239 (28.7%) cast votes, above the 10% participation needed for the election to be valid. Of those members casting ballots, 226 (94.6%) voted in favor of the slate, 10 (4.2%) abstained, and three (1.3%) voted against the ballot. The election results were certified at 13:10 GMT on 7 December 2018.

On behalf of the Board and ORCID staff, our thanks to everyone who submitted nominations and participated in the elections process, especially the members of our Nominating Committee. Please join me in welcoming our new and returning Board members:

Related posts Blog

Signing the ORCID Funder Open Letter

Thu, 06 Dec 2018 - 03:11 UTC

Co-authored by Christian Gutknecht and Michael Hill, respectively Specialist for Information Systems and Deputy Head of Strategy Support at the Swiss National Science Foundation 

Today, the Swiss National Science Foundation has signed the ORCID Funder Open Letter as part of our commitment to expand the integration of ORCID across funding data management systems (see press release). We believe ORCID can add substantial value to the data infrastructure of funders and hope that more will join this important initiative.

ORCID Integration at the SNSF Today

In 2017, 16,000 researchers were associated with 5800 ongoing Swiss National Science Foundation projects. Managing this amount of personal, academic, and financial data requires substantial infrastructure and resources. At the SNSF, our own in-house software called mySNF, lies at the heart of this infrastructure. mySNF can manage the full administrative life-cycle of a research project, from the submission of CVs and research proposals to the final collection of project output data.

This infrastructure is vital to efficient management of research funding data, and most funders rely on such systems. The systems and their underlying requirements are, however, different for different funders and, as a result, they are rarely directly interoperable. This means that researchers still need to submit separate CVs to individual funders because the requirements or submission formats vary; grants can still be difficult to identify and track online; funders cannot easily and systematically verify or share relevant information; and, accordingly, they cannot track research activity beyond their own infrastructure making longitudinal studies difficult.

Individually, many funders have embraced digitalisation. On a global scale, however, end-to-end data curation and exchange are still lacking due, at least in part, to the heterogeneity of CV and grant data. The SNSF is committed to improving this situation and, by signing the ORCID Open Letter, we encourage other funders to join the effort.

Already today, over 4,000 researchers have entered their ORCID iD in mySNF, which is then also mirrored in the SNSF’s public project output platform P3. mySNF also allows for researchers to import dataset and publication metadata directly from ORCID, and funded projects can in turn be exported to ORCID, albeit indirectly. Following the best practice guidelines for funders, the SNSF is furthermore committed to increasing integration of ORCID in mySNF through three separate initiatives.

Future Initiatives

The first initiative pursues the goal of developing a way for researchers to easily add their SNSF grant information to their ORCID records directly. Crossref’s aim to register DOIs for grants is obviously highly relevant in this regard; accordingly, the SNSF also participates in Crossref’s funder advisory board to define metadata attributes for grants. By providing grant data directly to Crossref and ORCID, researchers’ track records could be auto-populated and funding institutions could simplify the reporting and monitoring of applicants’ overlapping grants across funders.

The second initiative aims at crediting the work of peer reviewers and evaluation panel members by offering the option to easily add these efforts to their ORCID profile. As described by Jason Gush from New Zealand’s Royal Society Te Apārangi, the latest extension to the ORCID metadata model offers the opportunity to implement such a service. The SNSF is hoping to provide its reviewers and evaluators with this service, not only as an incentive but also as honest acknowledgement for their valuable work.

The third initiative was inspired by the ORCID Reducing Burden and Improving Transparency (ORBIT) project, where a group of funders investigated various ways of facilitating and increasing the integration of ORCID in their data management infrastructure. At the SNSF today, researchers still upload their CV in the form of a PDF formatted according to our specification. Based on the work initiated in ORBIT, we are now investigating how much CV data might be imported directly from ORCID into mySNF in the future and how such an import could best be implemented.

CV Data Alignment and Evaluation

All these efforts aim at improving the standardisation, reliability, and value of data and at facilitating its management. The actual data itself and what we do with it, however, is — at least to some extent — a separate matter. In an independent project, in close collaboration with ORCID and other stakeholders, we are therefore also investigating what actually constitutes valuable data in a CV. What do we as funders really need to know about the track record of applicants, and how can we best use this information to ensure fair evaluation procedures? If we can find some answers to these basic questions, then we might also have a chance at developing some common standards or guidelines for CVs and their evaluation.

More widespread ORCID integration on the one side, and more closely aligned CV requirements on the other, have the potential to truly transform how we think about and manage track record data in funding institutions. At the same time, global, end-to-end interoperability of CV and grant data would also allow for new ways of sharing and interacting with such data, providing valuable research opportunities and insights. The SNSF is proud to be a co-signatory of the ORCID Open Letter, which promotes these goals, and we encourage all funders to join this initiative.

Related Posts and Pages Blog

Scaling Up: Easier ORCID iD Authentication for Everyone

Tue, 04 Dec 2018 - 18:34 UTC

At its core, ORCID enables researchers to make connections between themselves (via their ORCID iD) and their activities and affiliations (via other identifiers and APIs).  These connections are asserted either by the researcher or, with their permission, by ORCID members.

Ensuring that researchers have control over their iD and the information connected to it is one of our core principles. To fully wield that control, researchers must be able to understand both what information has been asserted and who has made the assertion. Making this information transparent also helps build trust in iD-ID connections.

Assertion Anatomy

While assertions might seem straightforward, things can get complicated quickly. We care about three relationships in an assertion:  

  • Item origin - whoever published the activity or is the affiliated party  
  • Assertion origin - whoever collects the ORCID iD and makes the connection to an item
  • Source - whoever adds the information to the researcher’s ORCID record  

The “who” in these sources may be the same or different.  For example, a researcher can manually add something to their record, they can use a Search and Link Wizard, or they can give permission to a member to update their record.  At present, there’s no way of telling which of these three pathways were used to connect information to an ORCID record.

We think it is important to change that.  Doing so will both make it possible for researchers to request updates to incorrect information (such as a name misspelling), and for the consumers (such as universities, funders, publishers, and researchers) to make informed decisions about what information to re-use.

Engaging our Community

To explore methods for articulating assertions, we are launching Research Information Platform Engagement (RIPEN). The RIPEN program will allow us to test a technological approach to clarifying  the provenance of information on ORCID records, using JSON Web tokens (JWTs) to reduce the technical burden of integrating authenticated ORCID iDs into workflows. RIPEN brings together a number of projects and themes we have been working on since our launch, including researcher control, authentication, and auto-updates.

Our overarching goals for the RIPEN program are to:

  • Test our implementation. Ensure that our technology and messaging are easily understandable and meet community requirements
  • Improve data quality and trust. A primary goal is to improve trust in iD-ID connections, by ensuring adherence to ORCID best practices for authentication and assertion assurance
  • Broaden reach. Expand the community that can interact with ORCID technology by reducing technical development cost and barriers to implementation
Step-wise Approach

We will be rolling out the RIPEN program in three stages.  In the spirit of eating our own dog food, the first partner implementer is ... ORCID!  We will be testing out JWTs (pronounced “jots”) in our own systems, using them to collect authenticated iDs from staff, board and working group members, to delegate user permissions between our app for collecting iDs and our SalesForce CRM system, and to update ORCID records with affiliation assertions into ORCID records.  Another key part of the program is to collect data on the time and cost of implementing this technology compared with using our current three-legged OAuth methodology.  

We are starting our work now, and expect to share more about our progress around March 2019.  We are in the process of recruiting partners for Stage 2, which we anticipate launching early in 2019.   We will decide whether to move on to Stage 3 after evaluating the program in discussion with our Board, tentatively at their October 2019 meeting.

Stay tuned for more!

Related Posts and Pages Blog

Announcing our New Technology Team Structure

Mon, 03 Dec 2018 - 15:28 UTC

ORCID has gone through a huge staffing transformation this year, with new people, new roles, new teams, and promotions.. Our most recent change is the departure of Rob Peters as our Technology Director.  I am very thankful to Rob for his leadership and support during our start-up phase.  I will miss him, his uncompromising style, and zaniness -- including a sock puppet extravaganza at our recent all-hands staff meeting.  

I mean, where do you go from there!?

Fortunately, ORCID enjoys change.  It is in our blood. We are prepared for it. Here is our new technology leadership team:

Will Simpson, Technology Director.  Formerly second-in-command on our technology team, Will has been with ORCID longer than any other staffer, joining us as a member of the pre-launch consulting team in 2011.  He has been a key steward of the ORCID technology stack for seven years, and in his new role will be taking on responsibility for our technology strategy and the scalability of our technical infrastructure.


Liz Krznarich, Technology Lead.  Liz is continuing her role as a front-end developer, as well as taking on new responsibilities leading our software development process, managing tech team goals and initiatives, and ensuring high-performance operations of the ORCID Registry and other key systems. Liz runs marathons in sub-zero weather, so is well-practiced for her new role.


Tom Demeranville, Product Director. This position expands Tom’s previous role as Technology Advocate. He is now in charge of working with the entire ORCID team - and our community - to establish and develop our product roadmap.  He will ensure that our technology is responsive to our community and aligned with our mission. His work on ORBIT, and the European Commission funded ODIN, THOR, and FREYA projects demonstrate his fit for this role.  

Please join me in congratulating Will, Liz, and Tom -- I look forward to working with them as we continue to drive the ORCID mission forward.  It is long, hard work - and with them it will also be a lot of fun.

Related Posts/Pages Blog

A Year in ORBIT

Wed, 28 Nov 2018 - 19:50 UTC

Co-authored by Josh Brown and Tom Demeranville (both ORCID)

Last year, we announced the launch of the ORCID Reducing Burden and Improving Trust (ORBIT) project. Since then, we have been working hard, supported by our fantastic Funder Working Group (FWG), to deliver on the core project goals for 2018: to automate information flows into grant applications - saving researchers time, reducing duplicated effort and improving data quality; and to explore the ways that persistent identifiers can help to increase the openness and reusability of research information.

The FWG has a remit to oversee the ORBIT project work, and to advise ORCID on issues that are important to the funding community. Eighteen funding organisations from around the world are participating in the FWG, with representation from funders in Africa, Asia/Australasia, Europe, North and South America.  Since some of these funders support research in Antarctica, it’s fair to say we have research in every continent on planet Earth represented in the group! The funders are a mix of discipline-focused (e.g., the US National Institutes of Health and Wellcome Trust both focus on life sciences research) and multidisciplinary funders (like the Swiss National Science Foundation, or the Australian Research Council).

One of the first tasks the group completed was comparing the information typically required to submit a grant application.  We found that, while grant application requirements vary between funders, there is a common information ‘core’ that is collected across them that is also very well served by the existing ORCID record schema.

The FWG also examined the information funders collect from individuals tasked with reviewing grant applications.  We found more variations in the practice of grant review than grant application, from minimal information (name, address and organisation) to a full curriculum vitae, and again a good mapping with the existing ORCID record schema.

To understand whether ORCID record data could be re-used in funding applications, we analysed the 2017 ORCID public data file using the core application fields determined in the FWG analysis (above).  The results are published in a report describing the information connected to ORCID records, mechanisms of connection (always with the researcher in control!), and its provenance.  This report is already proving useful for organisations seeking to re-use ORCID data.

In June 2018, ORBIT project partners met face to face in Edinburgh at the International Network of Research Management Societies (INORMS) conference. We held a ‘kick off’ meeting for the ORBIT pathfinder projects, and presented the ORBIT project  to an audience of INORMS delegates at our ORBIT Community Forum. It was a packed afternoon, with contributions from NIH, SNF and Crossref, as well as discussions and a panel session. INORMS provided a welcoming opportunity to discuss the ORBIT project with the wider research community. Our thanks to our colleagues at the UK Association of Research Managers and Administrators (ARMA) for their generous support!

The ORBIT pathfinder projects are forging ahead with their plans to integrate ORCID into grants workflows.  ORBIT supports them through its Technical Advisory Group (TAG), a venue for the exchange of ideas, requirements, and plans between the funder members and the vendors that serve them (Terms of Reference).  Since the TAG was set up, two major grant application and management platforms -- CCT and Altum -- have both started to integrate ORCID and are now offering ORCID integration as a feature to their customers.  Both vendors are focussing on reducing the researcher effort required to providing high-quality information in the grant application process. Funders in the pathfinder group that are developing bespoke solutions are learning from these vendors’ experiences. One such funder, the Australian Research Council, are currently testing their integration, which enables applicants to use their ORCID record to add relevant publications to their applications. ARC expect 15,000 researchers to have benefitted from the integration by the end of 2018.

What’s next in ORBIT?

We have another full year of activities ahead of us!. We’ll be analysing the work of the pathfinder projects to quantify the time savings and other benefits of using ORCID. We’ll also be launching a new project sub-group to explore ways that funders could make their information demands more consistent, easier to automate, and more interoperable (more information about this group soon).  We are starting to explore how the new version of our API can support even more of the information that researchers need to provide to funders.  And, we will be working to extend the information available to funders about identifiers, and continuing to work with the community to adopt of FAIR principles for identifiers and the metadata linked to them.

Open and transparently-sourced research information is at the heart of ORCID.  In ORBIT, our goal is to engage the funding community to make it easy for researchers to share their information now and into the future.

Image courtesy of Wikipedia


Fast Iterations, Cowboys, and How to Scale 39,185% in Six Years!

Tue, 27 Nov 2018 - 20:52 UTC

Imagine something growing by 39,185%. That’s a farmer planting two tomatoes and harvesting 783,600. Or, a 0.2 lb baby panda growing up to weigh 3.9 tons, bigger than the average Asian elephant. It’s the kind of “hockey stick” user growth that people drool over in the startup world. ORCID has achieved it in just six years.

Joining ORCID in 2012 as tech lead was initially a leap for me. I had worked helping to grow five startups, but never anything in the nonprofit or academic space.  Six years later, upon my exit December 1st I wanted to reflect back on my experiences..

I was originally hired on as Lead Developer to help stabilize, scale, and speed up the software lifecycle of ORCID’s legacy-forked Java codebase. I joined shortly after the Registry was launched, at which time we had 10 servers and a team of three software consultants, serving a rapidly growing base of over 14K user researchers.  I remember my fish-out-of-water feeling the first time I presented on ORCID to a room full of multi-PhD’d academics at CERN, armed with my community college associates degree in mathematics and unfinished bachelor's degree. But we all shared a vision, and that brought us together to do incredible things.

Even though the domain of open research infrastructure was totally new to me, managing the day-to-day software release cycle and contributing to the code base are in my wheelhouse. We built a team that combined the best of  open, commercial, and startup cultures and we were able to quickly get fixes in place and start on a path of rapid scaling. My “cowboy” approach from working in fast-moving California startups turned out to be a good match for ORCID’s mission-focus nonprofit structure and international scale. Two big pain points in those early days were server stability and pushing the code base to an open source repository, in alignment with ORCID principles.  By the end of 2012, 2.5 months after our launch (!),we had grown to over 50,000 users and 25 member organizations.  By the end of 2013, we neared 500K users, from every country.

There were hurdles at the start, certainly. For the first two months I couldn’t build the codebase or access the server build scripts. Why? Because parts of our codebase were locked behind a software consulting company’s firewall. This meant having to push live changes I couldn’t test and modifying servers by hand (both terrible practices but with the advantage of making you understand exactly what you are doing!). Not having 100% access to all part of the codebase impressed on me just how important open source and sharing can be.

Today, ORCID has over 5.5 million users around the world, and we are nearing 1,000 members. My role grew too. I transitioned from Lead Developer to Technical Director in January 2016, and during my time here, I have led a tech team of nine spread across three continents and traveled to over 40 cities. I never did get my idea approved for a team meeting in Antarctica (it has the highest density of researchers in the world, perfect for ORCID!) Along the way, a couple of key lessons stand out when thinking about what makes the ORCID story so special:

  1. Community. At the first Board meeting I attended, ORCID had just four employees and 14 board members! How bizarre it seemed to have a ratio of three board members for every employee - something you’d never see in a Silicon Valley startup. While those numbers evened out as we grew, the Board has continued to be a lodestar. Over the years, I came to realize how much the ORCID community cares and also how much the ORCID community deserves credit. Any sacrifices I made as an early employee were returned by the community three-fold. You are truly amazing!   
  2. Embrace change. At launch, ORCID was following enterprise software processes and culture rules designed for large publishers. While those practices have merit, as a tiny startup, we needed to be unafraid to buck perceived best-practices and instead find the right practices for us. One example from the early days was our external software consultants insisting we go through load testing for every release. Of course, pushed to the servers, the reality didn’t match the test results. ORCID was spending a lot of time and money on something that kept proving ineffective. From a previous job at Fortune 500 company, I knew load testing usually was fraught with false assumptions. So instead, we created a culture of coders reading and understanding their code changes. ORCID was willing to engage new, more appropriate solutions every step of the way.
  3. Iterate fast, taking small steps toward huge goals. Pushing small changes as quickly as feasible to production has been a big part of our ability to scale. Even though the end goals were HUGE, breaking the steps down helped us get there. Small steps mean small risk. A great example is from my very first day. I knew the API first build had a critical flaw that is best described as monolithic. Mostly, this was tied to modeling the API about researchers after other APIs built for books. Researchers are far more complex than books! The team had to tackle it with small steps -- 27 iterations and hundreds of code commits to get to API v. 2.0 -- until we eventually had the API we needed to allow ORCID to continue to scale.

When I started there were eight production machines. Over the last six years we’ve had to double those numbers to increase the size/power of the servers to handle periods of rapid exponential growth. Currently, ORCID sees the most growth with the use of our APIs -- about 3,456,000 requests  a day and growing. Staying ahead of growth is ongoing work. I’m really proud to have been a part of the ORCID story, especially the early rough-and-tumble days. As I set out on my next ventures I hope ORCID finds new challenges and even bigger successes.


Better Together: Working with our Third Party Provider Partners

Mon, 26 Nov 2018 - 00:00 UTC

ORCID’s success relies on you, our community, building connections between your systems and the ORCID Registry to enable transparent and responsible information sharing.  We work with organizations across every sector in research and innovation, building relationships within and between them. Our work is not without its challenges, but we have outstanding partners all around the world who are building the integrations that will help achieve our common vision of an open and trusted research information infrastructure.

One of our strategic goals for 2018 is to strengthen our relationships with third party providers whose integrations are enabling our members to quickly and easily implement ORCID. This has inspired our “Better Together” webinar series, which highlights these relationships and collaborative success stories.

Digital Measures. Earlier this year, we worked with the team at Digital Measures by Watermark, a faculty research tracking platform, to launch their ORCID integration.  The launch webinar included a live demonstration of how ORCID can enhance the data that institutions gather about their researchers while simultaneously saving those researchers time in their reporting.  It was one of our best attended webinars this year. Nearly 20 universities have already begun using the Digital Measures ORCID integration. View the recorded event here.

Digital Science has integrated ORCID in several of their platforms and services, including Symplectic Elements, Dimensions, Overleaf, Figshare, and Altmetric.  Members of the ORCID and Digital Science teams provided an overview of these integrations and their functions for researchers and institutions in two webinars on November 13 and 14, 2018.  We also heard about a use case of these tools as used collectively by a group of research institutions. Tim Cain is director of the Ohio Information Exchange  (OIEx),  a portal that connects Ohio stakeholders to faculty and research from six Ohio universities, using the Dimensions and Elements platforms and enhanced by ORCID iDs.  View the recorded event here.

Interfolio, the creators of the Faculty Information System, have recently updated their ORCID integration to enable researchers to pull their research activity information into their faculty profile. This saves researchers time and reduces the risk of errors and duplication when updating their activity data on file at their institution.  Interfolio strives to provide a holistic view of faculty achievements and activity, and ORCID integration further empowers faculty to develop their academic story continuously across their career.

Join Interfolio and ORCID staff on Thursday, December 13 for a demonstration of these features and to hear about institutions that are using them. Register for the event here.

Information about more third party systems that have integrated ORCID can be found on our integration resources web pages.  If you are interested in collaborating or participating in a “Better Together” event, please contact us -- and be sure to join the upcoming webinars!  


Thank You!

Mon, 19 Nov 2018 - 21:53 UTC

ORCID Registry Scheduled Outage, December 15, 2018

Sun, 18 Nov 2018 - 23:44 UTC

On Saturday, December 15, 2018 we will be migrating our database to new hardware. During this transition we estimate that the ORCID Registry, including the Public and Member API and the ORCID Registry user interface, will be unavailable from 2pm UTC for up to eight hours.  

This scheduled outage will enable ORCID to upgrade our relational database management system, Postgres 9, to Postgres 10. Besides keeping ORCID’s software stack current, the upgrade will also enable us to move from binary replication to logical replication, which means we will be able to significantly reduce and possibly eliminate outages for future upgrades.    

We recognize that this will cause some inconvenience for organizations that have integrated ORCID and for users. We appreciate your understanding, and we will do our best to keep the downtime to a minimum.

If you haven’t already done so, we strongly recommend that you join the ORCID API Users Group, where we will be posting further updates before, during, and after the outage and/or that you follow us on Twitter (@ORCID_Org).  Please do let us know if you have any questions.


Learning Patience: Taking a Step Back on Affiliation Assertion Requirements

Tue, 06 Nov 2018 - 03:20 UTC

ORCID is committed to enabling traceable connections between researchers and their activities and affiliations.  This includes using identifiers for things (such as DOIs) and places (such as organization identifiers), as well as people. In many cases, however, identifiers are not yet widely used. In some cases, there is not yet an understanding that identifiers are needed.

When we first launched affiliation functionality in 2013 (see Organizational Affiliations Now Part of ORCID Record), our focus was on organization identifiers.  These made it possible for us to create an organization pick list for researchers to choose from when adding employment and education affiliation information to their ORCID record.  Since then, researchers have used this pick list to make over 5m such assertions, and increasingly their institutions are using the ORCID API to add affiliation information for their own researchers – to date, researchers have given permissions for over 100K such assertions.

However, what about researchers who have more than one affiliation at the same institution, over time or at the same time?  In this case, simply connecting a person’s ORCID ID with an organization ID is not enough. And even with additional role metadata, there is no clear way to resolve the affiliation: to find a web page or other independent digital information for that affiliation.  Some institutions have faculty and staff profile pages, but by and large these pages are removed when a faculty member moves to a new organization. And let’s not even ask about students, who most often don’t have any online representation hosted by their institution.

As part of our push toward trusted assertions (see Assertion Assurance Pathways: What Are They and Why Do They Matter?), we decided that our new API release candidate (3.0) should require affiliation assertions added to an ORCID record by any source to include either a persistent identifier – which we knew was a stretch – or, what we thought was achievable now, an affiliation start date.  Verifying that someone has ever worked at institution X is significantly harder than verifying that they worked at X during a particular time period.

However, thanks to your feedback on our new API release candidate, we now know that, for many in our community, this bar is currently too high. So, by popular request, we are temporarily rolling back the start date/identifier requirement for affiliations in API 3.0. We will be taking time over the next 6-9 months to work with the community to gain a better understanding of your workflows and information sources and to engage with partners to test approaches.  If you are interested in working with us on this project, please contact me.

In the meantime, we will be:

  1. Displaying “date created” for items on the ORCID record and in the API
  2. Requiring organization IDs for the asserting organization and the affiliation itself
  3. Ensuring that only those organizations that have a direct relationship with the affiliation may post it to the ORCID record.  This means that Institution X may ONLY post affiliations pertaining to their institution. We will be managing this using organization IDs for the asserting organization and the affiliation being posted
  4. Encouraging (but not requiring) the use of start dates in affiliation assertions
  5. Encouraging pilot integrations that test use of identifiers for the affiliation
  6. Encouraging inclusion of a local webpage URL (such as a faculty or staff profile) in the affiliation assertion, preferably in an archived format (see e.g.,

Our Engagement team will be responsible for working with members to ensure these guidelines are communicated, and also adhered to in our Collect & Connect badging processes.

We look forward to working with our community to improve transparency and trust in affiliation assertions. Please contact us if you have questions or suggestions.

Related ORCID posts

1ORCID API Versioning


Research resources now live -- join the pilot!

Fri, 02 Nov 2018 - 11:05 UTC

Earlier this year we announced a new data model to acknowledge research resource use on ORCID records. Now with the launch of the first release candidate of our API 3.0, we introduce a new section to the ORCID record: research resources.

Research resources are specialist resources used for research purposes, and can include anything from research facilities housing specialized equipment (laboratories, observatories, ships, etc.) to digital repositories; and from museums and galleries to field stations that house physical collections. Identifying which resources were used to create research findings improves research rigor and reporting, and increases transparency.

Like peer review activity, resource use can only be added to an ORCID record by a trusted organization (ORCID member organization), following collection of a researcher’s ORCID iD in a formal resource proposal or request process. And like the peer review section, the research resource section will not appear in an ORCID record until a resource connection has been made and added. Organizations that provide resources are invited to join our pilot project to integrate ORCID iDs and other persistent identifiers into resource proposal and award processes. Find out how below.

Recognizing resource use on ORCID records

Connecting information to your ORCID record starts with verifying your ORCID iD. In most cases, a resource provider requests that you verify your ORCID iD by signing into ORCID and granting them permission to update your ORCID record with information about your use of their resource. This typically occurs when you submit a request to use a resource or grant access credentials to a resource.

The resource provider uses this permission to connect information about your resource use to your ORCID record. Publicly recognizing the use of research resources in this way benefits you, the organizations you interact with that collect information from your ORCID record, and the resource provider themselves. Each resource item includes persistent identifiers: the organization ID for the resource host and the grant or project ID of the resource, which enable transparency and traceability. The resource provider (the trusted organization) is always listed as the source of the information.

Above is an example resource use recognition from Environmental Molecular Sciences Laboratory, a member of the resource pilot group.

Organizations: Join the research resource pilots

Our User Facilities and Publications Working Group defined two pilot projects: one for resource hosts to adopt ORCID iDs and other persistent identifiers into their resource proposal and award processes; and one for publishers to integrate award and resource identifiers into the publishing process. Connecting resources to ORCID records is a key part of the first pilot project.

We invite members of the ORCID community to test the research resources workflow as a part of our pilot group. Let us know your interest by completing our online form and our team will follow up.

We also invite the community to participate in the pilot project to integrate award and resource identifiers into the publishing process, so resource use can be recognized. Not certain which project is right for your organization? Get in touch with the ORCID Engagement Team to learn more.

For more information, please see:


ORCID Austria Workshop: Report and Next Steps

Thu, 25 Oct 2018 - 18:00 UTC

Earlier this year, the University of Natural Resources and Life Sciences (BOKU) hosted the ORCID Austria workshop in Vienna in cooperation with ORCID and “e-infrastructures Austria Plus”. About 60 participants from 25 Austrian institutions learned about the advantages of ORCID membership and the integration of ORCID iDs into university repositories, CRIS, and personnel systems.

In addition to presentations by ORCID staff, the workshop also included experiences and solutions of other countries and institutions. The presentations from Swiss and German ORCID members provided new perspectives about ORCID integration for institutions, and also rationale for establishing a national consortium. A presentation by Ulrike Krießmann from the Graz University of Technology demonstrated how they collected ORCID iDs from their researchers using their CRIS system. Since many Austrian research institutions are interested in integrating ORCID into their systems as a service for their researchers, the TU Graz example was very important.

Christian Gutknecht of the Swiss National Science Foundation (SNSF), talked about the Swiss experience with ORCID. In 2014, the University of Bern became the first research organization in Switzerland to join ORCID as an organizational member. They were soon followed by a number of other organizations, and there ensued in 2015 a discussion about establishing a Swiss national ORCID consortium. This did not come to pass, as the question of which institution should act as the consortium lead organization was not resolved. Currently, thirteen Swiss institutions – including seven research organizations, two funders and four publishers – are ORCID members.

Gutknecht also presented an update on the ORCID Funder Working Group and the ORBIT project (ORCID Reducing Burden and Improving Transparency), which aims to use persistent identifiers to improve the exchange of information between and within the different funder systems and databases. He noted that, in line with ORCID best practices, the SNSF requests ORCID iDs from their grant applicants. The Austrian national funder FWF (Austrian Science Fund) goes farther and has required ORCID iDs since 2016.

During the roundtable session, meeting participants discussed the possibility of creating an Austrian ORCID consortium and the coordination of such an infrastructure in Austria. The presentation on the German consortium ORCID-DE by Paul Vierkant offered helpful insights and advice. ORCID-DE has obtained funding from DFG for the period 2016-2019 to support this initiative. In addition to setting up a national contact point, and the BASE integration with ORCID, one of the other goals of the ORCID-DE consortium is to integrate ORCID with the GND (Gemeinsame Norm Datei), the international authority file of names managed by the Deutsche Nationalbibliothek. Vierkant also described the legal opinion commissioned by ORCID-DE to analyse ORCID from a data protection aspect. ORCID-DE had 41 members in May 2018, with numerous other institutions interested in joining.

New ORCID members in Austria and next steps

The workshop has been an important starting step for connecting stakeholders in the Austrian research community and establishing ORCID as the identifier for researchers. Subsequently, the University of Vienna and the University of Natural Resources and Life Sciences, Vienna (BOKU) have joined ORCID as institutional members. Both universities plan to soon integrate ORCID into their CRIS systems so that their researchers can connect their iDs. There are now four Austrian ORCID members -- three universities and the FWF. A minimum of five are needed for a national consortium.

In June "e-infrastructures Austria Plus" sent out a questionnaire to all workshop attendees from Austrian institutions about their interest in joining a national ORCID consortium. So far, six institutions have expressed their interest in joining and many more have expressed a general interest in ORCID. “e-infrastructures Austria Plus” will continue to help coordinate the Austrian research institutions and support the formation of an ORCID consortium. A top priority is to identify a consortium lead organization.

We’ll keep you updated on progress!

Anna-Laetitia Hikl is a CRIS Manager at the University of Natural Resources and Life Sciences - BOKU.


Celebrating Open Access Week with the 2018 Public Data File

Wed, 24 Oct 2018 - 12:00 UTC
Happy birthday to us! ORCID turned six this October. To celebrate our birthday and Open Access Week, we are releasing our 2018 Public Data File.

Releasing the annual public data file is a key ORCID principle. The file is a snapshot of all ORCID record data that researchers have marked public, in the ORCID Registry at the time that the file was created on October 1, 2018 -- information that our users have set to be visible to everyone. We publish this file once per year under a CC0 waiver.

Get the file

Our 2018 Public Data File can be downloaded from the ORCID repository. This year the file is available in v2.0 of the ORCID API message schema, the default since August 2018. API v2.0 supports quick views of ORCID records using summaries, displaying limited metadata in the activities section (affiliations, funding, works, and peer reviews). To provide all public Registry data, we have included a second file with all public data from each activity section of users’ ORCID records.

Previous files are available at our public data file page. See also our related support documentation.

Use our conversion library for JSON records

Unlike previous data files, the 2018 data file is available only in XML format rather than both XML and JSON. If you prefer JSON, we recommend using our ORCID Conversion Library available in our Github repository.

The converter is a single downloadable Java application and can generate JSON from XML in the default version ORCID message schema format (v2.0 and v2.1). Currently the converter can process only full record XML or the ORCID public data file. The converter is a new project, and we’re always looking for ways to improve it -- let us know your feedback!

Let us know how you’re using file

What can you do with the public data file? Your imagination is the limit! Some recent examples: John Bohannon used data from the public data file to track researchers’ global migration in his study “Restless minds” published in Science (May 2017, Vol. 356, Issue 6339), which was awarded the National Academies of Sciences, Engineering, and Medicine's 2018 Communication Award for newspapers and magazines. The Digital Research Yearbook created an “ORCID indicator” based on affiliation data in the public data file; the indicator is the proportion of researchers at an institution who have registered for an ORCID iD and connected it to their institution.

Use of the public data is governed by our Privacy Policy. As with other ORCID resources, we release the public data file under a CC0 1.0 Public Domain Dedication. We impose no restrictions on use the the file, and have created recommended community norms for use. Let us know how you put the public data file to use -- and thank you!


Inviting Your Feedback: Draft Recommendation for ORCID in Repositories

Mon, 22 Oct 2018 - 12:39 UTC

A few months ago, we announced the launch of the ORCID in repositories task force. This group, chaired by Michele Mennielli, International Membership and Partnership Manager at DuraSpace, was charged with reviewing and providing feedback on proposed recommendations for supporting ORCID in repository systems. In an unprecedented show of interest, we received over 40 applications from individuals interested in joining the task force.

Gathering input from across the repository community is a key priority for this project. However, due to constraints of time, space, and telecommunications, the size of the task force had to be limited.  With diversity a primary driver, 15 members were selected, representing 12 countries (on 6 continents!) and a variety of organization types. Now, after several months of scrutinizing documents and meeting across far-flung timezones, the task force is releasing its Draft recommendation: Supporting ORCID in repository systems for public review and comment.

The recommendation is open for comment through 15 Nov, 2018. You may comment directly in the draft.  We invite you to share the document widely with your peers and colleagues who have an interest in the use of ORCID in repositories. You may send us your comments by email to if you’d prefer to remain anonymous on the public document.  After the comment period, the task force will review the feedback and incorporate it into its final recommendation.

Our goal is to publish the final version of the document in December, 2018, after which we will launch work to incorporate the recommendations into our existing workflow documentation for repositories.  In parallel, we look forward to working with the repository community to adopt the recommendations, including informing the work of Projects Governance of open source platforms supported by DuraSpace.

Thank you in advance for your feedback!


Announcing the ORCID Board Slate for 2019

Mon, 08 Oct 2018 - 00:00 UTC

I am delighted to announce the slate for ORCID’s 2019 Board election.  

We received 25 nominations, and felt strongly that the candidates represented the best of ORCID -- a committed, collaborative community of users. The Nominating Committee is tasked with considering a complex set of potential contributions from nominees, including sector representation, gender, geography, professional expertise, and skills pertinent to Board service. A major thanks to Richard de Gris, Alison Mitchell, and our two external Nominating Committee members, Johanna McEntyre and Paul Vierkant, as well as to the ORCID staff for their support of our work.

After careful consideration, the Nominating Committee unanimously recommended the following candidates to be put forth for election to the ORCID Board, for a term from 2019-2021:

More information about the slate and elections process can be found on our 2019 election page.

All ORCID members in good standing as of October 8, 2018 are eligible to vote.  Online voting will be open from November 8 - December 7, 2018, and full instructions will be sent to the official contact at each member organization by November 7, 2018. Members also have the option to propose write-in candidates for the Board within 30 days of the slate being announced (by November 7, 2018) – full information can be found in our bylaws, Section III, Article 2.

In addition to participation on the ORCID Board, the Nominating Committee is working with the ORCID Board and staff to identify other avenues for nominees to formally participate in ORCID’s work.  Ongoing initiatives are listed on ORCID’s community webpage, and we look forward to sharing more about new initiatives rolling out in 2019.


Hong Kong ORCID Roundtable

Fri, 05 Oct 2018 - 00:00 UTC

About 20 participants from Hong Kong institutions gathered for a round table meeting on September 13, to discuss their experiences of integrating ORCID. Many of the institutions were early adopters of ORCID with much experience to share.

Our Hong Kong members utilize a variety of systems for their integrations, working with research information (CRIS) and repository systems, other vendors, as well as developing their own homegrown solutions to connect their researchers to ORCID and to their university.

Participants in the meeting agreed that the main challenges in implementing ORCID are around adoption, rather than technical implementation -  in particular, user education and outreach to researchers and administrators on how and why using ORCID benefits them. A presentation by Janice Chia, Scholarly Communications Librarian of Hong Kong Polytechnic University illustrated some of the ways they are tackling this issue, specifically communicating with researchers experiencing sign-in fatigue. However, past challenges can provide good training for a community undergoing a second integration in the future.

Representatives of the newly formed Hong Kong Access Federation, whose mission is to allow secure and expedited access to institutional digital resources, saw opportunities to leverage eduGAIN services to assist Hong Kong members in simplifying ORCID registration and sharing trusted affiliation information with their researchers. Universities saw this trusted connection workflow as a means to demonstrate time-saving benefits to researchers of registering and using their iD to automate ORCID record updates.

The meeting ended with a discussion about next steps, with participants agreeing to work together to develop a suite of shared ORCID outreach resources, with ORCID providing facilitation support. The ultimate goal is to improve outreach and communication between Hong Kong researchers, their research offices, and the Hong Kong Research Grants Council.

We look forward to working together with stakeholders in Hong Kong to raise awareness of ORCID, and to help researchers and their organizations alike to get the most out of ORCID across the research cycle.



Ch-ch-ch-ch-Changes: Lots and Lots of Changes

Thu, 04 Oct 2018 - 00:00 UTC

This has been a year of substantial internal change for ORCID.  Our transformational grant from the Helmsley Trust ended in March, and we took the opportunity to re-evaluate our programs.  This has led to the creation of our new Engagement team, formed by the merger of our previous Membership and Community teams. As of 1 October, this global team - structured by region (Americas; Asia-Pacific; and Europe, Middle East & Africa) - is providing member support, managing user tickets, and helping to build regional communities of practice.

I am pleased to announce that Matthew Buys is leading the Engagement team.  Matt started at ORCID in 2015, hired on using Helmsley Trust funding, to lead our membership efforts in Middle East and Africa.  He subsequently took on responsibility for Europe and Canada too, and last year was promoted into the position of Membership Director.  In his new role, he is leading a team of 12, six of whom have joined ORCID this year. Each team member is responsible for a specific region or set of countries, and for end-to-end support for members and users in those countries.  

Matt is supported by three regional Engagement managers: Ana Heredia is leading our Americas team, and new team member Ivo Wijnbergen is leading our EMEA team. For the time being, Matt will serve as interim lead of our entirely new Asia-Pacific team.  

As if that were not enough change, at the same time that we were recruiting and onboarding the new team members and training everyone in their new roles, we also moved onto a new support ticketing system in September, and improved how we are handing badging for our Collect and Connect program.

But wait, yes, there IS MORE.

Alice Meadows, who formerly led the Community team, is moving into a new role as our Communications Director.  Alice came to ORCID with Matt in the Helmsley class of 2015. She is very much looking forward to moving into a role where she can focus on her first love.  She will be responsible for working with our regional teams to establish and implement our communications strategy, ensuring that we remain on message – and that our message is clear and well-articulated.

At the same time, Laura Paglione has recently left us to start in a new role as an independent consultant.  Laura was ORCID employee #2 and ever my unfailing #2, leading our technical team until 2016, when she moved into a new role as Director of Strategic Initiatives.  Laura has been an invaluable team member, responsible for more things than I can name easily in a short post: developing the look and feel of the ORCID website and Registry, ensuring we have a solid technical infrastructure, leading efforts to define how to cite (and implement citation of) peer review, and establishing our Trust Program, not to mention doing a huge amount of work on our internal information- sharing platforms including SalesForce and our first user ticketing system. I -- and all of us -- will miss her dearly.  I am very happy that she will be making time for ORCID in her consultancy. Look for Laura at Identity Management meetings and leading our 2019 project on person citations.

Clearly, 2018 has seen a lot churn at ORCID.  We have not had this level of change since 2015 when we doubled our team size.  But amid it all, our goal remains the same: to serve our community effectively. Coming up on our sixth anniversary later this month, we are:

  • Growing up, getting closer every day to being fully supported by our membership fees. Thank you to everyone for your ongoing support!
  • Growing stronger, with close to 1000 members and well over 5m registered users.  We foster the development of communities of practice to scale adoption in regional communities, often working with ORCID consortia to do so.  Over half our members now participate in these consortia, which are run by locally-supported community managers.  
  • Growing more connections, both in volume and variety.  We have expanded our data model in API v. 3.0 to support more research information use cases for asserting affiliations and exposing the resources that researchers use.  We welcome partners to test the new API in our sandbox.  Your feedback is essential!
  • Continuing to focus on transparency and trust.  We are partnering with identifier providers to ensure that these connections are discoverable and support open research.  We are working to define concepts and practice around trusted assertions and FAIR persistent identifiers.  Look for more on this in the coming months.
  • Encouraging the adoption and use of ORCID as a key component of the broader open research information infrastructure. We will soon be launching a partners program for research information platform providers to make it even easier for organizations to use ORCID, regardless of their size or technical capabilities.  More on this soon.

We will continue to engage with our community -- here, on social media, and at the events we host and attend -- to ensure we are meeting your needs as ORCID adoption continues to increase. Your comments and suggestions are always welcome.


New Feature Alert: Upgraded Affiliation Types

Tue, 02 Oct 2018 - 00:00 UTC

Enabling transparent and trustworthy connections between researchers and their contributions and affiliations is at the center of ORCID’s mission. This enables researchers to be recognized for the many different types of valuable work they do.

Since last year, we have dedicated a lot of time to expanding organizational affiliations on the ORCID Registry. After gathering community feedback, developing a data model, and testing, we are delighted to announce that our expanded affiliation types are now available on our newly released API 3.0!

With this release, the ORCID Registry now supports seven types of affiliations in four sections:

  • Education and (new) qualifications: the formal education relationship between a person and an organization, either in an higher/tertiary education program, a professional or vocational training program, a certification, or a continuing education program.
  • Employment: a work relationship between a person and an organization
  • Invited positions and distinctions (new): formal relationships outside of employment between a person and an organization, such as a serving as an visiting researcher, an honorary fellow, or being distinguished with an award or honorary degree
  • Membership and service (new): membership in an organization, or donation of time or other resources in the service of an organization

Several ORCID members will be helping us to beta test this functionality over the coming months.

Member organizations interested in beta testing the new affiliation types, please contact us!

Related blog posts Related Knowledge Base articles   Blog

Streamlining Faculty Reporting: ORCID and Digital Measures

Fri, 28 Sep 2018 - 00:00 UTC

Research activity tracking, publishing, funding platforms are incorporating ORCID into workflows. Organizations across the research community are using these platforms to enhance data quality and reduce the data entry burden for their users.These platforms also reduce technical barriers for implementing ORCID.  

ORCID member organization Digital Measures is one such platform. Used by several ORCID members participating in the US national consortium to manage faculty activity reporting, Digital Measures by Watermark launched the first phase of its ORCID integration this summer. Already, 19 US research institutions have started to use the new ORCID functionality. 

Digital Measures by Watermark allows institutions to facilitate collection of activity data from faculty, saving time and duplication of effort for both researchers and research administrators. It is used by more than 400,000 faculty members in over 15 countries to share stories of personal and institutional success. Their ORCID integration streamlines data sharing, enabling the researcher to import their works directly from ORCID -- bringing us closer to achieving our goal of allowing researchers to “Enter Once, Reuse Often”.

"The power of Digital Measures by Watermark lies in illuminating the multitude of important contributions faculty are making to their fields, students, institution and community.” says Kate Kaczmarczik, Product Marketing Manager at Watermark Insights, “With this new ORCID integration we collectively take a big step forward. With a few clicks a faculty member can represent their full body of publications in Digital Measures by Watermark, and faculty and administrators alike can have full confidence in the comprehensiveness and accuracy of that information."

At a recent webinar, members of the Digital Measures by Watermark and ORCID teams explored the value of each of these tools, as well as providing a live demonstration of how they work together. A recording of the webinar and the slides are now available.

For more information about implementing ORCID using Digital Measures by Watermark, please contact us.






So Long, Farewell, Auf Wiedersehn, Goodbye…

Thu, 27 Sep 2018 - 09:07 UTC

This week is a bittersweet one for me. On October 1, I will be changing my status from one of the longest-standing employees of ORCID to being an independent consultant. I am excited to start this new stage in my career, and happy that in this new role I will be continuing to support ORCID in identity management and other projects. I definitely will miss the depth of my current day-to-day involvement, but I’m excited to see how the organization evolves as I step away.

Naturally, I’ve found myself being a bit nostalgic. I remember the website from when I joined in June 2012, before we had our current branding, and were still working with the pilot version of our registry. My first task as Technical Director was to manage the development of the first production version of the Registry. Laure and I set an aggressive four-month (!) timeline to launch the Registry. We cajoled a set of partners whose integrations would launch along with the registry, and we all worked together to build our early membership and technology offering.

The pre-launch ORCID site, September 2012

Launch day was timed to coincide with our 16 October, 2012 Board meeting, in Berlin, Germany. The launch was successful - people found the ORCID site and very enthusiastically started to register - but it also highlighted how sometimes infrastructure is not quite ready for community demand. We selected Rackspace as the “safe choice” to host our website and the Registry database. What we hadn’t realized is that we’d be using their brand new server bank, which hadn’t yet been proven out. On launch day Rackspace had capped our server memory at 1 MB with no ability to scale. As a result, the ORCID site was not available to everyone who wanted to access it. Working across timezones (Berlin to Texas), and on a massive sleep debt, finally at 4PM in Texas (10PM for me in Berlin!) I was able to negotiate a doubling of memory, but it still wasn’t enough! Thankfully the excitement about our launch outweighed the disappointment of spotty access.

Rackspace on launch day - capped at 1MB of memory! October 16, 2012

After the launch, our two-person ORCID team started to grow. I found this picture from March 2013 of our full-team meeting in our “office”. Everyone still works from their own space today, and many early employees are still with ORCID five years later.

The ORCID team, March 2013

By early 2013, the Registry started coming into its own, though it looked a bit different from the way it does today. We had plans to include many items in ORCID records. However, to meet our aggressive schedule, we launched with only the ability to add works. We did a lot of work to identify a community-condoned source of organization identifiers and, by the end of 2013, the Registry also supported user-assertions of employment and education affiliations.

The ORCID Record at launch (screenshot from July 2013)

I was also tickled to find a snapshot of what we thought was a heavy support week a little after our one-year anniversary when we got 167 (!) emails - up 43% from the week before. At the time we wondered how we would be able to scale. With over 350,000 researchers, and nearly 100 member organizations, it felt as if we had come such a long way in such a short time. Just over five months after launch, on April 1, 2013 (April Fools Day in the US), we demonstrated our ability to localize the ORCID site into other languages by pretending that it had been taken over by Orcs, and translating the site into Orcish (yes - there is such a language; check out the translator.) While the joke didn’t fully resonate with our global user base, the proof of concept was successful and, by the end of the second year, we had added support for seven languages. During our second year we also added a significant number of new features including affiliations, and a certified privacy policy. We kicked off our third year with seven significant sets of new functionality, culminating in the release of a new interface that largely reflects what is on the site today.

The new ORCID Record interface. December, 2014

By this time, with over one million iD-holders, and over 150 member organizations, we started to seriously think about ways that we could scale the organization to meet our upcoming demands. In 2015, the generosity of the Leona M and Harry B Helmsley Charitable Trust enabled us to double our staffing, significantly increasing our outreach capacity. As we grew, I also transitioned into a new role, with responsibility to think more deeply about how we should prepare for ORCID’s future. I spearheaded the development of the ORCID Trust program, built our relationships with the Federated Identity Management (FIM) and the OpenPharma communities, and explored possible futures with our Board and community through strategic visioning exercises, which laid the foundation for our 2018 Strategic Plan.

ORCID, you have come such a long way from humble beginnings, and I am so proud to have contributed to your success. I am thrilled that I will have the opportunity to continue my service to you and continue to work with your fantastic community as I take this next step of my journey. And to all of my ORCID teammates, thank you for the memories and the laughs, for welcoming me into your homes in our video calls, introducing me to your families, and being such an important part of the last six years. I look forward to all of our future conversations as our paths continue to cross.

The ORCID Team at annual full-team meeting, August 2017