Project

General

Profile

Revision 9780

Added by Chris Jones over 4 years ago

Merge changes from the 2.6.0 release.

View differences:

genericGuide.tmpl
1 1

  
2
	<!-- CONTENT SECTION
3
    ======================================================================= -->
4
	<article id="RegistryGuide">
2
	<article style="font-size: .5em" id="RegistryGuide">
5 3
		<div class="container">
6 4
		
7 5
			<div class="row-fluid">
......
11 9
				</p>
12 10
				<p>
13 11
					This guide provides information on how to complete the registration form.
14
					There are up to 11 sections to the form; some fields are required (denoted by an asterisk *),
15
					while others are optional.
12
					There are multiple sections to the form, and some fields are required
13
					(denoted by an asterisk * or in a tooltip), while others are optional.
16 14
				</p>
17 15
				<p>	
18 16
					Information on individual fields and examples for their content are provided below.
......
20 18
			</div>
21 19
			
22 20
			<div class="row-fluid">
23
				<h4><a name="Submitter">Submitter</a></h4>
21
				<h4><a name="BasicInformation">Basic Information</a></h4>
24 22
				<p>
25
					<span class="text-info">*First name, *Last name: </span>
26
					The first and last names of the person completing this form.
23
					*Data Set Title:
24
					A descriptive title of the data set. The title should
25
					provide enough information for someone casually scanning a list of data
26
					sets to know whether the data are relevant to them. This implies that the
27
					data context should be indicated in the title without making the title be
28
					too long. In general, the title should indicate what kind of data were
29
					collected and the spatial, taxonomic, and temporal extents the data set
30
					covers.
27 31
				</p>
28
				
29
			</div>
30
			
31
			<div class="row-fluid">
32
				<h4><a name="BasicInformation">Basic Information</a></h4>
33 32
				<p>
34
					<span class="text-info">*Data Set Title:</span>
35
					A descriptive title
36
					of the data set. The title should provide enough information for
37
					someone casually scanning a list of data sets to know whether the data are
38
					relevant to them.  This implies that the data context should be indicated 
39
					in the title without making the title be too long. In general, the title
40
					should indicate what kind of data were collected and the spatial,
41
					taxonomic, and temporal extents the data set covers.
33
					Funding: Add the award number from the funding agency. Type in
34
					a keyword to look up award numbers. Multiple award numbers can be separated by commas.
42 35
				</p>
43 36
				
44
				<div class="span6">
37
				<div>
45 38
					<em>Examples of descriptive titles: </em>
46 39
					<ul>
47 40
						<li>Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988.</li>
48 41
						<li>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</li>
49 42
					</ul>
50 43
				</div>
51
				<div class="span6">
44
				<div>
52 45
					<em>Examples of incomplete titles: </em>
53 46
					<ul>
54 47
						<li>Mammals Data</li>
......
56 49
					</ul>	
57 50
				</div>
58 51
					
59
[% IF cfg == 'nceas' %]
52
				[% IF cfg == 'nceas' %]
60 53
				<span class="text-info">*NCEAS Project(s):</span>
61 54
				<p>Select one or more
62 55
					NCEAS activities from the list to indicate that the data set is
......
68 61
					sets that contribute to synthesis can be included in the repository and should
69 62
					be associated with the appropriate NCEAS activities.
70 63
				</p>
71
[% END %]
64
				[% END %]
72 65

  
73
[% IF cfg == 'esa' || cfg == 'ltss' %]  
66
				[% IF cfg == 'esa' || cfg == 'ltss' %]  
74 67

  
75 68
				<span class="text-info">*Organization Name:</span>
76 69
				<p>The name of the organization with which the data set is
......
80 73
					set was generated; that the data set is owned by the organization; etc.
81 74
				</p>
82 75
				
83
				<div class="span6">
76
				<div>
84 77
					<em>Examples of correct organization names: </em>
85 78
					<ul>
86 79
						<li>University of Michigan Biological Station</li>
......
88 81
						<li>National Center for Ecological Analysis and Synthesis</li>
89 82
					</ul>
90 83
				</div>
91
				<div class="span6">
84
				<div>
92 85
					<em>Examples of incorrect organization names: </em>
93 86
					<ul>
94 87
						<li>Michigan Station</li>
......
97 90
					</ul>	
98 91
				</div>				
99 92

  
100
[% END %]
93
				[% END %]
101 94

  
102
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
95
				[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
103 96

  
104 97
				<span class="text-info">*[% config.site | ucfirst %] Name:</span>
105 98
				<p>Select a [% config.site %] from the drop-down list to indicate that the data set is
......
116 109
					with a locality keyword.
117 110
				</p> 
118 111

  
119
[% END %]
112
				[% END %]
120 113

  
121 114
			</div>
122 115
			
123 116
			<div class="row-fluid">
124
				<h4><a name="DataSetOriginator">Principal Data Set Owner</a></h4> 
117
				<h4><a name="DataSetOriginator">People and Organizations</a></h4> 
125 118

  
126
				<p>The person responsible for developing the data set. For example, the principal 
127
					investigator in a collaborative project, the first author of the main publication using the data set, etc. 
128
					The first and last names of the principal data set owner are required; the organization name, e-mail, phone, fax, and
129
					address information are optional.
119
				<p>
120
					Add one or more people, organizations, or position names
121
					associated with the dataset. At least one entry with a Creator role is
122
					required, and creators will be listed in the dataset citation. The person
123
					responsible for developing the data set. Other roles include, for example,
124
					the principal investigator in a collaborative project, the first author of
125
					the main publication using the data set, etc. The organization name, e-mail,
126
					online link, phone, fax, and address information are optional.
130 127
				</p>
131

  
132
				<p><em>Note: </em>If there is more than one owner, information 
133
					about the co-owner(s) can be provided in the <em>Associated Parties</em> section below.
128
				<p>
129
					Use the Add Person or Organization button to add entries to
130
					the list. Use the Edit icon (pencil) to change an entry. Use the Update
131
					Person or Organization button to update the entry, or Add Person or
132
					Organization to duplicate a changed entry. If you have entered several
133
					associated parties and want to change the order in which they appear, use
134
					the up and down arrows.
134 135
				</p>
135 136

  
136
				<p><span class="text-info">*First Name:</span>
137
				The first name of the principal data set owner.</p>
137
				<p>*First Name: The given name(s) of the person.</p>
138 138
				
139
				<p><span class="text-info">*Last Name:</span>
140
				The last name (surname) of the principal data set owner.</p>
139
				<p>*Last Name: The last name (surname) of the person.</p>
141 140
				
142
				<p><span class="text-info">Organization Name:</span>
143
				The name of the organization from which the data set
144
				originated.</p>
141
				<p>Organization Name: The name of the organization from which
142
				the data set originated, if any</p>
145 143
				
146
				<p><span class="text-info">E-Mail:</span>
147
				The e-mail address by which the principal data set owner can be contacted.</p>
144
				<p>Position Name: A named position in an organization from which
145
				the data set originated, if any.</p>
146

  
147
				<p>E-Mail: The e-mail address by which the person or organization can be contacted.</p>
148 148
				
149
				<p><span class="text-info">Phone:</span>
150
				The phone number of the principal data set owner, including the area code (999-999-9999).</p>
149
				<p>Phone: The phone number of the person or organization, including the area code (999-999-9999).</p>
151 150
				
152
				<p><span class="text-info">FAX:</span>
153
				The fax number of the principal data set owner, including the area code (999-999-9999).</p>
151
				<p>FAX: The fax number of the person or organization, including the area code (999-999-9999).</p>
154 152
				
155
				<p><span class="text-info">Street Information:</span>
156
				A comma-separated list of street number, street, unit,
153
				<p>Street Information: A comma-separated list of street number, street, unit,
157 154
				etc.<br> <em>Example: </em> 735 State Street, Suite 300</p>
158 155
				
159
				<p><span class="text-info">City:</span>
160
				The city
161
				name of the principal data set owner's address.</p>
156
				<p>City: The city name of the person or organization's
157
				address.</p>
162 158
				
163
				<p><span class="text-info">U.S. State or Territory:</span>
164
				Select a U.S. state or territory from the drop-down menu for the principal data set owner's address. If the address is not in 
165
				the United States, used the "Other State/Province" field below. For a shortcut,
166
				press the first letter of the state on your keyboard (e.g.,  M-key to skip to Maine).</p>
159
				<p>U.S. State or Territory: Select a U.S. state or territory
160
				from the drop-down menu for the principal data set owner's address. If the
161
				address is not in the United States, used the "Other State/Province" field
162
				below. For a shortcut, press the first letter of the state on your keyboard
163
				(e.g., M-key to skip to Maine).</p>
167 164
				
168
				<p><span class="text-info">Other State/Province:</span>
169
				A non-U.S. state or a province for 
170
				the principal data set owner's address.</p>
165
				<p>Other State/Province: A non-U.S. state or a province for the
166
				person or organization's address.</p>
171 167
				
172
				<p><span class="text-info">Postal Code:</span>
173
				The postal code or ZIP code
174
				for the principal data set owner's address.</p>
168
				<p>Postal Code: The postal code or ZIP code for the person or organization's address.</p>
175 169
				
176
				<p><span class="text-info">Country:</span>
177
				The country
178
				for the principal data set owner's address.</p>
170
				<p>Country: The country for the person or organization's
171
				address.</p>
179 172
			
180 173
			</div>
181
			
174
						
182 175
			<div class="row-fluid">
183
				<h4><a name="AdditionalOriginators">Associated Parties</a></h4> 
184

  
185
				<p>If applicable, enter the first and last names of an associated party (e.g., co-owner of the data set, a data custodian/steward, a metadata provider, a user of 
186
				the data set), select a role for this person, and click on "Add Associated Party".  Repeat to add another associated party.</p>
187

  
188
				<p>To edit an entry, click on the name of the person entered, change the name and/or 
189
				the role, and click on the area just right of the drop-down menu for the role (the text fields and the drop-down menu will disappear). To delete an entry, click on the "X". 
190
				If you have entered several associated parties and want to change the order in which they appear, use the blue up and down arrows.</p>
191
				
192
			</div>
193
			
194
			<div class="row-fluid">
195 176
				<h4><a name="DataSetAbstract">*Data Set Abstract</a></h4>
196 177
				<p>Short (maximum of 350 words) summary of the purpose and content of the data set. 
197 178
					Entering a data set abstract is required.
......
380 361
					digital (e.g., computer file) or hardcopy (e.g., paper), or specify any other type of data medium the data are recorded on (e.g., video tape).
381 362
				</p>
382 363
				<p>
383
					<span class="text-info">*Usage Rights:</span> Specify the usage rights that apply
384
					to the data set (e.g., no restrictions, obtain permission from data set owner(s), cite the data set in publications, etc.). 
364
					*Usage Rights:
365
					[% IF cfg == 'metacatui' &&  config.abbrev == 'ARCTIC' %]
366
						Choose either the:
367
						<ul>
368
							<li>
369
								<a href="https://creativecommons.org/publicdomain/zero/1.0/">
370
									Creative Commons Public Domain Dedication (CC-0)
371
								</a>
372
							</li>
373
							<li>
374
								<a href="https://creativecommons.org/licenses/by/4.0/">
375
									Creative Commons Attribution License(CC-BY)
376
								</a>	
377
							</li>
378
						</ul>
379
						Choosing CC-0, you waive your interest in your work and place the
380
						work as completely as possible in the public domain so others may freely
381
						use the work without restriction under copyright or database law.
382
						Attribution for your work is still expected according to norms in your
383
						research field. Choosing CC-BY licenses your work, and you let others
384
						copy, distribute, display, and perform your copyrighted work, and
385
						derivative works based upon it, but only if they give you appropriate
386
						credit. For more information on choosing, see the
387
						<a href="https://blog.datadryad.org/2011/10/05/why-does-dryad-use-cc0/">Dryad discussion</a> 
388
						and the 
389
						<a href="http://www.bitlaw.com/copyright/unprotected.html">Bitlaw commentary</a>.
390
					[% ELSE %]
391
						Specify the usage rights that apply to the data set (e.g., no restrictions, 
392
						obtain permission from data set owner(s), cite the data set in publications, etc.). 
393
					[% END %]
385 394
				</p>
386 395
				<p>
387 396
					<span class="text-info">URL:</span> If available, provide a link for the
388 397

  

Also available in: Unified diff