British Library DataCite Workshop University of Glasgow, 13 June 2014 Programme

Transcription

1 British Library DataCite Workshop University of Glasgow, 13 June 2014 Programme Welcome Intro #bldatacite #jiscmrd Intro to working with DataCite Applying DOIs to cite data Case study: University of Leeds Lunch DataCite technical services hands-on demo Final questions & Close

2 Working with the British Library and DataCite University of Glasgow June Elizabeth Newbold & Rachael Kotarski

3 Introduction to working with DataCite Background What is DataCite How it works DOIs Requirements Landing pages Persistence Metadata Schema Use

4 What is DataCite and why the need? A Registration Agency for DOI names providing a shared infrastructure for minting DOIs. Addressing the challenges of: Identifying datasets Citing data Linking articles and data Supports researchers by enabling them to locate, identify and cite research datasets with confidence Supports data centres by providing workflows and infrastructure to identify and cite datasets Supports publishers by enabling research articles to be linked to underlying data

5 DataCite timeline 2009: DataCite founded with 7 members : Pilot projects begin with Data Centres 16 full members; >1,000,000 DOIs registered DataCite metadata specification released Shared technical infrastructure established : Formal contracts sent to UK data centres BL-JISC data citation workshop series Grow to 11 UK clients Version 3 of Metadata Schema released 2014: 21 UK clients (as of June)

6 How does DataCite work? International DOI Foundation Member DataCite DataCite is: not for profit organisation a member of the IDF a Registration Agency for DOI names Member Institution Member Institution Member Institution Data Centre Data Centre Data clients Data Centre Data Centre Data clients Data Centre Data Centre Data clients

7 DOIs Persistent Identifiers: DOIs The Digital Object Identifier is a persistent identifier that directs users to an object, even if it changes location. If an object moves, the new location is given to the existing DOI, so that it directs users to the same object in the new location. Why DOIs? Global Widely adopted - most widely used identifier for research articles Governance and infrastructure Standardised - ISO 26324:2012

8 Anatomy of a DOI A DOI is formed of a prefix, in the form of 10.#### and a suffix, separated by / Assign a prefix to data centres unique to an organisation The format of the suffix is determined by the data centre unique for each object /chosen_by.DataCentre-1 Prefix Suffix These are used to form URLs by adding the resolving domain, e.g.:

9 British Library's role in DataCite International DOI Foundation Member DataCite Member Institution Data Centre Data Centre Data Client The British Library is one of 18 international members of DataCite We are an allocating agent We provide the DataCite infrastructure, enabling UK Data Centres to mint DOIs for data Although our aim is to support researchers, we do not work with individuals - they must deposit to a data centre

10 Who we are currently working with View online:

11 Why institutions? The persistence of identifiers can only be determined by the holders of the data So data must be stored some where that is accessible, and well managed for the long term This means that we need to make sure data centres we work with are appropriately managed for data curation and preservation

12 What is expected of an institution? We supply DOIs for datasets as long as a data centre: Provides mandatory metadata for its datasets Provides a landing page for each dataset Can maintain working URLs for its registered datasets Has trusted curation and preservation policies in place

13 Open Resolution Target (landing page) DOIs must resolve to a publicly accessible landing page The landing page must be open Describe the data objects and include at least the mandatory metadata and DOI

14 DOIs resolve to an open landing page

15 DOIs resolve to an open landing page

16 Data Persistence Data clients must: have a clear and public indication to preserve the data or have responsibility for providing access to the data over the long term How can this be satisfied? By having a formal data preservation plan An operational service level agreement Clear intention in a mission statement

17 Data Discovery Mandatory metadata must be provided according to the DataCite metadata scheme Metadata must be made freely available for discovery purposes Specifically under CC0 Develop and implement suitable quality control measures to ensure compliance with the metadata scheme

18 Aims of the metadata schema a core list of metadata properties chosen for accurate identification of data for citation and retrieval purposes Support citation and discovery of datasets Must be suitable for all types of data Must work with all disciplines and subjects domain agnostic Do this in the simplest manner

19 Metadata Schema DataCite Metadata Schema: Small mandatory element set for identification and the creation of citations DOI Title Creator Publisher Publication year

20 The Metadata Schema mandatory properties Identifier (with type attribute) A unique string that identifies a resource the allowed value is the DOI Creator (with type and name identifier attributes) The main researchers involved in producing the dataset Title (with optional type attribute) A name by which the resource is known Publisher PublicationYear Year in which the data was or will be made publicly available

21 Citation The mandatory metadata elements are required for registration and minting DOIs but also provide the elements for the citation. Recommend citation style: Creator (Publication Year): Title. Publisher. Identifier Rees, A.P.; (2012): Impact of phosphate and iron fertilisation on rates of nitrogen fixation in surface waters by stable-isotope mass spectrometry during the FEEP programme cruise PO311. British Oceanographic Data Centre (BODC), Natural Environment Research Council (NERC). A18A-1F9AC95AA7BF

22 Citation

23 The Metadata Schema optional and recommended properties These properties help describe the dataset by providing the opportunity for more detailed description Recommended properties (R) Subject Contributor Date ResourceType RelatedIdentifier Description GeoLocation Optional properties (O) Language AlternativeIdentifier Size Format Version Rights

24 Useful information: Slides from workshops, FAQS etc: DataCite metadata schema: DataCite metadata Google discussion group: datacite-metadata Videos of minting DOIs: Using the DataCite store 1: Using the DataCite store 2:

25 Using DOIs to cite data Versioning Granularity Restricted data

26 What should I put a DOI on? There are various things to consider: You should follow best practice, may need to consider best practice of many communities DOIs cannot express relationships DataCite metadata accommodates a variety of relationships

27 Caution! You cannot delete a DOI Mandatory metadata should not be changed You should be clear on your policy, but it may also need to be adaptable

28 Versioning Data should be cited so that others can replicate your work. Either for comparison or reuse If the data changes after citation, how can it be validated? An adaptable policy, considering: Will all updates require a new DOI: Minor or major changes How to manage versions: Waves, slices or full copies Format changes? Image from Flickr user Diana Beideman CC-BY-NC-SA

29 Versioning - metadata Version - an optional field to record version number can be used in conjunction with Related Identifier to indicate various updates RelatedIdentifier field options: IsContinuedBy Continues IsNewVersionOf IsPreviousVersionOf IsVariantFormOf IsOriginalFormOf IsIdenticalTo

30 Updated data: Versioning

31 Versioning useful links There are various community approaches to this: Data citation and linking (DCC): Data Citation Guidelines for Data Providers and Archives (ESIP):

32 Granularity Researchers may only use or want to cite a small section of a full dataset Sensible unit of citation without becoming unmanageable

33 Granularity Example taken from Simon Cole s (Southampton) presentation, Dec 2012

34 Granularity - metadata relatedidentifier field options: IsPartOf HasPart IsCompiledBy Compiles IsSupplementTo Supplements

35 Restricted data We only require the landing page to be open Data may be embargoed, restricted to academics behind a paywall Use the rights property in the metadata scheme Information on restrictions should also ideally be recorded on the landing page If data can never be used by anyone, consider whether a DOI is needed Image from Flickr user robokow CC-BY

36 Thank you Web: search.datacite.org

37 References Great new guide for those setting up and managing a data archive/repository: Managing and Sharing Research Data (2014). Corti L., Van den Eynden V., Bishop L., Woollard M. Nice article on how data sharing is not pre-publication : The latest weapon in publishing data: the Polar Bear. (2014). Edmunds S.