Project

General

Profile

metacat / lib / style / common / templates / genericGuide.tmpl @ 2150

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: jones $'
8
  *     '$Date: 2004-01-07 11:02:11 -0800 (Wed, 07 Jan 2004) $'
9
  * '$Revision: 1991 $'
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 and help how to
38
fill in the [% orgabbrev %] Data Registry Form. Some fields are required
39
and some fields are optional. A red asterisk (<b><font size=
40
"4" color="#ff0000">*</font></b>) indicates that a
41
field is required. A few fields are repeatable up to ten times.
42
Those are the data set originator names and keyword information.
43
Note that those repeatable fields are also optional, so you need to
44
fill in only as many of those as you need.</p> 
45

    
46
<p>Information on individual fields and examples
47
for their content follow.</p>
48

    
49
<p>&nbsp</p>
50
<hr>
51
<a name="BasicInformation"></a>
52
<p><b><font size="4" color="#0000ff">BASIC INFORMATION</font></b> 
53
<p>&nbsp</p>
54

    
55
<p><font size="4"><b>Name of Person completing this form:</b></font> 
56
Enter the name of the person completing this form (your name).<font size="2"></font></p>
57

    
58
[% IF cfg == 'nceas' %]
59
<p><font size="4"><b>Working Group(s):</b></font> Select one or more
60
NCEAS activities from the list to indicate that the data set is
61
affiliated with that working group or activity.  We use "affiliation" 
62
in a rather permissive sense to mean, for example, that the data set was or has
63
been generated by the activity; that the owner of the data is affiliated
64
with the activity, or that the data set is owned by the activity, etc. Both
65
derived data sets that result from synthesis activities and original raw data
66
sets that contribute to synthesis can be included in the repository and should
67
be associated with the appropriate NCEAS activities.
68
<font size="2"></font></p>
69
[% ELSE %]
70
<p><font size="4"><b>[% usite %] Name:</b></font> Select a
71
[% lsite %] from the drop-down list to indicate that the data set is
72
affiliated with the [% lsite %]. We use "affiliation" in a rather
73
permissive sense to mean, for example, that the data set was or has
74
been generated at the [% lsite %]; that the originator is affiliated
75
with the [% lsite %], or was affiliated with the [% lsite %] when the data
76
set was generated, that the data set is owned by the [% lsite %], etc.
77
<font size="2"></font></p>
78

    
79
<p>Note: If the data was collected at a site other than an OBFS
80
[% lsite %] listed in the pull-down menu, you can indicate so in the
81
abstract and/or title. You can also indicate this in the keywords
82
with a locality keyword. You may also indicate the locality in the
83
dataset title below, if appropriate.</p>
84
[% END %]
85

    
86
<b><font size="4"></font></b>
87
<p><b><font size="4">Data Set Title:</font></b> Descriptive title
88
of the data set. In general the title should provide enough information for
89
someone casually scanning a list of data sets to know whether the data are
90
relevant to them.  This implies that the data context should be indicated 
91
in the title without making the title be too long. In general, the title
92
should indicate what kind of data were collected and the spatial,
93
taxonomic, and temporal extents the data covers.</p>
94

    
95
<p>Examples:</p>
96

    
97
<p>Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988.</p>
98

    
99
<p>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</p>
100

    
101
<p>Bad Examples (not enough information):</p>
102

    
103
<p>Mammals Data</p>
104
<p>Abundance Data</p>
105
<p>Meterological Data</p>
106

    
107
<p>&nbsp</p>
108
<hr>
109
<a name="DataSetOriginator"></a>
110
<p><b><font size="4" color="#0000ff">DATA SET ORIGINATOR</font></b> 
111
<p>&nbsp</p>
112

    
113
Person(s) or organization that developed the data
114
set. The first originator provided on the form is EITHER an
115
individual person OR an organization, including optional address
116
information.</p>
117

    
118
<p>This originator and the data set contact below may be the same
119
person or organization.</p>
120

    
121
<b><font size="4"></font></b>
122
<p><b><font size="4">Originator's Role:</font> <font size="5">
123
</font></b>You will probably just want to leave the generic
124
default, which is "originator", but you can choose a more specific
125
originator's role (e.g. Principal Investigator, Publisher, etc.)
126
from the pull-down list, if appropriate, e.g Principal
127
Investigator.</p>
128

    
129
<b><font size="4"></font></b>
130
<p><b><font size="4">First Name:</font> <font size="5">
131
</font></b>Self-explanatory.</p>
132

    
133
<b><font size="4"></font></b>
134
<p><b><font size="4">Last Name:</font> <font size="5">
135
</font></b>Self-explanatory.</p>
136

    
137
<b><font size="4"></font></b>
138
<p><b><font size="4">Organization Name:</font> <font size="5">
139
</font></b>The name of the organization from which the data
140
originate (not required of you provide first/last names above)</p>
141

    
142
<b><font size="4"></font></b>
143
<p><b><font size="4">Originator Address Information (for Individual
144
or Organization):</font></b></p>
145

    
146
<p><b><font size="4">E-Mail:</font> <font size="5"></font></b>The
147
e-mail address under which the originator can be contacted.</p>
148

    
149
<b><font size="4"></font></b>
150
<p><b><font size="4">Phone:</font> <font size="5">
151
</font></b>Originator's phone number in the format area code plus
152
number, 999-999-9999.</p>
153

    
154
<b><font size="4"></font></b>
155
<p><b><font size="4">Delivery Information:</font> <font size="5">
156
</font></b>A comma-separated list of street number, street, Unit,
157
etc., comma-separated). Example: 735 State Street, Suite 300</p>
158

    
159
<b><font size="4"></font></b>
160
<p><b><font size="4">City:</font> <font size="5"></font></b>City
161
name of the originator address.</p>
162

    
163
<b><font size="4"></font></b>
164
<p><b><font size="4">State:</font> <font size="5"></font></b>Select
165
a state for the address from the pull-down menu. For a shortcut,
166
press the C-key to skip to California.</p>
167

    
168
<b><font size="4"></font></b>
169
<p><b><font size="4">ZIP:</font> <font size="5"></font></b>The ZIP
170
code of the originator address.</p>
171

    
172

    
173
<p>&nbsp</p>
174
<hr>
175
<a name="AdditionalOriginators"></a>
176
<p><b><font size="4" color="#0000ff">ADDITIONAL ORIGINATORS</font></b> 
177
<p>&nbsp</p>
178

    
179

    
180
Enter the first and last names of up to 10 additional
181
originators, and select their specific role from the pull-down
182
menu. The default for the role pull-down menu is Principal
183
Investigator. Example: First Name: Mark; Last Name: Seablad; Role:
184
Editor</p>
185

    
186

    
187
<p>&nbsp</p>
188
<hr>
189
<a name="DataSetAbstract"></a>
190
<b><font size="4"></font></b>
191
<p><b><font size="4">Data Set Abstract:</font> <font size="5">
192
</font></b>Short (approximately 1/2 page or less) summary of the
193
purpose and content of the dataset.</p>
194

    
195
<p>Example: Data were collected every year in summer and fall from
196
1967 to 1979. Trapping was conducted only in the fall from 1980 to
197
1988. For each specimen taken, data were recorded on species, date,
198
location, time, sex, and body measurements including total length,
199
length of tail, length of hind foot, length of ear, and body mass.
200
The purpose of the data was to index the population size of all
201
species present over a long time period.&nbsp;</p>
202

    
203
<p>&nbsp</p>
204
<hr>
205
<a name="KeywordInformation"></a>
206
<p><b><font size="4" color="#0000ff">KEYWORD INFORMATION</font></b> 
207
<p>&nbsp</p>
208

    
209
Provide information for up to ten keywords here. The
210
information is provided in groups of three fields: keyword, keyword
211
type and keyword thesaurus, as follows. Keyword information will be
212
useful for locating data in catalog searches. The keywords listed
213
here may or may not appear in the title or abstract. Both the
214
keyword type and thesaurus are optional.</p>
215

    
216
<p>Examples: keyword: Peromyscus; Keyword Type: taxonomic; Keyword
217
Thesaurus: none</p>
218

    
219
<b><font size="4"></font></b>
220
<p><b><font size="4">Keyword:</font></b> Commonly used formalized
221
word( s) or phrase( s) used to describe the subject.</p>
222

    
223
<b><font size="4"></font></b>
224
<p><b><font size="4">Keyword Type:</font> <font size="5">
225
</font></b>Term used to group similar keywords. Default: none. The
226
different types are:</p>
227

    
228
<p>theme: keyword identifies a particular subject or topic</p>
229

    
230
<p>discipline: keyword identifies a branch of instruction or
231
specialized learning</p>
232

    
233
<p>taxonomic: keyword identifies a particular taxa</p>
234

    
235
<p>place: keyword identifies a place</p>
236

    
237
<p>stratum: keyword identifies the layer(s) of any deposited
238
substance</p>
239

    
240
<p>temporal: keyword identifies a time period related to the
241
dataset</p>
242

    
243
<p>theme: keyword identifies a particular subject or topic</p>
244

    
245
<font size="1"></font>
246

    
247
 <b><font size="4"></font></b>
248
<p><b><font size="4">Keyword Thesaurus:</font> <font size="5">
249
</font></b>The Name of the formally registered thesaurus, or a
250
similar authoritative source of keywords, from which the keyword
251
was chosen. Default: none (no thesaurus used; used own
252
keywords)</p>
253

    
254
<p>An example for a thesaurus is the <a href=
255
"http://gcmd.nasa.gov/valids/">NASA Global Change Master Directory
256
(GCMD)</a>. Have a look at the GCMD keywords to get an idea of what
257
keywords they use. If you find suitable keywords there that
258
appropriately describe your data, use them and select GCMD for the
259
keywords' thesaurus.</p>
260

    
261
<p>&nbsp</p>
262
<hr>
263
<a name="TemporalCoverageOfData"></a>
264
<p><b><font size="4" color="#0000ff">TEMPORAL COVERAGE OF DATA</font></b> 
265
<p>&nbsp</p>
266

    
267
<p><b><font size="4">Beginning Date of Data Set:</font> <font size=
268
"5"></font></b>The first year (and optionally month, or month and
269
day) of the collection/creation of the data set, in the format
270
yy/mm/dd.</p>
271

    
272
<b><font size="4"></font></b>
273
<p><b><font size="4">Ending Date of Data Set:</font> <font size=
274
"5"></font></b>The last year (and optionally month, or month and
275
day) for the collection/creation of the data set, in the format
276
yy/mm/dd. <b>If your dataset is open-ended, leave the ending date
277
open</b>, provide no ending date at all.</p>
278

    
279
<p>&nbsp</p>
280
<hr>
281
<a name="SpatialCoverageOfData"></a>
282
<p><b><font size="4" color="#0000ff">SPATIAL COVERAGE OF DATA</font></b> 
283
<p>&nbsp</p>
284

    
285
<p><b><font size="4">Geographic Description</font><font size="4">:</font></b>
286
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
287
about the general location of the study.
288
</p>
289

    
290
<p><b><font size="4">Coordinates</font> (in Degrees, Minutes and
291
Seconds)<font size="4">:</font> <font size="5">
292
</font></b>Coordinates provide the location where the data set was
293
collected.</p>
294

    
295
[% IF cfg != 'nceas' %]
296
<p><b>Note the checkbox "Use [% lsite %] coordinates"</b>. If checked,
297
this box indicates that the data were collected at the [% lsite %]. If
298
you check this box, you don't need to fill in the lat./long. fields
299
below). 
300

    
301
However, I presently do not have the coordinates for some
302
[% orgabbrev %] [% lsite %]s, which will be indicated when you 
303
submit the form. In this case, you will have to provide the coordinates 
304
in the corresponding fields. (Please contact [%adminname %] at <a href=
305
"mailto:[% recipient %]">[% recipient %]</a> if you
306
have the missing coordinates for any of the sites.)</p>
307
[% END %]
308

    
309
<p>Enter <b>one lat./long. pair only to indicate a point
310
location</b>. Enter both lat./long pairs to indicate a bounding
311
box, with the first pair indicating the northwest corner and the
312
second pair the southeast corner of the box. At least one
313
lat./long. pair is required. Pull-down lists provide the North (N)
314
or South (S) orientation for the latitudes, and the West (W) and
315
East (E) orientation for the longitudes.</p>
316

    
317
<p>If you enter <b>one coordinate pair only</b>: This indicates a
318
point location. You may want to do this if you only know the
319
general location of a site on the [% lsite %]. In this case provide the
320
point coordinates for the [% lsite %]. Example: 36&deg; 12' 30"N and
321
121&deg;33'3"W</p>
322

    
323
<p>If you enter <b>both coordinate pairs</b>: This indicates a
324
bounding box. The first coordinate pair is the northwest corner and
325
the second coordinate pair is the southeast corner of the bounding
326
box.</p>
327

    
328
<p>&nbsp</p>
329
<hr>
330
<a name="TaxonomicCoverage"></a>
331
<p><b><font size="4" color="#0000ff">TAXONOMIC COVERAGE OF DATA</font></b> 
332
<p>&nbsp</p>
333

    
334
<p><b><font size="4">List of taxa</font><font size="4">:</font></b>
335
Provide a list of the taxa that are associated with this data set. 
336
This includes taxa for which the data set contains measurements, and taxa
337
for which the data have relevance in less direct ways.  In general, if a
338
data user searching for a particular taxonomic name should find this data
339
then the taxon should be included in this list. The Taxon Rank should 
340
indicate the level in the taxonomic hierarchy (e.g., Phylum or Species) 
341
and the Taxonomic Name should be the scientific name for the organism at 
342
that level (e.g., Ursus arctos).  You can add mutliple taxa to the list by
343
clicking the "Add taxon" button.
344
</p>
345

    
346
<p>&nbsp</p>
347
<hr>
348
<a name="Methods"></a>
349
<p><b><font size="4" color="#0000ff">METHODS</font></b> 
350
<p>&nbsp</p>
351

    
352
<p><b><font size="4">Title of method</font><font size="4">:</font></b>
353
Provide an optional title for the method (e.g., Zooplankton abundance using
354
radial quadrat subsampling).
355
</p>
356

    
357
<p><b><font size="4">Method description</font><font size="4">:</font></b>
358
Describe the methods used to generate the data.  This is intended to be a
359
general overview of the methods that is suitable to help a potential user
360
of the data decide if the data are appropriate for their purposes.  You can
361
add multiple paragraphs to the description by clicking the "Add Paragraph"
362
button.
363
</p>
364

    
365
<p><b><font size="4">Description of Study Extent</font><font size="4">:</font></b>
366
Describe the temporal, spatial and taxonomic extent of the study, supplementing
367
the information on coverage provided above. For example, if the temporal
368
coverage of the data is 1990-2000, you might provide details about any years
369
that were missed or the months in which sampling actually occurred. If you
370
provide information in this field (Study Extent), then you must also provide
371
a Methods Description and a Sampling description.
372
</p>
373

    
374
<p><b><font size="4">Sampling Description</font><font size="4">:</font></b>
375
Describe the sampling design of the study. For example, you might describe
376
the way in which treatments were assigned to sampling units.  If you provide
377
information in this field (Sampling Description), then you must also provide
378
a Methods Description and a Study Extent.
379
</p>
380

    
381
<p>&nbsp</p>
382
<hr>
383
<a name="DataSetContactAddress"></a>
384
<p><b><font size="4" color="#0000ff">DATA SET CONTACT ADDRESS</font></b> 
385
<p>&nbsp</p>
386

    
387
Address to contact for more information on the data
388
set or to obtain the data described by this entry. This is
389
analogous to the Originator Address Information above. Please see
390
there.</p>
391

    
392

    
393
<p>&nbsp</p>
394
<hr>
395
<a name="DistributionIinformation"></a>
396
<p><b><font size="4" color="#0000ff">DISTRIBUTION INFORMATION</font></b> 
397

    
398
<p>&nbsp</p>
399
<a name=Site-specificCode></a>
400
<b><font size="4"></font></b>
401
<p><b><font size="4">Dataset Name or Identifier (important)</font>:</b> 
402
Enter the datasets filename (and path) here, if available.  Alternatively,
403
use other pertinent information that can help to identify and locate
404
the dataset within your site's data management system (this may include
405
references to hardcopy information, such as file numbers, etc.).  Keep in
406
mind that this information, while not required, can be extremely useful
407
for locating the dataset at a [% lsite %].</p>
408

    
409
<b><font size="4"></font></b>
410
<p><b><font size="4">Data Medium</font>:</b> The kind of medium the
411
data is recorded on.</p>
412

    
413
<b><font size="4"></font></b>
414
<p><b><font size="4">Other Data Medium</font></b>: Specify any
415
other data medium you use. &nbsp;</p>
416

    
417

    
418
<p><b><font size="4">Use Constraints:</font> <font size="5">
419
</font></b>Choose from a pull-down list with use constraints apply
420
to this data set. Examples: public domain; obtain permission from
421
PI.</p>
422

    
423
<b><font size="4"></font></b>
424
<p><b><font size="4">Other Use Constraints:</font></b> Specify any
425
other use constraints.</p>
426

    
427
<b><font size="4"></font></b>
428
<p><b><font size="4">URL</font></b>: Provide any network link here for the
429
location of the actual data set (if available) or for more
430
metadata<b>.</b></p>
431

    
432
<p>&nbsp</p>
433
<hr>
434
<a name="AdditionalInformation"></a>
435
<b><font size="4"></font></b>
436
<p><b><font size="4">Additional Information/Remarks:</font></b> Add
437
any information here that you deem relevant to the data set and
438
that is not covered in the form.</p>
439

    
440
<p>&nbsp;</p>
441
<p>&nbsp;</p>
442

    
443
[% INCLUDE "genericFooter.tmpl" %]