1
|
<!--
|
2
|
* '$RCSfile$'
|
3
|
* Copyright: 2000 Regents of the University of California and the
|
4
|
* National Center for Ecological Analysis and Synthesis
|
5
|
* For Details: http://www.nceas.ucsb.edu/
|
6
|
*
|
7
|
* '$Author: sgarg $'
|
8
|
* '$Date: 2005-01-10 16:26:18 -0800 (Mon, 10 Jan 2005) $'
|
9
|
* '$Revision: 2363 $'
|
10
|
*
|
11
|
* This program is free software; you can redistribute it and/or modify
|
12
|
* it under the terms of the GNU General Public License as published by
|
13
|
* the Free Software Foundation; either version 2 of the License, or
|
14
|
* (at your option) any later version.
|
15
|
*
|
16
|
* This program is distributed in the hope that it will be useful,
|
17
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
18
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
19
|
* GNU General Public License for more details.
|
20
|
*
|
21
|
* You should have received a copy of the GNU General Public License
|
22
|
* along with this program; if not, write to the Free Software
|
23
|
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
24
|
-->
|
25
|
|
26
|
[% INCLUDE "genericHeader.tmpl" %]
|
27
|
|
28
|
[% IF cfg == 'nrs' %]
|
29
|
[% lsite = 'reserve' %]
|
30
|
[% usite = 'Reserve' %]
|
31
|
[% ELSE %]
|
32
|
[% lsite = 'station' %]
|
33
|
[% usite = 'Station' %]
|
34
|
[% END %]
|
35
|
|
36
|
|
37
|
<p>This guide provides information on how to
|
38
|
fill in the online [% orgabbrev %] Data Registry Form. Some fields are required
|
39
|
and some fields are optional. Required fields appear in <b><font color="#ff0000">red</font></b>.
|
40
|
A few fields are repeatable up to ten times. These are the associated parties, keywords, taxa, and methods fields.
|
41
|
Note that those repeatable fields are also optional, so you need to
|
42
|
fill in only as many of those as you need.</p>
|
43
|
|
44
|
<p>Information on individual fields and examples
|
45
|
for their content are provided below.</p>
|
46
|
|
47
|
<p> </p>
|
48
|
<hr>
|
49
|
<a name="BasicInformation"></a>
|
50
|
<p><b><font size="4" color="#0000ff">BASIC INFORMATION</font></b>
|
51
|
<p> </p>
|
52
|
|
53
|
<p><font size="4"><b>Name of Person completing this form:</b></font>
|
54
|
Enter the name of the person completing this form (your name).<font size="2"></font></p>
|
55
|
|
56
|
[% IF cfg == 'nceas' %]
|
57
|
<p><font size="4"><b>Working Group(s):</b></font> Select one or more
|
58
|
NCEAS activities from the list to indicate that the data set is
|
59
|
affiliated with that working group or activity. We use "affiliation"
|
60
|
in a rather permissive sense to mean, for example, that the data set was or has
|
61
|
been generated by the activity; that the owner of the data is affiliated
|
62
|
with the activity; or that the data set is owned by the activity, etc. Both
|
63
|
derived data sets that result from synthesis activities and original raw data
|
64
|
sets that contribute to synthesis can be included in the repository and should
|
65
|
be associated with the appropriate NCEAS activities.
|
66
|
<font size="2"></font></p>
|
67
|
[% ELSE %]
|
68
|
<p><font size="4"><b>[% usite %] Name:</b></font> Select a
|
69
|
[% lsite %] from the drop-down list to indicate that the data set is
|
70
|
affiliated with the [% lsite %]. We use "affiliation" in a rather
|
71
|
permissive sense to mean, for example, that the data set was or has
|
72
|
been generated at the [% lsite %]; that the originator is affiliated
|
73
|
with the [% lsite %], or was affiliated with the [% lsite %] when the data
|
74
|
set was generated, that the data set is owned by the [% lsite %], etc.
|
75
|
<font size="2"></font></p>
|
76
|
|
77
|
<p>Note: If the data was collected at a site other than an OBFS
|
78
|
[% lsite %] listed in the pull-down menu, you can indicate so in the
|
79
|
abstract and/or title. You can also indicate this in the keywords
|
80
|
with a locality keyword. You may also indicate the locality in the
|
81
|
dataset title below, if appropriate.</p>
|
82
|
[% END %]
|
83
|
|
84
|
<b><font size="4"></font></b>
|
85
|
<p><b><font size="4">Data Set Title:</font></b> A descriptive title
|
86
|
of the data set. In general the title should provide enough information for
|
87
|
someone casually scanning a list of data sets to know whether the data are
|
88
|
relevant to them. This implies that the data context should be indicated
|
89
|
in the title without making the title be too long. In general, the title
|
90
|
should indicate what kind of data were collected and the spatial,
|
91
|
taxonomic, and temporal extents the data covers.</p>
|
92
|
|
93
|
<p>Examples:</p>
|
94
|
|
95
|
<p>Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988.</p>
|
96
|
|
97
|
<p>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</p>
|
98
|
|
99
|
<p>Bad Examples (not enough information):</p>
|
100
|
|
101
|
<p>Mammals Data</p>
|
102
|
<p>Abundance Data</p>
|
103
|
<p>Meteorological Data</p>
|
104
|
|
105
|
<p> </p>
|
106
|
<hr>
|
107
|
<a name="DataSetOriginator"></a>
|
108
|
<p><b><font size="4" color="#0000ff">PRINCIPAL DATA SET OWNER</font></b>
|
109
|
<p> </p>
|
110
|
|
111
|
The person(s) or organization that developed the data
|
112
|
set. The first and last names of the principal data set owner are required; the organization name, phone, fax, email and
|
113
|
address information are optional.</p>
|
114
|
|
115
|
<p>This principal data set owner and the data set contact (below) may be the same
|
116
|
person.</p>
|
117
|
|
118
|
<b><font size="4"></font></b>
|
119
|
<p><b><font size="4">First Name:</font> <font size="5">
|
120
|
</font></b>The first name of the person.</p>
|
121
|
|
122
|
<b><font size="4"></font></b>
|
123
|
<p><b><font size="4">Last Name:</font> <font size="5">
|
124
|
</font></b>The last name (surname) of the person.</p>
|
125
|
|
126
|
<b><font size="4"></font></b>
|
127
|
<p><b><font size="4">Organization Name:</font> <font size="5">
|
128
|
</font></b>The name of the organization from which the data
|
129
|
originate.</p>
|
130
|
|
131
|
<p><b><font size="4">E-Mail:</font> <font size="5"></font></b>The
|
132
|
e-mail address by which the principal data set owner can be contacted.</p>
|
133
|
|
134
|
<b><font size="4"></font></b>
|
135
|
<p><b><font size="4">Phone:</font> <font size="5">
|
136
|
</font></b>Principal data set owner's phone number, in the format area code plus
|
137
|
number, 999-999-9999.</p>
|
138
|
|
139
|
<b><font size="4"></font></b>
|
140
|
<p><b><font size="4">FAX:</font> <font size="5">
|
141
|
</font></b>Principal data set owner's fax machine number, in the format area code plus
|
142
|
number, 999-999-9999.</p>
|
143
|
|
144
|
<b><font size="4"></font></b>
|
145
|
<p><b><font size="4">Street Address Information:</font> <font size="5">
|
146
|
</font></b>A comma-separated list of street number, street, unit,
|
147
|
etc. Example: 735 State Street, Suite 300</p>
|
148
|
|
149
|
<b><font size="4"></font></b>
|
150
|
<p><b><font size="4">City:</font> <font size="5"></font></b>City
|
151
|
name of the principal data set owner's address.</p>
|
152
|
|
153
|
<b><font size="4"></font></b>
|
154
|
<p><b><font size="4">State:</font> <font size="5"></font></b>Select
|
155
|
a state for the address from the pull-down menu. For a shortcut,
|
156
|
press the C-key to skip to California.</p>
|
157
|
|
158
|
<b><font size="4"></font></b>
|
159
|
<p><b><font size="4">Postal Code:</font> <font size="5"></font></b>The postal code, or ZIP code,
|
160
|
of the principal data set owner's address.</p>
|
161
|
|
162
|
|
163
|
<p> </p>
|
164
|
<hr>
|
165
|
<a name="AdditionalOriginators"></a>
|
166
|
<p><b><font size="4" color="#0000ff">ASSOCIATED PARTIES</font></b>
|
167
|
<p> </p>
|
168
|
|
169
|
|
170
|
Enter the first and last names of up to 10 additional
|
171
|
owners or other associated parties, and select their specific role from the pull-down
|
172
|
menu. The default for the role pull-down menu is Principal
|
173
|
Investigator. Example: First Name: Mark; Last Name: Seablad; Role:
|
174
|
Owner.</p>
|
175
|
|
176
|
|
177
|
<p> </p>
|
178
|
<hr>
|
179
|
<a name="DataSetAbstract"></a>
|
180
|
<b><font size="4"></font></b>
|
181
|
<p><b><font size="4" color="#0000ff">DATA SET ABSTRACT</font></b>
|
182
|
<p> </p>
|
183
|
|
184
|
<p>Short (approximately 1/2 page or less) summary of the
|
185
|
purpose and content of the dataset. Entering a data set abstract is required.</p>
|
186
|
|
187
|
<p>Example: Data were collected every year in summer and fall from
|
188
|
1967 to 1979. Trapping was conducted only in the fall from 1980 to
|
189
|
1988. For each specimen taken, data were recorded on species, date,
|
190
|
location, time, sex, and body measurements including total length,
|
191
|
length of tail, length of hind foot, length of ear, and body mass.
|
192
|
The purpose of the data was to index the population size of all
|
193
|
species present over a long time period. </p>
|
194
|
|
195
|
<p> </p>
|
196
|
<hr>
|
197
|
<a name="KeywordInformation"></a>
|
198
|
<p><b><font size="4" color="#0000ff">KEYWORD INFORMATION</font></b>
|
199
|
<p> </p>
|
200
|
|
201
|
Provide information for up to ten keywords. The
|
202
|
information is provided in groups of three fields: keyword, keyword
|
203
|
type and keyword thesaurus. Keyword information is
|
204
|
used for locating data in catalog searches. The keywords listed
|
205
|
here may or may not appear in the title or abstract. Both the
|
206
|
keyword type and thesaurus are optional.</p>
|
207
|
|
208
|
<p>Examples: Keyword: Peromyscus; Keyword Type: taxonomic; Keyword
|
209
|
Thesaurus: none.</p>
|
210
|
|
211
|
<b><font size="4"></font></b>
|
212
|
<p><b><font size="4">Keyword:</font></b> Commonly used formalized
|
213
|
word(s) or phrase(s) used to describe the subject.</p>
|
214
|
|
215
|
<b><font size="4"></font></b>
|
216
|
<p><b><font size="4">Keyword Type:</font> <font size="5">
|
217
|
</font></b>Term used to group similar keywords. Default: none. The
|
218
|
different types are:</p>
|
219
|
|
220
|
<p>theme: keyword identifies a particular subject or topic</p>
|
221
|
|
222
|
<p>place: keyword identifies a place</p>
|
223
|
|
224
|
<p>stratum: keyword identifies the layer(s) of any deposited
|
225
|
substance</p>
|
226
|
|
227
|
<p>temporal: keyword identifies a time period related to the
|
228
|
dataset</p>
|
229
|
|
230
|
<p>taxonomic: keyword identifies a particular taxa</p>
|
231
|
|
232
|
<font size="1"></font>
|
233
|
|
234
|
<b><font size="4"></font></b>
|
235
|
<p><b><font size="4">Keyword Thesaurus:</font> <font size="5">
|
236
|
</font></b>The name of the formally registered thesaurus, or a
|
237
|
similar authoritative source of keywords, from which the keyword
|
238
|
was chosen. Default: none (no thesaurus used; used own
|
239
|
keywords).</p>
|
240
|
|
241
|
<p>An example for a thesaurus is the <a href=
|
242
|
"http://gcmd.nasa.gov/valids/">NASA Global Change Master Directory
|
243
|
(GCMD)</a>. Have a look at the GCMD keywords to get an idea of what
|
244
|
keywords they use. If you find suitable keywords there that
|
245
|
appropriately describe your data, use them and select GCMD for the
|
246
|
keywords' thesaurus.</p>
|
247
|
|
248
|
<p>Click on the "Add Keyword" button to continue adding keywords.</p>
|
249
|
|
250
|
<p> </p>
|
251
|
<hr>
|
252
|
<a name="TemporalCoverageOfData"></a>
|
253
|
<p><b><font size="4" color="#0000ff">TEMPORAL COVERAGE OF DATA</font></b>
|
254
|
<p> </p>
|
255
|
|
256
|
<p><b><font size="4">Beginning Date of Data Set:</font> <font size=
|
257
|
"5"></font></b>The first year, month, and
|
258
|
day of the collection/creation of the data set. A beginning date is required. Type in the year, and choose the month and the day from the
|
259
|
drop down menus.</p>
|
260
|
|
261
|
<b><font size="4"></font></b>
|
262
|
<p><b><font size="4">Ending Date of Data Set:</font> <font size=
|
263
|
"5"></font></b>The last year, month, and
|
264
|
day for the collection/creation of the data set. <b>If your dataset is open-ended, leave the ending date
|
265
|
open</b>, providing no ending date at all. Type in the year, and choose the month and the day from the
|
266
|
drop down menus.</p>
|
267
|
|
268
|
<p> </p>
|
269
|
<hr>
|
270
|
<a name="SpatialCoverageOfData"></a>
|
271
|
<p><b><font size="4" color="#0000ff">SPATIAL COVERAGE OF DATA</font></b>
|
272
|
<p> </p>
|
273
|
|
274
|
<p><b><font size="4">Geographic Description</font><font size="4">:</font></b>
|
275
|
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. This field supplements the coordinates below and helps orient the data user
|
276
|
about the general location of the study.
|
277
|
</p>
|
278
|
|
279
|
<p><b><font size="4">Coordinates</font> (in Degrees, Minutes and
|
280
|
Seconds)<font size="4">:</font> <font size="5">
|
281
|
</font></b>Coordinates provide the location where the data set was
|
282
|
collected.</p>
|
283
|
|
284
|
[% IF cfg != 'nceas' %]
|
285
|
<p><b>Note the checkbox "Use [% lsite %] coordinates"</b>. If checked,
|
286
|
this box indicates that the data were collected at the [% lsite %]. If
|
287
|
you check this box, you don't need to fill in the lat./long. fields
|
288
|
below).
|
289
|
|
290
|
However, I presently do not have the coordinates for some
|
291
|
[% orgabbrev %] [% lsite %]s, which will be indicated when you
|
292
|
submit the form. In this case, you will have to provide the coordinates
|
293
|
in the corresponding fields. (Please contact [%adminname %] at <a href=
|
294
|
"mailto:[% recipient %]">[% recipient %]</a> if you
|
295
|
have the missing coordinates for any of the sites.)</p>
|
296
|
[% END %]
|
297
|
|
298
|
<p>At least one lat./long. pair is required. Pull-down lists provide the North (N)
|
299
|
or South (S) orientation for the latitudes, and the West (W) and
|
300
|
East (E) orientation for the longitudes.</p>
|
301
|
|
302
|
<p>If you enter <b>one coordinate pair only</b>: This indicates a
|
303
|
point location. You may want to do this if you only know the
|
304
|
general location of a site on the [% lsite %]. In this case provide the
|
305
|
point coordinates for the [% lsite %]. Example: 36° 12' 30"N and
|
306
|
121°33'3"W</p>
|
307
|
|
308
|
<p>If you enter <b>both coordinate pairs</b>: This indicates a
|
309
|
bounding box. The first coordinate pair is the northwest corner and
|
310
|
the second coordinate pair is the southeast corner of the bounding
|
311
|
box.</p>
|
312
|
|
313
|
<p> </p>
|
314
|
<hr>
|
315
|
<a name="TaxonomicCoverage"></a>
|
316
|
<p><b><font size="4" color="#0000ff">TAXONOMIC COVERAGE OF DATA</font></b>
|
317
|
<p> </p>
|
318
|
|
319
|
<p><b><font size="4">List of taxa</font><font size="4">:</font></b>
|
320
|
Provide a list of the taxa that are associated with this data set.
|
321
|
This includes taxa for which the data set contains measurements, and taxa
|
322
|
for which the data have relevance in less direct ways. In general, if a
|
323
|
data user searching for a particular taxonomic name should find this data,
|
324
|
then the taxon should be included in this list. The Taxon Rank should
|
325
|
indicate the level in the taxonomic hierarchy (e.g., Phylum, Species, etc.)
|
326
|
and the Taxonomic Name should be the scientific name for the organism at
|
327
|
that level (e.g., Ursus arctos). You can add multiple taxa to the list by
|
328
|
clicking the "Add taxon" button.
|
329
|
</p>
|
330
|
|
331
|
<p><b><font size="4">Taxonomic Authority</font><font size="4">:</font></b> Include the name
|
332
|
or a complete citation for an authoritative source used for taxonomic information.</p>
|
333
|
|
334
|
<p> </p>
|
335
|
<hr>
|
336
|
<a name="Methods"></a>
|
337
|
<p><b><font size="4" color="#0000ff">METHODS</font></b>
|
338
|
<p> </p>
|
339
|
|
340
|
<p><b><font size="4">Title of method</font><font size="4">:</font></b>
|
341
|
Provide a title for the method (e.g., Zooplankton abundance using
|
342
|
radial quadrat sub-sampling).
|
343
|
</p>
|
344
|
|
345
|
<p><b><font size="4">Method description</font><font size="4">:</font></b>
|
346
|
Describe the methods used to generate the data. This is intended to be a
|
347
|
general overview of the methods that is suitable to help a potential user
|
348
|
of the data decide if the data are appropriate for their purposes. You can
|
349
|
add multiple paragraphs to the description by clicking the "Add paragraph"
|
350
|
button.
|
351
|
</p>
|
352
|
|
353
|
<p><b><font size="4">Description of Study Extent</font><font size="4">:</font></b>
|
354
|
Describe the temporal, spatial and taxonomic extent of the study, supplementing
|
355
|
the information on coverage provided above. For example, if the temporal
|
356
|
coverage of the data is 1990-2000, you might provide details about any years
|
357
|
that were missed or the months in which sampling actually occurred. If you
|
358
|
provide information in this field (Study Extent), then you must also provide
|
359
|
a Methods Description and a Sampling Description.
|
360
|
</p>
|
361
|
|
362
|
<p><b><font size="4">Sampling Description</font><font size="4">:</font></b>
|
363
|
Describe the sampling design of the study. For example, you might describe
|
364
|
the way in which treatments were assigned to sampling units. If you provide
|
365
|
information in this field (Sampling Description), then you must also provide
|
366
|
a Methods Description and a Study Extent.
|
367
|
</p>
|
368
|
|
369
|
<p> </p>
|
370
|
<hr>
|
371
|
<a name="DataSetContactAddress"></a>
|
372
|
<p><b><font size="4" color="#0000ff">DATA SET CONTACT</font></b>
|
373
|
<p> </p>
|
374
|
|
375
|
An address, phone, and email to contact for more information on the data
|
376
|
set or to obtain the data described by this entry. This is
|
377
|
analogous to the Principal Data Set Owner information above. Please see
|
378
|
that section for more information on filling out the individual fields. If the Data Set Contact and the
|
379
|
Principal Data Set Owner are the same, check the box provided, and the information you previously filled out for
|
380
|
the Principal Data Set Owner will automatically be filled into this section.</p>
|
381
|
|
382
|
|
383
|
<p> </p>
|
384
|
<hr>
|
385
|
<a name="DistributionIinformation"></a>
|
386
|
<p><b><font size="4" color="#0000ff">DISTRIBUTION INFORMATION</font></b>
|
387
|
|
388
|
<p> </p>
|
389
|
<a name=Site-specificCode></a>
|
390
|
<b><font size="4"></font></b>
|
391
|
<p><b><font size="4">Dataset Name or Identifier (important)</font>:</b>
|
392
|
Enter the dataset's filename(s) (and path) here, if available. Alternatively,
|
393
|
use other pertinent information that can help to identify and locate
|
394
|
the dataset within your site's data management system (this may include
|
395
|
references to hardcopy information, such as file numbers, etc.). Keep in
|
396
|
mind that this information, while not required, can be extremely useful
|
397
|
for locating the dataset at a [% lsite %].</p>
|
398
|
|
399
|
<b><font size="4"></font></b>
|
400
|
<p><b><font size="4">Data Medium</font>:</b> Choose the type of medium the
|
401
|
data is recorded on from the drop down menu</p>
|
402
|
|
403
|
<b><font size="4"></font></b>
|
404
|
<p><b><font size="4">Other Data Medium</font></b>: Specify any
|
405
|
other data medium the data is recorded on. </p>
|
406
|
|
407
|
|
408
|
<p><b><font size="4">Use Constraints:</font> <font size="5">
|
409
|
</font></b>From the pull-down list, choose the use constraints that apply
|
410
|
to this data set. Examples: no restrictions, obtain permission from
|
411
|
originator(s), etc.</p>
|
412
|
|
413
|
<b><font size="4"></font></b>
|
414
|
<p><b><font size="4">Other Use Constraints:</font></b> Specify any
|
415
|
other use constraints that apply to the data set.</p>
|
416
|
|
417
|
<b><font size="4"></font></b>
|
418
|
<p><b><font size="4">URL</font></b>: Provide a link here for the
|
419
|
location of the actual data set (if available) or for more
|
420
|
metadata<b>.</b></p>
|
421
|
|
422
|
<a name="AdditionalInformation"></a>
|
423
|
<b><font size="4"></font></b>
|
424
|
<p><b><font size="4">Additional Information/Remarks:</font></b> Add
|
425
|
any additional information here that you deem relevant to the data set, which has not been covered in the form.</p>
|
426
|
|
427
|
<p> </p>
|
428
|
<hr>
|
429
|
<p> </p>
|
430
|
<p> </p>
|
431
|
|
432
|
[% INCLUDE "genericFooter.tmpl" %]
|