-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy path01-register-doi.html
More file actions
178 lines (176 loc) · 9.18 KB
/
01-register-doi.html
File metadata and controls
178 lines (176 loc) · 9.18 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
<!DOCTYPE html>
<html>
<head>
<title>Author Carpentry</title>
<link rel="stylesheet" href="css/site.css">
</head>
<body>
<header>
<a href="http://authorcarpentry.github.io"><img src="img/AClogo.jpg" alt="Author Carpentry logo"></a>
</header>
<nav>
<ul>
<li>
<a href=".">Lesson</a>
</li>
<li>
<a href="00-intro-dois.html">Intro</a>
</li>
<li>
<a href="01-register-doi.html">Register a DOI</a>
</li>
<li>
<a href="mailto:authorcarpentry@library.caltech.edu">Contact Us</a>
</li>
</ul>
</nav>
<section>
<h1 id="register-a-doi">
Register a DOI
</h1>
<p>
15 min
</p>
<hr />
<p>
Learning Objectives:
</p>
<ul>
<li>
Register a DOI for a scholarly work using an open repository (Zenodo)
</li>
<li>
Create appropriate metadata to describe a new work
</li>
</ul>
<hr />
<h2 id="open-repositories">
Open repositories
</h2>
<p>
Open science and <a href="https://www.force11.org/group/fairgroup/fairprinciples">FAIR principles</a> encourage scholars to put more of their content online in an open format. Scholarly works can be added online repositories that centralize, store, and share the results. Most repositories will be associated with a DOI Registration Agency and will generate DOIs for every item that is stored. Generating a DOI is one factor that you can use to determine whether a repository is trustworthy. There are different types of repositories that may be appropriate for your scholarly works.
</p>
<h3 id="domain-specific-repositories">
Domain-specific repositories
</h3>
<p>
There are many repositories that focus on a specific type of data or data from a certain field. If one exists for your data, subject specific repositories are great because individuals looking for a specific type of data will know to check that repository. A subject-specific repository can collect data from researchers around the world and customize the way the data is displayed. This can make it easier to find and reuse the data. One challenge for domain-specific repositories is ensuring a consistent source of funding-you should monitor the repositories you use to ensure that your data remains available.
</p>
<p>
You can find a good listing of subject-specific repositories at <a href="http://journals.plos.org/plosone/s/data-availability#loc-recommended-repositories">PLOS</a>.<br /> A more complete list of repositories is available at <a href="http://www.re3data.org">re3data</a>
</p>
<h3 id="institutional-repositories">
Institutional repositories
</h3>
<p>
Many institutions host data repositories, often through the library, to preserve the data collected at the institution. These repositories are often general and can take any scholarly works that are associated with the institution. Because these repositories are associated with an institution, they may have a more consistent source of funding. However, they often do not have the customization available in a domain-specific repository.
</p>
<p>
An example of an institutional data repository is <a href="https://data.caltech.edu">CaltechDATA</a>
</p>
<h3 id="general-repositories">
General repositories
</h3>
<p>
A number of general repositories exist that can collect any type of scholarly output. These can be associated with a publisher, like <a href="https://data.mendeley.com/">Mendeley Data</a> or <a href="https://figshare.com/">Figshare</a>. Some institutions also run general repositories that are open to all, like the <a href="https://dataverse.harvard.edu/">Harvard Dataverse</a>, <a href="http://datadryad.org/">Dryad</a>, or <a href="https://www.zenodo.org/">Zenodo</a>. These general repositories can be free (Mendeley Data, Harvard Dataverse, Zenodo), charge per submission (Dryad), or have size limitations (Figshare). We’re going to use Zenodo because it is free, open, and associated with CERN which provides institutional backing and permanance.
</p>
<h2 id="generating-a-doi-with-zenodo">
Generating a DOI with Zenodo
</h2>
<p>
To begin, go to <a href="https://www.zenodo.org/">Zenodo</a> and get an account by clicking the sign up button in the upper right hand corner. Then click the ‘Upload’ link at the top of the screen and the green ‘New Upload’ button. You’ll see a place to drag and drop the files you’re going to upload. Then click the green upload button.If the uploader gives an error message you may have to refresh the page first.
</p>
<p>
Click on the “Reserve a DOI button”. You’ll get a DOI that you can use to reference your scholarly content, but it wont’t resolve until you publish your record.
</p>
<p>
Next, you’ll have to enter the metadata that describes your scholarly work, some of which will be registered with your DOI.
</p>
<h3 id="basic-information">
Basic Information
</h3>
<p>
First, select the type of object you’re uploading. Is it a publication, poster, presentation, data set, image, video/audio, software, or lesson? You can have multiple individual files associated with a Zenodo record, and you’ll want to group them in bunches that other users would want to download together. For example, if you have lots of data files from the same experiment you would want to upload them to one record. If you have presentations on different topics you would want to upload them to separate records.
</p>
<p>
In most cases you’ll want to let Zenodo add the DOI and publication date.<br /> Next, enter a title, authors, and description. Make your description detailed enough so that others can understand the files you’re uploading. It’s also good to enter some keywords to enable discovery.
</p>
<h3 id="access-and-licensing">
Access and Licensing
</h3>
<p>
Zenodo allows your files to be open, embargoed, restricted, or closed. Embargoed files become public on a selected data. Access to restricted files can provided to specified users, and closed files are completely restricted. Because we’re doing open science, select open!
</p>
<p>
You should select a standard license for your files. There is a lot of issues to consider when selecting a license, and we have an entire <a href="https://authorcarpentry.github.io/licensing-cc/">lesson</a> on the topic. For data sets a “Creative Commons Zero” license is a good choice. For presentations and images a “Creative Commons Attribution 4.0” license is a good choice. On Zenodo you sometimes have to type out the entire license name before it finds it.
</p>
<h3 id="communities">
Communities
</h3>
<p>
Zenodo has user-selected communities of records. These are self-organizing classifications, and there may or may not be one that matches your work.
</p>
<h3 id="funding">
Funding
</h3>
<p>
The funding field in Zenodo is specific to European Union grants (FP7 and Horizon 2020 programs). If you get funding under these programs your work will automatically be reported. Zenodo currently recommends you add additional funding in the “Additional Notes” field (this is less than optimal).
</p>
<h3 id="related-identifiers">
Related Identifiers
</h3>
<p>
Related identifiers are a way to connect different works together. For example, let’s say you have a data set that is associated with a paper. You can add the paper DOI to Zenodo as a related identifier with “is supplemented by this upload” as the description in the second field.
</p>
<p>
Note: This relation is registered with type “is supplemented by” with DataCite because all DataCite related identifiers are in referenced to the registered work.
</p>
<h3 id="contributors-and-other-metadata">
Contributors and Other Metadata
</h3>
<p>
You can provide some basic descriptions of contributors to a work that are not authors. Your options are a bit more basic than discussed in the <a href="https://authorcarpentry.github.io/contributor-and-credit/">attribution lesson</a>.
</p>
<p>
There other more specialized metadata categories for References, Subjects, and other descriptors. These may or may not be relevant to your work.
</p>
<h2 id="finishing-up">
Finishing up
</h2>
<p>
Once you have your metadata entered, click Save. Then click Publish to share your record. You’ll see that Zenodo brings you to the public record page for your work. Zenodo provides a citation that includes your newly created DOI. We’ll be using this DOI throughout the rest of the workshop.
</p>
<h2 id="getting-metadata">
Getting Metadata
</h2>
<p>
We can utilize the first set of skills for getting metadata from a DOI on the DOI we just got from Zenodo. We’ll utilize DataCite instead of CrossRef, but it works exactly the same. In your web browser go to:
</p>
<p>
https://api.datacite.org/works/10.5281/zenodo.6780628
</p>
<p>
substituting your DOI. We can also get citations. In a terminal window type
</p>
<p>
curl -LH “Accept:text/x-bibliography; style=apa” https://doi.org/10.5281/zenodo.6780628
</p>
<p>
and you’ll get a APA formatted ciation for your new scholarly work!
</p>
<hr />
<p>
Previous: <a href="00-intro-dois.html">Anatomy of a DOI</a>
</p>
</section>
<footer>
<span>© Lesson Contributors</span>
<span><a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img
alt="Creative Commons License" style="vertical-align: middle;"
src="https://i.creativecommons.org/l/by/4.0/80x15.png" /></a></span>
<span>This work is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution
4.0 International License</a></span>
</footer>
</body>
</html>