Module Documentation: eml-project
Back to EML Contents
The EML Project Module describes the research context in which the dataset was created, including description of over-all motivations and goals, funding, personnel, etc. This is also the module to describe over-all sampling methods for the project.

Element Definitions:

eml-project
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
identifierOptionalMultiple Times
researchProjectOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Research protocol descriptors
Summary:
Container of all research projects in which context the dataset was created.
Description:
eml-project elements describe various aspects of the research project within which researchers created the associated dataset. The association of a dataset with this project metadata is established in eml-dataset
Example:

Lineage:
eml-project was introduced in EML 2.0. It replaces eml-research, which was introduced into EML 1.4 as replacement for eml-context.
identifier
Content of this field: Description of this field:
Elements: Required?: How many:
Attributes: Required?: Default Value:

Tooltip:
Unique identifier
Summary:
The unique identifier of this metadata file or object.
Description:
The identifier field provides a unique identifier for this metadata documentation. It will most likely be part of a sequence of numbers or letters that are meaningful in a larger context, such as a metadata catalog. That larger system can be identified in the "system" attribute. Multiple identifiers can be listed corresponding to different catalog systems.
Example:
<identifier system="metacat">nceas.3.2</identifier>
Lineage:
The 'identifier' field is derived from the eml-dataset meta_file_id filed in EML 1.4.
researchProject
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
titleOptionalMultiple Times
personnelOptionalMultiple Times
cov:temporalCovOptionalMultiple Times
geographicCovOptionalMultiple Times
abstractOptionalMultiple Times
fundingOptionalMultiple Times
siteDescriptionOptionalMultiple Times
designDescriptionOptionalMultiple Times
researchProjectOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Research project descriptor
Summary:
Descriptor of research project in which context the dataset was created.
Description:
Research project element is a descriptor of various programmatic aspects within which researchers created this dataset. It can also include general research goals and motivations, data collection methods, equations, formulas. But see 'eml-protocol' for more areas to provide methodological detail.
Example:

Lineage:
The researchProject element was introduced into EML 1.4.
title
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Project Title
Summary:
Title of the project.
Description:
A descriptive title for the research project.
Example:
Species diversity in Tennessee riparian habitats.
Lineage:
Introduced into EML 1.4.
personnel
Content of this field: Description of this field:
Type: rp:ResponsibleParty
Attributes: Required?: Default Value:

Tooltip:
Originator
Summary:
The party who created the research project.
Description:
The party who created the research project.
Example:

Lineage:
FGDC-STD-001.1-1999 (nbii-fgdc-std-001.1-1999)
geographicCov
Content of this field: Description of this field:
Type: cov:GeographicCoverage
Attributes: Required?: Default Value:

Tooltip:
Geographical coverage
Summary:
Geographical coverage of the site of the project.
Description:
This element is to specify the geographical coordinates of the site of the project: latitude and longitude.
Example:

Lineage:
The geographicCoverage element was introduced into EML 1.4.
abstract
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
paragraphOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Abstract
Summary:
Descriptive abstract.
Description:
Descriptive abstract in paragraph of text.
Example:

Lineage:
The abstract element was introduced into EML 1.4.
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
funding
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
paragraphOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Funding
Summary:
Funding information.
Description:
Grant and contract numbers, names and addresses of funding sources described in paragraph of text.
Example:

Lineage:
The funding element was introduced into EML 1.4.
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
siteDescription
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
paragraphOptionalMultiple Times
cit:citationOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Site description
Summary:
Site description.
Description:
Description of the site of the project. It is intended to include general descriptions of the habitiat in paragraph form. Likewise, information on geography, geology, hydrology, history, and climate should be included here if desired.
Example:

Lineage:
The siteDescription element was introduced into EML 1.4.
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
designDescription
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
pro:protocolOptionalMultiple Times
samplingOptionalMultiple Times
paragraphOptionalMultiple Times
cit:citationOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Experimental or Sampling design
Summary:
Experimental or Sampling design of the project
Description:
Experimental or Sampling design: the design method, plots, samplings, descriptive paragraph of text or citation from a source.
Example:

Lineage:
The designDescription element was introduced into EML 1.4.
sampling
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
temporalCovOptionalMultiple Times
frequencyOptionalMultiple Times
paragraphOptionalMultiple Times
cit:citationOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Temporal sampling regime
Summary:
Temporal sampling regime
Description:
Information necessary to understand temporal sampling regime: temporal boundaries, frequency of occurrence, descriptive paragraph of text or citation from a source.
Example:

Lineage:
The sampling element was introduced into EML 1.4.
temporalCov
Content of this field: Description of this field:
Type: cov:TemporalCoverage
Attributes: Required?: Default Value:

Tooltip:
Temporal Coverage
Summary:
Information on the periods of time that sampling took place
Description:
Information necessary to understand temporal sampling regime: temporal boundaries, frequency of occurrence, descriptive paragraph of text or citation from a source.
Example:

Lineage:
The sampling element was introduced into EML 1.4.
frequency
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Sampling frequency
Summary:
Information on the rate of sampling
Description:
The frequency field is intended to document the sampling rate for the specific method employed.
Example:

Lineage:
The sampling element was introduced into EML 1.4.
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Attribute Definitions:

system

Type: xs:string

Use: optional


Tooltip:
Catalog system
Summary:
The catalog system in which this identifier is used.
Description:
This element gives the name of the catalog system in which this identifier is used. It is useful to determine the scope of the identifier, and to determine the semantics of the various subparts of the identifier. Unresolved issue: can or should this be a URI/URL pointing to the catalog system, or just the name?
Example:
<identifier system="metacat">nceas.3.2</identifier>
Lineage:
New to EML 2.0.

Complex Type Definitions:

Simple Type Definitions:

Web Contact: jones@nceas.ucsb.edu