Metacat

<!--

  *  '$RCSfile$'

  *    Copyright: 2000 Regents of the University of California and the

  *               National Center for Ecological Analysis and Synthesis

  *  For Details: http://www.nceas.ucsb.edu/

  *

  *   '$Author: jones $'

  *     '$Date: 2004-01-07 11:02:11 -0800 (Wed, 07 Jan 2004) $'

  * '$Revision: 1991 $'

  * 

  * This program is free software; you can redistribute it and/or modify

  * it under the terms of the GNU General Public License as published by

  * the Free Software Foundation; either version 2 of the License, or

  * (at your option) any later version.

  *

  * This program is distributed in the hope that it will be useful,

  * but WITHOUT ANY WARRANTY; without even the implied warranty of

  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

  * GNU General Public License for more details.

  *

  * You should have received a copy of the GNU General Public License

  * along with this program; if not, write to the Free Software

  * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

-->

[% INCLUDE "genericHeader.tmpl" %]

[% IF cfg == 'nrs' %]

  [% lsite = 'reserve' %]

  [% usite = 'Reserve' %]

[% ELSE %]

  [% lsite = 'station' %]

  [% usite = 'Station' %]

[% END %]

<p>This guide provides information and help how to

fill in the [% orgabbrev %] Data Registry Form. Some fields are required

and some fields are optional. A red asterisk (<b><font size=

"4" color="#ff0000">*</font></b>) indicates that a

field is required. A few fields are repeatable up to ten times.

Those are the data set originator names and keyword information.

Note that those repeatable fields are also optional, so you need to

fill in only as many of those as you need.</p> 

<p>Information on individual fields and examples

for their content follow.</p>

<p>&nbsp</p>

<hr>

<a name="BasicInformation"></a>

<p><b><font size="4" color="#0000ff">BASIC INFORMATION</font></b> 

<p>&nbsp</p>

<p><font size="4"><b>Name of Person completing this form:</b></font> 

Enter the name of the person completing this form (your name).<font size="2"></font></p>

[% IF cfg == 'nceas' %]

<p><font size="4"><b>Working Group(s):</b></font> Select one or more

NCEAS activities from the list to indicate that the data set is

affiliated with that working group or activity.  We use "affiliation" 

in a rather permissive sense to mean, for example, that the data set was or has

been generated by the activity; that the owner of the data is affiliated

with the activity, or that the data set is owned by the activity, etc. Both

derived data sets that result from synthesis activities and original raw data

sets that contribute to synthesis can be included in the repository and should

be associated with the appropriate NCEAS activities.

<font size="2"></font></p>

[% ELSE %]

<p><font size="4"><b>[% usite %] Name:</b></font> Select a

[% lsite %] from the drop-down list to indicate that the data set is

affiliated with the [% lsite %]. We use "affiliation" in a rather

permissive sense to mean, for example, that the data set was or has

been generated at the [% lsite %]; that the originator is affiliated

with the [% lsite %], or was affiliated with the [% lsite %] when the data

set was generated, that the data set is owned by the [% lsite %], etc.

<font size="2"></font></p>

<p>Note: If the data was collected at a site other than an OBFS

[% lsite %] listed in the pull-down menu, you can indicate so in the

abstract and/or title. You can also indicate this in the keywords

with a locality keyword. You may also indicate the locality in the

dataset title below, if appropriate.</p>

[% END %]

<b><font size="4"></font></b>

<p><b><font size="4">Data Set Title:</font></b> Descriptive title

of the data set. In general the title should provide enough information for

someone casually scanning a list of data sets to know whether the data are

relevant to them.  This implies that the data context should be indicated 

in the title without making the title be too long. In general, the title

should indicate what kind of data were collected and the spatial,

taxonomic, and temporal extents the data covers.</p>

<p>Examples:</p>

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

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

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

<p>Mammals Data</p>

<p>Abundance Data</p>

<p>Meterological Data</p>

<p>&nbsp</p>

<hr>

<a name="DataSetOriginator"></a>

<p><b><font size="4" color="#0000ff">DATA SET ORIGINATOR</font></b> 

<p>&nbsp</p>

Person(s) or organization that developed the data

set. The first originator provided on the form is EITHER an

individual person OR an organization, including optional address

information.</p>

<p>This originator and the data set contact below may be the same

person or organization.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Originator's Role:</font> <font size="5">

</font></b>You will probably just want to leave the generic

default, which is "originator", but you can choose a more specific

originator's role (e.g. Principal Investigator, Publisher, etc.)

from the pull-down list, if appropriate, e.g Principal

Investigator.</p>

<b><font size="4"></font></b>

<p><b><font size="4">First Name:</font> <font size="5">

</font></b>Self-explanatory.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Last Name:</font> <font size="5">

</font></b>Self-explanatory.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Organization Name:</font> <font size="5">

</font></b>The name of the organization from which the data

originate (not required of you provide first/last names above)</p>

<b><font size="4"></font></b>

<p><b><font size="4">Originator Address Information (for Individual

or Organization):</font></b></p>

<p><b><font size="4">E-Mail:</font> <font size="5"></font></b>The

e-mail address under which the originator can be contacted.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Phone:</font> <font size="5">

</font></b>Originator's phone number in the format area code plus

number, 999-999-9999.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Delivery Information:</font> <font size="5">

</font></b>A comma-separated list of street number, street, Unit,

etc., comma-separated). Example: 735 State Street, Suite 300</p>

<b><font size="4"></font></b>

<p><b><font size="4">City:</font> <font size="5"></font></b>City

name of the originator address.</p>

<b><font size="4"></font></b>

<p><b><font size="4">State:</font> <font size="5"></font></b>Select

a state for the address from the pull-down menu. For a shortcut,

press the C-key to skip to California.</p>

<b><font size="4"></font></b>

<p><b><font size="4">ZIP:</font> <font size="5"></font></b>The ZIP

code of the originator address.</p>

<p>&nbsp</p>

<hr>

<a name="AdditionalOriginators"></a>

<p><b><font size="4" color="#0000ff">ADDITIONAL ORIGINATORS</font></b> 

<p>&nbsp</p>

Enter the first and last names of up to 10 additional

originators, and select their specific role from the pull-down

menu. The default for the role pull-down menu is Principal

Investigator. Example: First Name: Mark; Last Name: Seablad; Role:

Editor</p>

<p>&nbsp</p>

<hr>

<a name="DataSetAbstract"></a>

<b><font size="4"></font></b>

<p><b><font size="4">Data Set Abstract:</font> <font size="5">

</font></b>Short (approximately 1/2 page or less) summary of the

purpose and content of the dataset.</p>

<p>Example: Data were collected every year in summer and fall from

1967 to 1979. Trapping was conducted only in the fall from 1980 to

1988. For each specimen taken, data were recorded on species, date,

location, time, sex, and body measurements including total length,

length of tail, length of hind foot, length of ear, and body mass.

The purpose of the data was to index the population size of all

species present over a long time period.&nbsp;</p>

<p>&nbsp</p>

<hr>

<a name="KeywordInformation"></a>

<p><b><font size="4" color="#0000ff">KEYWORD INFORMATION</font></b> 

<p>&nbsp</p>

Provide information for up to ten keywords here. The

information is provided in groups of three fields: keyword, keyword

type and keyword thesaurus, as follows. Keyword information will be

useful for locating data in catalog searches. The keywords listed

here may or may not appear in the title or abstract. Both the

keyword type and thesaurus are optional.</p>

<p>Examples: keyword: Peromyscus; Keyword Type: taxonomic; Keyword

Thesaurus: none</p>

<b><font size="4"></font></b>

<p><b><font size="4">Keyword:</font></b> Commonly used formalized

word( s) or phrase( s) used to describe the subject.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Keyword Type:</font> <font size="5">

</font></b>Term used to group similar keywords. Default: none. The

different types are:</p>

<p>theme: keyword identifies a particular subject or topic</p>

<p>discipline: keyword identifies a branch of instruction or

specialized learning</p>

<p>taxonomic: keyword identifies a particular taxa</p>

<p>place: keyword identifies a place</p>

<p>stratum: keyword identifies the layer(s) of any deposited

substance</p>

<p>temporal: keyword identifies a time period related to the

dataset</p>

<p>theme: keyword identifies a particular subject or topic</p>

<font size="1"></font>

 <b><font size="4"></font></b>

<p><b><font size="4">Keyword Thesaurus:</font> <font size="5">

</font></b>The Name of the formally registered thesaurus, or a

similar authoritative source of keywords, from which the keyword

was chosen. Default: none (no thesaurus used; used own

keywords)</p>

<p>An example for a thesaurus is the <a href=

"http://gcmd.nasa.gov/valids/">NASA Global Change Master Directory

(GCMD)</a>. Have a look at the GCMD keywords to get an idea of what

keywords they use. If you find suitable keywords there that

appropriately describe your data, use them and select GCMD for the

keywords' thesaurus.</p>

<p>&nbsp</p>

<hr>

<a name="TemporalCoverageOfData"></a>

<p><b><font size="4" color="#0000ff">TEMPORAL COVERAGE OF DATA</font></b> 

<p>&nbsp</p>

<p><b><font size="4">Beginning Date of Data Set:</font> <font size=

"5"></font></b>The first year (and optionally month, or month and

day) of the collection/creation of the data set, in the format

yy/mm/dd.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Ending Date of Data Set:</font> <font size=

"5"></font></b>The last year (and optionally month, or month and

day) for the collection/creation of the data set, in the format

yy/mm/dd. <b>If your dataset is open-ended, leave the ending date

open</b>, provide no ending date at all.</p>

<p>&nbsp</p>

<hr>

<a name="SpatialCoverageOfData"></a>

<p><b><font size="4" color="#0000ff">SPATIAL COVERAGE OF DATA</font></b> 

<p>&nbsp</p>

<p><b><font size="4">Geographic Description</font><font size="4">:</font></b>

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

about the general location of the study.

</p>

<p><b><font size="4">Coordinates</font> (in Degrees, Minutes and

Seconds)<font size="4">:</font> <font size="5">

</font></b>Coordinates provide the location where the data set was

collected.</p>

[% IF cfg != 'nceas' %]

<p><b>Note the checkbox "Use [% lsite %] coordinates"</b>. If checked,

this box indicates that the data were collected at the [% lsite %]. If

you check this box, you don't need to fill in the lat./long. fields

below). 

However, I presently do not have the coordinates for some

[% orgabbrev %] [% lsite %]s, which will be indicated when you 

submit the form. In this case, you will have to provide the coordinates 

in the corresponding fields. (Please contact [%adminname %] at <a href=

"mailto:[% recipient %]">[% recipient %]</a> if you

have the missing coordinates for any of the sites.)</p>

[% END %]

<p>Enter <b>one lat./long. pair only to indicate a point

location</b>. Enter both lat./long pairs to indicate a bounding

box, with the first pair indicating the northwest corner and the

second pair the southeast corner of the box. At least one

lat./long. pair is required. Pull-down lists provide the North (N)

or South (S) orientation for the latitudes, and the West (W) and

East (E) orientation for the longitudes.</p>

<p>If you enter <b>one coordinate pair only</b>: This indicates a

point location. You may want to do this if you only know the

general location of a site on the [% lsite %]. In this case provide the

point coordinates for the [% lsite %]. Example: 36° 12' 30"N and

121&deg;33'3"W</p>

<p>If you enter <b>both coordinate pairs</b>: This indicates a

bounding box. The first coordinate pair is the northwest corner and

the second coordinate pair is the southeast corner of the bounding

box.</p>

<p>&nbsp</p>

<hr>

<a name="TaxonomicCoverage"></a>

<p><b><font size="4" color="#0000ff">TAXONOMIC COVERAGE OF DATA</font></b> 

<p>&nbsp</p>

<p><b><font size="4">List of taxa</font><font size="4">:</font></b>

Provide a list of the taxa that are associated with this data set. 

This includes taxa for which the data set contains measurements, and taxa

for which the data have relevance in less direct ways.  In general, if a

data user searching for a particular taxonomic name should find this data

then the taxon should be included in this list. The Taxon Rank should 

indicate the level in the taxonomic hierarchy (e.g., Phylum or Species) 

and the Taxonomic Name should be the scientific name for the organism at 

that level (e.g., Ursus arctos).  You can add mutliple taxa to the list by

clicking the "Add taxon" button.

</p>

<p>&nbsp</p>

<hr>

<a name="Methods"></a>

<p><b><font size="4" color="#0000ff">METHODS</font></b> 

<p>&nbsp</p>

<p><b><font size="4">Title of method</font><font size="4">:</font></b>

Provide an optional title for the method (e.g., Zooplankton abundance using

radial quadrat subsampling).

</p>

<p><b><font size="4">Method description</font><font size="4">:</font></b>

Describe the methods used to generate the data.  This is intended to be a

general overview of the methods that is suitable to help a potential user

of the data decide if the data are appropriate for their purposes.  You can

add multiple paragraphs to the description by clicking the "Add Paragraph"

button.

</p>

<p><b><font size="4">Description of Study Extent</font><font size="4">:</font></b>

Describe the temporal, spatial and taxonomic extent of the study, supplementing

the information on coverage provided above. For example, if the temporal

coverage of the data is 1990-2000, you might provide details about any years

that were missed or the months in which sampling actually occurred. If you

provide information in this field (Study Extent), then you must also provide

a Methods Description and a Sampling description.

</p>

<p><b><font size="4">Sampling Description</font><font size="4">:</font></b>

Describe the sampling design of the study. For example, you might describe

the way in which treatments were assigned to sampling units.  If you provide

information in this field (Sampling Description), then you must also provide

a Methods Description and a Study Extent.

</p>

<p>&nbsp</p>

<hr>

<a name="DataSetContactAddress"></a>

<p><b><font size="4" color="#0000ff">DATA SET CONTACT ADDRESS</font></b> 

<p>&nbsp</p>

Address to contact for more information on the data

set or to obtain the data described by this entry. This is

analogous to the Originator Address Information above. Please see

there.</p>

<p>&nbsp</p>

<hr>

<a name="DistributionIinformation"></a>

<p><b><font size="4" color="#0000ff">DISTRIBUTION INFORMATION</font></b> 

<p>&nbsp</p>

<a name=Site-specificCode></a>

<b><font size="4"></font></b>

<p><b><font size="4">Dataset Name or Identifier (important)</font>:</b> 

Enter the datasets filename (and path) here, if available.  Alternatively,

use other pertinent information that can help to identify and locate

the dataset within your site's data management system (this may include

references to hardcopy information, such as file numbers, etc.).  Keep in

mind that this information, while not required, can be extremely useful

for locating the dataset at a [% lsite %].</p>

<b><font size="4"></font></b>

<p><b><font size="4">Data Medium</font>:</b> The kind of medium the

data is recorded on.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Other Data Medium</font></b>: Specify any

other data medium you use. &nbsp;</p>

<p><b><font size="4">Use Constraints:</font> <font size="5">

</font></b>Choose from a pull-down list with use constraints apply

to this data set. Examples: public domain; obtain permission from

PI.</p>

<b><font size="4"></font></b>

<p><b><font size="4">Other Use Constraints:</font></b> Specify any

other use constraints.</p>

<b><font size="4"></font></b>

<p><b><font size="4">URL</font></b>: Provide any network link here for the

location of the actual data set (if available) or for more

metadata<b>.</b></p>

<p>&nbsp</p>

<hr>

<a name="AdditionalInformation"></a>

<b><font size="4"></font></b>

<p><b><font size="4">Additional Information/Remarks:</font></b> Add

any information here that you deem relevant to the data set and

that is not covered in the form.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

[% INCLUDE "genericFooter.tmpl" %]