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

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

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

    
48

    
49

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

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

    
54
[% IF cfg == 'nceas' %]
55
<tr><td colspan="2" align="left"><span class="text-info">*NCEAS Project(s):</span><span class="regtext"> Select one or more
56
NCEAS activities from the list to indicate that the data set is
57
affiliated with that working group or activity.  We use "affiliation" 
58
in a rather permissive sense to mean, for example, that the data set was or has
59
been generated by the activity; that the owner of the data is affiliated
60
with the activity; that the data set is owned by the activity; etc. Both
61
derived data sets that result from synthesis activities and original raw data
62
sets that contribute to synthesis can be included in the repository and should
63
be associated with the appropriate NCEAS activities.</td></tr>
64
[% END %]
65

    
66
[% IF cfg == 'esa' || cfg == 'ltss' %]  
67

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

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

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

    
84
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
85

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

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

    
101
[% END %]
102

    
103

    
104

    
105

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

    
108

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    
161

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

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

    
171

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

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

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

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

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

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

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

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

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

    
212

    
213

    
214
<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>  
215

    
216

    
217
<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 
218
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". 
219
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>
220

    
221

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

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

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

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

    
236

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

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

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

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

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

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

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

    
274
<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>
275

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

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

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

    
286

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

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

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

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

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

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

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

    
323

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

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

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

    
341

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

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

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

    
354
			</div> <!-- end row-fluid -->
355

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