Project

General

Profile

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: mecum $'
8
  *     '$Date: 2017-03-24 18:30:10 -0700 (Fri, 24 Mar 2017) $'
9
  * '$Revision: 10195 $'
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 $templates.header %]
27

    
28
<table class="intro" cellpadding="8" cellspacing="0">
29

    
30
<tr><td align="left"><span class="emphasis">Guide for Completing the Data [% config.type %] Form</td></tr>
31
<tr><td align="left"><span class="regtext">This guide provides information on how to fill in the online [% config.abbrev %] Data [% config.type %] Form. 
32
There are 11 sections to the form; some fields are required (denoted by an asterisk *),
33
while others are optional. When you are done completing a section, you have the option of clicking on "<span class="colorbold">Hide</span>" 
34
(on the right side of each section header) to hide the information you just entered. Information on individual fields and examples for their content are provided below.
35
</span></td></tr>
36
</table>
37

    
38

    
39
<table class="tables" cellpadding="8" cellspacing="0">
40

    
41
<tr class="sectheader"><td class="borderbottom" colspan="2" align="left"><a name="Submitter"></a>
42
NAME OF SUBMITTER</td></tr> 
43
<tr><td colspan="2" align="left"><span class="label">
44
*First name, *Last name:</span><span class="regtext"> 
45
The first and last names of the person completing this form.</span></td></tr>
46

    
47
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="BasicInformation"></a>
48
BASIC INFORMATION</td></tr> 
49
<tr><td colspan="2" align="left"><span class="label">*Data Set Title:</span><span class="regtext"> A descriptive title
50
of the data set. The title should provide enough information for
51
someone casually scanning a list of data sets to know whether the data are
52
relevant to them.  This implies that the data context should be indicated 
53
in the title without making the title be too long. In general, the title
54
should indicate what kind of data were collected and the spatial,
55
taxonomic, and temporal extents the data set covers.</span></td></tr>
56

    
57
<tr><td align="left"><span class="regtext"><u>Examples of descriptive titles:</u></td>
58
<td align="left"><span class="regtext"><u>Examples of incomplete titles:</u></td></tr>
59

    
60
<tr><td align="left" valign="top"><span class="regtext">Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988.
61

    
62

    
63

    
64
<br>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</td>
65

    
66
<td align="left" valign="top"><span class="regtext">Mammals Data<br><br>Water Chemistry Data</td></tr>
67

    
68
[% IF cfg == 'nceas' %]
69
<tr><td colspan="2" align="left"><span class="label">*NCEAS Project(s):</span><span class="regtext"> Select one or more
70
NCEAS activities from the list to indicate that the data set is
71
affiliated with that working group or activity.  We use "affiliation" 
72
in a rather permissive sense to mean, for example, that the data set was or has
73
been generated by the activity; that the owner of the data is affiliated
74
with the activity; that the data set is owned by the activity; etc. Both
75
derived data sets that result from synthesis activities and original raw data
76
sets that contribute to synthesis can be included in the repository and should
77
be associated with the appropriate NCEAS activities.</td></tr>
78
[% END %]
79

    
80
[% IF cfg == 'esa' || cfg == 'ltss' %]  
81

    
82
<tr><td colspan="2" align="left"><span class="label">*Organization Name:</span>
83
<span class="regtext">The name of the organization with which the data set is
84
affiliated. We use "affiliation" in a rather permissive sense to mean, for example, that the data set was or has
85
been generated at the organization; that the owner of the data is affiliated
86
with the organization or was affiliated with the organization when the data
87
set was generated; that the data set is owned by the organization; etc.</td></tr>
88

    
89
<tr><td align="left"><span class="regtext"><u>Examples of correct organization names:</u></td>
90
   <td align="left"><span class="regtext"><u>Examples of incorrect organization names:</u></td></tr>
91

    
92
<tr><td align="left" valign="top"><span class="regtext">University of Michigan Biological Station
93
<br>Duke University FACE Facility<br>National Center for Ecological Analysis and Synthesis</br></td>
94
  <td align="left"><span class="regtext">Michigan Station<br>Duke University<br>University of California Santa Barbara</br>
95
</td></tr>
96
[% END %]
97

    
98
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
99

    
100
<tr><td colspan="2" align="left"><span class="label">*[% config.site | ucfirst %] Name:</span>
101
<span class="regtext">Select a [% config.site %] from the drop-down list to indicate that the data set is
102
affiliated with the [% config.site %]. We use "affiliation" in a rather
103
permissive sense to mean, for example, that the data set was or has
104
been generated at the [% config.site %]; that the owner is affiliated
105
with the [% config.site %] or was affiliated with the [% config.site %] when the data
106
set was generated; or that the data set is owned by the [% config.site %]; etc.
107
</td></tr>
108

    
109
<tr><td colspan="2" align="left"><span class="regtext"><u>Note:</u>
110
If the data were collected at a site other than a
111
[% config.site %] listed in the drop-down menu, you can indicate so in the
112
abstract and/or title. You can also indicate this in the keywords
113
with a locality keyword.</span></td></tr> 
114

    
115
[% END %]
116

    
117

    
118

    
119

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

    
122

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

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

    
131
<tr><td colspan="2" align="left"><span class="label">*First Name:</span>
132
<span class="regtext">The first name of the principal data set owner.</span></td></tr>
133

    
134
<tr><td colspan="2" align="left"><span class="label">*Last Name:</span>
135
<span class="regtext">The last name (surname) of the principal data set owner.</span></td></tr>
136

    
137
<tr><td colspan="2" align="left"><span class="label">Organization Name:</span>
138
<span class="regtext">The name of the organization from which the data set
139
originated.</span></td></tr>
140

    
141
<tr><td colspan="2" align="left"><span class="label">E-Mail:</span>
142
<span class="regtext">The e-mail address by which the principal data set owner can be contacted.</span></td></tr>
143

    
144
<tr><td colspan="2" align="left"><span class="label">Phone:</span>
145
<span class="regtext">The phone number of the principal data set owner, including the area code (999-999-9999).</span></td></tr>
146

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

    
150
<tr><td colspan="2" align="left"><span class="label">Street Information:</span>
151
<span class="regtext">A comma-separated list of street number, street, unit,
152
etc.<br> <u>Example:</u> 735 State Street, Suite 300</span></td></tr>
153

    
154
<tr><td colspan="2" align="left"><span class="label">City:</span>
155
<span class="regtext">The city
156
name of the principal data set owner's address.</span></td></tr>
157

    
158
<tr><td colspan="2" align="left"><span class="label">U.S. State or Territory:</span>
159
<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 
160
the United States, used the "Other State/Province" field below. For a shortcut,
161
press the first letter of the state on your keyboard (e.g.,  M-key to skip to Maine).</span></td></tr>
162

    
163
<tr><td colspan="2" align="left"><span class="label">Other State/Province:</span>
164
<span class="regtext">A non-U.S. state or a province for 
165
the principal data set owner's address.</span></td></tr>
166

    
167
<tr><td colspan="2" align="left"><span class="label">Postal Code:</span>
168
<span class="regtext">The postal code or ZIP code
169
for the principal data set owner's address.</span></td></tr>
170

    
171
<tr><td colspan="2" align="left"><span class="label">Country:</span>
172
<span class="regtext">The country
173
for the principal data set owner's address.</span></td></tr>
174

    
175

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

    
178
<tr><td colspan="2" align="left"><span class="regtext">
179
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 
180
the data set), select a role for this person, and click on "Add Associated Party".  Repeat to add another associated party.</td></tr> 
181
<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 
182
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".
183
 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>
184

    
185

    
186
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
187
<a name="DataSetAbstract"></a>*DATA SET ABSTRACT</td></tr>
188

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

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

    
200
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
201
<a name="KeywordInformation"></a>KEYWORD INFORMATION</td></tr>
202

    
203
<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 
204
fields: keyword, keyword type, and keyword thesaurus. Repeat steps 1-4 below for each additional keyword.</td></tr>
205

    
206
<tr><td colspan="2" align="left"><span class="regtext">Have a look at the <a href=
207
"http://gcmd.nasa.gov/Resources/valids/gcmd_parameters.html" target="nasa">NASA Global Change Master Directory
208
(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>
209

    
210
<tr><td colspan="2" align="left"><span class="label">1. Keyword: </span><span class="regtext"> Enter a
211
word or phrase that describes your data set.</span></td></tr>
212

    
213
<tr><td colspan="2" align="left"><span class="label">2. Keyword Type: </span>
214
<span class="regtext">Select the keyword type (a term used to group similar keywords). The different types are ("none" is the default):
215

    
216
   <ul>
217
      <li>Theme: the keyword identifies a particular subject or topic.</li>
218
      <li>Place: the keyword identifies a place.</li>
219
      <li>Stratum: the keyword identifies the layer(s) of any deposited substance.</li>
220
      <li>Temporal: the keyword identifies a time period related to the data set.
221
      <li>Taxonomic: the keyword identifies a particular taxon.</li>
222
</ul></span></td></tr>
223
<tr><td colspan="2" align="left"><span class="label">3. Keyword Thesaurus: </span><span class="regtext">Select whether you used the NASA Global Change Master Directory
224
(GCMD) or not to choose your keywords.</span></td></tr> 
225

    
226

    
227

    
228
<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>  
229

    
230

    
231
<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 
232
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". 
233
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>
234

    
235

    
236
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
237
<a name="TemporalCoverageOfData"></a>TEMPORAL COVERAGE OF DATA</td></tr>
238

    
239
<tr><td colspan="2" align="left"><span class="label">*Start Date:</span><span class="regtext"> The first year, month, and
240
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
241
drop-down menus.</span></td></tr>
242

    
243
<tr><td colspan="2" align="left"><span class="label">Stop Date:</span><span class="regtext"> The last year, month, and
244
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> 
245
<u>Note:</u> Leave "Stop Date" blank if your data set is open-ended.</span></td></tr>
246

    
247
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
248
<a name="SpatialCoverageOfData"></a>SPATIAL COVERAGE OF DATA</span></td></tr> 
249

    
250

    
251
<tr><td colspan="2" align="left"><span class="label">*Geographic Description:</span><span class="regtext"> 
252
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.
253
This field supplements the coordinates provided below and helps orient the data user about the general location of the study.</span></td></tr>
254

    
255
<tr><td colspan="2" align="left"><span class="label">*Coordinates:</span><span class="regtext"></span><span class="regtext"> The latitude and longitude
256
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 
257
the North (N) or South (S) orientation for the latitudes, and the West (W) or East (E) orientation for the longitudes.</span></td></tr>
258

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

    
262
<tr><td colspan="2" align="left"><span class="regtext">If you enter <b>both coordinate pairs</b>: This indicates a
263
bounding box. The first coordinate pair is the northwest corner and
264
the second coordinate pair is the southeast corner of the bounding
265
box.</span></td></tr>
266

    
267
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
268
<a name="TaxonomicCoverage"></a>
269
TAXONOMIC COVERAGE OF DATA</td></tr>
270

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

    
278
<tr><td colspan="2" align="left"><span class="regtext">Please check the <a href="http://www.itis.gov/" target="itis">Integrated Taxonomic Information System</a> for correct spelling of taxonomic names.</span></td></tr>
279
<tr><td colspan="2" align="left"><span class="regtext">For each taxon, follow the three steps below:</span></td></tr>
280
<tr><td colspan="2" align="left"><span class="label">1. Taxonomic Rank:</span><span class="regtext"> Enter the level in the taxonomic hierarchy 
281
(Kingdom, Phylum, Class, Order, Family, Genus, or Species).</span></td></tr> 
282
<tr><td colspan="2" align="left"><span class="label">2. Taxonomic Name:</span><span class="regtext"> Enter the scientific name for the level 
283
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>
284

    
285
<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>
286

    
287
<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 
288
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 
289
down arrows.</span></td></tr>
290

    
291
<tr><td colspan="2" align="left"><span class="label">Taxonomic Reference:</span><span class="regtext"> The name
292
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>
293

    
294
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
295
<a name="Methods"></a>DATA COLLECTION METHODS</td></tr> 
296

    
297

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

    
301
<tr><td colspan="2" align="left"><span class="label">Method Description:</span><span class="regtext"> Description of the method used.  
302
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.  
303
You can add multiple paragraphs to the description by clicking on the "Add Paragraph to Method Description"
304
button (paragraphs added by using the ENTER key in the Method Description field will not appear as paragraphs in the submitted form).
305
</span></td></tr>
306

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

    
310
<tr><td colspan="2" align="left"><span class="label">Extent of Study Description:</span><span class="regtext">
311
 Describe the temporal, spatial and taxonomic extent of the study, supplementing
312
the information on coverage provided above. For example, if the temporal
313
coverage of the data is 1990-2000, you might provide details about any years
314
that were missed or the months in which sampling actually occurred. If you
315
provide information in this field (Extent of Study Description), then you must also provide
316
a Method Title, a Method Description and a Sampling Description.</span></td></tr>
317

    
318
<tr><td colspan="2" align="left"><span class="label">Sampling Description:</span><span class="regtext">
319
Describe the sampling design of the study. For example, you might describe
320
the way in which treatments were assigned to sampling units.  If you provide
321
information in this field (Sampling Description), then you must also provide
322
a a Method Title, a Method Description and an Extent of Study Description.
323
</span></td></tr>
324

    
325
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
326
<a name="DataSetContactAddress"></a>                                   
327
DATA SET CONTACT</td></tr>
328

    
329
<tr><td colspan="2" align="left"><span class="regtext">Contact information of the person to be contacted for more information on the data
330
set or to obtain the data set itself. This is analogous to the Principal Data Set Owner information above. Please 
331
<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 
332
individual fields. If the Data Set Contact and the Principal Data Set Owner are the same, check the box provided.</span></td></tr>
333

    
334

    
335
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
336
<a name="DistributionIinformation"></a>
337
DISTRIBUTION INFORMATION</font></td></tr> 
338

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

    
344
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
345
Keep in mind that this information, although not required, can be extremely useful
346
for locating the data set at a [% config.site %].
347
[%END%]
348
</span></td></tr>
349
<tr><td colspan="2" align="left"><span class="label">*Data Medium</font>:</span><span class="regtext"> Specify whether the data medium is 
350
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>
351

    
352

    
353
<tr><td colspan="2" align="left"><span class="label">*Usage Rights:</span><span class="regtext"> Specify the usage rights that apply
354
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>
355

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

    
359
<a name="AdditionalInformation"></a>
360
<tr><td class="borderbottom" colspan="2" align="left"><span class="label">Additional Information:</span><span class="regtext"> Add
361
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 
362
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.).</span></td></tr>
363
</table>
364
<p></p>
365

    
366
[% INCLUDE $templates.footer %]
(9-9/30)