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
				<span class="regtext"> 
30
					The first and last names of the person completing this form.
31
				</span>
32
				
33
			</div>
34
				
35
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="BasicInformation"></a>
36
BASIC INFORMATION</td></tr> 
37
<tr><td colspan="2" align="left"><span class="text-info">*Data Set Title:</span><span class="regtext"> A descriptive title
38
of the data set. The title should provide enough information for
39
someone casually scanning a list of data sets to know whether the data are
40
relevant to them.  This implies that the data context should be indicated 
41
in the title without making the title be too long. In general, the title
42
should indicate what kind of data were collected and the spatial,
43
taxonomic, and temporal extents the data set covers.</span></td></tr>
44

    
45
<tr><td align="left"><span class="regtext"><u>Examples of descriptive titles:</u></td>
46
<td align="left"><span class="regtext"><u>Examples of incomplete titles:</u></td></tr>
47

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

    
50

    
51

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

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

    
56
[% IF cfg == 'nceas' %]
57
<tr><td colspan="2" align="left"><span class="text-info">*NCEAS Project(s):</span><span class="regtext"> 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; 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.</td></tr>
66
[% END %]
67

    
68
[% IF cfg == 'esa' || cfg == 'ltss' %]  
69

    
70
<tr><td colspan="2" align="left"><span class="text-info">*Organization Name:</span>
71
<span class="regtext">The name of the organization with which the data set is
72
affiliated. We use "affiliation" in a rather permissive sense to mean, for example, that the data set was or has
73
been generated at the organization; that the owner of the data is affiliated
74
with the organization or was affiliated with the organization when the data
75
set was generated; that the data set is owned by the organization; etc.</td></tr>
76

    
77
<tr><td align="left"><span class="regtext"><u>Examples of correct organization names:</u></td>
78
   <td align="left"><span class="regtext"><u>Examples of incorrect organization names:</u></td></tr>
79

    
80
<tr><td align="left" valign="top"><span class="regtext">University of Michigan Biological Station
81
<br>Duke University FACE Facility<br>National Center for Ecological Analysis and Synthesis</br></td>
82
  <td align="left"><span class="regtext">Michigan Station<br>Duke University<br>University of California Santa Barbara</br>
83
</td></tr>
84
[% END %]
85

    
86
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
87

    
88
<tr><td colspan="2" align="left"><span class="text-info">*[% config.site | ucfirst %] Name:</span>
89
<span class="regtext">Select a [% config.site %] from the drop-down list to indicate that the data set is
90
affiliated with the [% config.site %]. We use "affiliation" in a rather
91
permissive sense to mean, for example, that the data set was or has
92
been generated at the [% config.site %]; that the owner is affiliated
93
with the [% config.site %] or was affiliated with the [% config.site %] when the data
94
set was generated; or that the data set is owned by the [% config.site %]; etc.
95
</td></tr>
96

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

    
103
[% END %]
104

    
105

    
106

    
107

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

    
110

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

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

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

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

    
125
<tr><td colspan="2" align="left"><span class="text-info">Organization Name:</span>
126
<span class="regtext">The name of the organization from which the data set
127
originated.</span></td></tr>
128

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

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

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

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

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

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

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

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

    
159
<tr><td colspan="2" align="left"><span class="text-info">Country:</span>
160
<span class="regtext">The country
161
for the principal data set owner's address.</span></td></tr>
162

    
163

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

    
166
<tr><td colspan="2" align="left"><span class="regtext">
167
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 
168
the data set), select a role for this person, and click on "Add Associated Party".  Repeat to add another associated party.</td></tr> 
169
<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 
170
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".
171
 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>
172

    
173

    
174
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
175
<a name="DataSetAbstract"></a>*DATA SET ABSTRACT</td></tr>
176

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

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

    
188
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
189
<a name="KeywordInformation"></a>KEYWORD INFORMATION</td></tr>
190

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

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

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

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

    
204
   <ul>
205
      <li>Theme: the keyword identifies a particular subject or topic.</li>
206
      <li>Place: the keyword identifies a place.</li>
207
      <li>Stratum: the keyword identifies the layer(s) of any deposited substance.</li>
208
      <li>Temporal: the keyword identifies a time period related to the data set.
209
      <li>Taxonomic: the keyword identifies a particular taxon.</li>
210
</ul></span></td></tr>
211
<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
212
(GCMD) or not to choose your keywords.</span></td></tr> 
213

    
214

    
215

    
216
<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>  
217

    
218

    
219
<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 
220
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". 
221
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>
222

    
223

    
224
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
225
<a name="TemporalCoverageOfData"></a>TEMPORAL COVERAGE OF DATA</td></tr>
226

    
227
<tr><td colspan="2" align="left"><span class="text-info">*Start Date:</span><span class="regtext"> The first year, month, and
228
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
229
drop-down menus.</span></td></tr>
230

    
231
<tr><td colspan="2" align="left"><span class="text-info">Stop Date:</span><span class="regtext"> The last year, month, and
232
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> 
233
<u>Note:</u> Leave "Stop Date" blank if your data set is open-ended.</span></td></tr>
234

    
235
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
236
<a name="SpatialCoverageOfData"></a>SPATIAL COVERAGE OF DATA</span></td></tr> 
237

    
238

    
239
<tr><td colspan="2" align="left"><span class="text-info">*Geographic Description:</span><span class="regtext"> 
240
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.
241
This field supplements the coordinates provided below and helps orient the data user about the general location of the study.</span></td></tr>
242

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

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

    
250
<tr><td colspan="2" align="left"><span class="regtext">If you enter <b>both coordinate pairs</b>: This indicates a
251
bounding box. The first coordinate pair is the northwest corner and
252
the second coordinate pair is the southeast corner of the bounding
253
box.</span></td></tr>
254

    
255
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
256
<a name="TaxonomicCoverage"></a>
257
TAXONOMIC COVERAGE OF DATA</td></tr>
258

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

    
266
<tr><td colspan="2" align="left"><span class="regtext">Please check the <a href=
267
"http://darwin.zoology.gla.ac.uk/~rpage/MyToL/www/index.php" target="darwin">Glasgow Taxonomic Name Server</a> or the <a href=
268
"http://www.itis.usda.gov/" target="itis">Integrated Taxonomic Information System</a> for correct spelling 
269
of taxonomic names.</span></td></tr>
270
<tr><td colspan="2" align="left"><span class="regtext">For each taxon, follow the three steps below:</span></td></tr>
271
<tr><td colspan="2" align="left"><span class="text-info">1. Taxonomic Rank:</span><span class="regtext"> Enter the level in the taxonomic hierarchy 
272
(Kingdom, Phylum, Class, Order, Family, Genus, or Species).</span></td></tr> 
273
<tr><td colspan="2" align="left"><span class="text-info">2. Taxonomic Name:</span><span class="regtext"> Enter the scientific name for the level 
274
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>
275

    
276
<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>
277

    
278
<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 
279
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 
280
down arrows.</span></td></tr>
281

    
282
<tr><td colspan="2" align="left"><span class="text-info">Taxonomic Reference:</span><span class="regtext"> The name
283
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>
284

    
285
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
286
<a name="Methods"></a>DATA COLLECTION METHODS</td></tr> 
287

    
288

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

    
292
<tr><td colspan="2" align="left"><span class="text-info">Method Description:</span><span class="regtext"> Description of the method used.  
293
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.  
294
You can add multiple paragraphs to the description by clicking on the "Add Paragraph to Method Description"
295
button (paragraphs added by using the ENTER key in the Method Description field will not appear as paragraphs in the submitted form).
296
</span></td></tr>
297

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

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

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

    
316
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
317
<a name="DataSetContactAddress"></a>                                   
318
DATA SET CONTACT</td></tr>
319

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

    
325

    
326
<tr class="sectheader"><td class="topbottom" colspan="2" align="left">
327
<a name="DistributionIinformation"></a>
328
DISTRIBUTION INFORMATION</font></td></tr> 
329

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

    
335
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
336
Keep in mind that this information, although not required, can be extremely useful
337
for locating the data set at a [% config.site %].
338
[%END%]
339
</span></td></tr>
340
<tr><td colspan="2" align="left"><span class="text-info">*Data Medium</font>:</span><span class="regtext"> Specify whether the data medium is 
341
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>
342

    
343

    
344
<tr><td colspan="2" align="left"><span class="text-info">*Usage Rights:</span><span class="regtext"> Specify the usage rights that apply
345
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>
346

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

    
350
<a name="AdditionalInformation"></a>
351
<tr><td class="borderbottom" colspan="2" align="left"><span class="text-info">Additional Information:</span><span class="regtext"> Add
352
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 
353
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.).</span></td></tr>
354
</table>
355

    
356
			</div> <!-- end row-fluid -->
357

    
358
		</div>
359
	</article>
360
[% INCLUDE $templates.footer %]
(6-6/10)