500 likes | 531 Views
Collections. Vegetation sampling. We observe and collect data on soil. More soil. Once a plot is set up, the fun begins!. Marl outcrop – Lake Waccamaw, Columbus Co, NC.
E N D
Fall line rock outcrop vegetation , with Amphianthus pusillus and Diamorpha smallii - Forty Acre Rock HP, Lancaster Co, SC
Why an exchange standard? • Many research questions require lots of data • Facilitate exchange ! • Write input/output just once • Encourage others to participate (eg US Forest Service) • Safe & documented long-term storage of plot data
Key design features • Many kinds of plots !!! • Easy search • Easy citation and linkage • Easy download • XML input and output options • Users can annotate plots and determinations • Support of taxon concepts
Locality Plot Observation/ Collection Event Plot/Inventory database Specimen or Object Occurrence database Bio-Taxon Taxonomic database Biodiversity data structure Vegetation Type Vegetation type database
Core elements of VegBank Project Plot Plot Observation Taxon / Individual Observation Taxon Interpretation Plot Interpretation
VegBank consists of three integrated databases • The Plot Database • The Plant Database • The Community Database
The VegBank ERD • Available at: http://vegbank.org/vegdocs/design/erd/vegbank_erd.pdf • Click tables for data dictionary and constrained vocabulary
Plot • Embargos • Named Place
Observation • Project • Disturbance Obs • Soil Obs • Soil taxon • Graphic • Observation Synonym
Taxon Observation • Importance values • Author name Taxon Interpretation • Which taxon • Who decided and why • Stem or collective • Voucher information
Strata & Cover • Stratum method • Stratum type • Stratum • Cover method • Cover Index
Interpretationcontinued • Plants • Tax Interpretation • Taxon Alt • Communities • Class • Interpretation
Problematic taxa of ecological datasets • Carex sp. • Crustose lichen • Hairy sedge #6. • Sporobolus sp. #1 • Picea glauca – engelmannii complex • Potentilla simplex or P. canadensis • Carya ovata sec. Gleason 1952
Party • Project Contr. • Obs Contr. • Role
Utilities • User defined • Notes • Revisions
Taxonomic database challenge:Standardizing organisms and communities The problem: Integration of data potentially representing different times, places, investigators and taxonomic standards. The traditional solution: A standard list of organisms / communities.
Standardized taxon lists fail • to allow dataset integration • The reasons include: • Taxonomic concepts are not defined (just lists), • Relationships among concepts are not defined • The user cannot reconstruct the database as viewed at an arbitrary time in the past, • Multiple party perspectives on taxonomic concepts and names cannot be supported or reconciled.
Three concepts of subalpine fir Splitting one species into two illustrates the ambiguity often associated with scientific names. Abies bifolia Abies lasiocarpa Abies lasiocarpa sec. Little sec. USDA PLANTS sec. Flora North America
One concept ofAbieslasiocarpa USDA Plants & ITIS Abies lasiocarpa var. lasiocarpa var. arizonica
A narrow concept of Abies lasiocarpa Flora North America Abies lasiocarpa Abies bifolia Partnership with USDA plants to provide plant concepts for data integration
High-elevation fir trees of western North America AZ NM CO WY MT AB eBC wBC WA OR Distribution Abies lasiocarpa var. arizonica Abies lasiocarpa var. lasiocarpa USDA - ITIS Abies lasiocarpa Abies bifolia Flora North America A B C Minimal concepts
Andropogon virginicus complex in the Carolinas 9 elemental units; 17 base concepts, 27 scientific names
Relationships among conceptsallow comparisons and conversions • Congruent, equal (=) • Includes (>) • Included in (<) • Overlaps (><) • Disjunct (|) • and others …
Party Perspective • The Party Perspective on a concept includes: • Status – Standard, Nonstandard, Undetermined • Correlation with other concepts – Equal, Greater, Lesser, Overlap, Undetermined. • Start & Stop dates for tracking changes
Intended functionality • Organisms are labeled by reference to concept (name-reference combination), • Party perspectives on concepts and names can be dynamic, but remain perfectly archived, • User can select which party perspective to follow, • Different names systems are supported, • Enhanced stability in recognized concepts by separating name assignment and rank from concept.