Revision 2412
Added by sgarg over 19 years ago
| lib/style/common/templates/genericGuide.tmpl | ||
|---|---|---|
| 36 | 36 |
<table class="intro" cellpadding="8" cellspacing="0"> |
| 37 | 37 |
|
| 38 | 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. There are 11 sections to the form - some fields are required (denoted by an asterisk *), |
|
| 41 |
while others are optional. When you are done completing a section, you have the option of clicking on "Hide" (on the right side of each section header) |
|
| 42 |
to hide the information you just entered. Information on individual fields and examples for their content are provided below.</span></td></tr> |
|
| 39 |
<tr><td align="left"><span class="regtext">This guide provides information on how to fill in the online [% orgabbrev %] Data Registry Form. |
|
| 40 |
There are 11 sections to the form; some fields are required (denoted by an asterisk *), |
|
| 41 |
while others are optional. When you are done completing a section, you have the option of clicking on "<span class="colorbold">Hide</span>" |
|
| 42 |
(on the right side of each section header) to hide the information you just entered. Information on individual fields and examples for their content are provided below. |
|
| 43 |
</span></td></tr> |
|
| 44 |
</table> |
|
| 43 | 45 |
|
| 44 | 46 |
|
| 45 |
|
|
| 46 | 47 |
<table class="tables" cellpadding="8" cellspacing="0"> |
| 47 | 48 |
|
| 48 | 49 |
<tr class="sectheader"><td class="borderbottom" colspan="2" align="left"><a name="BasicInformation"></a> |
| 49 |
BASIC INFORMATION - name of person completing this form.</td></tr>
|
|
| 50 |
BASIC INFORMATION</td></tr> |
|
| 50 | 51 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label"> |
| 51 | 52 |
*First name, *Last name:</span><span class="regtext"> |
| 52 | 53 |
The first and last names of the person completing this form.</span></td></tr> |
| ... | ... | |
| 63 | 64 |
<td align="left"><span class="regtext"><u>Examples of incomplete titles:</u></td></tr> |
| 64 | 65 |
|
| 65 | 66 |
<tr class="sectbody"><td align="left" valign="top"><span class="regtext">Hastings Reserve (CA) Small Mammal Trapline Data from 1972 to 1988. |
| 67 |
|
|
| 68 |
|
|
| 69 |
|
|
| 66 | 70 |
<br>Tassajara Hot Springs Reserve Water Chemistry Data from 1990 to 2000.</td> |
| 67 | 71 |
|
| 68 |
<td align="left" valign="top"><span class="regtext">Mammals Data<br>Water Chemistry Data</td></tr> |
|
| 72 |
<td align="left" valign="top"><span class="regtext">Mammals Data<br><br>Water Chemistry Data</td></tr>
|
|
| 69 | 73 |
|
| 70 | 74 |
|
| 71 | 75 |
[% IF cfg == 'nceas' %] |
| ... | ... | |
| 84 | 88 |
|
| 85 | 89 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">*Organization Name:</span> |
| 86 | 90 |
<span class="regtext">The name of the organization with which the data set is |
| 87 |
affiliated. We use "affiliation" in a rather |
|
| 88 |
permissive sense to mean, for example, that the data set was or has |
|
| 91 |
affiliated. We use "affiliation" in a rather permissive sense to mean, for example, that the data set was or has |
|
| 89 | 92 |
been generated at the organization; that the owner of the data is affiliated |
| 90 | 93 |
with the organization or was affiliated with the organization when the data |
| 91 | 94 |
set was generated; that the data set is owned by the organization; etc.</td></tr> |
| ... | ... | |
| 124 | 127 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"><a name="DataSetOriginator"></a>PRINCIPAL DATA SET OWNER</td></tr> |
| 125 | 128 |
|
| 126 | 129 |
|
| 127 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">The person responsible for developing the data set. For example, the principal
|
|
| 130 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">The person responsible for developing the data set. For example, the principal |
|
| 128 | 131 |
investigator in a collaborative project, the first author of the main publication using the data set, etc. |
| 129 | 132 |
The first and last names of the principal data set owner are required; the organization name, e-mail, phone, fax, and |
| 130 | 133 |
address information are optional.</span></td></tr> |
| ... | ... | |
| 166 | 169 |
|
| 167 | 170 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Other State/Province:</span> |
| 168 | 171 |
<span class="regtext">The state (other than the ones from the drop-down menu above) or province for |
| 169 |
the principal data set owner's address. </span></td></tr>
|
|
| 172 |
the principal data set owner's address.</span></td></tr> |
|
| 170 | 173 |
|
| 171 | 174 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Postal Code:</span> |
| 172 | 175 |
<span class="regtext">The postal code or ZIP code |
| ... | ... | |
| 181 | 184 |
|
| 182 | 185 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext"> |
| 183 | 186 |
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 |
| 184 |
the data set), select a role for this person, and click on "Add Associated Party". Repeat to add another associated party.</tr>.
|
|
| 187 |
the data set), select a role for this person, and click on "Add Associated Party". Repeat to add another associated party.</td></tr>
|
|
| 185 | 188 |
<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 |
| 186 |
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".
|
|
| 189 |
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". |
|
| 187 | 190 |
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> |
| 188 | 191 |
|
| 189 | 192 |
|
| ... | ... | |
| 314 | 317 |
button (paragraphs added by using the ENTER key in the Method Description field will not appear as paragraphs in the submitted form). |
| 315 | 318 |
</span></td></tr> |
| 316 | 319 |
|
| 317 |
<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Click on the "Describe Another Method" button |
|
| 318 |
to describe another method.</span></td></tr> |
|
| 320 |
<!--<tr class="sectbody"><td colspan="2" align="left"><span class="regtext">Click on the "Describe Another Method" button
|
|
| 321 |
to describe another method.</span></td></tr>-->
|
|
| 319 | 322 |
|
| 320 | 323 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Extent of Study Description:</span><span class="regtext"> |
| 321 | 324 |
Describe the temporal, spatial and taxonomic extent of the study, supplementing |
| ... | ... | |
| 323 | 326 |
coverage of the data is 1990-2000, you might provide details about any years |
| 324 | 327 |
that were missed or the months in which sampling actually occurred. If you |
| 325 | 328 |
provide information in this field (Extent of Study Description), then you must also provide |
| 326 |
a Method Title, a Method Description and a Sampling Description. |
|
| 327 |
</span></td></tr> |
|
| 329 |
a Method Title, a Method Description and a Sampling Description.</span></td></tr> |
|
| 328 | 330 |
|
| 329 | 331 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">Sampling Description:</span><span class="regtext"> |
| 330 | 332 |
Describe the sampling design of the study. For example, you might describe |
| ... | ... | |
| 339 | 341 |
|
| 340 | 342 |
<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 |
| 341 | 343 |
set or to obtain the data set itself. This is analogous to the Principal Data Set Owner information above. Please |
| 342 |
<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
|
|
| 343 |
Principal Data Set Owner are the same, check the box provided.</td></tr>
|
|
| 344 |
<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 |
|
| 345 |
individual fields. If the Data Set Contact and the Principal Data Set Owner are the same, check the box provided.</span></td></tr>
|
|
| 344 | 346 |
|
| 345 | 347 |
|
| 346 | 348 |
<tr class="sectheader"><td class="topbottom" colspan="2" align="left"> |
| ... | ... | |
| 365 | 367 |
to the data set. </span></td></tr> |
| 366 | 368 |
|
| 367 | 369 |
<tr class="sectbody"><td colspan="2" align="left"><span class="label">URL:</span><span class="regtext"> If available, provide a link for the |
| 368 |
location of more metadata or the data set itself (this URL should be as permanent as possible)<b>.</span></td></tr>
|
|
| 370 |
location of more metadata or the data set itself (this URL should be as permanent as possible).</span></td></tr> |
|
| 369 | 371 |
|
| 370 | 372 |
<a name="AdditionalInformation"></a> |
| 371 | 373 |
<tr class="sectbody"><td class="borderbottom" colspan="2" align="left"><span class="label">Additional Information:</span><span class="regtext"> Add |
| 372 | 374 |
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 |
| 373 |
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.)</span></td></tr> |
|
| 375 |
of a computer file, you could specify the file format here (e.g., Excel, Access, FoxPro, DBase, etc.).</span></td></tr>
|
|
| 374 | 376 |
</table> |
| 375 | 377 |
<p></p> |
| 376 | 378 |
|
Also available in: Unified diff
Changes to the Data Registry Guide made by Veronique Connolly