Revision 2363
Added by sgarg almost 20 years ago
| lib/style/common/templates/genericGuide.tmpl | ||
|---|---|---|
| 34 | 34 |
[% END %] |
| 35 | 35 |
|
| 36 | 36 |
|
| 37 |
<p>This guide provides information and help how to |
|
| 38 |
fill in the [% orgabbrev %] Data Registry Form. Some fields are required |
|
| 39 |
and some fields are optional. A red asterisk (<b><font size= |
|
| 40 |
"4" color="#ff0000">*</font></b>) indicates that a |
|
| 41 |
field is required. A few fields are repeatable up to ten times. |
|
| 42 |
Those are the data set originator names and keyword information. |
|
| 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. |
|
| 43 | 41 |
Note that those repeatable fields are also optional, so you need to |
| 44 | 42 |
fill in only as many of those as you need.</p> |
| 45 | 43 |
|
| 46 | 44 |
<p>Information on individual fields and examples |
| 47 |
for their content follow.</p>
|
|
| 45 |
for their content are provided below.</p>
|
|
| 48 | 46 |
|
| 49 | 47 |
<p> </p> |
| 50 | 48 |
<hr> |
| ... | ... | |
| 61 | 59 |
affiliated with that working group or activity. We use "affiliation" |
| 62 | 60 |
in a rather permissive sense to mean, for example, that the data set was or has |
| 63 | 61 |
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
|
|
| 62 |
with the activity; or that the data set is owned by the activity, etc. Both
|
|
| 65 | 63 |
derived data sets that result from synthesis activities and original raw data |
| 66 | 64 |
sets that contribute to synthesis can be included in the repository and should |
| 67 | 65 |
be associated with the appropriate NCEAS activities. |
| ... | ... | |
| 84 | 82 |
[% END %] |
| 85 | 83 |
|
| 86 | 84 |
<b><font size="4"></font></b> |
| 87 |
<p><b><font size="4">Data Set Title:</font></b> Descriptive title
|
|
| 85 |
<p><b><font size="4">Data Set Title:</font></b> A descriptive title
|
|
| 88 | 86 |
of the data set. In general the title should provide enough information for |
| 89 | 87 |
someone casually scanning a list of data sets to know whether the data are |
| 90 | 88 |
relevant to them. This implies that the data context should be indicated |
| ... | ... | |
| 102 | 100 |
|
| 103 | 101 |
<p>Mammals Data</p> |
| 104 | 102 |
<p>Abundance Data</p> |
| 105 |
<p>Meterological Data</p> |
|
| 103 |
<p>Meteorological Data</p>
|
|
| 106 | 104 |
|
| 107 | 105 |
<p> </p> |
| 108 | 106 |
<hr> |
| 109 | 107 |
<a name="DataSetOriginator"></a> |
| 110 |
<p><b><font size="4" color="#0000ff">DATA SET ORIGINATOR</font></b>
|
|
| 108 |
<p><b><font size="4" color="#0000ff">PRINCIPAL DATA SET OWNER</font></b>
|
|
| 111 | 109 |
<p> </p> |
| 112 | 110 |
|
| 113 |
Person(s) or organization that developed the data |
|
| 114 |
set. The first originator provided on the form is EITHER an |
|
| 115 |
individual person OR an organization, including optional address |
|
| 116 |
information.</p> |
|
| 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> |
|
| 117 | 114 |
|
| 118 |
<p>This originator and the data set contact below may be the same
|
|
| 119 |
person or organization.</p>
|
|
| 115 |
<p>This principal data set owner and the data set contact (below) may be the same
|
|
| 116 |
person.</p> |
|
| 120 | 117 |
|
| 121 | 118 |
<b><font size="4"></font></b> |
| 122 |
<p><b><font size="4">Originator's Role:</font> <font size="5"> |
|
| 123 |
</font></b>You will probably just want to leave the generic |
|
| 124 |
default, which is "originator", but you can choose a more specific |
|
| 125 |
originator's role (e.g. Principal Investigator, Publisher, etc.) |
|
| 126 |
from the pull-down list, if appropriate, e.g Principal |
|
| 127 |
Investigator.</p> |
|
| 128 |
|
|
| 129 |
<b><font size="4"></font></b> |
|
| 130 | 119 |
<p><b><font size="4">First Name:</font> <font size="5"> |
| 131 |
</font></b>Self-explanatory.</p>
|
|
| 120 |
</font></b>The first name of the person.</p>
|
|
| 132 | 121 |
|
| 133 | 122 |
<b><font size="4"></font></b> |
| 134 | 123 |
<p><b><font size="4">Last Name:</font> <font size="5"> |
| 135 |
</font></b>Self-explanatory.</p>
|
|
| 124 |
</font></b>The last name (surname) of the person.</p>
|
|
| 136 | 125 |
|
| 137 | 126 |
<b><font size="4"></font></b> |
| 138 | 127 |
<p><b><font size="4">Organization Name:</font> <font size="5"> |
| 139 | 128 |
</font></b>The name of the organization from which the data |
| 140 |
originate (not required of you provide first/last names above)</p>
|
|
| 129 |
originate.</p>
|
|
| 141 | 130 |
|
| 142 |
<b><font size="4"></font></b> |
|
| 143 |
<p><b><font size="4">Originator Address Information (for Individual |
|
| 144 |
or Organization):</font></b></p> |
|
| 145 |
|
|
| 146 | 131 |
<p><b><font size="4">E-Mail:</font> <font size="5"></font></b>The |
| 147 |
e-mail address under which the originator can be contacted.</p>
|
|
| 132 |
e-mail address by which the principal data set owner can be contacted.</p>
|
|
| 148 | 133 |
|
| 149 | 134 |
<b><font size="4"></font></b> |
| 150 | 135 |
<p><b><font size="4">Phone:</font> <font size="5"> |
| 151 |
</font></b>Originator's phone number in the format area code plus
|
|
| 136 |
</font></b>Principal data set owner's phone number, in the format area code plus
|
|
| 152 | 137 |
number, 999-999-9999.</p> |
| 153 | 138 |
|
| 154 | 139 |
<b><font size="4"></font></b> |
| 155 |
<p><b><font size="4">Delivery Information:</font> <font size="5">
|
|
| 156 |
</font></b>A comma-separated list of street number, street, Unit,
|
|
| 157 |
etc., comma-separated). Example: 735 State Street, Suite 300</p>
|
|
| 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>
|
|
| 158 | 143 |
|
| 159 | 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> |
|
| 148 |
|
|
| 149 |
<b><font size="4"></font></b> |
|
| 160 | 150 |
<p><b><font size="4">City:</font> <font size="5"></font></b>City |
| 161 |
name of the originator address.</p>
|
|
| 151 |
name of the principal data set owner's address.</p>
|
|
| 162 | 152 |
|
| 163 | 153 |
<b><font size="4"></font></b> |
| 164 | 154 |
<p><b><font size="4">State:</font> <font size="5"></font></b>Select |
| ... | ... | |
| 166 | 156 |
press the C-key to skip to California.</p> |
| 167 | 157 |
|
| 168 | 158 |
<b><font size="4"></font></b> |
| 169 |
<p><b><font size="4">ZIP:</font> <font size="5"></font></b>The ZIP
|
|
| 170 |
code of the originator address.</p>
|
|
| 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>
|
|
| 171 | 161 |
|
| 172 | 162 |
|
| 173 | 163 |
<p> </p> |
| 174 | 164 |
<hr> |
| 175 | 165 |
<a name="AdditionalOriginators"></a> |
| 176 |
<p><b><font size="4" color="#0000ff">ADDITIONAL ORIGINATORS</font></b>
|
|
| 166 |
<p><b><font size="4" color="#0000ff">ASSOCIATED PARTIES</font></b>
|
|
| 177 | 167 |
<p> </p> |
| 178 | 168 |
|
| 179 | 169 |
|
| 180 | 170 |
Enter the first and last names of up to 10 additional |
| 181 |
originators, and select their specific role from the pull-down
|
|
| 171 |
owners or other associated parties, and select their specific role from the pull-down
|
|
| 182 | 172 |
menu. The default for the role pull-down menu is Principal |
| 183 | 173 |
Investigator. Example: First Name: Mark; Last Name: Seablad; Role: |
| 184 |
Editor</p>
|
|
| 174 |
Owner.</p>
|
|
| 185 | 175 |
|
| 186 | 176 |
|
| 187 | 177 |
<p> </p> |
| 188 | 178 |
<hr> |
| 189 | 179 |
<a name="DataSetAbstract"></a> |
| 190 | 180 |
<b><font size="4"></font></b> |
| 191 |
<p><b><font size="4">Data Set Abstract:</font> <font size="5"> |
|
| 192 |
</font></b>Short (approximately 1/2 page or less) summary of the |
|
| 193 |
purpose and content of the dataset.</p> |
|
| 181 |
<p><b><font size="4" color="#0000ff">DATA SET ABSTRACT</font></b> |
|
| 182 |
<p> </p> |
|
| 194 | 183 |
|
| 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 |
|
|
| 195 | 187 |
<p>Example: Data were collected every year in summer and fall from |
| 196 | 188 |
1967 to 1979. Trapping was conducted only in the fall from 1980 to |
| 197 | 189 |
1988. For each specimen taken, data were recorded on species, date, |
| ... | ... | |
| 206 | 198 |
<p><b><font size="4" color="#0000ff">KEYWORD INFORMATION</font></b> |
| 207 | 199 |
<p> </p> |
| 208 | 200 |
|
| 209 |
Provide information for up to ten keywords here. The
|
|
| 201 |
Provide information for up to ten keywords. The |
|
| 210 | 202 |
information is provided in groups of three fields: keyword, keyword |
| 211 |
type and keyword thesaurus, as follows. Keyword information will be
|
|
| 212 |
useful for locating data in catalog searches. The keywords listed
|
|
| 203 |
type and keyword thesaurus. Keyword information is
|
|
| 204 |
used for locating data in catalog searches. The keywords listed
|
|
| 213 | 205 |
here may or may not appear in the title or abstract. Both the |
| 214 | 206 |
keyword type and thesaurus are optional.</p> |
| 215 | 207 |
|
| 216 |
<p>Examples: keyword: Peromyscus; Keyword Type: taxonomic; Keyword
|
|
| 217 |
Thesaurus: none</p> |
|
| 208 |
<p>Examples: Keyword: Peromyscus; Keyword Type: taxonomic; Keyword
|
|
| 209 |
Thesaurus: none.</p>
|
|
| 218 | 210 |
|
| 219 | 211 |
<b><font size="4"></font></b> |
| 220 | 212 |
<p><b><font size="4">Keyword:</font></b> Commonly used formalized |
| 221 |
word( s) or phrase( s) used to describe the subject.</p>
|
|
| 213 |
word(s) or phrase(s) used to describe the subject.</p>
|
|
| 222 | 214 |
|
| 223 | 215 |
<b><font size="4"></font></b> |
| 224 | 216 |
<p><b><font size="4">Keyword Type:</font> <font size="5"> |
| ... | ... | |
| 227 | 219 |
|
| 228 | 220 |
<p>theme: keyword identifies a particular subject or topic</p> |
| 229 | 221 |
|
| 230 |
<p>discipline: keyword identifies a branch of instruction or |
|
| 231 |
specialized learning</p> |
|
| 232 |
|
|
| 233 |
<p>taxonomic: keyword identifies a particular taxa</p> |
|
| 234 |
|
|
| 235 | 222 |
<p>place: keyword identifies a place</p> |
| 236 | 223 |
|
| 237 | 224 |
<p>stratum: keyword identifies the layer(s) of any deposited |
| ... | ... | |
| 240 | 227 |
<p>temporal: keyword identifies a time period related to the |
| 241 | 228 |
dataset</p> |
| 242 | 229 |
|
| 243 |
<p>theme: keyword identifies a particular subject or topic</p>
|
|
| 230 |
<p>taxonomic: keyword identifies a particular taxa</p>
|
|
| 244 | 231 |
|
| 245 | 232 |
<font size="1"></font> |
| 246 | 233 |
|
| 247 | 234 |
<b><font size="4"></font></b> |
| 248 | 235 |
<p><b><font size="4">Keyword Thesaurus:</font> <font size="5"> |
| 249 |
</font></b>The Name of the formally registered thesaurus, or a
|
|
| 236 |
</font></b>The name of the formally registered thesaurus, or a
|
|
| 250 | 237 |
similar authoritative source of keywords, from which the keyword |
| 251 | 238 |
was chosen. Default: none (no thesaurus used; used own |
| 252 |
keywords)</p> |
|
| 239 |
keywords).</p>
|
|
| 253 | 240 |
|
| 254 | 241 |
<p>An example for a thesaurus is the <a href= |
| 255 | 242 |
"http://gcmd.nasa.gov/valids/">NASA Global Change Master Directory |
| ... | ... | |
| 258 | 245 |
appropriately describe your data, use them and select GCMD for the |
| 259 | 246 |
keywords' thesaurus.</p> |
| 260 | 247 |
|
| 248 |
<p>Click on the "Add Keyword" button to continue adding keywords.</p> |
|
| 249 |
|
|
| 261 | 250 |
<p> </p> |
| 262 | 251 |
<hr> |
| 263 | 252 |
<a name="TemporalCoverageOfData"></a> |
| ... | ... | |
| 265 | 254 |
<p> </p> |
| 266 | 255 |
|
| 267 | 256 |
<p><b><font size="4">Beginning Date of Data Set:</font> <font size= |
| 268 |
"5"></font></b>The first year (and optionally month, or month and
|
|
| 269 |
day) of the collection/creation of the data set, in the format
|
|
| 270 |
yy/mm/dd.</p>
|
|
| 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>
|
|
| 271 | 260 |
|
| 272 | 261 |
<b><font size="4"></font></b> |
| 273 | 262 |
<p><b><font size="4">Ending Date of Data Set:</font> <font size= |
| 274 |
"5"></font></b>The last year (and optionally month, or month and
|
|
| 275 |
day) for the collection/creation of the data set, in the format
|
|
| 276 |
yy/mm/dd. <b>If your dataset is open-ended, leave the ending date
|
|
| 277 |
open</b>, provide no ending date at all.</p>
|
|
| 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>
|
|
| 278 | 267 |
|
| 279 | 268 |
<p> </p> |
| 280 | 269 |
<hr> |
| ... | ... | |
| 306 | 295 |
have the missing coordinates for any of the sites.)</p> |
| 307 | 296 |
[% END %] |
| 308 | 297 |
|
| 309 |
<p>Enter <b>one lat./long. pair only to indicate a point |
|
| 310 |
location</b>. Enter both lat./long pairs to indicate a bounding |
|
| 311 |
box, with the first pair indicating the northwest corner and the |
|
| 312 |
second pair the southeast corner of the box. At least one |
|
| 313 |
lat./long. pair is required. Pull-down lists provide the North (N) |
|
| 298 |
<p>At least one lat./long. pair is required. Pull-down lists provide the North (N) |
|
| 314 | 299 |
or South (S) orientation for the latitudes, and the West (W) and |
| 315 | 300 |
East (E) orientation for the longitudes.</p> |
| 316 | 301 |
|
| ... | ... | |
| 335 | 320 |
Provide a list of the taxa that are associated with this data set. |
| 336 | 321 |
This includes taxa for which the data set contains measurements, and taxa |
| 337 | 322 |
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 |
|
| 323 |
data user searching for a particular taxonomic name should find this data,
|
|
| 339 | 324 |
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)
|
|
| 325 |
indicate the level in the taxonomic hierarchy (e.g., Phylum, Species, etc.)
|
|
| 341 | 326 |
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
|
|
| 327 |
that level (e.g., Ursus arctos). You can add multiple taxa to the list by
|
|
| 343 | 328 |
clicking the "Add taxon" button. |
| 344 | 329 |
</p> |
| 345 | 330 |
|
| 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> |
|
| 333 |
|
|
| 346 | 334 |
<p> </p> |
| 347 | 335 |
<hr> |
| 348 | 336 |
<a name="Methods"></a> |
| ... | ... | |
| 350 | 338 |
<p> </p> |
| 351 | 339 |
|
| 352 | 340 |
<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). |
|
| 341 |
Provide a title for the method (e.g., Zooplankton abundance using |
|
| 342 |
radial quadrat sub-sampling).
|
|
| 355 | 343 |
</p> |
| 356 | 344 |
|
| 357 | 345 |
<p><b><font size="4">Method description</font><font size="4">:</font></b> |
| 358 | 346 |
Describe the methods used to generate the data. This is intended to be a |
| 359 | 347 |
general overview of the methods that is suitable to help a potential user |
| 360 | 348 |
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"
|
|
| 349 |
add multiple paragraphs to the description by clicking the "Add paragraph"
|
|
| 362 | 350 |
button. |
| 363 | 351 |
</p> |
| 364 | 352 |
|
| ... | ... | |
| 368 | 356 |
coverage of the data is 1990-2000, you might provide details about any years |
| 369 | 357 |
that were missed or the months in which sampling actually occurred. If you |
| 370 | 358 |
provide information in this field (Study Extent), then you must also provide |
| 371 |
a Methods Description and a Sampling description.
|
|
| 359 |
a Methods Description and a Sampling Description.
|
|
| 372 | 360 |
</p> |
| 373 | 361 |
|
| 374 | 362 |
<p><b><font size="4">Sampling Description</font><font size="4">:</font></b> |
| ... | ... | |
| 381 | 369 |
<p> </p> |
| 382 | 370 |
<hr> |
| 383 | 371 |
<a name="DataSetContactAddress"></a> |
| 384 |
<p><b><font size="4" color="#0000ff">DATA SET CONTACT ADDRESS</font></b>
|
|
| 372 |
<p><b><font size="4" color="#0000ff">DATA SET CONTACT</font></b> |
|
| 385 | 373 |
<p> </p> |
| 386 | 374 |
|
| 387 |
Address to contact for more information on the data
|
|
| 375 |
An address, phone, and email to contact for more information on the data
|
|
| 388 | 376 |
set or to obtain the data described by this entry. This is |
| 389 |
analogous to the Originator Address Information above. Please see |
|
| 390 |
there.</p> |
|
| 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> |
|
| 391 | 381 |
|
| 392 | 382 |
|
| 393 | 383 |
<p> </p> |
| ... | ... | |
| 399 | 389 |
<a name=Site-specificCode></a> |
| 400 | 390 |
<b><font size="4"></font></b> |
| 401 | 391 |
<p><b><font size="4">Dataset Name or Identifier (important)</font>:</b> |
| 402 |
Enter the datasets filename (and path) here, if available. Alternatively,
|
|
| 392 |
Enter the dataset's filename(s) (and path) here, if available. Alternatively,
|
|
| 403 | 393 |
use other pertinent information that can help to identify and locate |
| 404 | 394 |
the dataset within your site's data management system (this may include |
| 405 | 395 |
references to hardcopy information, such as file numbers, etc.). Keep in |
| ... | ... | |
| 407 | 397 |
for locating the dataset at a [% lsite %].</p> |
| 408 | 398 |
|
| 409 | 399 |
<b><font size="4"></font></b> |
| 410 |
<p><b><font size="4">Data Medium</font>:</b> The kind of medium the
|
|
| 411 |
data is recorded on.</p>
|
|
| 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>
|
|
| 412 | 402 |
|
| 413 | 403 |
<b><font size="4"></font></b> |
| 414 | 404 |
<p><b><font size="4">Other Data Medium</font></b>: Specify any |
| 415 |
other data medium you use. </p>
|
|
| 405 |
other data medium the data is recorded on. </p>
|
|
| 416 | 406 |
|
| 417 | 407 |
|
| 418 | 408 |
<p><b><font size="4">Use Constraints:</font> <font size="5"> |
| 419 |
</font></b>Choose from a pull-down list with use constraints apply
|
|
| 420 |
to this data set. Examples: public domain; obtain permission from
|
|
| 421 |
PI.</p>
|
|
| 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>
|
|
| 422 | 412 |
|
| 423 | 413 |
<b><font size="4"></font></b> |
| 424 | 414 |
<p><b><font size="4">Other Use Constraints:</font></b> Specify any |
| 425 |
other use constraints.</p> |
|
| 415 |
other use constraints that apply to the data set.</p>
|
|
| 426 | 416 |
|
| 427 | 417 |
<b><font size="4"></font></b> |
| 428 |
<p><b><font size="4">URL</font></b>: Provide any network link here for the
|
|
| 418 |
<p><b><font size="4">URL</font></b>: Provide a link here for the |
|
| 429 | 419 |
location of the actual data set (if available) or for more |
| 430 | 420 |
metadata<b>.</b></p> |
| 431 | 421 |
|
| 432 |
<p> </p> |
|
| 433 |
<hr> |
|
| 434 | 422 |
<a name="AdditionalInformation"></a> |
| 435 | 423 |
<b><font size="4"></font></b> |
| 436 | 424 |
<p><b><font size="4">Additional Information/Remarks:</font></b> Add |
| 437 |
any information here that you deem relevant to the data set and |
|
| 438 |
that is not covered in the form.</p> |
|
| 425 |
any additional information here that you deem relevant to the data set, which has not been covered in the form.</p> |
|
| 439 | 426 |
|
| 427 |
<p> </p> |
|
| 428 |
<hr> |
|
| 440 | 429 |
<p> </p> |
| 441 | 430 |
<p> </p> |
| 442 | 431 |
|
Also available in: Unified diff
The guide on how to complete dr entries was updated to describe the current entryform.tmpl, and to fix bug 1302.
(Commit for Andrea Chadden by Saurabh Garg)