Patricia Feeney – 2019 September 13
We’ve all been subject to floods of conference invitations, it can be difficult to sort the relevant from the not-relevant or (even worse) sketchy conferences competing for our attention. In 2017, DataCite and Crossref started a working group to investigate creating identifiers for conferences and projects. Identifiers describe and disambiguate, and applying identifiers to conference events will help build clear durable connections between scholarly events and scholarly literature.
Chaired by Aliaksandr Birukou, the Executive Editor for Computer Science at Springer Nature, the group has met regularly over the past two years, collaborating to create use cases and define metadata to identify and describe conference series and events. We first asked for input on metadata specifications in April 2018. Technical implementation kicked off in February with a workshop at CERN to discuss the mechanics of making PIDs for conferences a reality.
Crossref has supported a number of conference publication-related PIDs for years - members can currently register PIDs for conference series publications, conference proceedings, and of course individual conference papers - and that won’t change, but we will also be supporting DOI registration for conferences. A crucial step towards this is of course integrating the new identifier into our metadata input schema.
We currently collect some limited metadata describing the conference itself such as theme, location, and dates as part of the conference series or proceeding metadata, but do not apply a DOI to that information. The new Conference ID records will include expanded metadata as defined by the working group. You’ll be able to register a distinct metadata record for a single conference. You’ll also be able to register a record for a conference series, and connect Conference IDs to conference proceeding metadata records and DOIs.
Changes to the conference-specific metadata are backwards compatible. Members will be able to register event metadata per usual, or can instead use the new event metadata to register an identifier for their conference event and/or series. This means a member can:
I’ve written up our proposal in this google doc and we want your feedback before we proceed with implementation. Please comment directly in the Google doc, open a Gitlab issue, or email@example.com. We’ll keep the document open for comments until September 30.
2020 January 14
2020 January 13
2019 December 17
2019 December 11