Project

General

Profile

« Previous | Next » 

Revision 1991

Revised the registry guide to include descriptions of the new fields, and
made some minor formatting changes.

View differences:

lib/style/common/templates/entryForm.tmpl
1314 1314
  </p>
1315 1315
  <table border="0" cellspacing="0" cellpadding="9" width="760" bgcolor="#c6d6e7">
1316 1316
    <tr> 
1317
      <td valign="TOP" colspan="3"><font size="-1" color="#ff0000"> 
1317
      <td valign="TOP" colspan="3">
1318 1318
        <input type="CHECKBOX" name="useOrigAddress" [%useOrigAddress%]>
1319 1319
        Use the same address as DATA SET ORIGINATOR above (If you check this box, 
1320
        you don't need to fill in the address fields below). </font></td>
1320
        you don't need to fill in the address fields below).</td>
1321 1321
    </tr>
1322 1322
    <tr> 
1323 1323
      <td valign="TOP" colspan="8"> 
1324
        <p><font size="-1"> 
1324
        <p>
1325 1325
          <input type="TEXT" name="origNamefirstContact" value="[%origNamefirstContact%]" size="40">
1326
          <b><font color="#ff0000">*</font>First Name</b></font></p>
1327
        <p><font size="-1"> 
1326
          <b><font color="#ff0000">*</font>First Name</b></p>
1327
        <p>
1328 1328
          <input type="TEXT" name="origNamelastContact" value="[%origNamelastContact%]" size="40">
1329
          <b><font color="#ff0000">*</font>Last Name</b></font></p>
1330
        <p><font size="-1"> 
1329
          <b><font color="#ff0000">*</font>Last Name</b></p>
1330
        <p>
1331 1331
          <input type="TEXT" name="origNameOrgContact" value="[%origNameOrgContact%]" size="60">
1332
          <b>Organization Name</b></font></p>
1333
        <p><font size="-1"><b>Originator Address Information (for Individual or 
1334
          Organization):</b></font></p>
1335
        <p><font size="-1"> 
1332
          <b>Organization Name</b></p>
1333
        <p><b>Originator Address Information (for Individual or 
1334
          Organization):</b></p>
1335
        <p>
1336 1336
          <input type="TEXT" name="origEmailContact" value="[%origEmailContact%]">
1337
          <b>E-Mail</b></font></p>
1338
        <p><font size="-1"> 
1337
          <b>E-Mail</b></p>
1338
        <p>
1339 1339
          <input type="TEXT" name="origPhoneContact" value="[%origPhoneContact%]">
1340
          <b>Phone</b></font></p>
1341
        <p><font size="-1"> 
1340
          <b>Phone</b></p>
1341
        <p>
1342 1342
          <input type="TEXT" name="origFAXContact" value="[%origFAXContact%]">
1343
          <b>FAX</b> </font></p>
1344
        <p><font size="-1"><b>Delivery information (number, street, unit, etc., 
1345
          comma-separated)</b></font></p>
1346
        <p><font size="-1"> 
1347
          <textarea rows="5" cols="60" name="origDeliveryContact">[%origDeliveryContact%]</textarea>
1348
          </font></p>
1349
        <p><font size="-1"> 
1343
          <b>FAX</b></p>
1344
        <p><b>Delivery information (number, street, unit, etc., 
1345
          comma-separated)</b></p>
1346
        <p>
1347
          <textarea rows="5" cols="60" name="origDeliveryContact">[%origDeliveryContact%]</textarea></p>
1348
        <p>
1350 1349
          <input type="TEXT" name="origCityContact" value="[%origCityContact%]" size="50">
1351
          <b>City</b></font></p>
1350
          <b>City</b></p>
1352 1351
        <p> 
1353 1352
          <select name="origStateContact">
1354 1353
	    [% IF form == 're_entry' %]	
......
1416 1415
            <option>Wisconsin</option>
1417 1416
            <option>Wyoming</option>
1418 1417
          </select>
1419
          <b><font size="-1">State</font></b>&nbsp;&nbsp;&nbsp;
1420
          <font size="-1"> 
1418
          <b>State</font></b>&nbsp;&nbsp;&nbsp;
1421 1419
          <input type="TEXT" name="origStateOtherContact" value="[%origStateOtherContact%]">
1422
          <b>Other State or Province</b></font>
1420
          <b>Other State or Province</b>
1423 1421
          </p>
1424
        <p><font size="-1"> 
1422
        <p>
1425 1423
          <input type="TEXT" name="origZIPContact" size="10" value="[%origZIPContact%]">
1426
          <b>ZIP</b></font></p>
1427
        <p><font size="-1"> 
1424
          <b>ZIP</b></p>
1425
        <p>
1428 1426
          <input type="TEXT" name="origCountryContact" value="[%origCountryContact%]">
1429
          <b>Country</b></font></p>
1427
          <b>Country</b></p>
1430 1428
      </td>
1431 1429
    </tr>
1432 1430
  </table>
lib/style/common/templates/genericGuide.tmpl
55 55
<p><font size="4"><b>Name of Person completing this form:</b></font> 
56 56
Enter the name of the person completing this form (your name).<font size="2"></font></p>
57 57

  
58
[% IF cfg == 'nceas' %]
59
<p><font size="4"><b>Working Group(s):</b></font> Select one or more
60
NCEAS activities from the list to indicate that the data set is
61
affiliated with that working group or activity.  We use "affiliation" 
62
in a rather permissive sense to mean, for example, that the data set was or has
63
been generated by the activity; that the owner of the data is affiliated
64
with the activity, or that the data set is owned by the activity, etc. Both
65
derived data sets that result from synthesis activities and original raw data
66
sets that contribute to synthesis can be included in the repository and should
67
be associated with the appropriate NCEAS activities.
68
<font size="2"></font></p>
69
[% ELSE %]
58 70
<p><font size="4"><b>[% usite %] Name:</b></font> Select a
59 71
[% lsite %] from the drop-down list to indicate that the data set is
60 72
affiliated with the [% lsite %]. We use "affiliation" in a rather
......
69 81
abstract and/or title. You can also indicate this in the keywords
70 82
with a locality keyword. You may also indicate the locality in the
71 83
dataset title below, if appropriate.</p>
84
[% END %]
72 85

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

  
77 95
<p>Examples:</p>
78 96

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

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

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

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

  
83 107
<p>&nbsp</p>
84 108
<hr>
85 109
<a name="DataSetOriginator"></a>
......
258 282
<p><b><font size="4" color="#0000ff">SPATIAL COVERAGE OF DATA</font></b> 
259 283
<p>&nbsp</p>
260 284

  
285
<p><b><font size="4">Geographic Description</font><font size="4">:</font></b>
286
Enter a general description of the geographic area in which the data were collected. This can be a simple place name (e.g., Santa Barbara) or a fuller description.  This field supplements the coordinates below and helps orient the data user
287
about the general location of the study.
288
</p>
289

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

  
295
[% IF cfg != 'nceas' %]
266 296
<p><b>Note the checkbox "Use [% lsite %] coordinates"</b>. If checked,
267 297
this box indicates that the data were collected at the [% lsite %]. If
268 298
you check this box, you don't need to fill in the lat./long. fields
......
274 304
in the corresponding fields. (Please contact [%adminname %] at <a href=
275 305
"mailto:[% recipient %]">[% recipient %]</a> if you
276 306
have the missing coordinates for any of the sites.)</p>
307
[% END %]
277 308

  
278 309
<p>Enter <b>one lat./long. pair only to indicate a point
279 310
location</b>. Enter both lat./long pairs to indicate a bounding
......
294 325
the second coordinate pair is the southeast corner of the bounding
295 326
box.</p>
296 327

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

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

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

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

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

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

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

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

Also available in: Unified diff