ORCID News

Subscribe to ORCID News feed
ORCID RSS Feed
Updated: 2 hours 51 min ago

ORCID in the Asia-Pacific Region: Involve, Engage, Consolidate

Fri, 17 May 2019 - 14:42 UTC

by

Chieh-Chih Estelle Cheng

Camillia Lu

Brian Minihan

 

The past year has been busy  for the ORCID Asia-Pacific community.  During the second half of 2018, a new APAC Engagement team was born: Brian Minihan, based in Hong Kong, and Camillia Lu and Estelle Cheng in Taiwan. We each have responsibility for specific countries across the region, and we also act as regional liaisons for communications and outreach (Brian), technology and product management (Estelle), and building and maintaining organizational partnership relationships (Camillia).

 

The new team’s first priority was to establish communications across various APAC community groups through regionally focused roundtable meetings, workshops and blog posts. We recently held our first in-person APAC Engagement team strategy meeting in Hong Kong to reflect on the past and look forward to the future. So now is the perfect time to share with our broader community more on our progress to date and our plans for the rest of this year!

 

We have identified three different stages of ORCID adoption in research workflows across our region:

  1. Involvement -- organizations that are working to get researchers and institutions involved in linking ORCID iDs to their research works and making them shareable and discoverable through identifiers.

  2. Engagement -- organizations that are communicating with partners with similar interests to build strength through numbers and reduce barriers in sharing research information.

  3. Consolidation -- members who are actively expanding existing connections and integrations in the community.

Involvement

At present, there are three ORCID consortia and 143 ORCID member organizations in the region; we support and interact with them in Cantonese, English, Japanese, and Mandarin.

 

Asia-Pacific makes up 14% of ORCID’s total membership and 32% of ORCID Registry usage. That usage is represented in the image below by shading - the more users in a country, the darker it appears on the map.

Engagement

We’re keenly focused on helping our community link research through ORCID and other identifiers. For example, Airiti,a prominent e-publishing platform for Chinese-language works, leverages its work registering DOIs and other activities in the persistent identifier community to engage with researchers and other institutions in Taiwan. Their search and link wizard -- recommended for those with Chinese-language publications -- enables users to quickly and easily import metadata from Airiti Library, including journal papers, proceedings, dissertations, and books. They are building the foundations to eventually link researchers, publishers, institutions, and funders through ORCID integration.

 

We are proud that our region has one of the highest ORCID member integration rates -- roughly 70% of APAC members have at least one integration, with third-party system integrations accounting for about 45% of these.

 

(106 ORCID integrations in Asia-Pacific by vendor system)

 

Integration examples via ORCID-enabled systems include:

 

Custom-built integrations from across the region include:

 

 

Consolidation

A significant number of initiatives by organizations to consolidate existing connections with ORCID are underway or in the planning process in our region.

 

The Australian ORCID Consortia Lead organization, Australian Access Federation, a National Research and Education Network (NREN), is undertaking an effort to define success in maturity several years after ORCID adoption nationally. They’re hoping to share their experience and leadership with emerging federated technology organizations, such as in Hong Kong, communicating AAF’s efforts in providing connections, as well as communication and technical resources. Royal Society Te Apārangi, the New Zealand ORCID Consortium Lead organization, works with other global organizations seeking to learn from its centralized NZ Hub ORCID integration, which supports New Zealand researchers looking to connect their funding and publications, and adding that metadata to NZ Hub users’ ORCID records.

Next Steps

In 2019, we’re planning ORCID staff visits to Northeast Asia including China, Japan, and Korea, following a visit to Australia and New Zealand in April/May. We will be holding our next ORCID members Town Hall Meeting on May 31 (morning hours in Asia Pacific). If you’re affiliated with an ORCID member organization, join us to hear more about our regional strategy, financials, and details from the Nominating Committee Chair for the next Board Election. Also look for us at the 6th World Conference on Research Integrity on June 2-5 in Hong Kong and the Crossref Live Kuala Lumpur event on July 8 at the Ministry of Education in Putrajaya, Malaysia.

 

Building on our success working with publishers and funders, reaching out to research administrators in Asia-Pacific is also a key strategy in 2019. Look out for details of our webinar about ORCID and research management later this year.

 

We also warmly invite you to participate in our working groups and other community initiatives, including volunteering to help test our user interface -- read more in Friends of ORCID.

Contact us directly or follow us on Twitter or LinkedIn!

Blog

ORCID API 3.0 is here!

Thu, 16 May 2019 - 19:52 UTC

We are pleased to announce the release of our new 3.0 ORCID API.  We’re excited about the new features it contains, including several new affiliation types, a new research resources section, token delegation to enable permission sharing between members, and improved transparency about the source of information in ORCID records.

New affiliation types

With the help of the community, we have expanded our affiliation section so that researchers can be associated with -- and get recognition for -- a wider range of professional activities. 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 a 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 serving as a 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

The API represents all of these affiliations in a similar way, so expanding an integration to use them is straightforward.  They have been available in the user interface for several months now, and researchers have already been busy adding them to their records themselves, with 39,855 distinctions added as of this week, 34,685 invited positions, 94,302 memberships, 107,894 qualifications, and 30,832 service affiliations.

For more information, please see New Feature Alert: Upgraded Affiliation Types and our new workflow documentation for Invited positions and distinctions and Membership and service.

Research resources

Our new research resources section connects people with the facilities and equipment they have been granted access to use.  Last year our User Facilities and Publications Working Group helped define how these should appear within our API.  Since then, several working group members have started adding research resources with our beta API, which was announced in Research Resources Now Live!

It’s great to see this evolve from an initial conversation with one member, to a community working group that developed a recommendations working paper, then on to a pilot implementation phase, and now into our production API. In addition, the working group helped establish requirements for tagging research resources in journal articles that are now incorporated into NISO’s recently released JATS 1.2 standard. More information is available in our research resource workflow documentation and there is a research resources API tutorial as well.

Blazing the trails of research resource acknowledgement are the Environmental Molecular Sciences Laboratory, Oak Ridge National Laboratory, and the Extreme Science and Engineering Discovery Environment (XSEDE), with several others in development. Publishers are also participating, with Wiley piloting the inclusion of research resources used in the production of submitted manuscripts in a unique acknowledgements section.

See the Source

Transparency is a core value of ORCID.  We have been working to enable more transparency about the sources of information posted to the ORCID Registry, and API 3.0 now distinguishes between the source of the ORCID iD → item connection, and the source of the item → ORCID record connection.  See Assertion Assurance Pathways: What Are They and Why Do They Matter for more information on why being able to see the source is so important to us.

Ensuring researcher control is a key facet of “See the Source", including assurance that researchers have given permission to use their iD and also including organization identifiers to clarify source identity.  

Items in records now display information about the member that made the connection between the iD and the item (the assertion origin), as well as the member that used the API to add the item (the source). Learn more in Where can I see the source of information in my ORCID record?  

“Seei the Source” also makes it clear when one member has enabled another to  act on their behalf by sharing permissions. We’ve updated our service provider workflow to reflect these changes, as well as creating a token delegation API tutorial, which provides more detail on these workflows. 

Other changes

Normalizing identifiers. We’ve introduced a new system-generated field, which expresses external identifiers (DOIs, PMCID, PMID, ArXiv, Bibcode, ISSNs, and ISBNs) in a normalized  format for the purposes of matching and grouping. Normalization is done based on the rules of the identifier type, and may include setting all alpha characters to lowercase, or transforming spaces, dashes, periods and other characters that can be treated as equivalent. It also adds standard prefixes and suffixes as appropriate. For example, http://doi.org/10.1/123, 10.1/123, and https://dx.doi.org/10.1/123 will all appear in this field as https://doi.org/10.1/123.  The existing identifier value is unmodified.

New work types. In response to community feedback, we’ve added or modified several work types, including:

  • Adding ‘preprint’ and ‘software’ to the list of supported work types
  • Migrating ‘dissertation’ to the more general ‘dissertation-thesis’
  • Improving the way we manage work types in API 3.0, enabling us to add new work types without requiring schema changes  

Other work types under consideration for adding to the Registry in future include annotations and physical objects (specimens, samples, etc).

New ID relationship type. As announced in New Features Alert! Improvements to Adding and Grouping Works, we’ve also added a new identifier relationship type of ‘version-of,’ to clearly show where one work is a version of another. This can be used to relate multiple versions of a dataset together, or to group preprints with the published version of a paper.

Upgrading

We learned a lot during the transition from API 1.2 to API 2. This time we’ve made the upgrade much easier to manage.  API 3.0 adds new functionality while only modifying existing functionality when absolutely necessary. This means integrators should be able to switch to the new API with a minimum of fuss. It also means that, although we recommend you start to plan your upgrade as soon as possible so that your organization and researchers can benefit from the new features, you have a lot of flexibility in deciding when to update to 3.0.  

The small list of potentially breaking changes are in our API release notes here and here. There are a few changes around optional/mandatory fields, JSON enumerations have been modified slightly, and we also have a small refactoring of our XML schemas, adding some new fields to contain the metadata required for the new functionality.

Sunsetting older versions

API 3.0 will be the default API version from September 1, 2019, when we will also remove all API 2.0 release candidate versions. However, we will continue to support API 2.0 and 2.1 for the foreseeable future, and will provide at least 12 months notice before switching off those versions.

Documentation

A big thank you to our beta testers for their feedback, to ORCID staff -- especially the Technical Team -- for their hard work developing our API 3.0, and to everyone in our community for your suggestions and support. If you have any questions or concerns about this new version of our API, please share your comments by joining the ORCID API User Group.

    Blog

Listening to Our Users: What We Learned from Our 2019 Community Survey

Tue, 14 May 2019 - 00:00 UTC

Earlier this year we carried out our third community survey. An impressive 11,201 of you responded, with 8,163 (72.9%) completing all the questions. Please see ORCID Community Survey 2019 for the full report.

As a researcher-centric organization, listening to our community is essential in order for us to improve our services and messaging through a better understanding of what you know about ORCID; of how, when, and why you’re using your iD, and of what you do and don’t like about ORCID. Surveys are a great tool for this and, as with previous surveys, we will be using your feedback to inform our strategic decision-making, and to improve our technology and communications.

Perceptions of ORCID remain overwhelmingly positive overall, though with variations by demographic, with librarians, respondents from Latin America & the Caribbean, and Interdisciplinary researchers the most enthusiastic. The vast majority (84.4%) agree or strongly agree that an ORCID iD is essential for researchers, and your support for requiring iDs is equally high -- 84% of respondent overall support this.

One noticeable change in your perceptions of ORCID is that we’re no longer considered the new PID on the block! With well over 6m ORCID iDs registered, we are moving out of our startup phase.“New” has been replaced by “Widely used” in the top five attributes you associate with ORCID, and the number of respondents who have had an iD for three or more years, which has grown from 13.9% in our 2015 survey to 35.3% in 2019.

When, how, and why you use your ORCID iD
  • You’re already actively using our newly introduced features -- additional affiliation types (17.5%) and the new research resources section (7%)
  • You’re connecting more information to your ORCID record than ever before (which aligns with our own Registry statistics), with early career respondents the most active users
  • You’re still most likely to use your iD when publishing an article, and to add publications to your record. But well over half of you now also want to be able to add anything you make public with your name associated to your record - a significant change from previous surveys
  • Editing your record is still prevalent; only about 25% of you have given your trusted parties permission to update your record, although our Registry statistics show that a much higher number -- around 75% -- have done so for at least one organization
  • Disambiguation, recognition, and discoverability continue to top the list of reasons why researchers register for an iD
What you need from us
  • Better communications about how to make the most of your ORCID record, in particular, authorizing trusted organizations (ORCID members) to update ORCID records. We’ll be working on our messaging on this and, in the meantime you can learn more in Six Ways to Make your ORCID iD Work for You!
  • Easier ways to manage your record, especially in terms of adding funding information, works, and managing visibility settings. We are working with the funding community to tackle adding funding information through our ORBIT project; we recently introduced an option to add works by identifier; and we are committed to improving our user interface further
  • Help with connecting anything you make publicly available to your record. Our Person Citations and Academia & Beyond projects will help us explore with researchers how ORCID can better support your needs
  • Improved understanding of the changing needs of researchers throughout their careers, from start to finish. To help with this, we are working on some in-depth user journey mapping, starting with the most highly used workflow - publishing a journal article
  • Better support for researchers in regions and communities with low membership and few opportunities to use their iD. For example, there is huge support for ORCID in Latin America, but very few members or integrations, and only one consortium (in Brazil). We are working with our consortia partners -- our regional experts -- to capitalize on this enthusiasm and grow our member community in these regions

As we become a more mature organization we have an ever greater responsibility to understand -- and address -- the needs of our users. We are lucky to have such an engaged and active community (a full 40% of respondents volunteered to get involved in UX testing and/or ORCID working groups!), and are hugely grateful to everyone who took the time to provide us with such valuable and interesting feedback.

The full report and anonymized dataset are now available.

Thank you again for your participation and feedback!

 

Blog

Improving the User Experience: Why, What, How?

Wed, 08 May 2019 - 17:34 UTC

2019 is ORCID’s  Year of the Researcher, and a key element of this is improving the user experience. It’s also the focus of my new role as ORCID’s first User Experience (UX) Designer. I onboarded in early February, and have started to work closely with our researchers as a user advocate and design strategist. Over the next couple months, you’ll notice changes  in the user interface (UI) as we evolve the ORCID website.

But what is user experience? And how do we design for it?

The user experience encompasses every interaction you have with ORCID -- not just the UI (our site, and what you see on the screen), but also anything from interaction design, the language we use on the site, the way we structure our information architecture, and how easy or difficult all of that is to use and understand. With 6.5m users already -- and 5,000 more registering every day -- it’s critical that we make the ORCID UX the best it can possibly be.

UX design differs from UI design in that we incorporate research as a basis for our design and technical decisions. This is vital because it takes assumptions out of the product development process, and ensures that we are capturing needs and expectations of people who are using the ORCID Registry.

We kicked off our first research initiative at the National Postdoctoral Association conference in mid-April, which generated really useful feedback and insights. Thank you to everyone who swung by our booth and helped us with usability testing and our five-second testing! It was so uplifting and motivating to chat with such passionate, opinionated people who are enthusiastic about ORCID’s mission. As part of that event, we got some first impressions on a new homepage that we’ve been working on, and the feedback thus far has been great.

I wanted to give a sneak peak of that new homepage with you all now.

The homepage is, in most cases, the first page that people see, so it’s important that we make a good impression. On our old homepage, our message was strong, but it had elements that competed for attention. We’ve restructured the content so that it follows a strong page hierarchy, in turn telling more of a story.

Our goal was to evoke a mood and feel that represents what we strive to be as an organization:open, transparent, and community driven. We hope we hit the mark!

We have a lot more improvements planned in the upcoming months. As we prioritize our research initiatives, I  invite anyone interested to sign up to help with ORCID UX research. This may include one-on-one interviews, quick preference tests, usability testing, and many other types of research. If you’re interested, please email support@orcid.org.

You can also share your suggestions for new ORCID features and functionality (and vote on other users’ ideas!) on our iDeasForum.

Blog

Nominations Now Open for ORCID Board Elections 2020

Thu, 02 May 2019 - 00:00 UTC

I am delighted to announce the start of this year’s search for dynamic and enthusiastic individuals from across the research community to join the ORCID Board.

Every year the ORCID Board nominations process gives the ORCID membership a direct voice in the organization’s governance. The Board’s composition and annual elections are an important part of ORCID’s charter, and the election process is a fantastic opportunity to ensure that ORCID grows and develops in close partnership with its members.

As this year’s Chair of the Nominations Committee, I look forward to working closely with the other Committee members, who represent an excellent variety of organizations, member types, and regions. They are:

The role of the Nominations Committee is to select a ‘slate’ of candidates that is balanced and diverse, taking into account different sectors, regions, skills, and non-profit status requirements as established in the ORCID bylaws, and we are also seeking to make the Board more representative of our community’s demographics. New Board members should ideally offer perspectives that are not represented (or fully represented) on the ORCID Board, and you can see the make-up of the current Board here.

Other than two unaffiliated researcher member positions (one of which will be open for this year’s election process), ORCID Board members must be from current ORCID member organizations, all of which are eligible to nominate representatives to serve on the Board. New Board members will serve for a period of three years, starting from the February 2020 Board meeting. They are expected to attend each of three annual Board meetings in person, and to play an active role in ORCID activities during the course of their term. To help achieve our goal of broad representation across sectors and regions, from 2020 we are introducing a Board Meeting Attendance Fund, to reduce financial barriers to participation in Board governance.  For more information about the roles and responsibilities of ORCID Board Directors, please see the Elections web page.

Please send us your recommendations for new ORCID Board members using this form. You can nominate yourself or (with their permission) another individual, Please be sure to tell us what strengths you would bring to the Board, and why you’re interested in serving. We will consider all recommendations received by August 1, 2019.

The slate will be presented to the current Board for approval at our September meeting, after which it will be announced publicly. The community has the choice of either voting on the slate or proposing additional candidates (within 30 days of the slate being announced), in which case the election will become a plurality vote by candidate. To propose additional candidates, a group of 20 or more members must submit a nomination in writing to ORCID before October 22, 2019. Note that the group may not include more than one member per consortium (for specific details, see Article III Section 2b of ORCID's Bylaws). We will send notifications and open the election by electronic ballot later in October.

The full process is summarized below:

ORCID Board 2020 Election Key Dates

Date

Activity

May 2, 2019

Call for Board member recommendations

August 1, 2019

Closing date for Board recommendations

September 17, 2019

Nominating Committee presents slate for Board approval

September 23, 2019

Slate made public

October 22, 2019

Closing date for alternative nominations

October 23, 2019

Voting opens

November 22, 2019

Voting closes, results announced at virtual Member meeting

January 1, 2020

Elected members start their term

February 11-12, 2020

Board meeting, London (UK)

We look forward to receiving your recommendations over the coming months.

Please contact the nominating committee with any questions, or feel free to reach out to me directly. When voting opens, ORCID will be sending proxies to each main contact listed on ORCID membership agreements. If you would like to update your membership contact information at any time between now and then, please contact ORCID Support.

Blog

Keeping ORCID Trusted and Trustworthy: Updates to our Privacy Policy

Wed, 01 May 2019 - 17:24 UTC

Privacy is a fundamental concern for ORCID. One of the bedrock principles that guide our operations is that "Researchers will control the defined privacy settings of their own ORCID record data" -- they decide what information they share, and who they share it with. We are committed to this principle even though the information in ORCID records is often available publicly from other sources.

Every year we review our privacy and security practices to ensure that they remain in line with this important principle and the other values outlined in the ORCID Trust Program. We also ensure that these practices reflect global best practices. We make any needed adjustments and then submit them for evaluation by a third party. This year our policy and practices were reviewed against assessment criteria of the EU-U.S. and Swiss-U.S. Privacy Shield Verification Program; TRUSTe has provided a letter of attestation of this review.

This year’s changes increased the privacy policy readability and made it easier to navigate how to get your questions and concerns addressed. We also made a few updates to our policy and practices to help strengthen your rights as an ORCID user and increase your privacy and data security protections.

These are the key updates to ORCID’s Privacy Policy:

  • Clearer release policy for government data requests. Our policy has always indicated that we may share information with regulators, enforcement agents, courts and/or other government entities if legally required to do so. In our most recent review, we decided that the language we used in this statement was ambiguous, leading to a lack of clarity about the conditions under which your data may be shared. We therefore removed the conditions of public safety or public policy, leaving only the legal requirement as a condition under which we would share data (section 6.4)
  • Stronger privacy protections for deactivated accounts. While email addresses have always been protected in our database, we have decided to provide additional privacy protections for addresses belonging to individuals who have decided to deactivate their account. We maintain email addresses so that, in future,  users can reactivate their ORCID iD if they wish. However, these addresses are now stored in a cryptographically-masked form that enables the iD to be matched to the email if the owner chooses to reactivate the account, but is not otherwise visible or accessible under any circumstance, including by ORCID staff (section 7.0)
  • Greater security for data “at rest”. ORCID data are now even more secure. They have always been encrypted when displayed on a webpage or sent, with your permission, to another system. Now data are also encrypted “at rest”, ie, stored in an encrypted filesystem. This means that even if a bad actor were able to get direct access to the hard drives in our data centre, they would still not be able to read any Registry data. This closes off a potential attack vector, and complements the many other security measures we have in place. (section 10.0)
  • Clearer policies for GDPR complaint handling. Under the European General Data Protection Regulations (GDPR), organizations are expected to handle complaints about the data they hold on individuals in a specific way. Our policy now clarifies these methods and provides a reference to the local Data Protection Agencies that can help with resolving complaints if needed (section 11.0)
  • All ORCID sites under one privacy policy. ORCID recently changed the tool we use to provide support services, including our helpdesk ticket handling, feature request forum, and help documentation. The previous tool had its own privacy policy and, with this change, the websites at support.orcid.org are now covered by ORCID’s privacy policy (section 15.0)

If you have any questions or concerns about ORCID’s privacy policy or these changes, please let us know

Thank you for your continued trust in ORCID!

  Blog

Eight, and Still Counting

Tue, 30 Apr 2019 - 02:10 UTC

Tomorrow would have been the fifth anniversary of my first day working for ORCID. Sadly, today is my last day, but five years is a nice round number. That said, the real number is eight, and still counting. Let me explain…

I was working with ORCID well before it launched, starting in 2011 when my boss Neil casually asked if I’d mind leading Jisc’sResearcher Identifier Task and Finish Group’. That was optimistically named as it turned out: they still haven’t finished. (I might be being a little bit facetious there - since then we’ve moved on from asking ‘should we adopt an identifier for researchers, and if so, which one?’ to deepening the integration of iDs and working with the members of the group, system vendors and the team at Jisc to innovate and create new tools to take advantage of the connections iDs have enabled. So, definitely not ‘finished’, but that’s actually a very good thing.)

One of my last tasks for Jisc was to deliver a keynote at the ORCID registry launch in Berlin in 2012, then I was off to CERN. While there, I was still working with ORCID as a member of the then Outreach Steering Group, and engaging with publishers and repository staff as we collected ORCID iDs for the authors who published in the High Energy Physics journals which participated in SCOAP3.

When I joined ORCID on May 1st 2014, at the time I thought my itinerary for the first month was crazy. I didn’t realise how well it prepared me for what was to come. I was straight off to Rome for CRIS 2014, which was basically part one of my induction, watching Laure work the room and getting to know the team at Cineca who would go on to form the first of our ‘modern’ national consortia. (With a pleasing symmetry, my last trip as an ORCID staffer was also to Italy, starting in Rome to meet the team at ANVUR, then to Bologna to visit Cineca, and finishing with a visit to the 4Science offices in Milan.)

After that first trip, I got home for a weekend, and then headed back out - this time to Chicago for my first board meeting, my second ORCID outreach meeting, and my first face-to-face meeting with ORCID team. At the same time, this was when I started to get to grips with the ODIN project, starting with a phone call at some insane hour of the night (whilst jetlagged to bits) with colleagues at the British Library. We started writing a report that is still shaping conversations now. I remember that particularly, because one of the other people on that call was Tom “Amazing” Demeranville, who later joined us to work on the THOR project and is now our Product Director. (Just for the record, I now have almost as many photos of Tom on my phone as I have of my own children. Make of that what you will.)

During that call, I was watching the sun come up over Chicago and Lake Michigan, until a river of clouds flowed in and gradually devoured the Chicago skyline. As you can see from this photo of the view taken during the call, it wasn’t at all distracting:

After that first month at ORCID, things really started to speed up. Over the years, these are some of the things I have learned:

  • Packing: there is no way you can travel from 30℃ heat in Qatar to -10℃ cold in New York without somehow being dressed wrongly for both climates, but you can go an incredibly long way for several weeks on one small backpack’s worth of clothes.
  • Bureaucracy: is totally unpredictable. Who could ever have guessed that applying in Switzerland for a Saudi visa as a British citizen whilst living in France would be anything other than straightforward? (It wasn’t. I didn’t go to Saudi Arabia. My apologies again to our friends at KAUST.)
  • A conversation that begins ‘Could you pass by Tokyo on your way home from Sweden?” tells you that several weeks of your life are about to be used up. (I’m still not sure how they got used up, they just vanished into a blur of jetlag and waking up from unplanned naps and trying to work out which airport I was in from the language on the signs.)
  • When your monthly expense report reaches 90 pages, you could climb Schiehallion in the time it takes to annotate all the receipts.
  • When your plane catches fire, you’re going to be late for your workshop. Possibly even 33 hours and four planes worth of late… (I still made it though.)

If we’re going to talk numbers, here are a few more: since joining ORCID I have visited 29 countries, some of them many, many times (cough, looking at you France…). I have helped to launch 10 consortia, and to lay the foundations for several more. Between all the various projects and integrations over the years, I have worked directly with colleagues from 40 countries that I can think of without looking it up - so the real number is probably higher.

As well as ODIN, I’ve helped to write the final report from the Alfred P. Sloan Foundation-funded Adoption and Integration Program, support the projects in the Jisc-ARMA ORCID pilot, design and deliver the THOR and Freya projects, and develop the bid that led to our biggest ever grant, from the Leona M. and Harry B. Helmsley Charitable Trust (that one followed from a call in which Laure asked me what I would do with a million dollars, which piqued my interest just a little). I chaired the program committee for the first three PIDapalooza festivals. Most recently, I’ve been lucky enough to work with a group of several dozen brilliant funding bodies on the ORBIT project. These collaborations have taught me that while ORCID is a vision and an infrastructure, it is above all a community: a global network of members, integrators, policy makers, contributors and researchers which taken all together makes that vision possible.

The experience of working with this global community has been one of the greatest privileges I can imagine. I’ve lost count of the number of times I’ve arrived at a meeting prepared to present a ‘solution’ only to listen to what the folks in the room had to say and think “actually, that’s a much better idea”. The travel and the work have been exciting, but the real adventure has been meeting so many brilliant, brilliant, minds. From Lima to Oslo to Singapore, the invention, energy, and commitment to making research better that I have encountered has been an inspiration. To everyone who has made the last eight years so electrifying, thank you from the bottom of my heart.

Here’s to the future.

  Blog

New Features Alert! Improvements to Adding and Grouping Works

Mon, 29 Apr 2019 - 15:22 UTC

Each year our project roadmap focuses on a specific sector and 2019 is the Year of the Researcher.  So we are delighted to announce three new features that have recently been developed to help researchers to add and manage works on their ORCID record -- adding works by identifier, the new preprints work type, and a new way of grouping works.

Adding works by identifier

You can now easily add works to your ORCID record using a DOI (Crossref, DataCite, and mEDRA only), PubMed ID, or ArXiv ID. This feature is available from within the works header on your ORCID record.

By selecting this option, you simply need to add the relevant ID, and the works data will be automatically populated, saving you the time and hassle of manually entering this information.

 

Please be sure to review the imported data before saving it to your record!

Please see Adding works by identifier for more information.

Preprint added as a new work type

In response to requests from our community, we are delighted to announce that preprints -- versions of a paper made publicly available before formal peer review and publication -- are now available as a work type.   Preprint items can be added to ORCID records using this work type, allowing them to be easily distinguished from other publication types.

New work relationship - version of

The same work may be added to ORCID records from different sources.  Works will be grouped together, based on shared identifiers (such as DOIs, ISBNs, etc.).  We have added a new grouping method version of so that alternate versions of works can be linked together, for example a pre-print might include the published versions DOI, or an older dataset might refer to a newer version.

There are now three types of identifier relationships for works:

  • A “part-of” identifier, such as an ISSN. Refers to the journal -- the article is “part of” the journal
  • A “self” identifier, such as a DOI.Refers to the individual work itself
  • A “version of’ identifier, such as an updated DOI.Refers to an alternate version of the work

For more information please refer to our KnowledgeBase article.

Watch this space!

We are currently working with our user community on testing new features that will allow users to manually group works together.

We greatly value feedback from our community and we encourage you to add any iDeas for how we can improve our registry or API to our iDeas Forum.

 

 

 

Blog

Our New ORCID Infographic

Tue, 23 Apr 2019 - 20:57 UTC

ORCID is a simple concept that can be surprisingly difficult to explain.  I know. I’ve been working at it for seven years now. With over 6m users and 1000 members around the world, we rely on our community to help explain what we are, how ORCID works, and why it matters. We need to make it easier for you, too!  

We are open infrastructure, built by and for the research community, that enables researchers to distinguish themselves online.

We have used all sorts of infrastructure imagery - roads, bridges, buildings, plumbing - to illustrate how ORCID helps to make connections between pieces of information. We host regular webinars with stakeholders to share real-life examples of ORCID in action (learn more about the next one in What’s New at ORCID?), and this year we are working to create a repository of demonstration videos.

We also created our “circle diagram” to illustrate the how each of our stakeholders -  researchers, employers, funders, and publishers - must take action to help build and use this infrastructure for everyone to benefit.  

Our new infographic, created in collaboration with IDC, continues our effort to support community understanding of our mission. It provides clear statements of the community needs that drove the founding of ORCID, statistics on how ORCID is being used to make connections between researchers and their contributions and affiliations, and information about the benefits for and impact of ORCID on researchers and organizations.  The infographic is available in Chinese, English, French, Portuguese, and Spanish.

Download the PDFs here to use the infographic today -- and let us know what you think!

Related Posts Blog

What’s New at ORCID? A Joint Library Carpentries/ORCID Webinar!

Wed, 17 Apr 2019 - 15:00 UTC

This post was co-authored by Chris Erdmann, Library Carpentry Community & Development Director and Alice Meadows, ORCID's Director of Communications 

We are delighted to announce that Library Carpentries and ORCID are co-hosting a webinar on What’s New at ORCID. Registration is free -- just add your name here -- and there will be plenty of opportunity for questions and discussion.

This webinar, at 10am ET on Thursday, May 16, will focus on ORCID’s new API v3.0, launching in May, which includes some valuable new features for researchers, their organizations, and the wider community alike:

  • New affiliation types. Enabling researchers to be recognized for more of their contributions:
    • Qualifications, such as continuing medical education and other certifications
    • Membership of an association, society, or other organization
    • Service, for example serving on a Board, as a reviewer, or other volunteer activity
    • Invited positions, such as a visiting fellowship
    • Distinctions, including prizes and awards
  • Research resources. To connect information about the use of facilities and equipment, special collections, and other resources to ORCID records
  • Schema changes. To ensure everyone can see the source of information on ORCID records

We’re especially pleased that we will be joined by some special guests from the Environmental Molecular Sciences Laboratory (EMSL) at Pacific Northwest National Laboratory (PNNL), an ORCID member organization and early adopter of our API 3.0. Their Deputy for User Services, Terry J Law, and her colleagues Nathan Tenney (Developer) and Courtney Carpenter (Data Analyst) will share their experience of implementing the new API, including adding information about EMSL’s resources to their researchers’ records (see example below).

We warmly invite anyone who’s interested in learning more about ORCID’s new API v3.0 to join us on May 16!

  Blog

Spend a Day with the ORCID Team!

Fri, 12 Apr 2019 - 15:54 UTC

Researchers are at the heart of all we do at ORCID and never more so than this year -- 2019 is our Year of the Researcher. We are focusing on increasing our understanding and more fully meeting the needs of our user community. And what better way of doing that than engaging directly with as many researchers as we can!?

We’re starting today at the National Postdoctoral Association meeting in Orlando, FL, where we will be talking to attendees about their use and experiences of ORCID. If you’re there, please be sure to stop by Table 4 and meet our Americas Engagement Team Lead, Ana Patricia Cardoso and our new User Experience Designer, Mallory Robertson.

We are also excited to be launching a competition to win a day with the ORCID team at our staff retreat in Sedona, AZ in October. We invite all researchers, anywhere in the world, and at any stage of your career, to tell us what you think of ORCID and why we should choose you to join us there.

We'll pay travel expenses of up to US$2,500, plus two nights stay at the hotel where we’re meeting. You'll get to spend a whole day with our awesome team! We'll review all complete entries* received by May 10, 2019, and the winner will be announced in mid June.

So, what are you waiting for? Tell us why you should be the lucky one of our six million plus users to join us in Arizona! We’re looking forward to hearing from you.

*Please note that we are only able to consider entries in English.

  Photo:  Wikimedia Blog

ORCID + Apograf

Thu, 28 Mar 2019 - 17:10 UTC

Apograf is an interactive platform that houses an extensive and continually updated collection of technical publications. Our vision is to provide a high-quality, secure, and transparent source of scientific papers — an alternative to the traditional publication and distribution models of scientific scholarship.  Given this vision, becoming an ORCID member was an easy decision with so many tangible benefits for our users — name disambiguation, interoperability, and the time-saving benefits of a single identifier for researchers to use throughout their career.

Our platform allows researchers and academics access to a rich collection of scientific publications, via a searchable database of content compliant with research funders’ Open Access policies. It includes original publications and also pulls from thousands of unique online content hosting locations, including OA journals, hybrid journals, institutional repositories, and disciplinary repositories. For any paywalled content, enriched metadata and links are provided to a user so they can purchase access, should they so choose.

Apograf allows users the ability to filter articles, and design their own feeds, including subscriptions to a handful of curated newsletters or preset filters. There’s also functionality built into the platform that allows users to create and share personalised collections as seen below.

 

Apograf is designed to give contributors more recognition and to incentivise peer review. So we use the ORCID member API to collect and display authenticated iDs, to improve recognition and discoverability of research outputs, and to enable interoperability with other systems (iDs work with many institutions, funders, and publishers). The beauty of the ORCID iD for Apograf is its persistence, as it can be used for the entirety of a researcher’s career.

 

Currently, an ORCID iD is required to upload a paper to Apograf or to conduct a peer review. Existing peer review peer can be a slow process and, because it’s often done by poorly incentivised, busy people it can also be inconsistent, unreliable, biased. Most reviewers are themselves scientists or researchers who could be spending their time doing original research or myriad other things.

With an upcoming blockchain integration, Apograf will offer improved peer review functionality. The introduction of tokens, along with a gamified leader-board style system, will give researchers more tangible reasons to spend their time on peer review.

The more a user participates in peer review, and the more their peer-reviewed article is referenced by other authors, the more tokens they have and, ultimately, the higher their position in the rating system. This combination of incentives, together with the rating system also makes life easier for grant application reviewers or those who are simply looking to collaborate with the best in a given field — a truly merit-based system.

As Apograf joins ORCID, thousands of publications and users — were they not already — will get connected to the Registry. Developing new platforms and supporting initiatives like ORCID are small steps in the grand scheme of things, but each one counts, and as they stack up we inch closer toward solving some of the challenges of scientific publishing. Apograf is proud to join ORCID in pursuing the establishment of an open, fair, and accessible scientific research ecosystem.

For more information, or to sign up for Apograf, please visit our website.

Blog

Evolving ORCID

Wed, 27 Mar 2019 - 00:00 UTC

ORCID is many things to many people.  It’s a helpful resource that saves researcher time, it’s a place for researchers to connect to their achievements, and it’s a way of distinguishing one researcher from another.  It’s also a tool that can help with reporting grant outcomes, filling out forms, understanding someone’s career, and linking up services. This complex interplay between users and functionality mean that it’s very important that, when we add things to the API or modify the user interface, we’ve really thought it through -- not only what new functionality will do, but also who the change will affect, how they will react, and what benefits it will bring.  

I’m the Product Director.  What does this mean? It means that I consider all the competing requirements and work out how to balance the time they will take to develop, the utility of the changes, and where they fit in our strategic roadmap.  My job is to help evolve ORCID  infrastructure so that it serves the whole research community.  I do all of this while trying to avoid a bad back from my temperamental office chair!  

Mine is a new role within ORCID and it marks our transition from energetic start-up to energetic small-medium sized not-for-profit organization. We are now at the point where the ORCID Registry is essential to the functioning of numerous other services -- from grant application and manuscript submission systems to individual user profiles -- and we need to change the way we work to match.  We have over a thousand members: two-thirds of them have one or more integrations, and all of them depend on us continuing to function as they expect. This means we must be mindful about how and how long we take to evolve. When we introduce changes we have to help all our members change along with us.

Requirements for change come from many sources, internal and external to ORCID.  Researchers, research institutions, funders, publishers, research facilities, infrastructure partners, librarians, repositories, working groups, data analysts, web developers, our Board and our staff have all got lots of great ideas about the future of ORCID (and If you’ve got a great idea, head over to our iDeas Forum and let us know!).  I and our cross-organization Product team ( Paula Demain, Estelle Cheng, and Ana Heredia) attempt to balance these requirements when deciding which things we should start working on.   You can read more in How Are New Features Decided? -- including how we decide if something is a feature or a bug.

We’re champions of ‘open’ and, because of that, our product development process is as open as our data.  You can see what we’ve got lined up for the future on our public product roadmap, which contains all the work we’ve committed to doing at some point. This is the functionality we’ve analysed, thought through, and are confident should be included in the Registry.  As time and resources allow, work is transferred from there to our Current Development Trello Board, where it is picked up by our Technology team and implemented, tested, and released.  We also maintain a Bugs Board, where we keep track of the bugs we find ourselves and the ones that are reported to us by the community.  Having all this out in the open means that if you report a bug, or request a feature, you can see it move through to our production service. Learn more about the process for reporting and fixing bugs in How Are Bugs Fixed?

I think ORCID has done a fantastic job of balancing what we do, who we do it for, and why.  ORCID is moving into a new era and we’re refining the way we work so that we continue to get that balance right as we grow.  I love my job here at ORCID, and I’m privileged to be involved.

Blog

Don’t lose access to your ORCID record!

Wed, 20 Mar 2019 - 10:58 UTC

Helping our users re-gain access to their ORCID account is our most common Help Desk ticket. Most often, this is because you’ve changed organizations and no longer have access to the email address connected with your account. There are some simple steps you can take to prevent this problem. 

Option 1. Add another email address to your account

The best way to make sure you maintain access to your ORCID account as you move around in your career is by adding at least one additional email address.  You can do this by following these steps, after logging in:

  • Under Account Settings, select Email and contact preferences, click Edit.
  • Enter an additional email address in the Add another email field and click Add.

  • A verification message will automatically be sent to each new address you add. Please click the verification link in the message to confirm your ownership of the email.

We strongly recommend that you add a personal email address as a back-up. This will help ensure you don’t lose access to your ORCID record, and that you’re easily able to reset your password. Each address has its own visibility setting, and ORCID will not share any email information that you have marked as private.

Option 2. Two-factor authentication

In the past, we hoped that security questions might be the answer, so these were available from the reset password and account settings pages. However, in recent years it has become clear that security questions are not the answer, and we have therefore removed this feature in the Registry, and we plan to remove existing questions and answers from our database as well soon. 
 
Instead, if you wish to make your ORCID account more secure, we recommend that you enable two-factor-authentication.

Should you have any additional questions or feedback, please let us know.
 

Blog

ORCID at Boston College: Create & Connect with PeopleSoft

Thu, 14 Mar 2019 - 18:30 UTC

(Originally posted on the Lyrasis Blog)

Boston College is one of the ORCID US Communitymember institutions leading the way for ORCID adoption at US research institutions (see current member list). Boston College became an ORCID member so they could take advantage of the name disambiguation, interoperability, and time-saving benefits of ORCID as a single identifier for researchers to use throughout their career, regardless of changes in name, discipline, or location. Boston College’s ORCID Libguide provides an excellent example for others to follow in promoting ORCID: https://libguides.bc.edu/orcid.

Boston College (BC) has integrated ORCID into their central identity management system to create an application known as “BC Create or Connect,” which provides a single portal for researchers at Boston College to start their journey with ORCID. The application allows researchers to register and connect their ORCID iD to their BC Eagle ID through the HR system PeopleSoft. From there, the system is configured to write/assert employment affiliation information to researchers’ ORCID records and collects ORCID iDs to display on public facing faculty profile pages.

A walk-through of the integration:

  • Researchers at Boston College go to http://www.bc.edu/orcid where they are taken to a screen asking them to login with their Eagle ID. This allows the system to verify the user and make sure they are in fact affiliated with the institution.
  • Once they log in with their institutional credentials, they are taken to a main ORCID page, “ORCID at BC” that explains what ORCID is and prompts users to “Create or Connect” their ORCID iD:

  • When a user clicks on the green “Create or Connect” button, the user is then asked to authorize permission for the institution to connect with their ORCID iD. In the case of Boston College, users are asked to allow BC to read any limited-access information they may have on their ORCID record (ORCID data visibility can be set set to public, private, or “trusted parties”/limited access), add or update biographical information on the user’s ORCID record, and add or update the user’s research activities:

  • From there, they will be asked to either log in to their ORCID record if they already have an ORCID iD, or they will be asked to register for an ORCID iD if they don’t have one yet. (It is free to register for an ORCID iD, and it takes very little time.) This process ensures that the connection between ORCID and Boston College is authenticated and trustworthy.
  • When a user authorizes these permissions, Boston College can then easily gather data about researcher activity through ORCID, as well as make trustworthy and accurate assertions about the faculty that are affiliated with the institution, providing a verified source confirming that this person does in fact work at Boston College:

The authenticated ORCID iD is then displayed on faculty’s public facing profile pages (see example here):

For more information, please contact orcidus@lyrasis.org. Many thanks to John O’Connor, Scholarly Communications Librarian at Boston College, for sharing this information via webinar (recording available 1:55-8:35). You may find John O'Connor on the BC Digital Scholarship website.

Please click here to learn more about the ORCID US Community consortium.

Blog

Connected Research!

Wed, 13 Mar 2019 - 15:56 UTC

This post was co-authored by Josh Brown, ORCID's Director of Partnerships, and Tom Demeranville, our Director of Product. Our thanks to Dr Carlin for his permission to share this use case.

At ORCID, our tagline is ‘connecting research and researchers’. Sometimes people ask us ‘what do you connect?’ and we usually refer them to our vision, which is of “a world where all who participate in research, scholarship, and innovation are uniquely identified and connected to their contributions across disciplines, borders, and time”.

In this blog post, we will explore one case study of what that vision looks like in reality: one researcher, connected to an institution, to the funding that has enabled their research, and to all of those connected to the outputs that communicate their research findings to the wider world.

Dr Leo Carlin is a researcher. He is a leukocyte biologist, based at the Cancer Research UK Beatson Institute in Glasgow. Looking at his ORCID record, you can get a sense of his career, and how active he is - memberships, education, employment, publications and funding are all here. For the purposes of this blog post though, we will focus on the fact that he received funding from UK Research and Innovation (UKRI), specifically for a project called "Regulation of Pulmonary Neutrophils In Vivo: Direct Interrogation by Intravital Microscopy," supported by the Medical Research Council.

If you click the grant number shown in the ORCID record, it takes you to the project page in UKRI’s Gateway to Research, which provides much more information about the project:

If you click the people tab, it shows that both Leo and his ORCID iD are associated with the grant:

Looking at Leo’s ORCID record, there are a lot of works added from Europe PMC. A search in Europe PMC using either the grant number or the ORCID iD returns this paper (a collaborative project and led by Cristina Lo Celso of Imperial College and the Francis Crick Institute) that work funded by the grant contributed to:

The record for the paper shows ORCID iDs for several co-authors too, as well as three other funding sources for the work that lead to this paper being published:

The link to the article at the publisher’s site uses a Digital Object Identifier to direct potential readers to the published paper.

This case study shows identifiers and infrastructures working in harmony to connect and share research achievements.

  Blog

Introducing the new OJS-ORCID plugin

Tue, 12 Mar 2019 - 09:27 UTC

The recent launch of version 3.1.2 of PKP's Open Journal System (OJS) marks an exciting moment -- an upgraded ORCID API plugin! Journals upgrading to OJS 3.1.2 can now request authenticated iDs from both contributing authors and co-authors, and Member API users can assert published works directly to an author's ORCID record with the author’s permission. All journals that upgrade to the latest version of OJS can benefit from the new features.

Like ORCID, OJS is an open-source, community-driven platform, which benefits from an engaged community of developer contributors. ORCID API support enabling collection of authenticated ORCID iDs was first launched in 2016 with OJS 3.0, through the work of community developers including the University of Pittsburgh. The latest additions were developed by a team of OJS community members in Germany, including Nils Weiher and Dulip Withanage of Heidelberg University (also an ORCID member through the German national consortium).

The plugin also fine-tunes the collection of authenticated ORCID iDs to meet the requirements of ORCID's best practices recognition program Collect & Connect: iDs are collected only by the ORCID API and cannot be entered or edited manually by the author or editor. Editors can request iDs and update permissions from authors and co-authors during production by sending an email from the submission metadata screen.

The expiration date of the access token clearly displays on the admin view of the author profile. ORCID iDs previously collected by the journal, but which cannot be confirmed as authenticated, still display in articles, but without the green iD icon on the public view.

ORCID members using the OJS plugin without any changes can meet the requirements the Authenticate, Display, and Connect badges and immediately receive Member API credentials.  

ORCID Plugin is available in  OJS3 Plugin gallery. Interested users can see a list of currently implemented features here.

Watch the upgraded ORCID Member API Plugin in action.

About PKP

The Public Knowledge Project is a multi-university initiative developing (free) open source software and conducting research to improve the quality and reach of scholarly publishing. PKP is best known for its work maintaining Open Journal Systems (OJS) and Open Monograph Press (OMP).

Blog

ORCID Annual Report for 2018 Now Available!

Wed, 06 Mar 2019 - 19:10 UTC

My Year in Review post provided an overview of our 2018 activities. Now, in our annual report you can learn more of the details - in words and pictures! Some of our key achievements:

  • ORCID adoption. Not only did our five millionth researcher register for an iD during 2018 but, even more importantly, we saw a significant increase in the number of records with at least one connection to another identifier.
  • Integrations. The number of ORCID member integrations increased by one third during 2018, expanding the opportunities for researchers to use their iD in situ. 73.6% of ORCID registrants have now authorized record updates from at least one member integration.
  • Sustainability. Reaching financial sustainability has been a core ORCID goal since the start. We made substantial progress toward this in 2018, increasing our membership by 20% - we broke 1000! - and maintaining our 2Q 2019 breakeven forecast.  
  • Infrastructure and technology. All ORCID integrators -- members and non-members -- are now using our API v2.0 or higher. We also launched the beta version of our API 3.0, which includes data fields for research resources and more affiliation types (qualifications, invited positions, distinctions, service, and membership).
  • Trust and transparency. As part of our ongoing commitment to openness, we kicked off an initiative to make it easier to see the source of information on ORCID records.
  • Communities of practice. Our consortia program grew to 70% of our membership in 2018, with ORCID consortia now in 21 countries. Our consortia lead organizations help develop ORCID communities of practice in their regions, encouraging best practice and expanding the use and adoption of iDs.
  • Engaging with the community. During 2018 we focused especially on the funder community through our ORBIT (ORCID Reducing Burden and Improving Transparency) initiative. In December nine funders showed their support for ORCID by signing an open letter committing their organizations to implementing ORCID using our best practices.

Working with you, our community, is at the heart of everything we do. We are grateful for your participation in our Board, our working groups and task forces, and workshops.  I’d like to take this opportunity to thank all of you for your continued support of ORCID as we move toward achieving our shared vision of a world where all who participate in research, scholarship, and innovation are uniquely identified and connected with their contributions and affiliations, across disciplines, borders, and time.

  Blog

ORCID Member Survey Report

Tue, 05 Mar 2019 - 23:21 UTC

As a community-led organization, listening to what you have to say about our services is critically important to ORCID, to ensure that we understand and meet your needs. So, over the past few years we have been surveying our community, and using your feedback to help us better serve you. This has included a survey of our consortia lead organizations, two community surveys (with a third under way!), and -- late last year -- our first member survey.

Carried out between September and November 2018, there were 170 responses, of which 126 (74%) were complete. The organization types that responded largely reflected our overall membership, with the vast majority (78%) from research institutions, which comprise 79% of our membership. Geographically, the responses were less representative, with Western Europe under-represented (25% compared with 56% of members) and the other regions somewhat over-represented.

A full report and the anonymized data set are now available; some of the learning points for ORCID include:

  • Disambiguation of researchers was the top reason given for joining ORCID, and most respondents focus on using ORCID to help researchers.  However, user adoption is seen as the biggest challenge to implementing ORCID
  • Access to the member API is the most valued membership benefit, but building and reviewing/launching an integration are considered the most challenging aspects of implementing ORCID
  • Communications with ORCID are rated highly, with high scores for our technical  documentation, but only around one third of respondents are using our freely available outreach resources
  • Members are largely positive about ORCID, shown through multiple modalities: a NetPromoter score of 38, high scores for questions about interactions with staff,  and perceived value of key member benefits.
  • We have more work to do to improve our members’ understanding of, and ability to demonstrate, the value of ORCID -- to themselves, their organizations, and their researchers

We are already starting to address these needs, including:

  • Launching the RIPEN (Research Information Platform ENgagement) program, which will enable simpler ORCID integrations through authenticated ORCID iD collection and secure cross-platform sharing of ORCID permission tokens
  • Working to improve the user experience, by ensuring a positive and consistent user experience and user accessibility across ORCID integrations
  • Sharing our successes, building on our 2018 Collecting the Evidence initiative to document and share ORCID successes and outcomes with the community, as well as identifying and addressing gaps in our understanding
  • Developing additional outreach resources, including: user stories and case studies; videos (available here, with more in progress); an infographic about the value of persistent identifiers for researchers; improvements to the content and navigation of our website (during 2019); and more

Our thanks to everyone who participated in the survey -- we really value your feedback! If you have other suggestions for how we can better serve our members, please contact us.

  Blog

Recommendations for Using ORCID in Repositories

Wed, 27 Feb 2019 - 00:00 UTC
History

Back in June, we announced the launch of the ORCID in Repositories Task Force, an intrepid group chaired by Michele Mennielli, International Membership and Partnership Manager at DuraSpace. The group was charged with drafting recommendations for repository platform developers, intended to ensure a consistent base level of support for ORCID across different platforms, allowing repository administrators to implement ORCID effectively ‘out of the box’.

A diverse team of 15 repository experts representing 12 countries on six continents convened and unveiled a draft recommendations for public comment in October 2018. After several weeks of vigorous discussion among ~30 community contributors and a final round of review by the Task Force, I’m thrilled announce the publication of the Task Force recommendations.

Outcomes

Key components of the recommendations include:

  • Support collecting authenticated ORCID iDs, which means that users sign into their ORCID accounts and authorize the repository to obtain their ORCID iD and (optionally) permission to update their ORCID records
  • Support other ways of obtaining ORCID iDs, including in mediated deposits and bulk uploads by repository managers, as well as automated deposits from other systems
  • Allow administrators to request authenticated ORCID iDs and ORCID record update permission from authors and co-authors, in cases where iDs are missing or have not been authenticated
  • Support displaying ORCID iDs wherever user/contributor information is displayed. ORCID iDs that have not been authenticated by their owner should be displayed slightly differently from those that have been authenticated
  • Support pulling and pushing information to and from ORCID
  • Provide testing, logging and reporting features for administrators
  • Support exposing ORCID iDs in metadata outputs, such as OAI-PMH XML, wherever possible
  • Provide documentation about ORCID features, for both administrators and end users
Thank you!

Many thanks to the Task Force members for their dedication and hard work, as well to all those who contributed to the public discussion. Input from such a diverse range of perspectives highlighted differences and commonalities among repositories, resulting in a document that embodies both consensus and compromise -- very much a reflection of the multi-faceted repository community.

Next steps

With community-endorsed recommendations complete, the next steps for ORCID and the repository community are:

  1. Advocate for adoption of the recommendations by repository platform providers
  2. Educate and support developers working to implement the recommendations

Leading the way, DuraSpace is the first organization to take up this charge. According to Michele Mennielli:

"DuraSpace will support and promote the Task Force recommendations throughout its community. The recommendations will be brought to the Governance of its community projects to be considered for the next roadmaps, and DuraSpace will collaborate with ORCID on outreach efforts aimed at spreading the word about the details of the recommendations."

We hope that many more repository platform providers will follow! Repositories are an integral and essential part of the global research infrastructure and rely on a network of systems connected by identifiers. Helping the global research community get the best from this network is our shared goal.

    Blog