Project

General

Profile

1 7867 leinfelder
[% INCLUDE $templates.header %]
2
3 7893 leinfelder
	<!-- 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 7934 leinfelder
			<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 7937 leinfelder
				<p>
30 7934 leinfelder
					The first and last names of the person completing this form.
31 7937 leinfelder
				</p>
32 7934 leinfelder
33 7935 leinfelder
			</div>
34 7936 leinfelder
35
			<div class="row-fluid">
36
				<a name="BasicInformation"></a>
37
				<h4>BASIC INFORMATION</h4>
38 7937 leinfelder
				<span class="text-info">*Data Set Title:</span>
39
				<p>A descriptive title
40 7936 leinfelder
				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 7937 leinfelder
				taxonomic, and temporal extents the data set covers.</p>
46 7935 leinfelder
47 7940 leinfelder
				<div class="span6">
48 7936 leinfelder
					<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 7940 leinfelder
				<div class="span6">
55 7936 leinfelder
					<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 7867 leinfelder
[% IF cfg == 'nceas' %]
63 7941 leinfelder
				<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 7867 leinfelder
[% END %]
75
76
[% IF cfg == 'esa' || cfg == 'ltss' %]
77
78 7941 leinfelder
				<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 7867 leinfelder
103
[% END %]
104
105
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
106
107 7941 leinfelder
				<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 7867 leinfelder
122
[% END %]
123
124 7941 leinfelder
			</div>
125
126 7942 leinfelder
			<div class="row-fluid">
127
				<a name="DataSetOriginator"></a>
128
				<h4>PRINCIPAL DATA SET OWNER</h4>
129 7867 leinfelder
130 7942 leinfelder
				<p>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.
134
				</p>
135 7867 leinfelder
136 7942 leinfelder
				<p><u>Note:</u>If there is more than one owner, information
137
					about the co-owner(s) can be provided in the ASSOCIATED PARTIES section below.
138
				</p>
139 7867 leinfelder
140 7942 leinfelder
				<p><span class="text-info">*First Name:</span>
141
				The first name of the principal data set owner.</p>
142
143
				<p><span class="text-info">*Last Name:</span>
144
				The last name (surname) of the principal data set owner.</p>
145
146
				<p><span class="text-info">Organization Name:</span>
147
				The name of the organization from which the data set
148
				originated.</p>
149
150
				<p><span class="text-info">E-Mail:</span>
151
				The e-mail address by which the principal data set owner can be contacted.</p>
152
153
				<p><span class="text-info">Phone:</span>
154
				The phone number of the principal data set owner, including the area code (999-999-9999).</p>
155
156
				<p><span class="text-info">FAX:</span>
157
				The fax number of the principal data set owner, including the area code (999-999-9999).</p>
158
159
				<p><span class="text-info">Street Information:</span>
160
				A comma-separated list of street number, street, unit,
161
				etc.<br> <u>Example:</u> 735 State Street, Suite 300</p>
162
163
				<p><span class="text-info">City:</span>
164
				The city
165
				name of the principal data set owner's address.</p>
166
167
				<p><span class="text-info">U.S. State or Territory:</span>
168
				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
169
				the United States, used the "Other State/Province" field below. For a shortcut,
170
				press the first letter of the state on your keyboard (e.g.,  M-key to skip to Maine).</p>
171
172
				<p><span class="text-info">Other State/Province:</span>
173
				A non-U.S. state or a province for
174
				the principal data set owner's address.</p>
175
176
				<p><span class="text-info">Postal Code:</span>
177
				The postal code or ZIP code
178
				for the principal data set owner's address.</p>
179
180
				<p><span class="text-info">Country:</span>
181
				The country
182
				for the principal data set owner's address.</p>
183
184
			</div>
185 7943 leinfelder
186
			<div class="row-fluid">
187
				<a name="AdditionalOriginators"></a>
188
				<h4>ASSOCIATED PARTIES</h4>
189 7867 leinfelder
190 7943 leinfelder
				<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
191
				the data set), select a role for this person, and click on "Add Associated Party".  Repeat to add another associated party.</p>
192 7867 leinfelder
193 7943 leinfelder
				<p>To edit an entry, click on the name of the person entered, change the name and/or
194
				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".
195
				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>
196
197
			</div>
198
199
			<div class="row-fluid">
200
				<a name="DataSetAbstract"></a>
201
				<h4>*DATA SET ABSTRACT</h4>
202
				<p>Short (maximum of 350 words) summary of the purpose and content of the data set.
203
					Entering a data set abstract is required.
204
				</p>
205
				<p>
206
					<u>Example:</u> Data were collected every year in summer and fall from
207
					1967 to 1979. Trapping was conducted only in the fall from 1980 to
208
					1988. For each specimen taken, data were recorded on species, date,
209
					location, time, sex, and body measurements including total length,
210
					length of tail, length of hind foot, length of ear, and body mass.
211
					The purpose of the data was to index the population size of all
212
					species present over a long time period.
213
				</p>
214
215
			</div>
216
217
			<div class="row-fluid">
218
				<a name="KeywordInformation"></a>
219
				<h4>KEYWORD INFORMATION</h4>
220
				<p>Provide information for as many keywords as needed. The information is provided in groups of three
221
					fields: keyword, keyword type, and keyword thesaurus. Repeat steps 1-4 below for each additional keyword.
222
				</p>
223
				<p>Have a look at the <a href="http://gcmd.nasa.gov/Resources/valids/gcmd_parameters.html" target="nasa">NASA Global Change Master Directory
224
					(GCMD)</a> (particularly under EARTH SCIENCE > Biosphere) and see if you can find keywords that appropriately describe your data set.
225
					If not, use your own keywords.
226
				</p>
227
				<p><span class="text-info">1. Keyword: </span>
228
					Enter a word or phrase that describes your data set.</p>
229
				<p><span class="text-info">2. Keyword Type: </span>
230
					Select the keyword type (a term used to group similar keywords). The different types are ("none" is the default):
231 7867 leinfelder
232 7943 leinfelder
					<ul>
233
						<li>Theme: the keyword identifies a particular subject or topic.</li>
234
						<li>Place: the keyword identifies a place.</li>
235
						<li>Stratum: the keyword identifies the layer(s) of any deposited substance.</li>
236
						<li>Temporal: the keyword identifies a time period related to the data set.
237
						<li>Taxonomic: the keyword identifies a particular taxon.</li>
238
					</ul>
239
				</p>
240
				<p><span class="text-info">3. Keyword Thesaurus: </span>
241
					Select whether you used the NASA Global Change Master Directory (GCMD) or not to choose your keywords.
242
				</p>
243
				<p>
244
					<span class="text-info">4. Click</span> on the <b>"Add Keyword"</b> button to add the keyword information provided.
245
				</p>
246
				<p>To edit a keyword entry, click on the keyword entered, change the keyword, keyword type, and/or keyword
247
					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".
248
					If you have entered several keywords and want to change the order in which they appear, use the blue up and down arrows.
249
				</p>
250
251
			</div>
252 7867 leinfelder
253 7944 leinfelder
			<div class="row-fluid">
254
				<a name="TemporalCoverageOfData"></a>
255
				<h4>TEMPORAL COVERAGE OF DATA</h4>
256
				<p><span class="text-info">*Start Date: </span>
257
					The first year, month, and
258
					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
259
					drop-down menus.
260
				</p>
261
				<p><span class="text-info">Stop Date:</span>
262
					The last year, month, and
263
					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.
264
				</p>
265
				<p>
266
					<u>Note:</u> Leave "Stop Date" blank if your data set is open-ended.
267
				</p>
268
			</div>
269
270
			<div class="row-fluid">
271
				<a name="SpatialCoverageOfData"></a>
272
				<h4>SPATIAL COVERAGE OF DATA</h4>
273
				<p><span class="text-info">*Geographic Description:</span>
274
					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.
275
					This field supplements the coordinates provided below and helps orient the data user about the general location of the study.
276
				</p>
277
				<p><span class="text-info">*Coordinates:</span>
278
					The latitude and longitude
279
					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
280
					the North (N) or South (S) orientation for the latitudes, and the West (W) or East (E) orientation for the longitudes.
281
				</p>
282
				<p>
283
					If you enter <b>one coordinate pair only</b>: This indicates a point location.
284
				</p>
285
				<p>If you enter <b>both coordinate pairs</b>: This indicates a
286
					bounding box. The first coordinate pair is the northwest corner and
287
					the second coordinate pair is the southeast corner of the bounding
288
					box.
289
				</p>
290
			</div>
291 7867 leinfelder
292
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
293
<a name="TaxonomicCoverage"></a>
294
TAXONOMIC COVERAGE OF DATA</td></tr>
295
296
<tr><td colspan="2" align="left"><span class="regtext">
297
Provide a list of the taxa that are associated with this data set.
298
This includes taxa for which the data set contains measurements, and taxa
299
for which the data have relevance in less direct ways.  In general, if a
300
data user searching for a particular taxonomic name should find this data set,
301
then the taxon should be included in this list.</span></td></tr>
302
303
<tr><td colspan="2" align="left"><span class="regtext">Please check the <a href=
304
"http://darwin.zoology.gla.ac.uk/~rpage/MyToL/www/index.php" target="darwin">Glasgow Taxonomic Name Server</a> or the <a href=
305
"http://www.itis.usda.gov/" target="itis">Integrated Taxonomic Information System</a> for correct spelling
306
of taxonomic names.</span></td></tr>
307
<tr><td colspan="2" align="left"><span class="regtext">For each taxon, follow the three steps below:</span></td></tr>
308 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">1. Taxonomic Rank:</span><span class="regtext"> Enter the level in the taxonomic hierarchy
309 7867 leinfelder
(Kingdom, Phylum, Class, Order, Family, Genus, or Species).</span></td></tr>
310 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">2. Taxonomic Name:</span><span class="regtext"> Enter the scientific name for the level
311 7867 leinfelder
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>
312
313
<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>
314
315
<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
316
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
317
down arrows.</span></td></tr>
318
319 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">Taxonomic Reference:</span><span class="regtext"> The name
320 7867 leinfelder
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>
321
322
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
323
<a name="Methods"></a>DATA COLLECTION METHODS</td></tr>
324
325
326 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">Method Title:</span><span class="regtext"> A title for the method used to generate
327 7867 leinfelder
the data (e.g., Measure of zooplankton abundance using radial quadrat sub-sampling).</span></td></tr>
328
329 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">Method Description:</span><span class="regtext"> Description of the method used.
330 7867 leinfelder
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.
331
You can add multiple paragraphs to the description by clicking on the "Add Paragraph to Method Description"
332
button (paragraphs added by using the ENTER key in the Method Description field will not appear as paragraphs in the submitted form).
333
</span></td></tr>
334
335
<!--<tr><td colspan="2" align="left"><span class="regtext">Click on the "Describe Another Method" button
336
to describe another method.</span></td></tr>-->
337
338 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">Extent of Study Description:</span><span class="regtext">
339 7867 leinfelder
 Describe the temporal, spatial and taxonomic extent of the study, supplementing
340
the information on coverage provided above. For example, if the temporal
341
coverage of the data is 1990-2000, you might provide details about any years
342
that were missed or the months in which sampling actually occurred. If you
343
provide information in this field (Extent of Study Description), then you must also provide
344
a Method Title, a Method Description and a Sampling Description.</span></td></tr>
345
346 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">Sampling Description:</span><span class="regtext">
347 7867 leinfelder
Describe the sampling design of the study. For example, you might describe
348
the way in which treatments were assigned to sampling units.  If you provide
349
information in this field (Sampling Description), then you must also provide
350
a a Method Title, a Method Description and an Extent of Study Description.
351
</span></td></tr>
352
353
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
354
<a name="DataSetContactAddress"></a>
355
DATA SET CONTACT</td></tr>
356
357
<tr><td colspan="2" align="left"><span class="regtext">Contact information of the person to be contacted for more information on the data
358
set or to obtain the data set itself. This is analogous to the Principal Data Set Owner information above. Please
359
<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
360
individual fields. If the Data Set Contact and the Principal Data Set Owner are the same, check the box provided.</span></td></tr>
361
362
363
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
364
<a name="DistributionIinformation"></a>
365
DISTRIBUTION INFORMATION</font></td></tr>
366
367 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">
368 7867 leinfelder
<a name=Site-specificCode></a>
369
Data Set Identifier:</span><span class="regtext"> If available, please enter a name or number that uniquely identifies and describes concisely the data set.
370
Alternatively, provide other pertinent information that can identify and locate the data set within your site's data management system.
371
372
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
373
Keep in mind that this information, although not required, can be extremely useful
374
for locating the data set at a [% config.site %].
375
[%END%]
376
</span></td></tr>
377 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">*Data Medium</font>:</span><span class="regtext"> Specify whether the data medium is
378 7867 leinfelder
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>
379
380
381 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">*Usage Rights:</span><span class="regtext"> Specify the usage rights that apply
382 7867 leinfelder
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>
383
384 7933 leinfelder
<tr><td colspan="2" align="left"><span class="text-info">URL:</span><span class="regtext"> If available, provide a link for the
385 7867 leinfelder
location of more metadata or the data set itself (this URL should be as permanent as possible).</span></td></tr>
386
387
<a name="AdditionalInformation"></a>
388 7933 leinfelder
<tr><td class="borderbottom" colspan="2" align="left"><span class="text-info">Additional Information:</span><span class="regtext"> Add
389 7867 leinfelder
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
390
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.).</span></td></tr>
391
</table>
392
393 7934 leinfelder
			</div> <!-- end row-fluid -->
394
395 7893 leinfelder
		</div>
396
	</article>
397 7867 leinfelder
[% INCLUDE $templates.footer %]