ORCID Integration Series: EMBL-EBI

In this third blog post we introduce you to the  EBI ORCID Hub we developed as part of the THOR project at EMBL-EBI, to integrate ORCID iDs into life science databases.

The European Bioinformatics Institute (EMBL-EBI)  is a centre for research and services in bioinformatics, and is part of the European Molecular Biology Laboratory (EMBL). There are hundreds of life sciences resources serving the biomedical research community, and at the European Bioinformatics Institute a number of essential resources do not incorporate ORCID iDs in their workflows yet. To support the adoption of ORCID iDs in data repositories we envisioned a Hub which manages the programmatic communication with the ORCID registry, keeps track of relevant ORCID records and makes integration with ORCID as easy as possible. Furthermore the creation of an ORCID Hub avoids duplication of integration efforts for many repositories.

EBI ORCID Hub Overview

As a first milestone, the Hub allows EBI databases to easily add ORCID authentication, e.g. on submission forms. Because ORCID records may already contain some of the information that is necessary, submission forms can be automatically filled in using this information. In the last couple of months we worked heavily on improving the EBI ORCID Hub, and supported our first adopters MetaboLights and EMPIAR as they integrated ORCID iDs in their workflows.

MetaboLights is a database for metabolomic data and derived information. It holds data from metabolic experiments, as well as metabolite structures, their roles, and other related metadata. The EBI ORCID Hub allows MetaboLights’ submitters to authenticate their login using their ORCID iD.

MetaboLights registration form integrated with ORCID authentication

Our second adopter is EMPIAR, a repository of electron microscopy images in structural biology. Like MetaboLights, they are using the ORCID Hub to identify their submitters by ORCID iD and to easily autofill their submission form.

EMPIAR registration form integrated with ORCID

We are now focussing on milestone 2: expanding the Hub functionality to push information to the ORCID registry. In practice, this means that data repositories will be able to let their users claim records to their ORCID profile. Following this, we would like to begin keeping track of ORCID records that were claimed through our Hub, and managing this information for the databases linked to it. The idea is to let databases know when their records are being claimed, or when claimed records are changed. For those among you who want to build something similiar, and all the curious developers, we have deposited the code on GitHub (https://github.com/thor-project/ebi).

ORCID Integration Series: CERN

CERN is a hub for all things High-Energy Physics (or HEP for short). Nearly all researchers in the HEP field make CERN their home for all or part of their research careers. Most of these researchers maintain separate university affiliations as well, making the CERN research community a distributed decentralized global network. When we’re designing information services, we have to consider this global family and devise ways for them to keep track of all their research, all in one place, automatically. Fortunately for us, we can take advantage of third party services developed by our partners in THOR in order to add needed functionality in a way that’s consistent, reliable, and shares our Open Science values.

Inspire, the primary database for HEP literature, provides a number of ways for researchers at CERN and abroad to stay on top of what’s happening in their field. Inspire is a literature aggregator, meaning that it harvests metadata from a suite of HEP-relevant journals that users can then search for pertinent literature. This metadata then feeds other services, such as HEPData, the repository for supplementary publication data in HEP, and allows us to automatically generate author profiles. Handling much of this information automatically is a great benefit for our users, and it makes Inspire a rich source for information specific to research in HEP. But this usefulness naturally doesn’t extend to other systems or disciplines. Tapping into the ORCID iD system will let our users be identified in a variety of scholarly systems and will help them link their HEP work to any other area of their research life.

In the Inspire author profiles, we already had a homegrown system for pushing and pulling works information to and from ORCID. For those authors who have associated an ORCID iD with their profile (a process that formerly required manual entry and manual verification), we are able to append works information from Inspire to their ORCID record, and we are able to pull works information from their ORCID record to display on the External works tab in their Inspire profile. We have now extended this functionality with the ability to authenticate through ORCID for other Inspire functions. This authentication is in place for Inspire’s literature and author suggestion functions and for correction of authors. Further modification of Inspire data via ORCID authentication will be rolled out with the new release of Inspire slated for later this year.

This additional functionality is an extension of Inspire’s upgrade to an all-new version of its underlying Invenio platform. The completely overhauled Invenio 3 includes a module for ORCID authentication, making Inspire’s integration painless. And since Invenio is underneath all of CERN’s scientific information systems (Inspire, HEPData, and Zenodo), this means we’re one step closer to an interoperable platform for researcher outputs.

We’ve also implemented ORCID authentication in HEPData. HEPData gathers its bibliographic metadata from Inspire, and Inspire pulls information on data related to publications from HEPData and displays it in the relevant author’s profile. There is already a direct connection to Inspire, so logging in with ORCID isn’t necessary to make this author-publication-data triangle possible. However, users now have the option of logging in with ORCID to access HEPData’s review and submission functions, providing a third party authentication choice that’s compatible with other scholarly systems.

At CERN, we were able to implement ORCID authentication straight out of the box, making it a simple and practical choice to offer our users for unifying and managing their scholarly identification needs.

ORCID Integration Series: PANGAEA

This is the first in a series of posts describing how THOR partners have recently integrated ORCID in their disciplinary data repositories. This post describes ORCID integration in PANGAEA, the Data Publisher for Earth & Environmental Science.

PANGAEA is rolling out a new version of its website. Developers and designers are currently ironing out a few remaining open issues. The release is expected for autumn 2016. Among major improvements in search, design, and usability, a key new feature is the integration of ORCID.

The new feature enables existing PANGAEA users to connect their PANGAEA profile with their ORCID iD, as demonstrated in the video below. 

With this connection, PANGAEA obtains the validated ORCID iD of its users from ORCID. By connecting their ORCID iD, users can also choose to sign in to PANGAEA using ORCID, as an alternative to signing in using PANGAEA user credentials. This can be handy when a user is already signed in to ORCID, or it is quicker to recall ORCID credentials.

Obtaining the validated ORCID iDs of its users is significant for PANGAEA as, contrary to a researcher’s name, the iD is unambiguous: two researchers with the same name can be distinguished by their respective iDs. The iD is also persistent through possible changes in a person’s name: the same researcher may change marital status, or their name may appear in different permutations, at times appear with full name, initials for first name, and with or without middle name (initial). Furthermore, the iD is actionable and can be used to discover information about the researcher.

For researchers, the greatest advantage of connecting their ORCID iD to their PANGAEA profile is that PANGAEA can then record the relationships between dataset publication DOIs and contributor ORCID iDs. This information is then shared with the global network of PID infrastructures, and researchers benefit from automated updates to their ORCID Record for data published at PANGAEA, gaining unambiguous attribution for published datasets and benefiting from greater credit for sharing data early.

Let’s take a look at how the ORCID integration in PANGAEA is making a difference to Dr Alice Lefebvre, GLOMAR Associate Scientist at the MARUM Center for Marine Environmental Sciences of the University of Bremen.

Alice has recently joined ORCID and decided to claim the 14 data publications deposited at PANGAEA that she has authored. As a consequence, Alice gains a more complete ORCID Record, one that does not just include her journal article publications but also her authorship in data publications a record that better reflects her true contribution to the scientific record. Alice was also surprised to learn about DataCite and the overview DataCite provides about her contributions.

The upcoming release of the PANGAEA website automates the sharing of information with the global network of PID infrastructures. Authors of datasets published at PANGAEA who have connected their ORCID iD, like Alice, will benefit from a workflow that ensures information appears automatically and accurately on their ORCID Record.

This shows how far the integration between disciplinary repositories and the global network of PID infrastructures has come over the past years, and how the persistent identification of contributors and research artefacts together with infrastructures that aggregate, process, and share information about persistently identified resources are driving and shaping 21st-century attribution, credit, communication, and measurement of scholarly activity.

Want to Know More?
Readers interested in performing an ORCID integration in their own disciplinary repository can find more information in our recent report, ‘Demonstration of Services to Integrate ORCIDs into Data Records and Database Systems.

ORCID Integration in Disciplinary Data Repositories

Researchers need to be linked to their data. Within THOR, we’ve been busy developing approaches to support the inclusion of ORCID iDs in disciplinary data repositories and data publication workflows.

The results are published in our latest report, ‘Demonstration of Services to Integrate ORCIDs into Data Records and Database Systems’ (10.5281/zenodo.58971), where you can read about the successful integration of ORCID in the databases and services of three THOR partners, each serving a distinct discipline: PANGAEA for Earth and Environmental Sciences, EMBL-EBI for Life Sciences, and CERN for High-Energy Physics.

These integrations were applied to live and operational production systems. This means that researchers in these disciplines are already benefiting from automated persistent identifier linking and linkage-information sharing within the global network of persistent identifier infrastructures.

The report describes the common experiences and challenges as well as the specific concerns each institution faced. These case studies can therefore serve as models for other institutions looking at integrating ORCID in their own systems and workflows.

As a companion to the report, over the next month PANGAEA, CERN, and EMBL-EBI will contribute to a series of posts on the THOR blog that summarise their recent advancements with ORCID integration. We will demonstrate the benefits of ORCID integration, and offer a practical guide to performing your own integrations. 

If you have any questions, please email info@project-thor.eu for more information.

Year 1 in Review

It has been a year since THOR launched in June 2015 and a natural time to take stock of what the project has achieved and some of the ways that our understanding has matured.

In the THOR vision, persistent identifiers are the default. They are the new normal. And they are interlinked and embedded in the services that researchers use every day. They help researchers to get clear unambiguous credit for the full range of their work – articles, data, software, and more. They enable data centres, universities and funders to track the impact of the research that they enable. They enable publishers to fully incorporate data into scholarly communications. They support a new research infrastructure.

Taken together, this means better evidence-based research and credit where it is due.

The THOR partners are working to make this vision a reality.  We’ve made healthy progress. The THOR Dashboard helps to track activity in the persistent identifier space. If you visit it, you can see the month-to-month progress from years of data.


The dashboard currently tracks the activity of THOR partners DataCite and ORCID. DataCite is the leading provider of persistent identifiers for data. It assigns DOIs at over 700 and growing data centres around the world. ORCID is the leading provider of persistent identifiers for researchers.

The graph shows continued strong growth with over six million DataCite DOIs assigned to data and other research artefacts, and over two million ORCID IDs for individual researchers.

Over the past year, our research efforts have focused on better understanding how persistent identifiers can be more interoperable and better interlinked. We’ve published a report on how to overcome barriers between PID platforms for contributors, artefacts and organisations. We’ve also produced a report on persistent identifier linking in scholarly e-Infrastructure that extends the thinking about PIDs to cover institutions and funding information. This hard thinking is now resulting in new services to build up links between PIDs and exchange information about them.

We know that we can only achieve our vision by changing the way that the systems work – the ones used by researchers every day. In THOR’s first year, we’ve integrated ORCIDs into essential production services in life sciences, high energy physics, and earth and environmental sciences. This means that they can automatically link deposited datasets with a unique and persistent identifier for their contributors.

Through the website, social media, events and webinars we’ve shared and learned from you about how persistent identifier services can make a difference in research. We’ve talked to and heard from many thousands of people – researchers, data managers, administrators, funders, journal editors and publishers, and more. This has enriched our understanding and, we hope, will result in better services, more robust infrastructure, and more rapid adoption. Many of the events are recorded and are available on the THOR YouTube channel.

If you are passionate about the possibilities that persistent identifiers present for research, you may want to become an Ambassador. Ambassadors work together and with THOR partners to encourage wider understanding and adoption of persistent identifiers. To learn more about getting started with adopting and using persistent identifiers, you can also visit the Knowledge Hub.

THOR stands for technical and human infrastructure for open research. As you can see, we’ve been working hard throughout the first year to make a difference from both perspectives: new understanding, services, integrations; more listening, talking, and sharing what we learn.

We plan to be blogging over the coming weeks to share more about new persistent identifier services and integrations in production services.

Dynamic Data Citation Webinar

This blog post by Martin Fenner has been cross-posted from the DataCite blog.

On July 12, 2016, DataCite invited Andreas Rauber to present the recommendations for dynamic data citation of the RDA Data Citation Working Group in a webinar.


Andreas is one of the co-chairs of the RDA working group, and he gave a throughout overview of the recommendations, and the thinking that went into them. The final recommendations are available since last fall, and the current focus of the working group is to help with implementations.

The recommendations have to be implemented in the data center, but DataCite is happy to help coordinate the work, and to provide feedback to Andreas and the rest of the working group where needed. Of particular importance from a DataCite perspective is recommendation 8:

Query PID: Assign a new PID to the query if either the query is new or if the result set returned from an earlier identical query is different due to changes in the data. Otherwise, return the existing PID.

Assigning a persistent identifier (not only) when a dataset is originally generated, but also when a dataset is about to be cited, is central not only to the working group recommendations for dynamic data citation, but also crucial for other data citation use cases. Data exist at different levels, from raw data possibly generated by a machine, to highly processed data used in a publication. The figure below – presented by Robin Dasler from CERN at the THOR Workshop  on July 7 in Amsterdam – demostrates this for high-energy physics (HEP):


DataCite DOIs are intended as citation identifiers. They are persistent identifiers and provide standardized metadata, including links to associated publications, contributors and funders. They thus focus on the data in the top section of the pyramid. While we can also use DataCite DOIs for the other levels of the pyramid, sometimes other identifiers are more appropriate for raw, non-persistent data generated my machines. Dynamic data citation can be seen as a variant of the process that this pyramid describes.

If you could not attend last week or you want to review the session, the recording of the webinar is available:

The THOR project will work with interested data centers on dynamic data citation in the coming 12 months, hopefully leading to important feedback and a few more implementations of the RDA working group recommendations. Please contact us if you work for a data center and are interested in participating.

Highlights Workshop: Identifiers – Infrastructure, Impact and Innovation

On Thursday July 7 2016, project THOR organised the workshop: Identifiers – Infrastructure, Impact and Innovation to showcase the research and work done by all THOR partners during the project’s first year. The event in Amsterdam attracted a mixed audience of representatives from publishing companies, universities and research institutions.

After an introduction to the THOR project by Adam Farquhar (British Library), the day was divided into three sessions. The first one focused on persistent identifier linking, the next session on data publishing and the last one on THOR services. Slides of all presentations can be found on the THOR Knowledge Hub.

IMG_0654 (2)

Photo: Introduction to Project THOR and persistent identifiers

Persistent Identifier Linking

During the first session on persistent identifier linking, Martin Fenner (DataCite), Laura Rueda (DataCite) and Tom Demeranville (ORCID) explained more about challenges in linking data sets to other data sets, dynamic data and how to identify multiple versions of the same data set. The complexities involved in cross-linking databases and how to establish a fully interoperable system were discussed as well. Good quality metadata is crucial. Lack of standards and low adoption complicate matters even more. Despite these challenges, the THOR team has achieved a lot during the project’s first year. For example, THOR partners have contributed to the ORCiD auto update functionality and DataCite event data.

The ORCiD auto update functionality enables researchers to easily search and link their works via DataCite search to their ORCiD records and with DataCite’s event data it is possible to collect events, e.g. data citations in journal articles, around DataCite DOIs. These are great achievements and evidently, more research will be done by the THOR project to address the other challenges.

IMG_0664 (2)

Photo: Tom Demeranville, Martin Fenner and Laura Rueda presenting on persistent identifier linking

Data Publishing

The second session of the day focused on data publishing: Catriona MacCallum (PLOS), Michaela Torkar (F1000), Hylke Koers (Elsevier), presented on data policies in their respective publishing companies. A lot of data that is generated is not being published, because most authors only focus on article publication. A cultural change is needed as by the time a paper is submitted to a journal it is generally too late.

Martin Fenner (DataCite) agrees in his presentation that it is challenging to make the underlying data of a publication publically available and even if the data is made available it is not very accessible, for example because it is hidden in a file format like PDF. Other challenges for data-article linking are again the lack of good quality metadata and the fact that there is a wide range of data submission systems. Integrating persistent identifiers into the data publishing workflow might overcome these problems. However, globally unique identifiers should be used instead of local identifiers. Challenges for a centralized infrastructure are authentication and ownership for the data infrastructure management.


Photo: Josh Brown (ORCID) and Paul Groth introducing the publishing panel

After the presentations Paul Groth (Elsevier Labs) led a panel discussion on the challenges and opportunities of data publishing. Key questions that were discussed included: Should a publisher be responsible for data publishing? Or, are data repositories responsible for data publishing? These questions are not easily answered but all panellists agreed publishers should work together with researchers and other stakeholders to establish community standards for good quality data. The persistency of data accessibility is a stamp of approval, therefore good quality metadata and the use of persistent identifiers are crucial.

Next to these technical infrastructure requirements, it is evident a human infrastructure needs to be in place as well. Another question arose: Would authors commit to having their data accessible forever? According to the panel, incentives and a cultural change are needed for researchers to publish their data. In order to make this change and to achieve a shared infrastructure to push data publishing, more research and workshop discussions between the different stakeholders should take place. The THOR team will continue these discussions the coming months of the project.


Photo: Panel discussion on Data Publishing

THOR Services

In the final session of the day Florian Graef (EMBL-EBI), Markus Stocker (PANGAEA), Robin Dasler (CERN) and Laura Rueda (DataCite) presented on THOR Services. They gave demonstrations of ORCiD integration in data submission systems within their respective repositories in biological and medical sciences, earth and environmental sciences and high-energy physics.

The demonstrations of ORCiD integration within data set claiming services and workflows show clear advantages; see the example at EBI: there’s a wide variety of databases and maintenance of one single service is a lot easier. See the ORCiD integration within PANGAEA demonstration as well. Next steps for continued implementation of persistent identifiers within the research cycle across the different disciplines have been identified: claiming services for previously published data and alignment of identifiers.


Photo: Markus Stocker explaining more about ORCiD integration at PANGAEA

Of course, a lot more was discussed during the workshop so check out the presentations and please get in touch in case you were unable to join us and you have any questions! The coming year we will keep you up to date with further achievements of the THOR project through our blog posts and website. Thanks to everybody for their outstanding contributions to valuable discussions in Amsterdam and we welcome you at one of our next events!

July 7, 2016 THOR Workshop: Identifiers – Infrastructure, Impact and Innovation

Would you like to learn more about persistent identifiers, data-article linking, integration services, dynamic data citation, and much more? And how these interoperable research services will lead to opportunities for innovation and foster open science?

Join us on July 7, 2016 for our Workshop: Identifiers – Infrastructure, Impact and Innovation in Amsterdam!

Since its start in July 2015, Project THOR -Technical and Human infrastructure for Open Research – has been working towards seamless integration between articles, data, and researchers across the research lifecycle, and a lot has been accomplished. During this one-day workshop, the THOR team will demonstrate tangible outputs of the past year, how these achievements are benefiting the research community, and where we are going next.

Through demonstrations and expert talks, the THOR project partners British Library, ORCID, DataCite, Elsevier Labs, PLoS, EBI, CERN, and PANGAEA will showcase the research and concrete work done by the different disciplines. Challenges and opportunities for linking persistent identifiers as ORCID iDs and DOIs will be discussed by showing concrete examples from pilot communities (High-Energy Physics, Biological and Medical Sciences, Geoscientific and Environmental Sciences). Progress on DataCite DOI and ORCID iD auto-update, data publishing workflows, dynamic data identification and citation will be presented during a mixed programme of presentations and discussions.

The workshop is kindly hosted by Elsevier Labs, and is a great opportunity for research organisations, data scientists and publishers to get in touch with experts from different disciplines, share ideas and state-of-the-art practice and help to shape exciting new developments.

Register here!

The preliminary program:

9.00 Registration
9.30 Welcome to the day and Introduction to Project THOR

Adam Farquhar (The British Library)

10.00 THOR Research, persistent identifiers linking, ORCID auto update, presentations and Q&A

Martin Fenner (DataCite), Laura Rueda (DataCite), Tom Demeranville (ORCID EU)

11.00 Coffee break
11.30 Data Publishing Workflows, presentations followed by panel discussion

Paul Groth (Elsevier Labs), Catriona MacCallum (PLOS), Michaela Torkar (F1000), Martin Fenner (DataCite)

13.00 Lunch
14.00 THOR Services, presentations, demonstrations and Q&A

Markus Stocker (PANGAEA), Florian Graef (EMBL-EBI), Robin Dasler (CERN)

15.30 Concluding remarks and networking

Register here soon as we have limited spaces available! We hope to see you on July 7 in Amsterdam! Follow us on Twitter for updated announcements regarding the workshop. If you have any questions regarding this workshop, please get in touch!

EU Projects Collaboration Meeting – Events and Communications

A range of European and global initiatives is under way to support research practices and sharing in the digital era. To best serve diverse research communities with e-infrastructures and overarching services, Project THOR, in partnership with AARC and OpenAIRE, has organised a one-day meeting on Thursday June 2nd, at DANS in the Hague, to coordinate collaboration with other EU Horizon 2020 projects to identify co-working and cooperation opportunities. The meeting focused on the communication and outreach activities of the projects, and the following projects/organisations were represented: LEARN, INDIGO DataCloud, EGI, EDISON, EuroCRIS, FOSTER, READ, EUDAT, OpenDreamKit, PRACE, OpenMinTed, and LIBER.

It was a great opportunity to get so many representatives of EU H2020 projects altogether in one room and to discuss how to multiply the impact of all project efforts. Of course, all these different projects have different missions and objectives. For example, project THOR focuses on using persistent identifiers to enable an interoperable research infrastructure, OpenMinTed focuses on text and data mining, OpenDreamKit delivers an open digital research environment toolkit for the advancement of mathematics, and there are many more differences. However, all these projects contribute to the advancement of science by further developing and promoting wider use of research infrastructures throughout Europe and globally, and the target audiences for most of these projects overlap.

Some of the projects are already joining forces and organising webinars, workshops and conferences together. During the meeting all projects indicated their planned workshops and events on a timeline, this gave a clear picture for collaboration, and for identifying any gaps, for example if some of the research communities are underserved.

IMG_0606 (2)

Photo: Project representatives adding their workshops, webinars and events to the timeline.

Some of the upcoming events in June and July you don’t want to miss:

Next to events planning, other topics were discussed. For example the use of social media to promote events, the evaluation of events, sustainability of the projects, and how to deliver good quality trainings for all different research disciplines. Next to this, all projects will share other projects’ resources to make sure available training materrials are more widely disseminated and accessible for everybody. Some of the projects have a wide range of online training materials available, see for example the PRACE Training Portal and the EUDAT Training Programme. Keep an eye on all our websites for more training materials!

At the Digital Infrastructures for Research Conference in Krakow, the EU H2020 projects will continue discussions on co-organising events to best serve the entire research community and analyse any gaps. During this meeting, we will also discuss where the projects can support each other on a technical level. We will focus on research collaboration opportunities to make existing infrastructures better connected and interoperable and discuss possibilities of integrating services. By adding functionalities, we will strengthen what’s already there to further advance European research and innovation.


Photo: Project representatives of the various EU H2020 projects.

If you have any suggestions or questions, please get in touch during one of the events or contact us online. Keep an eye on our websites and social media accounts for announcements of more interesting workshops and events!




Organisation IDs for scholarly communications: where next?

On April 17, as part of FORCE 2016 in Portland Oregon, Crossref, and THOR partners DataCite and ORCID convened a workshop to discuss the current state of the art in organisation identifiers. We discussed this issue previously in a post on the ORCID blog, and we’re pleased to report back to you all that the workshop was a big success. Since then, we’ve been pulling together our notes and thoughts on the issue of organisation identifiers, and we’d like to share the headlines with you.

The community represented at the meeting agreed strongly with our conclusions that there is no solution available today that meets all the scholarly communications community’s needs. It is clear that the community needs a solution based on open data (for a community infrastructure such as this, CC-Zero is really the only appropriate license for the data). We need  a robust, high-volume API if we are to build infrastructure around organisation identifiers. This infrastructure needs to have transparent, community-led governance, and a responsive, properly resourced entity to maintain all of this.

The workshop was underpinned by a discussion document which gathered together existing work undertaken by NISO, Jisc and CASRAI, and others. These outlined the shortcomings of current approaches, and set out core requirements which any solution aiming to provide organisation identifiers for scholarly communications should address. While we acknowledge that there are commercial and community-led initiatives that offer partial solutions to the problems we face, they are focussed, naturally enough, on the needs of their sub-section of the community. For them to broaden their offer or to change their practice might not make commercial sense, or might not be possible (thanks to a lack of staff or technical infrastructure for example). That said, whatever comes next will need to work alongside these providers as a partner facing similar challenges and, with a bit of luck, sharing solutions.

What emerged from the workshop was a consensus that a detailed use-case-driven approach is a useful way to understand the core issues at work with identifying organisations, and more than this provides a good way to spot common issues. By placing these at the heart of a new organisation identifier infrastructure, we can help to create a service that will help to meet the needs of the widest possible section of our community.

We took a number of ideas away from the workshop:

  • There needs to be a collective action plan for the next three years to help to implement an organisation identifier solution for scholarly communications.
  • We need to think about the structure and governance (both for data and the parent organisation) that will best serve the community
  • We need a solid, core ID technology for both the highest level organisation and hierarchies beneath them
  • We need to define a robust, low-barrier, accessible mechanism for organisation to take ownership of their IDs, and to update them (each organisation needs to KNOW that they have an ID, to USE it, and to KEEP IT UP-TO-DATE for it to succeed).

We are starting this initiative by gathering as broad a sample as possible of the use cases you, the scholarly communications community, need organisation identifiers to address.

We invite interested members of the community to read our discussion document and to send their comments and use cases to us using our survey.

We’ll digest and analyse this information, and keep you all up to date. We’ll gather together and support the work of task groups where appropriate, to bring in expertise from the community. We’ll present reports, updates and proposals publicly to gather your feedback, and we will meet again at a co-convened persistent identifier-themed event in Reykjavik, Iceland, in the week beginning November 7. Hold the date, and watch this space!
Geoffrey Bilder, Josh Brown, and Patricia Cruse.