LISA VIII 69 June 2017 Dominic Bordelon Library Technology Specialist ESO Libraries LISA VIII 7 June 2017 2 Digital Object Identifiers persistent globally unique resolvable Can be assigned to publications data ID: 603649
Download Presentation The PPT/PDF document "First Light for DOIs at ESO" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
First Light for DOIs at ESO
LISA VIII, 6-9 June 2017
Dominic Bordelon
Library Technology Specialist
ESO LibrariesSlide2
LISA VIII, 7 June 2017
2
Digital Object Identifiers: persistent, globally unique, resolvable
Can be assigned to publications, data,
physical objectsExample: 10.18727/0722-6691/5000Resolvable by prepending https://doi.org/Citable (unambiguously)As a URL, avoids link rotMachine-readable when citedRepositories offer (linked) metadata (for humans and machines)
Why DOIs?
DOI prefix
ESO
Suffix (arbitrary)Slide3
LISA VIII, 7 June 2017
3
Initiated by the Library
Articles in quarterly publication
The MessengerProduced by the education and Public Outreach Department (ePOD)Observing programmes and runs (raw data)Data products (reduced/processed data)Produced by the Science ArchiveIn particular: for citationWhy DOIs at ESO?Slide4
LISA VIII, 7 June 2017
4
A Registering Authority
A “landing page” for every resource
I.e., a DOI cannot resolve directly to a data file or article PDFUpload resource metadata to Registering AuthorityNeeds to be formatted in a certain wayTen-year promise for persistenceRequirements for DOIsSlide5
LISA VIII, 7 June 2017
5
Typical project and software questions
E.g., choices of language and DB, staffing
…Multiple departments want to use them, so…Who is responsible ESO-wide for DOIs? (A: Library)Who is responsible in each department?How to deal with diverse technologies and needs among departments?How to translate metadata describing different kinds of resources into a common format?How to make a system that future, unknown clients will also be able to use?Questions to considerSlide6
LISA VIII, 7 June 2017
6
Mid 2015: began discussions within Library and with Archive/
ePOD
Which Registering Authority? DataCiteTechnische Informationsbibliothek (TIB)March 2016: contract with TIBAugust 2016: development startedFebruary 2017: minimum viable productMarch 2017: launched with first DOIsESO Planning & TimelineSlide7
DOI Service
[ESO Library]
DOI Registration
and Metadata Upload
Science Archive
ePOD
(Messenger)
Others at ESO?
🌎
Landing pages at
doi.eso.org
(After reg., DOIs resolve to
…)
Architecture & Process
= HTTPSlide8
8
DOI Minting ExampleSlide9
9
DOI Minting ExampleSlide10
10
DOI Minting ExampleSlide11
11
DOI
Minting ExampleSlide12
12
DOI
Minting ExampleSlide13
13
DOI
Minting ExampleSlide14
LISA VIII, 7 June 2017
14
Decoupled from other departments’ applications and servers
HTTP interface
DOI Service and a department can be black boxes to one anotherDataCite Metadata Schema (DCMS) as data modelE.g.: Messenger author and Archive PI both become “creator” in DCMSCrosswalks between departments and DCMS are necessaryDataCite XML is the system’s most important output“DOIs as a service” for ESO departments
Programming ArchitectureSlide15
LISA VIII, 7 June 2017
15
Example record:
https://doi.org/
10.18727/0722-6691/5001Namespacing within ESO’s DOI prefixServe custom landing pages (e.g., per department)Next-consecutive-integer DOI mintingMachine-readable metadata embedded on landing pages (view source)schema.org/JSON-LD for discovery (e.g. by Google)<meta name=“DC.{field}” …> tags for reference managers
FeaturesSlide16
LISA VIII, 7 June 2017
16
Improve automation among departments
Science Archive’s implementation
“On-the-fly” DOI’s? (like STScI)What’s next?Slide17
LISA VIII, 7 June 2017
17
How
to deal with diverse technologies and needs among departments
?Decoupled architecture + HTTP interfaceHow to translate metadata describing different kinds of resources into a common format?DCMS as data model + crosswalksA system that future, unknown clients will also be able to use
ConclusionsSlide18
Meeting XYZ, X Dec 2020, Confidential/ESO Internal Use/Public
18
Machine-readability (e.g., using DOIs) is needed
for Big
Data;DOIs are integral for an effective Open Science ecosystem.ConclusionsSlide19
LISA VIII, 7 June 2017
19
Dominic Bordelon, Library Technology Specialist
@
dominicbordelondominic.bordelon@eso.orgESO Libraries team: (library@eso.org)Uta Grothkopf, Head LibrarianSilvia Meakins, Library Technology SpecialistMaría
Eugenia Gómez, Librarian (Chile)Thanks