Project

General

Profile

1
[% INCLUDE $templates.header %]
2

    
3
	<!-- CONTENT SECTION
4
    ======================================================================= -->
5
	<article id="EntryReview">
6
		<div class="container">
7
		
8
			<div class="row-fluid">
9
				<h2>Registry Guide</h2>
10
				<p class="lead">
11
					Guide for Completing the Data [% config.type %] Form
12
				</p>
13
				<p>
14
					This guide provides information on how to complete the registration form.
15
					There are up to 11 sections to the form; some fields are required (denoted by an asterisk *),
16
					while others are optional.
17
				</p>
18
				<p>	
19
					Information on individual fields and examples for their content are provided below.
20
				</p>
21
			</div>
22
			
23
			<div class="row-fluid">
24
			
25
				<h4>NAME OF SUBMITTER</h4><a name="Submitter"></a>
26
				<span class="text-info">
27
					*First name, *Last name:
28
				</span>
29
				<p> 
30
					The first and last names of the person completing this form.
31
				</p>
32
				
33
			</div>
34
			
35
			<div class="row-fluid">
36
				<a name="BasicInformation"></a>
37
				<h4>BASIC INFORMATION</h4>
38
				<span class="text-info">*Data Set Title:</span>
39
				<p>A descriptive title
40
				of the data set. The title should provide enough information for
41
				someone casually scanning a list of data sets to know whether the data are
42
				relevant to them.  This implies that the data context should be indicated 
43
				in the title without making the title be too long. In general, the title
44
				should indicate what kind of data were collected and the spatial,
45
				taxonomic, and temporal extents the data set covers.</p>
46
				
47
				<div class="span6">
48
					<u>Examples of descriptive titles:</u>
49
					<ul>
50
						<li>Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988.</li>
51
						<li>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</li>
52
					</ul>
53
				</div>
54
				<div class="span6">
55
					<u>Examples of incomplete titles:</u>
56
					<ul>
57
						<li>Mammals Data</li>
58
						<li>Water Chemistry Data</li>
59
					</ul>	
60
				</div>
61
					
62
[% IF cfg == 'nceas' %]
63
				<span class="text-info">*NCEAS Project(s):</span>
64
				<p>Select one or more
65
					NCEAS activities from the list to indicate that the data set is
66
					affiliated with that working group or activity.  We use "affiliation" 
67
					in a rather permissive sense to mean, for example, that the data set was or has
68
					been generated by the activity; that the owner of the data is affiliated
69
					with the activity; that the data set is owned by the activity; etc. Both
70
					derived data sets that result from synthesis activities and original raw data
71
					sets that contribute to synthesis can be included in the repository and should
72
					be associated with the appropriate NCEAS activities.
73
				</p>
74
[% END %]
75

    
76
[% IF cfg == 'esa' || cfg == 'ltss' %]  
77

    
78
				<span class="text-info">*Organization Name:</span>
79
				<p>The name of the organization with which the data set is
80
					affiliated. We use "affiliation" in a rather permissive sense to mean, for example, that the data set was or has
81
					been generated at the organization; that the owner of the data is affiliated
82
					with the organization or was affiliated with the organization when the data
83
					set was generated; that the data set is owned by the organization; etc.
84
				</p>
85
				
86
				<div class="span6">
87
					<u>Examples of correct organization names:</u>
88
					<ul>
89
						<li>University of Michigan Biological Station</li>
90
						<li>Duke University FACE Facility</li>
91
						<li>National Center for Ecological Analysis and Synthesis</li>
92
					</ul>
93
				</div>
94
				<div class="span6">
95
					<u>Examples of incorrect organization names:</u>
96
					<ul>
97
						<li>Michigan Station</li>
98
						<li>Duke University</li>
99
						<li>University of California Santa Barbara</li>
100
					</ul>	
101
				</div>				
102

    
103
[% END %]
104

    
105
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
106

    
107
				<span class="text-info">*[% config.site | ucfirst %] Name:</span>
108
				<p>Select a [% config.site %] from the drop-down list to indicate that the data set is
109
					affiliated with the [% config.site %]. We use "affiliation" in a rather
110
					permissive sense to mean, for example, that the data set was or has
111
					been generated at the [% config.site %]; that the owner is affiliated
112
					with the [% config.site %] or was affiliated with the [% config.site %] when the data
113
					set was generated; or that the data set is owned by the [% config.site %]; etc.
114
				</p>
115
				<p><u>Note:</u>
116
					If the data were collected at a site other than a
117
					[% config.site %] listed in the drop-down menu, you can indicate so in the
118
					abstract and/or title. You can also indicate this in the keywords
119
					with a locality keyword.
120
				</p> 
121

    
122
[% END %]
123

    
124
			</div>
125
			
126

    
127
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="DataSetOriginator"></a>PRINCIPAL DATA SET OWNER</td></tr> 
128

    
129

    
130
<tr><td colspan="2" align="left"><span class="regtext">The person responsible for developing the data set. For example, the principal 
131
investigator in a collaborative project, the first author of the main publication using the data set, etc.
132
 The first and last names of the principal data set owner are required; the organization name, e-mail, phone, fax, and
133
address information are optional.</span></td></tr>
134

    
135
<tr><td colspan="2" align="left"><span class="regtext"><u>Note:</u><span class="regtext"> If there is more than one owner, information 
136
about the co-owner(s) can be provided in the ASSOCIATED PARTIES section below.</span>
137

    
138
<tr><td colspan="2" align="left"><span class="text-info">*First Name:</span>
139
<span class="regtext">The first name of the principal data set owner.</span></td></tr>
140

    
141
<tr><td colspan="2" align="left"><span class="text-info">*Last Name:</span>
142
<span class="regtext">The last name (surname) of the principal data set owner.</span></td></tr>
143

    
144
<tr><td colspan="2" align="left"><span class="text-info">Organization Name:</span>
145
<span class="regtext">The name of the organization from which the data set
146
originated.</span></td></tr>
147

    
148
<tr><td colspan="2" align="left"><span class="text-info">E-Mail:</span>
149
<span class="regtext">The e-mail address by which the principal data set owner can be contacted.</span></td></tr>
150

    
151
<tr><td colspan="2" align="left"><span class="text-info">Phone:</span>
152
<span class="regtext">The phone number of the principal data set owner, including the area code (999-999-9999).</span></td></tr>
153

    
154
<tr><td colspan="2" align="left"><span class="text-info">FAX:</span>
155
<span class="regtext">The fax number of the principal data set owner, including sthe area code (999-999-9999).</span></td></tr>
156

    
157
<tr><td colspan="2" align="left"><span class="text-info">Street Information:</span>
158
<span class="regtext">A comma-separated list of street number, street, unit,
159
etc.<br> <u>Example:</u> 735 State Street, Suite 300</span></td></tr>
160

    
161
<tr><td colspan="2" align="left"><span class="text-info">City:</span>
162
<span class="regtext">The city
163
name of the principal data set owner's address.</span></td></tr>
164

    
165
<tr><td colspan="2" align="left"><span class="text-info">U.S. State or Territory:</span>
166
<span class="regtext">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 
167
the United States, used the "Other State/Province" field below. For a shortcut,
168
press the first letter of the state on your keyboard (e.g.,  M-key to skip to Maine).</span></td></tr>
169

    
170
<tr><td colspan="2" align="left"><span class="text-info">Other State/Province:</span>
171
<span class="regtext">A non-U.S. state or a province for 
172
the principal data set owner's address.</span></td></tr>
173

    
174
<tr><td colspan="2" align="left"><span class="text-info">Postal Code:</span>
175
<span class="regtext">The postal code or ZIP code
176
for the principal data set owner's address.</span></td></tr>
177

    
178
<tr><td colspan="2" align="left"><span class="text-info">Country:</span>
179
<span class="regtext">The country
180
for the principal data set owner's address.</span></td></tr>
181

    
182

    
183
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="AdditionalOriginators"></a>ASSOCIATED PARTIES</td></tr> 
184

    
185
<tr><td colspan="2" align="left"><span class="regtext">
186
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 
187
the data set), select a role for this person, and click on "Add Associated Party".  Repeat to add another associated party.</td></tr> 
188
<tr><td colspan="2" align="left"><span class="regtext">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.</tr>
191

    
192

    
193
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
194
<a name="DataSetAbstract"></a>*DATA SET ABSTRACT</td></tr>
195

    
196
<tr><td colspan="2" align="left"><span class="regtext">Short (maximum of 350 words) summary of the
197
purpose and content of the data set. Entering a data set abstract is required.</td></tr>
198

    
199
<tr><td colspan="2" align="left"><span class="regtext"><u>Example:</u> Data were collected every year in summer and fall from
200
1967 to 1979. Trapping was conducted only in the fall from 1980 to
201
1988. For each specimen taken, data were recorded on species, date,
202
location, time, sex, and body measurements including total length,
203
length of tail, length of hind foot, length of ear, and body mass.
204
The purpose of the data was to index the population size of all
205
species present over a long time period.</td></tr>
206

    
207
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
208
<a name="KeywordInformation"></a>KEYWORD INFORMATION</td></tr>
209

    
210
<tr><td colspan="2" align="left"><span class="regtext">Provide information for as many keywords as needed. The information is provided in groups of three 
211
fields: keyword, keyword type, and keyword thesaurus. Repeat steps 1-4 below for each additional keyword.</td></tr>
212

    
213
<tr><td colspan="2" align="left"><span class="regtext">Have a look at the <a href=
214
"http://gcmd.nasa.gov/Resources/valids/gcmd_parameters.html" target="nasa">NASA Global Change Master Directory
215
(GCMD)</a> (particularly under EARTH SCIENCE > Biosphere) and see if you can find keywords that appropriately describe your data set.  If not, use your own keywords.</span></td></tr>
216

    
217
<tr><td colspan="2" align="left"><span class="text-info">1. Keyword: </span><span class="regtext"> Enter a
218
word or phrase that describes your data set.</span></td></tr>
219

    
220
<tr><td colspan="2" align="left"><span class="text-info">2. Keyword Type: </span>
221
<span class="regtext">Select the keyword type (a term used to group similar keywords). The different types are ("none" is the default):
222

    
223
   <ul>
224
      <li>Theme: the keyword identifies a particular subject or topic.</li>
225
      <li>Place: the keyword identifies a place.</li>
226
      <li>Stratum: the keyword identifies the layer(s) of any deposited substance.</li>
227
      <li>Temporal: the keyword identifies a time period related to the data set.
228
      <li>Taxonomic: the keyword identifies a particular taxon.</li>
229
</ul></span></td></tr>
230
<tr><td colspan="2" align="left"><span class="text-info">3. Keyword Thesaurus: </span><span class="regtext">Select whether you used the NASA Global Change Master Directory
231
(GCMD) or not to choose your keywords.</span></td></tr> 
232

    
233

    
234

    
235
<tr><td colspan="2" align="left"><span class="regtext"><b>4.</b> Click on the <b>"Add Keyword"</b> button to add the keyword information provided.</span>  
236

    
237

    
238
<tr><td colspan="2" align="left"><span class="regtext">To edit a keyword entry, click on the keyword entered, change the keyword, keyword type, and/or keyword 
239
thesaurus, and click on the area just right of the thesaurus drop-down menu (the text field and the drop-down menus will disappear).  To delete an entry, click on the "X". 
240
If you have entered several keywords and want to change the order in which they appear, use the blue up and down arrows.</span></td></tr>
241

    
242

    
243
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
244
<a name="TemporalCoverageOfData"></a>TEMPORAL COVERAGE OF DATA</td></tr>
245

    
246
<tr><td colspan="2" align="left"><span class="text-info">*Start Date:</span><span class="regtext"> The first year, month, and
247
day of the collection/creation of the data set. A start date is required. Type in the year (yyyy), and choose the month and the day from the
248
drop-down menus.</span></td></tr>
249

    
250
<tr><td colspan="2" align="left"><span class="text-info">Stop Date:</span><span class="regtext"> The last year, month, and
251
day for the collection/creation of the data set. Type in the year, and choose the month and the day from the drop-down menus.<br> 
252
<u>Note:</u> Leave "Stop Date" blank if your data set is open-ended.</span></td></tr>
253

    
254
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
255
<a name="SpatialCoverageOfData"></a>SPATIAL COVERAGE OF DATA</span></td></tr> 
256

    
257

    
258
<tr><td colspan="2" align="left"><span class="text-info">*Geographic Description:</span><span class="regtext"> 
259
Enter a general description of the geographic area in which the data were collected. This can be a simple place name (e.g., Santa Barbara) or a fuller description.
260
This field supplements the coordinates provided below and helps orient the data user about the general location of the study.</span></td></tr>
261

    
262
<tr><td colspan="2" align="left"><span class="text-info">*Coordinates:</span><span class="regtext"></span><span class="regtext"> The latitude and longitude
263
coordinates (in degrees, minutes and seconds) of the location where the data were collected. At least one lat/long pair is required. From the drop-down menus, select 
264
the North (N) or South (S) orientation for the latitudes, and the West (W) or East (E) orientation for the longitudes.</span></td></tr>
265

    
266
<tr><td colspan="2" align="left"><span class="regtext">If you enter <b>one coordinate pair only</b>: This indicates a
267
point location.</span></td></tr>
268

    
269
<tr><td colspan="2" align="left"><span class="regtext">If you enter <b>both coordinate pairs</b>: This indicates a
270
bounding box. The first coordinate pair is the northwest corner and
271
the second coordinate pair is the southeast corner of the bounding
272
box.</span></td></tr>
273

    
274
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
275
<a name="TaxonomicCoverage"></a>
276
TAXONOMIC COVERAGE OF DATA</td></tr>
277

    
278
<tr><td colspan="2" align="left"><span class="regtext">
279
Provide a list of the taxa that are associated with this data set. 
280
This includes taxa for which the data set contains measurements, and taxa
281
for which the data have relevance in less direct ways.  In general, if a
282
data user searching for a particular taxonomic name should find this data set,
283
then the taxon should be included in this list.</span></td></tr> 
284

    
285
<tr><td colspan="2" align="left"><span class="regtext">Please check the <a href=
286
"http://darwin.zoology.gla.ac.uk/~rpage/MyToL/www/index.php" target="darwin">Glasgow Taxonomic Name Server</a> or the <a href=
287
"http://www.itis.usda.gov/" target="itis">Integrated Taxonomic Information System</a> for correct spelling 
288
of taxonomic names.</span></td></tr>
289
<tr><td colspan="2" align="left"><span class="regtext">For each taxon, follow the three steps below:</span></td></tr>
290
<tr><td colspan="2" align="left"><span class="text-info">1. Taxonomic Rank:</span><span class="regtext"> Enter the level in the taxonomic hierarchy 
291
(Kingdom, Phylum, Class, Order, Family, Genus, or Species).</span></td></tr> 
292
<tr><td colspan="2" align="left"><span class="text-info">2. Taxonomic Name:</span><span class="regtext"> Enter the scientific name for the level 
293
entered under Taxonomic Rank (e.g., <i>Animalia</i>, <i>Chordata</i>, <i>Mammalia</i>, <i>Carnivoria</i>, <i>Ursidae</i>, <i>Ursus</i>, or <i>Ursus arctos</i>).</span></td></tr>
294

    
295
<tr><td colspan="2" align="left"><span class="regtext"><b>3.</b> Click on the <b>"Add Taxon"</b> button to add the taxonomic information.</span></td></tr>
296

    
297
<tr><td colspan="2" align="left"><span class="regtext">To edit an entry, click on the taxonomic information entered, change the taxonomic rank and/or name, and click on the area just right of the text field for the name (the two text 
298
fields will disappear).  To delete an entry, click on the "X". If you have entered several taxa and want to change the order in which they appear, use the blue up and 
299
down arrows.</span></td></tr>
300

    
301
<tr><td colspan="2" align="left"><span class="text-info">Taxonomic Reference:</span><span class="regtext"> The name
302
or complete citation of the source(s) used for identifying and naming taxa (e.g., name of a field guide, key, or nomenclature revision). </span></td></tr>
303

    
304
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
305
<a name="Methods"></a>DATA COLLECTION METHODS</td></tr> 
306

    
307

    
308
<tr><td colspan="2" align="left"><span class="text-info">Method Title:</span><span class="regtext"> A title for the method used to generate
309
the data (e.g., Measure of zooplankton abundance using radial quadrat sub-sampling).</span></td></tr>
310

    
311
<tr><td colspan="2" align="left"><span class="text-info">Method Description:</span><span class="regtext"> Description of the method used.  
312
This is intended to be a general method description that is suitable to help potential users of the data decide if the data are appropriate for their purposes.  
313
You can add multiple paragraphs to the description by clicking on the "Add Paragraph to Method Description"
314
button (paragraphs added by using the ENTER key in the Method Description field will not appear as paragraphs in the submitted form).
315
</span></td></tr>
316

    
317
<!--<tr><td colspan="2" align="left"><span class="regtext">Click on the "Describe Another Method" button
318
to describe another method.</span></td></tr>-->
319

    
320
<tr><td colspan="2" align="left"><span class="text-info">Extent of Study Description:</span><span class="regtext">
321
 Describe the temporal, spatial and taxonomic extent of the study, supplementing
322
the information on coverage provided above. For example, if the temporal
323
coverage of the data is 1990-2000, you might provide details about any years
324
that were missed or the months in which sampling actually occurred. If you
325
provide information in this field (Extent of Study Description), then you must also provide
326
a Method Title, a Method Description and a Sampling Description.</span></td></tr>
327

    
328
<tr><td colspan="2" align="left"><span class="text-info">Sampling Description:</span><span class="regtext">
329
Describe the sampling design of the study. For example, you might describe
330
the way in which treatments were assigned to sampling units.  If you provide
331
information in this field (Sampling Description), then you must also provide
332
a a Method Title, a Method Description and an Extent of Study Description.
333
</span></td></tr>
334

    
335
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
336
<a name="DataSetContactAddress"></a>                                   
337
DATA SET CONTACT</td></tr>
338

    
339
<tr><td colspan="2" align="left"><span class="regtext">Contact information of the person to be contacted for more information on the data
340
set or to obtain the data set itself. This is analogous to the Principal Data Set Owner information above. Please 
341
<a href="[% cgiPrefix %]/register-dataset.cgi?cfg=[%cfg%]&amp;stage=guide#DataSetOriginator" target="_self">see that section</a> for more information on filling out the 
342
individual fields. If the Data Set Contact and the Principal Data Set Owner are the same, check the box provided.</span></td></tr>
343

    
344

    
345
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
346
<a name="DistributionIinformation"></a>
347
DISTRIBUTION INFORMATION</font></td></tr> 
348

    
349
<tr><td colspan="2" align="left"><span class="text-info">
350
<a name=Site-specificCode></a>
351
Data Set Identifier:</span><span class="regtext"> If available, please enter a name or number that uniquely identifies and describes concisely the data set. 
352
Alternatively, provide other pertinent information that can identify and locate the data set within your site's data management system. 
353

    
354
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
355
Keep in mind that this information, although not required, can be extremely useful
356
for locating the data set at a [% config.site %].
357
[%END%]
358
</span></td></tr>
359
<tr><td colspan="2" align="left"><span class="text-info">*Data Medium</font>:</span><span class="regtext"> Specify whether the data medium is 
360
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).</span></td></tr>
361

    
362

    
363
<tr><td colspan="2" align="left"><span class="text-info">*Usage Rights:</span><span class="regtext"> Specify the usage rights that apply
364
to the data set (e.g., no restrictions, obtain permission from data set owner(s), cite the data set in publications, etc.). </span></td></tr>
365

    
366
<tr><td colspan="2" align="left"><span class="text-info">URL:</span><span class="regtext"> If available, provide a link for the
367
location of more metadata or the data set itself (this URL should be as permanent as possible).</span></td></tr>
368

    
369
<a name="AdditionalInformation"></a>
370
<tr><td class="borderbottom" colspan="2" align="left"><span class="text-info">Additional Information:</span><span class="regtext"> Add
371
any additional information here that you deem relevant to the data set, which has not been covered in the form.  For example, if the data set is in the form 
372
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.).</span></td></tr>
373
</table>
374

    
375
			</div> <!-- end row-fluid -->
376

    
377
		</div>
378
	</article>
379
[% INCLUDE $templates.footer %]
(6-6/10)