'$RCSfile: eml-dataset.xsd,v $' Copyright: 1997-2002 Regents of the University of California, University of New Mexico, and Arizona State University Sponsors: National Center for Ecological Analysis and Synthesis and Partnership for Interdisciplinary Studies of Coastal Oceans, University of California Santa Barbara Long-Term Ecological Research Network Office, University of New Mexico Center for Environmental Studies, Arizona State University Other funding: National Science Foundation (see README for details) The David and Lucile Packard Foundation For Details: http://knb.ecoinformatics.org/ '$Author: jones $' '$Date: 2003-11-06 20:15:20 $' '$Revision: 1.51 $' This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA eml-dataset

The eml-dataset module contains general information that describes dataset resources. It is intended to provide overview information about the dataset: broad information such as the title, abstract, keywords, contacts, maintenance history, purpose, and distribution of the data themselves. The eml-dataset module also imports many other modules that are used to describe the dataset in fine detail. Specifically, it uses the eml-methods module to describe methodology used in collecting or processing the dataset, the eml-project module to describe the overarching research context and experimental design, the eml-access module to define access control rules for the data and metadata, and the eml-entity module to provide detailed information about the logical structure of the dataset. A dataset can be (and often is) composed of a series of data entities (tables) that are linked together by particular integrity constraints. The eml-dataset module, like other modules, may be "referenced" via the <references> tag. This allows a dataset to be described once, and then used as a reference in other locations within the EML document via its ID.

all datasets yes Dataset Descriptors The dataset field encompasses all information about a single dataset. The dataset field encompasses all information about a single dataset. A dataset is defined as all of the information describing a data collection event. This event may take place over some period of time and include many actual collections (a time series or remote sensing application) or it could be just one actual collection (a day in the field). Dataset DatasetType is the base type for the dataset element. DatasetType is the base type for the dataset element. The dataset field encompasses all information about a single dataset. A dataset is defined as all of the information describing a data collection event. This event may take place over some period of time and include many actual collections (a time series or remote sensing application) or it could be just one actual collection (a day in the field). Purpose A description of the purpose of this dataset. A description of the purpose of this dataset. Note that this element requires DocBook style formatting. See eml-text for more information. Maintenance A description of the maintenance of this data resource. A description of the maintenance of this data resource. This includes information about the frequency of update, and whether there is ongoing data collection. Contact The contact for this dataset The contact field contains contact information for this dataset. This is the person or institution to contact with questions about the use, interpretation of a data set. Data Set Publisher The publisher of this data set The publisher of this data set. At times this is a traditional publishing house, but it may also simply be an institution that is making the data available in a published (ie, citable) format. Publication place The location that the resource was published. The pubPlace field is the location where the resource was published, which may be different from where the resource was created. San Francisco, CA, USA New Yor, NY, USA methods The methods field documents scientific methods used in the collection of this dataset. The methods field documents scientific methods used in the collection of this dataset. It includes information on items such as tools, instrument calibration and software. project The project field contains information on the project in which this dataset was collected. The project field contains information on the project in which this dataset was collected. It includes information such as project personell, funding, study area, project design and related projects. The project description can also contain documentation on subprojects. access The access field defines access control rules for this dataset. The access field defines access control rules for this dataset. Any access control rules defined here will apply to the entire dataset. Access allows you to define who can access this dataset if it is stored in an online storage system that is EML compliant. data table The dataTable field documents the dataTable(s) that make up this dataset. The dataTable field documents the dataTable(s) that make up this dataset. A dataTable could be anything from a Comma Seperated Value (CSV) file to a spreadsheet to a table in an RDBMS. spatial raster The spatialRaster field describes any spatial raster images included in this dataset. The spatialRaster field describes any spatial raster images included in this dataset. spatial vector The spatialVector field describes any spatial vectors included in this dataset. The spatialVector field describes any spatial vectors included in this dataset. stored procedure The storedProcedure field contains information about any stored procedures included with this dataset. The storedProcedure field contains information about any stored procedures included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset. view The view field contains information about any views included with this dataset. The view field contains information about any view included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset. other entity The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. (i.e. it is not a table, spatialRaster, spatialVector, storedProcedure or view.) OtherEntity allows the documentation of basic entity fields as well as a plain text field to allow you to type your entity. Maintenance Type The maintenance type defines the fields for the maintenance element. It encompasses all information related to the maintenance and upkeep of this dataset. The maintenance type defines the fields for the maintenance element. Maintenance Description A text description of the maintenance of this data resource. A text description of the maintenance of this data resource. Note that this field must be marked up using DocBook like tagging. See eml-text for more information. Maintenance Update Frequency Frequency with which changes and additions are made to the datset after the initial dataset is completed. Frequency with which changes and additions are made to the datset after the initial dataset is completed. The values for this field must come from the enumeration MaintUpFreqType. Change History A description of changes made to the data since its release. A description of changes made to the data since its release. Change Scope An expression describing the scope to which the documented change was applied. The expression should unambigously identify the entity(s) and attribute(s) that were changed. Old Value The previous value of the data prior to the change. The previous value or an expression that describes the previous value of the data. Change Date The date the changes were applied. The date the changes were applied. Comment Explanation or justification for the change made to the data. Explanation or justification for the change made to the data.