Revision 2402
Added by sgarg over 19 years ago
| lib/style/common/templates/genericGuide.tmpl | ||
|---|---|---|
| 33 | 33 |
[% usite = 'Station' %] |
| 34 | 34 |
[% END %] |
| 35 | 35 |
|
| 36 |
<table class="intro" cellpadding="8" cellspacing="0"> |
|
| 36 | 37 |
|
| 37 |
<p>This guide provides information on how to |
|
| 38 |
fill in the online [% orgabbrev %] Data Registry Form. Some fields are required |
|
| 39 |
and some fields are optional. Required fields appear in <b><font color="#ff0000">red</font></b>. |
|
| 40 |
A few fields are repeatable up to ten times. These are the associated parties, keywords, taxa, and methods fields. |
|
| 41 |
Note that those repeatable fields are also optional, so you need to |
|
| 42 |
fill in only as many of those as you need.</p> |
|
| 38 |
<tr><td align="left"><span class="emphasis">Guide for Completing the Data Registry Form</td></tr> |
|
| 39 |
<tr><td align="left"><span class="regtext">This guide provides information on how to |
|
| 40 |
fill in the online [% orgabbrev %] Data Registry Form. Some fields are required (denoted by an asterisk *) |
|
| 41 |
and some fields are optional. The associated parties, keywords, taxa, and methods fields are repeatable (i.e., you may input additional associated parties, keywords, etc. if needed). |
|
| 42 |
</span></td></tr> |
|
| 43 |
<tr><td align="left"><span class="regtext">Information on individual fields and examples |
|
| 44 |
for their content are provided below.</td></tr> |
|
| 45 |
<tr><td></td></tr> |
|
| 43 | 46 |
|
| 44 |
<p>Information on individual fields and examples |
|
| 45 |
for their content are provided below.</p> |
|
| 46 | 47 |
|
| 47 |
<p> </p> |
|
| 48 |
<hr> |
|
| 49 |
<a name="BasicInformation"></a> |
|
| 50 |
<p><b><font size="4" color="#0000ff">BASIC INFORMATION</font></b> |
|
| 51 |
<p> </p> |
|
| 48 |
<table class="tables" cellpadding="8" cellspacing="0"> |
|
| 52 | 49 |
|
| 53 |
<p><font size="4"><b>Name of Person completing this form:</b></font> |
|
| 54 |
Enter the name of the person completing this form (your name).<font size="2"></font></p> |
|
| 55 | 50 |
|
| 51 |
|
|
| 52 |
<tr class="sectheader"><td class="borderbottom" colspan="2" align="left"><a name="BasicInformation"></a> |
|
| 53 |
BASIC INFORMATION - name of person completing this form.</td></tr> |
|
| 54 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label"> |
|
| 55 |
*First name, *Last name:</span><span class="regtext"> |
|
| 56 |
The first and last names of the person completing this form.</span></td></tr> |
|
| 57 |
|
|
| 58 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Data Set Title:</span><span class="regtext"> A descriptive title |
|
| 59 |
of the data set. The title should provide enough information for |
|
| 60 |
someone casually scanning a list of data sets to know whether the data are |
|
| 61 |
relevant to them. This implies that the data context should be indicated |
|
| 62 |
in the title without making the title be too long. In general, the title |
|
| 63 |
should indicate what kind of data were collected and the spatial, |
|
| 64 |
taxonomic, and temporal extents the data set covers.</span></td></tr> |
|
| 65 |
|
|
| 66 |
<tr class="sectbody"><td align="left"><span class="regtext"><u>Examples of descriptive titles:</u></td> |
|
| 67 |
<td align="left"><span class="regtext"><u>Examples of incomplete titles:</u></td></tr> |
|
| 68 |
|
|
| 69 |
<tr class="sectbody"><td align="left" valign="top"><span class="regtext">Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988. |
|
| 70 |
<br>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</td> |
|
| 71 |
|
|
| 72 |
<td align="left" valign="top"><span class="regtext">Mammals Data<br>Water Chemistry Data</td></tr> |
|
| 73 |
|
|
| 74 |
|
|
| 56 | 75 |
[% IF cfg == 'nceas' %] |
| 57 |
<p><font size="4"><b>Working Group(s):</b></font> Select one or more
|
|
| 76 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*NCEAS Project(s):</span><span class="regtext"> Select one or more
|
|
| 58 | 77 |
NCEAS activities from the list to indicate that the data set is |
| 59 | 78 |
affiliated with that working group or activity. We use "affiliation" |
| 60 | 79 |
in a rather permissive sense to mean, for example, that the data set was or has |
| 61 | 80 |
been generated by the activity; that the owner of the data is affiliated |
| 62 |
with the activity; or that the data set is owned by the activity, etc. Both
|
|
| 81 |
with the activity; that the data set is owned by the activity; etc. Both
|
|
| 63 | 82 |
derived data sets that result from synthesis activities and original raw data |
| 64 | 83 |
sets that contribute to synthesis can be included in the repository and should |
| 65 |
be associated with the appropriate NCEAS activities. |
|
| 66 |
<font size="2"></font></p> |
|
| 67 |
[% ELSE %] |
|
| 68 |
<p><font size="4"><b>[% usite %] Name:</b></font> Select a |
|
| 69 |
[% lsite %] from the drop-down list to indicate that the data set is |
|
| 84 |
be associated with the appropriate NCEAS activities.</td></tr> |
|
| 85 |
[% END %] |
|
| 86 |
|
|
| 87 |
[% IF cfg == 'esa' || cfg == 'ltss' %] |
|
| 88 |
|
|
| 89 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Organization Name:</span> |
|
| 90 |
<span class="regtext">The name of the organization with which the data set is |
|
| 91 |
affiliated. We use "affiliation" in a rather |
|
| 92 |
permissive sense to mean, for example, that the data set was or has |
|
| 93 |
been generated at the organization; that the owner of the data is affiliated |
|
| 94 |
with the organization or was affiliated with the organization when the data |
|
| 95 |
set was generated; that the data set is owned by the organization; etc.</td></tr> |
|
| 96 |
|
|
| 97 |
<tr class="sectbody"><td align="left"><span class="regtext"><u>Examples of correct organization names:</u></td> |
|
| 98 |
<td align="left"><span class="regtext"><u>Examples of incorrect organization names:</u></td></tr> |
|
| 99 |
|
|
| 100 |
<tr class="sectbody"><td align="left" valign="top"><span class="regtext">University of Michigan Biological Station |
|
| 101 |
<br>Duke University FACE Facility<br>National Center for Ecological Analysis and Synthesis</br></td> |
|
| 102 |
<td align="left"><span class="regtext">Michigan Station<br>Duke University<br>University of California Santa Barbara</br> |
|
| 103 |
</td></tr> |
|
| 104 |
[% END %] |
|
| 105 |
|
|
| 106 |
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%] |
|
| 107 |
|
|
| 108 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*[% usite %] Name:</span> |
|
| 109 |
<span class="regtext">Select a [% lsite %] from the drop-down list to indicate that the data set is |
|
| 70 | 110 |
affiliated with the [% lsite %]. We use "affiliation" in a rather |
| 71 | 111 |
permissive sense to mean, for example, that the data set was or has |
| 72 |
been generated at the [% lsite %]; that the originator is affiliated
|
|
| 73 |
with the [% lsite %], or was affiliated with the [% lsite %] when the data
|
|
| 74 |
set was generated, that the data set is owned by the [% lsite %], etc.
|
|
| 75 |
<font size="2"></font></p>
|
|
| 112 |
been generated at the [% lsite %]; that the owner is affiliated
|
|
| 113 |
with the [% lsite %] or was affiliated with the [% lsite %] when the data |
|
| 114 |
set was generated; or that the data set is owned by the [% lsite %]; etc.
|
|
| 115 |
</td></tr>
|
|
| 76 | 116 |
|
| 77 |
<p>Note: If the data was collected at a site other than an OBFS |
|
| 78 |
[% lsite %] listed in the pull-down menu, you can indicate so in the |
|
| 117 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext"><u>Note:</u> |
|
| 118 |
If the data were collected at a site other than a |
|
| 119 |
[% lsite %] listed in the drop-down menu, you can indicate so in the |
|
| 79 | 120 |
abstract and/or title. You can also indicate this in the keywords |
| 80 |
with a locality keyword. You may also indicate the locality in the
|
|
| 81 |
dataset title below, if appropriate.</p> |
|
| 121 |
with a locality keyword.</span></td></tr>
|
|
| 122 |
|
|
| 82 | 123 |
[% END %] |
| 83 | 124 |
|
| 84 |
<b><font size="4"></font></b> |
|
| 85 |
<p><b><font size="4">Data Set Title:</font></b> A descriptive title |
|
| 86 |
of the data set. In general the title should provide enough information for |
|
| 87 |
someone casually scanning a list of data sets to know whether the data are |
|
| 88 |
relevant to them. This implies that the data context should be indicated |
|
| 89 |
in the title without making the title be too long. In general, the title |
|
| 90 |
should indicate what kind of data were collected and the spatial, |
|
| 91 |
taxonomic, and temporal extents the data covers.</p> |
|
| 92 | 125 |
|
| 93 |
<p>Examples:</p> |
|
| 94 | 126 |
|
| 95 |
<p>Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988.</p> |
|
| 96 | 127 |
|
| 97 |
<p>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</p>
|
|
| 128 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="DataSetOriginator"></a>PRINCIPAL DATA SET OWNER</td></tr>
|
|
| 98 | 129 |
|
| 99 |
<p>Bad Examples (not enough information):</p> |
|
| 100 | 130 |
|
| 101 |
<p>Mammals Data</p> |
|
| 102 |
<p>Abundance Data</p> |
|
| 103 |
<p>Meteorological Data</p> |
|
| 131 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">The person responsible for developing the data set. For example, the principal |
|
| 132 |
investigator in a collaborative project, the first author of the main publication using the data set, etc. |
|
| 133 |
The first and last names of the principal data set owner are required; the organization name, e-mail, phone, fax, and |
|
| 134 |
address information are optional.</span></td></tr> |
|
| 104 | 135 |
|
| 105 |
<p> </p> |
|
| 106 |
<hr> |
|
| 107 |
<a name="DataSetOriginator"></a> |
|
| 108 |
<p><b><font size="4" color="#0000ff">PRINCIPAL DATA SET OWNER</font></b> |
|
| 109 |
<p> </p> |
|
| 136 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext"><u>Note:</u><span class="regtext"> If there is more than one owner, information |
|
| 137 |
about the co-owner(s) can be provided in the ASSOCIATED PARTIES section below.</span> |
|
| 110 | 138 |
|
| 111 |
The person(s) or organization that developed the data |
|
| 112 |
set. The first and last names of the principal data set owner are required; the organization name, phone, fax, email and |
|
| 113 |
address information are optional.</p> |
|
| 139 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*First Name:</span> |
|
| 140 |
<span class="regtext">The first name of the principal data set owner.</span></td></tr> |
|
| 114 | 141 |
|
| 115 |
<p>This principal data set owner and the data set contact (below) may be the same
|
|
| 116 |
person.</p>
|
|
| 142 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Last Name:</span>
|
|
| 143 |
<span class="regtext">The last name (surname) of the principal data set owner.</span></td></tr>
|
|
| 117 | 144 |
|
| 118 |
<b><font size="4"></font></b>
|
|
| 119 |
<p><b><font size="4">First Name:</font> <font size="5">
|
|
| 120 |
</font></b>The first name of the person.</p>
|
|
| 145 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Organization Name:</span>
|
|
| 146 |
<span class="regtext">The name of the organization from which the data set
|
|
| 147 |
originated.</span></td></tr>
|
|
| 121 | 148 |
|
| 122 |
<b><font size="4"></font></b> |
|
| 123 |
<p><b><font size="4">Last Name:</font> <font size="5"> |
|
| 124 |
</font></b>The last name (surname) of the person.</p> |
|
| 149 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">E-Mail:</span> |
|
| 150 |
<span class="regtext">The e-mail address by which the principal data set owner can be contacted.</span></td></tr> |
|
| 125 | 151 |
|
| 126 |
<b><font size="4"></font></b> |
|
| 127 |
<p><b><font size="4">Organization Name:</font> <font size="5"> |
|
| 128 |
</font></b>The name of the organization from which the data |
|
| 129 |
originate.</p> |
|
| 152 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Phone:</span> |
|
| 153 |
<span class="regtext">The phone number of the principal data set owner, including the area code (999-999-9999).</span></td></tr> |
|
| 130 | 154 |
|
| 131 |
<p><b><font size="4">E-Mail:</font> <font size="5"></font></b>The
|
|
| 132 |
e-mail address by which the principal data set owner can be contacted.</p>
|
|
| 155 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">FAX:</span>
|
|
| 156 |
<span class="regtext">The fax number of the principal data set owner, including sthe area code (999-999-9999).</span></td></tr>
|
|
| 133 | 157 |
|
| 134 |
<b><font size="4"></font></b> |
|
| 135 |
<p><b><font size="4">Phone:</font> <font size="5"> |
|
| 136 |
</font></b>Principal data set owner's phone number, in the format area code plus |
|
| 137 |
number, 999-999-9999.</p> |
|
| 158 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Street Information:</span> |
|
| 159 |
<span class="regtext">A comma-separated list of street number, street, unit, |
|
| 160 |
etc.<br> <u>Example:</u> 735 State Street, Suite 300</span></td></tr> |
|
| 138 | 161 |
|
| 139 |
<b><font size="4"></font></b> |
|
| 140 |
<p><b><font size="4">FAX:</font> <font size="5"> |
|
| 141 |
</font></b>Principal data set owner's fax machine number, in the format area code plus |
|
| 142 |
number, 999-999-9999.</p> |
|
| 162 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">City:</span> |
|
| 163 |
<span class="regtext">The city |
|
| 164 |
name of the principal data set owner's address.</span></td></tr> |
|
| 143 | 165 |
|
| 144 |
<b><font size="4"></font></b>
|
|
| 145 |
<p><b><font size="4">Street Address Information:</font> <font size="5">
|
|
| 146 |
</font></b>A comma-separated list of street number, street, unit,
|
|
| 147 |
etc. Example: 735 State Street, Suite 300</p>
|
|
| 166 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">State:</span>
|
|
| 167 |
<span class="regtext">Select
|
|
| 168 |
a state from the drop-down menu for the principal data set owner's address. For a shortcut,
|
|
| 169 |
press the first letter of the state on your keyboard (e.g., M-key to skip to Maine).</span></td></tr>
|
|
| 148 | 170 |
|
| 149 |
<b><font size="4"></font></b>
|
|
| 150 |
<p><b><font size="4">City:</font> <font size="5"></font></b>City
|
|
| 151 |
name of the principal data set owner's address.</p>
|
|
| 171 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Other State/Province:</span>
|
|
| 172 |
<span class="regtext">The state (other than the ones from the drop-down menu above) or province for
|
|
| 173 |
the principal data set owner's address. </span></td></tr>
|
|
| 152 | 174 |
|
| 153 |
<b><font size="4"></font></b> |
|
| 154 |
<p><b><font size="4">State:</font> <font size="5"></font></b>Select |
|
| 155 |
a state for the address from the pull-down menu. For a shortcut, |
|
| 156 |
press the C-key to skip to California.</p> |
|
| 175 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Postal Code:</span> |
|
| 176 |
<span class="regtext">The postal code or ZIP code |
|
| 177 |
for the principal data set owner's address.</span></td></tr> |
|
| 157 | 178 |
|
| 158 |
<b><font size="4"></font></b>
|
|
| 159 |
<p><b><font size="4">Postal Code:</font> <font size="5"></font></b>The postal code, or ZIP code,
|
|
| 160 |
of the principal data set owner's address.</p>
|
|
| 179 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Country:</span>
|
|
| 180 |
<span class="regtext">The country
|
|
| 181 |
for the principal data set owner's address.</span></td></tr>
|
|
| 161 | 182 |
|
| 162 | 183 |
|
| 163 |
<p> </p> |
|
| 164 |
<hr> |
|
| 165 |
<a name="AdditionalOriginators"></a> |
|
| 166 |
<p><b><font size="4" color="#0000ff">ASSOCIATED PARTIES</font></b> |
|
| 167 |
<p> </p> |
|
| 184 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="AdditionalOriginators"></a>ASSOCIATED PARTIES</td></tr> |
|
| 168 | 185 |
|
| 186 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext"> |
|
| 187 |
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 |
|
| 188 |
the data set), select a role for this person, and click on "Add Associated Party". Repeat to add another associated party.</tr>. |
|
| 189 |
<tr class="sectbody"><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 |
|
| 190 |
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". |
|
| 191 |
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> |
|
| 169 | 192 |
|
| 170 |
Enter the first and last names of up to 10 additional |
|
| 171 |
owners or other associated parties, and select their specific role from the pull-down |
|
| 172 |
menu. The default for the role pull-down menu is Principal |
|
| 173 |
Investigator. Example: First Name: Mark; Last Name: Seablad; Role: |
|
| 174 |
Owner.</p> |
|
| 175 | 193 |
|
| 194 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 195 |
<a name="DataSetAbstract"></a>*DATA SET ABSTRACT</td></tr> |
|
| 176 | 196 |
|
| 177 |
<p> </p> |
|
| 178 |
<hr> |
|
| 179 |
<a name="DataSetAbstract"></a> |
|
| 180 |
<b><font size="4"></font></b> |
|
| 181 |
<p><b><font size="4" color="#0000ff">DATA SET ABSTRACT</font></b> |
|
| 182 |
<p> </p> |
|
| 197 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Short (approximately 1/2 page or less) summary of the |
|
| 198 |
purpose and content of the data set. Entering a data set abstract is required.</td></tr> |
|
| 183 | 199 |
|
| 184 |
<p>Short (approximately 1/2 page or less) summary of the |
|
| 185 |
purpose and content of the dataset. Entering a data set abstract is required.</p> |
|
| 186 |
|
|
| 187 |
<p>Example: Data were collected every year in summer and fall from |
|
| 200 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext"><u>Example:</u> Data were collected every year in summer and fall from |
|
| 188 | 201 |
1967 to 1979. Trapping was conducted only in the fall from 1980 to |
| 189 | 202 |
1988. For each specimen taken, data were recorded on species, date, |
| 190 | 203 |
location, time, sex, and body measurements including total length, |
| 191 | 204 |
length of tail, length of hind foot, length of ear, and body mass. |
| 192 | 205 |
The purpose of the data was to index the population size of all |
| 193 |
species present over a long time period. </p>
|
|
| 206 |
species present over a long time period.</td></tr>
|
|
| 194 | 207 |
|
| 195 |
<p> </p> |
|
| 196 |
<hr> |
|
| 197 |
<a name="KeywordInformation"></a> |
|
| 198 |
<p><b><font size="4" color="#0000ff">KEYWORD INFORMATION</font></b> |
|
| 199 |
<p> </p> |
|
| 208 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 209 |
<a name="KeywordInformation"></a>KEYWORD INFORMATION</td></tr> |
|
| 200 | 210 |
|
| 201 |
Provide information for up to ten keywords. The |
|
| 202 |
information is provided in groups of three fields: keyword, keyword |
|
| 203 |
type and keyword thesaurus. Keyword information is |
|
| 204 |
used for locating data in catalog searches. The keywords listed |
|
| 205 |
here may or may not appear in the title or abstract. Both the |
|
| 206 |
keyword type and thesaurus are optional.</p> |
|
| 211 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Keyword information is used for locating data in catalog searches. |
|
| 212 |
The keywords listed here may or may not appear in the title or abstract.</td></tr> |
|
| 207 | 213 |
|
| 208 |
<p>Examples: Keyword: Peromyscus; Keyword Type: taxonomic; Keyword |
|
| 209 |
Thesaurus: none.</p> |
|
| 214 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Have a look at the <a href= |
|
| 215 |
"http://gcmd.nasa.gov/Resources/valids/gcmd_parameters.html" target="nasa">NASA Global Change Master Directory |
|
| 216 |
(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> |
|
| 210 | 217 |
|
| 211 |
<b><font size="4"></font></b> |
|
| 212 |
<p><b><font size="4">Keyword:</font></b> Commonly used formalized |
|
| 213 |
word(s) or phrase(s) used to describe the subject.</p> |
|
| 218 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Keyword: </span><span class="regtext"> A |
|
| 219 |
word or phrase used to describe the topic.</span></td></tr> |
|
| 214 | 220 |
|
| 215 |
<b><font size="4"></font></b> |
|
| 216 |
<p><b><font size="4">Keyword Type:</font> <font size="5"> |
|
| 217 |
</font></b>Term used to group similar keywords. Default: none. The |
|
| 218 |
different types are:</p> |
|
| 221 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Keyword Type: </span> |
|
| 222 |
<span class="regtext">Term used to group similar keywords. "None" is the default.</span></td></tr> |
|
| 219 | 223 |
|
| 220 |
<p>theme: keyword identifies a particular subject or topic</p>
|
|
| 224 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">The different types are:</span></td></tr>
|
|
| 221 | 225 |
|
| 222 |
<p>place: keyword identifies a place</p>
|
|
| 226 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">- Theme: the keyword identifies a particular subject or topic.</span></td></tr>
|
|
| 223 | 227 |
|
| 224 |
<p>stratum: keyword identifies the layer(s) of any deposited |
|
| 225 |
substance</p> |
|
| 228 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">- Place: the keyword identifies a place.</span></td></tr> |
|
| 226 | 229 |
|
| 227 |
<p>temporal: keyword identifies a time period related to the
|
|
| 228 |
dataset</p>
|
|
| 230 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">- Stratum: the keyword identifies the layer(s) of any deposited
|
|
| 231 |
substance.</span></td></tr>
|
|
| 229 | 232 |
|
| 230 |
<p>taxonomic: keyword identifies a particular taxa</p> |
|
| 233 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">- Temporal: the keyword identifies a time period related to the |
|
| 234 |
dataset.</span></td></tr> |
|
| 231 | 235 |
|
| 232 |
<font size="1"></font>
|
|
| 236 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">- Taxonomic: the keyword identifies a particular taxa.</span></td></tr>
|
|
| 233 | 237 |
|
| 234 |
<b><font size="4"></font></b> |
|
| 235 |
<p><b><font size="4">Keyword Thesaurus:</font> <font size="5"> |
|
| 236 |
</font></b>The name of the formally registered thesaurus, or a |
|
| 237 |
similar authoritative source of keywords, from which the keyword |
|
| 238 |
was chosen. Default: none (no thesaurus used; used own |
|
| 239 |
keywords).</p> |
|
| 238 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Keyword Thesaurus: </span><span class="regtext">Select whether you used the NASA Global Change Master Directory |
|
| 239 |
(GCMD) or not to choose your keywords.</span></td></tr> |
|
| 240 | 240 |
|
| 241 |
<p>An example for a thesaurus is the <a href= |
|
| 242 |
"http://gcmd.nasa.gov/valids/">NASA Global Change Master Directory |
|
| 243 |
(GCMD)</a>. Have a look at the GCMD keywords to get an idea of what |
|
| 244 |
keywords they use. If you find suitable keywords there that |
|
| 245 |
appropriately describe your data, use them and select GCMD for the |
|
| 246 |
keywords' thesaurus.</p> |
|
| 247 | 241 |
|
| 248 |
<p>Click on the "Add Keyword" button to continue adding keywords.</p> |
|
| 249 | 242 |
|
| 250 |
<p> </p> |
|
| 251 |
<hr> |
|
| 252 |
<a name="TemporalCoverageOfData"></a> |
|
| 253 |
<p><b><font size="4" color="#0000ff">TEMPORAL COVERAGE OF DATA</font></b> |
|
| 254 |
<p> </p> |
|
| 243 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Click on the "Add Keyword" button to add the keyword information entered. Enter as many keywords as needed. |
|
| 244 |
To edit an entry, click on the keyword entered, change the keyword, type, and/or thesaurus, and click on the area just right of the thesaurus drop-down menu (the text field and |
|
| 245 |
the drop-down menus will disappear). To delete an entry, click on the "X". If you have entered several keywords and want to change the order in which they appear, use the blue up and |
|
| 246 |
down arrows.</span></td></tr> |
|
| 255 | 247 |
|
| 256 |
<p><b><font size="4">Beginning Date of Data Set:</font> <font size= |
|
| 257 |
"5"></font></b>The first year, month, and |
|
| 258 |
day of the collection/creation of the data set. A beginning date is required. Type in the year, and choose the month and the day from the |
|
| 259 |
drop down menus.</p> |
|
| 248 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 249 |
<a name="TemporalCoverageOfData"></a>TEMPORAL COVERAGE OF DATA</td></tr> |
|
| 260 | 250 |
|
| 261 |
<b><font size="4"></font></b> |
|
| 262 |
<p><b><font size="4">Ending Date of Data Set:</font> <font size= |
|
| 263 |
"5"></font></b>The last year, month, and |
|
| 264 |
day for the collection/creation of the data set. <b>If your dataset is open-ended, leave the ending date |
|
| 265 |
open</b>, providing no ending date at all. Type in the year, and choose the month and the day from the |
|
| 266 |
drop down menus.</p> |
|
| 251 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Start Date:</span><span class="regtext"> The first year, month, and |
|
| 252 |
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 |
|
| 253 |
drop-down menus.</span></td></tr> |
|
| 267 | 254 |
|
| 268 |
<p> </p> |
|
| 269 |
<hr> |
|
| 270 |
<a name="SpatialCoverageOfData"></a> |
|
| 271 |
<p><b><font size="4" color="#0000ff">SPATIAL COVERAGE OF DATA</font></b> |
|
| 272 |
<p> </p> |
|
| 255 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Stop Date:</span><span class="regtext"> The last year, month, and |
|
| 256 |
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> |
|
| 257 |
<u>Note:</u> Leave "Stop Date" blank if your data set is open-ended.</span></td></tr> |
|
| 273 | 258 |
|
| 274 |
<p><b><font size="4">Geographic Description</font><font size="4">:</font></b> |
|
| 275 |
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 |
|
| 276 |
about the general location of the study. |
|
| 277 |
</p> |
|
| 259 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 260 |
<a name="SpatialCoverageOfData"></a>SPATIAL COVERAGE OF DATA</span></td></tr> |
|
| 278 | 261 |
|
| 279 |
<p><b><font size="4">Coordinates</font> (in Degrees, Minutes and |
|
| 280 |
Seconds)<font size="4">:</font> <font size="5"> |
|
| 281 |
</font></b>Coordinates provide the location where the data set was |
|
| 282 |
collected.</p> |
|
| 283 | 262 |
|
| 284 |
[% IF cfg != 'nceas' %] |
|
| 285 |
<p><b>Note the checkbox "Use [% lsite %] coordinates"</b>. If checked, |
|
| 286 |
this box indicates that the data were collected at the [% lsite %]. If |
|
| 287 |
you check this box, you don't need to fill in the lat./long. fields |
|
| 288 |
below). |
|
| 263 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Geographic Description:</span><span class="regtext"> |
|
| 264 |
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. |
|
| 265 |
This field supplements the coordinates provided below and helps orient the data user about the general location of the study.</span></td></tr> |
|
| 289 | 266 |
|
| 290 |
However, I presently do not have the coordinates for some |
|
| 291 |
[% orgabbrev %] [% lsite %]s, which will be indicated when you |
|
| 292 |
submit the form. In this case, you will have to provide the coordinates |
|
| 293 |
in the corresponding fields. (Please contact [%adminname %] at <a href= |
|
| 294 |
"mailto:[% recipient %]">[% recipient %]</a> if you |
|
| 295 |
have the missing coordinates for any of the sites.)</p> |
|
| 296 |
[% END %] |
|
| 267 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Coordinates:</span><span class="regtext"></span><span class="regtext"> The latitude and longitude |
|
| 268 |
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 |
|
| 269 |
the North (N) or South (S) orientation for the latitudes, and the West (W) or East (E) orientation for the longitudes.</span></td></tr> |
|
| 297 | 270 |
|
| 298 |
<p>At least one lat./long. pair is required. Pull-down lists provide the North (N) |
|
| 299 |
or South (S) orientation for the latitudes, and the West (W) and |
|
| 300 |
East (E) orientation for the longitudes.</p> |
|
| 271 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">If you enter <b>one coordinate pair only</b>: This indicates a |
|
| 272 |
point location.</span></td></tr> |
|
| 301 | 273 |
|
| 302 |
<p>If you enter <b>one coordinate pair only</b>: This indicates a |
|
| 303 |
point location. You may want to do this if you only know the |
|
| 304 |
general location of a site on the [% lsite %]. In this case provide the |
|
| 305 |
point coordinates for the [% lsite %]. Example: 36° 12' 30"N and |
|
| 306 |
121°33'3"W</p> |
|
| 307 |
|
|
| 308 |
<p>If you enter <b>both coordinate pairs</b>: This indicates a |
|
| 274 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">If you enter <b>both coordinate pairs</b>: This indicates a |
|
| 309 | 275 |
bounding box. The first coordinate pair is the northwest corner and |
| 310 | 276 |
the second coordinate pair is the southeast corner of the bounding |
| 311 |
box.</p>
|
|
| 277 |
box.</span></td></tr>
|
|
| 312 | 278 |
|
| 313 |
<p> </p> |
|
| 314 |
<hr> |
|
| 279 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 315 | 280 |
<a name="TaxonomicCoverage"></a> |
| 316 |
<p><b><font size="4" color="#0000ff">TAXONOMIC COVERAGE OF DATA</font></b> |
|
| 317 |
<p> </p> |
|
| 281 |
TAXONOMIC COVERAGE OF DATA</td></tr> |
|
| 318 | 282 |
|
| 319 |
<p><b><font size="4">List of taxa</font><font size="4">:</font></b>
|
|
| 283 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">
|
|
| 320 | 284 |
Provide a list of the taxa that are associated with this data set. |
| 321 | 285 |
This includes taxa for which the data set contains measurements, and taxa |
| 322 | 286 |
for which the data have relevance in less direct ways. In general, if a |
| 323 |
data user searching for a particular taxonomic name should find this data, |
|
| 324 |
then the taxon should be included in this list. The Taxon Rank should |
|
| 325 |
indicate the level in the taxonomic hierarchy (e.g., Phylum, Species, etc.) |
|
| 326 |
and the Taxonomic Name should be the scientific name for the organism at |
|
| 327 |
that level (e.g., Ursus arctos). You can add multiple taxa to the list by |
|
| 328 |
clicking the "Add taxon" button. |
|
| 329 |
</p> |
|
| 287 |
data user searching for a particular taxonomic name should find this data set, |
|
| 288 |
then the taxon should be included in this list.</span></td></tr> |
|
| 330 | 289 |
|
| 331 |
<p><b><font size="4">Taxonomic Authority</font><font size="4">:</font></b> Include the name |
|
| 332 |
or a complete citation for an authoritative source used for taxonomic information.</p> |
|
| 290 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Please check the <a href= |
|
| 291 |
"http://darwin.zoology.gla.ac.uk/~rpage/MyToL/www/index.php" target="darwin">Glasgow Taxonomic Name Server</a> or the <a href= |
|
| 292 |
"http://www.itis.usda.gov/" target="itis">Integrated Taxonomic Information System</a> for correct spelling |
|
| 293 |
of taxonomic names.</td></tr> |
|
| 333 | 294 |
|
| 334 |
<p> </p> |
|
| 335 |
<hr> |
|
| 336 |
<a name="Methods"></a> |
|
| 337 |
<p><b><font size="4" color="#0000ff">METHODS</font></b> |
|
| 338 |
<p> </p> |
|
| 295 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Taxon Rank:</span><span class="regtext"> Indicates the level in the taxonomic hierarchy |
|
| 296 |
(Kingdom, Phylum, Class, Order, Family, Genus, or Species).</span></td></tr> |
|
| 297 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Taxon Name:</span><span class="regtext"> The scientific name for the level |
|
| 298 |
entered under Taxon 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> |
|
| 339 | 299 |
|
| 340 |
<p><b><font size="4">Title of method</font><font size="4">:</font></b>
|
|
| 341 |
Provide a title for the method (e.g., Zooplankton abundance using
|
|
| 342 |
radial quadrat sub-sampling).
|
|
| 343 |
</p>
|
|
| 300 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Click on the "Add Taxon" button to add the taxonomic information. Add as many taxa as needed.
|
|
| 301 |
To edit an entry, click on the taxonomic information entered, change the taxon rank and/or name, and click on the area just right of the text field for the name (the two text
|
|
| 302 |
fields will disappear). To delete an entry, click on the "X". If you have entered several taxon and want to change the order in which they appear, use the blue up and
|
|
| 303 |
down arrows.</span></td></tr>
|
|
| 344 | 304 |
|
| 345 |
<p><b><font size="4">Method description</font><font size="4">:</font></b> |
|
| 346 |
Describe the methods used to generate the data. This is intended to be a |
|
| 347 |
general overview of the methods that is suitable to help a potential user |
|
| 348 |
of the data decide if the data are appropriate for their purposes. You can |
|
| 349 |
add multiple paragraphs to the description by clicking the "Add paragraph" |
|
| 350 |
button. |
|
| 351 |
</p> |
|
| 305 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Taxonomic Reference:</span><span class="regtext"> The name |
|
| 306 |
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> |
|
| 352 | 307 |
|
| 353 |
<p><b><font size="4">Description of Study Extent</font><font size="4">:</font></b> |
|
| 354 |
Describe the temporal, spatial and taxonomic extent of the study, supplementing |
|
| 308 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 309 |
<a name="Methods"></a>DATA COLLECTION METHODS</td></tr> |
|
| 310 |
|
|
| 311 |
|
|
| 312 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Method Title:</span><span class="regtext"> A title for the method used to generate |
|
| 313 |
the data (e.g., Measure of zooplankton abundance using radial quadrat sub-sampling).</span></td></tr> |
|
| 314 |
|
|
| 315 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Method Description:</span><span class="regtext"> Description of the method used. |
|
| 316 |
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. |
|
| 317 |
You can add multiple paragraphs to the description by clicking on the "Add Paragraph to Method Description" |
|
| 318 |
button (paragraphs added by using the ENTER key in the Method Description field will not appear as paragraphs in the submitted form). |
|
| 319 |
</span></td></tr> |
|
| 320 |
|
|
| 321 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Click on the "Describe New Method" button |
|
| 322 |
to describe another method.</span></td></tr> |
|
| 323 |
|
|
| 324 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Extent of Study Description:</span><span class="regtext"> |
|
| 325 |
Describe the temporal, spatial and taxonomic extent of the study, supplementing |
|
| 355 | 326 |
the information on coverage provided above. For example, if the temporal |
| 356 | 327 |
coverage of the data is 1990-2000, you might provide details about any years |
| 357 | 328 |
that were missed or the months in which sampling actually occurred. If you |
| 358 |
provide information in this field (Study Extent), then you must also provide
|
|
| 359 |
a Methods Description and a Sampling Description.
|
|
| 360 |
</p>
|
|
| 329 |
provide information in this field (Extent of Study Description), then you must also provide
|
|
| 330 |
a Method Title, a Method Description and a Sampling Description.
|
|
| 331 |
</span></td></tr>
|
|
| 361 | 332 |
|
| 362 |
<p><b><font size="4">Sampling Description</font><font size="4">:</font></b>
|
|
| 333 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Sampling Description:</span><span class="regtext">
|
|
| 363 | 334 |
Describe the sampling design of the study. For example, you might describe |
| 364 | 335 |
the way in which treatments were assigned to sampling units. If you provide |
| 365 | 336 |
information in this field (Sampling Description), then you must also provide |
| 366 |
a Methods Description and a Study Extent.
|
|
| 367 |
</p>
|
|
| 337 |
a a Method Title, a Method Description and an Extent of Study Description.
|
|
| 338 |
</span></td></tr>
|
|
| 368 | 339 |
|
| 369 |
<p> </p> |
|
| 370 |
<hr> |
|
| 340 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 371 | 341 |
<a name="DataSetContactAddress"></a> |
| 372 |
<p><b><font size="4" color="#0000ff">DATA SET CONTACT</font></b> |
|
| 373 |
<p> </p> |
|
| 342 |
DATA SET CONTACT</td></tr> |
|
| 374 | 343 |
|
| 375 |
An address, phone, and email to contact for more information on the data |
|
| 376 |
set or to obtain the data described by this entry. This is |
|
| 377 |
analogous to the Principal Data Set Owner information above. Please see |
|
| 378 |
that section for more information on filling out the individual fields. If the Data Set Contact and the |
|
| 379 |
Principal Data Set Owner are the same, check the box provided, and the information you previously filled out for |
|
| 380 |
the Principal Data Set Owner will automatically be filled into this section.</p> |
|
| 344 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Contact information of the person to be contacted for more information on the data |
|
| 345 |
set or to obtain the data set itself. This is analogous to the Principal Data Set Owner information above. Please |
|
| 346 |
<a href="@cgi-prefix@/register-dataset.cgi?cfg=[%cfg%]&stage=guide#DataSetOriginator" target="_self">see that section</a> for more information on filling out the individual fields. If the Data Set Contact and the |
|
| 347 |
Principal Data Set Owner are the same, check the box provided.</td></tr> |
|
| 381 | 348 |
|
| 382 | 349 |
|
| 383 |
<p> </p> |
|
| 384 |
<hr> |
|
| 350 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
|
| 385 | 351 |
<a name="DistributionIinformation"></a> |
| 386 |
<p><b><font size="4" color="#0000ff">DISTRIBUTION INFORMATION</font></b>
|
|
| 352 |
DISTRIBUTION INFORMATION</font></td></tr>
|
|
| 387 | 353 |
|
| 388 |
<p> </p>
|
|
| 354 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">
|
|
| 389 | 355 |
<a name=Site-specificCode></a> |
| 390 |
<b><font size="4"></font></b> |
|
| 391 |
<p><b><font size="4">Dataset Name or Identifier (important)</font>:</b> |
|
| 392 |
Enter the dataset's filename(s) (and path) here, if available. Alternatively, |
|
| 393 |
use other pertinent information that can help to identify and locate |
|
| 394 |
the dataset within your site's data management system (this may include |
|
| 395 |
references to hardcopy information, such as file numbers, etc.). Keep in |
|
| 396 |
mind that this information, while not required, can be extremely useful |
|
| 397 |
for locating the dataset at a [% lsite %].</p> |
|
| 356 |
Data Set Identifier:</span><span class="regtext"> If available, please enter a name or number that uniquely identifies and describes concisely the data set. |
|
| 357 |
Alternatively, provide other pertinent information that can identify and locate the data set within your site's data management system. |
|
| 398 | 358 |
|
| 399 |
<b><font size="4"></font></b> |
|
| 400 |
<p><b><font size="4">Data Medium</font>:</b> Choose the type of medium the |
|
| 401 |
data is recorded on from the drop down menu</p> |
|
| 359 |
[% IF cfg == 'obfs' || cfg == 'nrs' || cfg == 'specnet'%] |
|
| 360 |
Keep in mind that this information, although not required, can be extremely useful |
|
| 361 |
for locating the data set at a [% lsite %]. |
|
| 362 |
[%END%] |
|
| 363 |
</span></td></tr> |
|
| 364 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Data Medium</font>:</span><span class="regtext"> Specify whether the data medium is |
|
| 365 |
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> |
|
| 402 | 366 |
|
| 403 |
<b><font size="4"></font></b> |
|
| 404 |
<p><b><font size="4">Other Data Medium</font></b>: Specify any |
|
| 405 |
other data medium the data is recorded on. </p> |
|
| 406 | 367 |
|
| 368 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Usage Constraints:</span><span class="regtext"> Specify the usage constraints that apply |
|
| 369 |
to the data set. </span></td></tr> |
|
| 407 | 370 |
|
| 408 |
<p><b><font size="4">Use Constraints:</font> <font size="5"> |
|
| 409 |
</font></b>From the pull-down list, choose the use constraints that apply |
|
| 410 |
to this data set. Examples: no restrictions, obtain permission from |
|
| 411 |
originator(s), etc.</p> |
|
| 371 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">URL:</span><span class="regtext"> If available, provide a link for the |
|
| 372 |
location of more metadata or the data set itself (this URL should be as permanent as possible)<b>.</span></td></tr> |
|
| 412 | 373 |
|
| 413 |
<b><font size="4"></font></b> |
|
| 414 |
<p><b><font size="4">Other Use Constraints:</font></b> Specify any |
|
| 415 |
other use constraints that apply to the data set.</p> |
|
| 416 |
|
|
| 417 |
<b><font size="4"></font></b> |
|
| 418 |
<p><b><font size="4">URL</font></b>: Provide a link here for the |
|
| 419 |
location of the actual data set (if available) or for more |
|
| 420 |
metadata<b>.</b></p> |
|
| 421 |
|
|
| 422 | 374 |
<a name="AdditionalInformation"></a> |
| 423 |
<b><font size="4"></font></b> |
|
| 424 |
<p><b><font size="4">Additional Information/Remarks:</font></b> Add |
|
| 425 |
any additional information here that you deem relevant to the data set, which has not been covered in the form.</p> |
|
| 375 |
<tr class="sectbody"><td class="borderbottom" colspan="2" align="left"><span class="label">Additional Information:</span><span class="regtext"> Add |
|
| 376 |
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 |
|
| 377 |
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.)</span></td></tr> |
|
| 378 |
</table> |
|
| 379 |
<p></p> |
|
| 426 | 380 |
|
| 427 |
<p> </p> |
|
| 428 |
<hr> |
|
| 429 |
<p> </p> |
|
| 430 |
<p> </p> |
|
| 431 |
|
|
| 432 | 381 |
[% INCLUDE "genericFooter.tmpl" %] |
Also available in: Unified diff
Changes made to Data Registry Guide by Veronique Connolly
(Commit done by Saurabh Garg for Veronique)