Project

General

Profile

metacat / lib / style / common / templates / metacatui / genericGuide.tmpl @ 7926

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
<table class="tables" cellpadding="8" cellspacing="0">
24

    
25
<tr class="sectheader"><td class="borderbottom" colspan="2" align="left"><a name="Submitter"></a>
26
NAME OF SUBMITTER</td></tr> 
27
<tr><td colspan="2" align="left"><span class="label">
28
*First name, *Last name:</span><span class="regtext"> 
29
The first and last names of the person completing this form.</span></td></tr>
30

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

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

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

    
46

    
47

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

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

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

    
64
[% IF cfg == 'esa' || cfg == 'ltss' %]  
65

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

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

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

    
82
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%]
83

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

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

    
99
[% END %]
100

    
101

    
102

    
103

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

    
106

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

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

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

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

    
121
<tr><td colspan="2" align="left"><span class="label">Organization Name:</span>
122
<span class="regtext">The name of the organization from which the data set
123
originated.</span></td></tr>
124

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

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

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

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

    
138
<tr><td colspan="2" align="left"><span class="label">City:</span>
139
<span class="regtext">The city
140
name of the principal data set owner's address.</span></td></tr>
141

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

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

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

    
155
<tr><td colspan="2" align="left"><span class="label">Country:</span>
156
<span class="regtext">The country
157
for the principal data set owner's address.</span></td></tr>
158

    
159

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

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

    
169

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

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

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

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

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

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

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

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

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

    
210

    
211

    
212
<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>  
213

    
214

    
215
<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 
216
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". 
217
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>
218

    
219

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

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

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

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

    
234

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

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

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

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

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

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

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

    
272
<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>
273

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

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

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

    
284

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

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

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

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

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

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

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

    
321

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

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

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

    
339

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

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

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

    
352
		</div>
353
	</article>
354
[% INCLUDE $templates.footer %]