Element Definitions:
|
eml-constraint |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
identifier | Required | Multiple Times |
constraint | Required | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Relational integrity constraint descriptors
Summary:
Describes the relational integrity constraints of a relational
database.
Description:
Describes the relational integrity constraints of a relational
database. This includes primary keys, foreign keys, unique keys, etc.
Example:
Lineage:
New in EML 2.0
|
identifier |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
system | optional |
|
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.
|
constraint |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
name | Optional | Once |
tableName | Optional | Once |
type | Required | Once |
relatedTable | Optional | Multiple Times |
description | Optional | Once |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Integrity constraint
Summary:
Information about the integrity constraint being defined.
Description:
Complete information needed to reconstruct this integrity
constraint for enforcement in a system such as a relational
database management system.
Example:
Lineage:
New in EML 2.0
|
name |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
constraint name
Summary:
name of the field that this constraint is tied to
Description:
name of the field that this constraint is tied to. This
could also be the name of an independent constraint such
as a trigger or an autonumber generator.
Example:
LocationID, TABLE1_NUMBER_GEN1
Lineage:
New in EML 2.0
|
tableName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
table to which this constraint is tied
Summary:
table to which this constraint is tied
Description:
table to which this constraint is tied. In the instance
of a key, it is the name of the table in which it is
defined.
Example:
site_properties
Lineage:
New in EML 2.0
|
type |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
type of constraint
Summary:
the type of constraint being defined
Description:
the type of constraint being defined. This is
what kind of constraint this is.
Example:
primary key, foreign key, unique key
Lineage:
New in EML 2.0
|
relatedTable |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
table to which this constraint links its table
Summary:
table to which this constraint links its table
Description:
table to which this constraint links its table. This
should be used for all foreign keys.
Example:
site_properties
Lineage:
New in EML 2.0
|
description |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
constraint description
Summary:
description of the constraint
Description:
description of the constraint. Any additional
information that may be needed to fully understand
the constraint.
Example:
Lineage:
New in EML 2.0
|
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:
|