<?xml version="1.0" encoding="UTF-8"?>
<eml:eml xmlns:eml="eml://ecoinformatics.org/eml-2.1.0" xmlns:stmml="http://www.xml-cml.org/schema/stmml-1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ds="eml://ecoinformatics.org/dataset-2.1.0" xsi:schemaLocation="eml://ecoinformatics.org/eml-2.1.0&#10;&#9;&#9;&#9;&#9;http://nis.lternet.edu/schemas/EML/eml-2.1.0/eml.xsd" packageId="knb-lter-bnz.218.10" system="knb" scope="system">
<access scope="document" order="allowFirst" authSystem="knb">
<allow>
<principal>uid=BNZ,o=lter,dc=ecoinformatics,dc=org</principal>
<permission>all</permission>
</allow>
<allow>
<principal>public</principal>
<permission>read</permission>
</allow>
</access>
<dataset>
<shortName>knb-lter-bnz.218.10</shortName>
<title>Species list for Bonanza Creek Experimental Forest</title>
<creator>
<individualName>
<givenName>Teresa</givenName>
<givenName>Nettleton</givenName>
<surName>Hollingsworth</surName>
</individualName>
<positionName>USDA Forest Service Research Ecologist</positionName>
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit, PNW Research Station, USDA Forest Service, P.O. Box 756780,University of Alaska Fairbanks</deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK </administrativeArea>
<postalCode>99775</postalCode>
<country>United States</country>
</address>
<phone phonetype="voice">(907) 474-2424</phone>
<phone phonetype="fax">(907) 474-6251</phone>
<electronicMailAddress>thollingsworth@fs.fed.us</electronicMailAddress>
<onlineUrl>http://www.becru.uaf.edu/personnel/Teresa.htm</onlineUrl>
</creator>
<metadataProvider>
<organizationName>Bonanza Creek LTER</organizationName>
<positionName>Data Manager</positionName>
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit </deliveryPoint>
<deliveryPoint>University of Alaska Fairbanks</deliveryPoint>
<deliveryPoint>P.O. Box 756780 </deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK</administrativeArea>
<postalCode>99775</postalCode>
<country>USA</country>
</address>
<phone phonetype="voice">907-474-6364</phone>
<phone phonetype="fax">907-474-6251</phone>
<electronicMailAddress>jpdowning@alaska.edu</electronicMailAddress>
<onlineUrl>http://www.lter.uaf.edu</onlineUrl>
</metadataProvider>
<associatedParty>
<individualName>
<givenName>Brian</givenName>
<surName>Charlton</surName>
</individualName>
<positionName>Research Technician</positionName>
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit University of Alaska Fairbanks  School of Agriculture and Land Resources Management P.O. Box 756780</deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK </administrativeArea>
<postalCode>99775-6780</postalCode>
<country>United States</country>
</address>
<phone phonetype="voice">(907) 474-5104</phone>
<phone phonetype="fax">(907) 474-6251</phone>
<role>Associated investigator</role>
</associatedParty>
<associatedParty>
<individualName>
<givenName>Jamie</givenName>
<surName>Hollingsworth</surName>
</individualName>
<positionName>Bonanza Creek LTER Site Manager</positionName>
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit University of Alaska Fairbanks  School of Agriculture and Land Resources Management P.O. Box 756780</deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK </administrativeArea>
<postalCode>99775</postalCode>
<country>United States</country>
</address>
<phone phonetype="voice">(907) 474-7470</phone>
<phone phonetype="fax">(907) 474-6251</phone>
<role>Associated investigator</role>
</associatedParty>
<associatedParty>
<individualName>
<givenName>Teresa</givenName>
<givenName>Nettleton</givenName>
<surName>Hollingsworth</surName>
</individualName>
<!--No position or title info on file for this person (pers/title when lead_contact=0)-->
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit, PNW Research Station, USDA Forest Service, P.O. Box 756780,University of Alaska Fairbanks</deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK </administrativeArea>
<postalCode>99775</postalCode>
<country>United States</country>
</address>
<phone phonetype="voice">(907) 474-2424</phone>
<phone phonetype="fax">(907) 474-6251</phone>
<role>Associated investigator</role>
</associatedParty>
<associatedParty>
<individualName>
<givenName>Mark</givenName>
<surName>Winterstein</surName>
</individualName>
<positionName>MS Student</positionName>
<address>
<deliveryPoint>University of Alaska Fairbanks</deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK</administrativeArea>
<postalCode>99775</postalCode>
<country>USA</country>
</address>
<!--No phone info on file for this person (pers/tel1 when lead_contact=0)-->
<!--No fax info on file for this person-->
<role>Associated investigator</role>
</associatedParty>
<pubDate>1996-04-01</pubDate>
<abstract>
<para>The Species list for Bonanza Creek Experimental Forest dataset includes a listing of all species documented at the Bonanza Creek Experimental Forest, Fairbanks, Alaska, USA. Vascular and non-vascular plant species lists were compiled by long-term vegetation monitoring and vascular and non-vascular plant collections. Plant identifications were made according to Viereck and Little and Eric Hulten. Animal species lists were compiled by physical (sitings, track, and scat) observations and published documents/reports</para>
</abstract>
<keywordSet>
<keyword>species</keyword>
<keywordThesaurus>Biological Diversity</keywordThesaurus>
</keywordSet>
<intellectualRights>
<section>
<title>Access to Data</title>
<para>While metadata will be freely available to those requesting it, the data manager will assure that any restrictions on access to data sets in the database will be enforced. Data will not be released without proper permission first being obtained from the investigator who generated the data. </para>
</section>
<section>
<title>Use of data</title>
<para> Researchers should receive adequate acknowledgment for the use of their data by others and should be provided with copies of publications using their data. Users of data from the data base must be aware that data is not to be sold or redistributed.</para>
</section>
<section>
<title>Citing Bonanza Creek LTER Datasets</title>
<para>It is considered a matter of professional ethics to acknowledge the work of other scientists. Thus, the Data User will properly cite the Data Set in any publications or in the metadata of any derived data products that were produced using the Data Set. </para>
</section>
</intellectualRights>
<distribution id="distributionReference">
<online>
<url>http://www.lter.uaf.edu/data_detail.cfm?datafile_pkey=218</url>
</online>
</distribution>
<coverage>
<geographicCoverage id="geoReference">
<geographicDescription>Site information unavailable</geographicDescription>
<boundingCoordinates>
<westBoundingCoordinate>-148.2482407</westBoundingCoordinate>
<eastBoundingCoordinate>-148.2482407</eastBoundingCoordinate>
<northBoundingCoordinate>64.69779026</northBoundingCoordinate>
<southBoundingCoordinate>64.69779026</southBoundingCoordinate>
</boundingCoordinates>
</geographicCoverage>
<temporalCoverage>
<rangeOfDates>
<beginDate>
<calendarDate>1987-01-01</calendarDate>
</beginDate>
<endDate>
<calendarDate>2009-01-01</calendarDate>
</endDate>
</rangeOfDates>
</temporalCoverage>
</coverage>
<maintenance>
<description>
<section>
<title>Status</title>
<para>Completed</para>
</section>
</description>
</maintenance>
<contact>
<organizationName>Bonanza Creek LTER</organizationName>
<positionName>Data Manager</positionName>
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit </deliveryPoint>
<deliveryPoint>University of Alaska Fairbanks</deliveryPoint>
<deliveryPoint>P.O. Box 756780 </deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK</administrativeArea>
<postalCode>99775</postalCode>
<country>USA</country>
</address>
<phone phonetype="voice">907-474-6364</phone>
<phone phonetype="fax">907-474-6251</phone>
<electronicMailAddress>jpdowning@alaska.edu</electronicMailAddress>
<onlineUrl>http://www.lter.uaf.edu</onlineUrl>
</contact>
<publisher>
<organizationName>Bonanza Creek LTER</organizationName>
<address>
<deliveryPoint>Boreal Ecology Cooperative Research Unit </deliveryPoint>
<deliveryPoint>University of Alaska Fairbanks</deliveryPoint>
<deliveryPoint>P.O. Box 756780 </deliveryPoint>
<city>Fairbanks</city>
<administrativeArea>AK</administrativeArea>
<postalCode>99775</postalCode>
<country>USA</country>
</address>
<phone phonetype="voice">907-474-6364</phone>
<phone phonetype="fax">907-474-6251</phone>
</publisher>
<pubPlace>Bonanza Creek LTER</pubPlace>
<methods>
<methodStep>
<description>
<section>
<title>Methods</title>
<para>Vascular and non-vascular plant species lists were compiled by long-term vegetation monitoring and vascular and non-vascular plant collections. Plant identifications were made according to Viereck and Little and Eric Hulten (see "Supporting Documents"). Animal species lists were compiled by physical (sitings, track, and scat) observations and published documents/reports (see "Supporting Documents").</para>
</section>
</description>
</methodStep>
<sampling>
<studyExtent>
<coverage>
<geographicCoverage>
<references>geoReference</references>
</geographicCoverage>
<temporalCoverage>
<rangeOfDates>
<beginDate>
<calendarDate>1987-01-01</calendarDate>
</beginDate>
<endDate>
<calendarDate>2009-01-01</calendarDate>
</endDate>
</rangeOfDates>
</temporalCoverage>
</coverage>
</studyExtent>
<samplingDescription>
<section>
<title>Sampling Frequency</title>
<para>Ongoing</para>
</section>
</samplingDescription>
</sampling>
</methods>
<dataTable>
<entityName>218_AnimalSpeciesList.txt</entityName>
<!--No data table description found (df_loc/df_desc)-->
<physical>
<objectName>218_AnimalSpeciesList.txt</objectName>
<dataFormat>
<textFormat>
<numHeaderLines>1</numHeaderLines>
<recordDelimiter>\n</recordDelimiter>
<physicalLineDelimiter>\n</physicalLineDelimiter>
<attributeOrientation>column</attributeOrientation>
<simpleDelimited>
<fieldDelimiter>\t</fieldDelimiter>
</simpleDelimited>
</textFormat>
</dataFormat>
<distribution>
<online>
<url>http://metacat.lternet.edu/das/dataAccessServlet?docid=knb-lter-bnz..&amp;urlTail=/ascii/files/218_AnimalSpeciesList.txt</url>
</online>
</distribution>
</physical>
<attributeList>
<attribute>
<attributeName>kingdom_name</attributeName>
<attributeLabel>kingdom_name</attributeLabel>
<attributeDefinition>kingdom_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>kingdom_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>order_name</attributeName>
<attributeLabel>order_name</attributeLabel>
<attributeDefinition>order_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>order_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>family_name</attributeName>
<attributeLabel>family_name</attributeLabel>
<attributeDefinition>family_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>family_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>genus</attributeName>
<attributeLabel>genus</attributeLabel>
<attributeDefinition>genus</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>genus<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>species</attributeName>
<attributeLabel>species</attributeLabel>
<attributeDefinition>species</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>species<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>subspecies_var</attributeName>
<attributeLabel>subspecies_var</attributeLabel>
<attributeDefinition>subspecies_var</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>subspecies_var<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>common_name</attributeName>
<attributeLabel>common_name</attributeLabel>
<attributeDefinition>common_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>common_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>notes</attributeName>
<attributeLabel>notes</attributeLabel>
<attributeDefinition>Notes/Synonyms</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>Notes/Synonyms</definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
</attributeList>
</dataTable>
<dataTable>
<entityName>218_PlantSpeciesList.txt</entityName>
<!--No data table description found (df_loc/df_desc)-->
<physical>
<objectName>218_PlantSpeciesList.txt</objectName>
<dataFormat>
<textFormat>
<numHeaderLines>1</numHeaderLines>
<recordDelimiter>\n</recordDelimiter>
<physicalLineDelimiter>\n</physicalLineDelimiter>
<attributeOrientation>column</attributeOrientation>
<simpleDelimited>
<fieldDelimiter>\t</fieldDelimiter>
</simpleDelimited>
</textFormat>
</dataFormat>
<distribution>
<online>
<url>http://metacat.lternet.edu/das/dataAccessServlet?docid=knb-lter-bnz..&amp;urlTail=/ascii/files/218_AnimalSpeciesList.txt</url>
</online>
</distribution>
</physical>
<attributeList>
<attribute>
<attributeName>kingdom_name</attributeName>
<attributeLabel>kingdom_name</attributeLabel>
<attributeDefinition>kingdom_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>kingdom_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>order_name</attributeName>
<attributeLabel>order_name</attributeLabel>
<attributeDefinition>order_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>order_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>family_name</attributeName>
<attributeLabel>family_name</attributeLabel>
<attributeDefinition>family_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>family_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>genus</attributeName>
<attributeLabel>genus</attributeLabel>
<attributeDefinition>genus</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>genus<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>species</attributeName>
<attributeLabel>species</attributeLabel>
<attributeDefinition>species</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>species<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>subspecies_var</attributeName>
<attributeLabel>subspecies_var</attributeLabel>
<attributeDefinition>subspecies_var</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>subspecies_var<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>common_name</attributeName>
<attributeLabel>common_name</attributeLabel>
<attributeDefinition>common_name</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>common_name<!--warning: used the attribute (variable) name as definition and description. it would be better to provide a better description in the DB (datafilevariables/description) or code and code defintion DB  (datafilevaribles/valucodes) with structured code and code-definition pairs (i.e; code=definition-of-code, code2=definition-of-code2) the pairs must be comma separated--></definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
<attribute>
<attributeName>notes</attributeName>
<attributeLabel>notes</attributeLabel>
<attributeDefinition>Notes/Synonyms</attributeDefinition>
<storageType>string</storageType>
<measurementScale>
<nominal>
<nonNumericDomain>
<textDomain>
<definition>Notes/Synonyms</definition>
</textDomain>
</nonNumericDomain>
</nominal>
</measurementScale>
<!--No missing value/character in database (datafilevarible/errorcode)-->
</attribute>
</attributeList>
</dataTable>
</dataset>
</eml:eml>

