file

Element <structMap>

The structural map section <structMap> is the heart of a

METS

document. It provides a means for organizing the digital conten

represented by the <file> elements in the <fileSec> of t

he METS

document into a coherent hierarchical structure. Such

hierarchical structure can be presented to users to facilitate

their

comprehension and navigation of the digital content. It c

further be applied to any purpose requiring an understanding of

the structural relationship of the content files or par

ts of the

content files. The organization may be specified to any lev

el of

granularity (intellectual and or physical) that is desire

d. Since

the <structMap> element is repeatable, more than one

organization can be applied to the digital content represen

ted by

e METS document.

Element <structLink>

The structural link section element <structLink> allows for

the

specification of hyperlinks between the different component

s of

a METS structure that are delineated in a structural map. T

his

element is a container for a single, repeatable element,

<smLink>, which indicates a hyperlink between two nodes in

the structural map. The <structLink> section in the MET

document is identified using its XML ID attributes.

Element <behaviorSec>

A behavior section element <behaviorSec> associates

executable behaviors with content in the METS document by

means of a repeatable behavior <behavior> element. This

element has an interface definition <interfaceDef> ele

ment that

represents an abstract definition of the set of behavio

represented by a particular behavior section. A <behavior

element also has a <mechanism> element, which is used to p

oint

to a module of executable code that implements and runs the

behavior defined by the interface definition. The <behavio

rSec>

element, which is repeatable as well as nestable, can be used

group individual behaviors within the structure of the METS

document.

Element <techMD>

A technical metadata element <techMD> records technical

metadata about a component of the METS object, such as a

digital content file. The <techMD> element conforms to

same

generic datatype as the <dmdSec>, <rightsMD>, <sourceMD>

and <digiprovMD> elements, and supports the same sub-

elements and attributes. A technical metadata element can

either

wrap the metadata (mdWrap) or reference it in an externa

location (mdRef) or both. METS allows multiple <techM

elements; and technical metadata can be associated with

any

METS element that supports an ADMID attribute.

Element <rightsMD>

An intellectual property rights metadata element <rights

MD>

records information about copyright and licensing pertaining to

a component of the METS object. The <rightsMD> elemen

conforms to same generic datatype as the <dmdSec>,

<techMD>, <sourceMD> and <digiprovMD> elements, and

supports the same sub-elements and attributes. A rights m

etadata

element can either wrap the metadata (mdWrap) or refere

nce it

in an external location (mdRef) or both. METS allows mu

ltiple

<rightsMD> elements; and rights metadata can be associ

ated

with any METS element that supports an ADMID attribute.

Element <sourceMD>

A source metadata element <sourceMD> records descriptive

and

administrative metadata about the source format or me

dia of a

component of the METS object such as a digital content

file. It

is often used for discovery, data administration or prese

rvation

of the digital object. The <sourceMD> element conforms to

same generic datatype as the <dmdSec>, <techMD>,

<rightsMD>, and <digiprovMD> elements, and supports the

same sub-elements and attributes. A source metadata elem

ent

can either wrap the metadata (mdWrap) or reference it in

external location (mdRef) or both. METS allows multipl

<sourceMD> elements; and source metadata can be associat

with any METS element that supports an ADMID attribute.

Element <digiprovMD>

A digital provenance metadata element <digiprovMD> can be

used to record any preservation-related actions taken on the

various files that comprise a digital object (e.g., thos

subsequent to the initial digitization of the files such as

transformation or migrations) or, in the case of born

digital

materials, the files

’

creation. In short, digital provenance should

be used to record information that allows both archival/li

brary

staff and scholars to understand what modifications have b

een

made to a digital object and/or its constituent parts during i

ts life

cycle. This information can then be used to judge how those

processes might have altered or corrupted the object

’

s ability to

accurately represent the original item. One might, for

example,

record master derivative relationships and the process

by which

those derivations have been created.

Element <file>

The file element <file> provides access to the content files

for

the digital object being described by the METS document. A

<file> element may contain one or more <FLocat> ele

ments

which provide pointers to a content file and/or a <FContent>

element which wraps an encoded version of the file. Embeddi

files using <FContent> can be a valuable feature for exch

anging

digital objects between repositories or for archiving versi

ons of

digital objects for off-site storage. All <FLocat> and

<FContent> elements should identify and/or contain iden

tical

copies of a single file. The <file> element is recursi

ve, thus

allowing sub-files or component files of a larger file to

be listed

in the inventory.

Element <div>

The structural divisions of the hierarchical organization

provided

by a <structMap> are represented by division <div> elements

which can be nested to any depth. Each <div> element can

represent either an intellectual (logical) division or

a physical

division. Every <div> node in the structural map hierarchy

may

be connected (via subsidiary <mptr> or <fptr> elements) to

content files that represent that div's portion of the

whole

document.

Element <mptr>

Like the <fptr> element, the METS pointer element <mptr

represents digital content that manifests its parent <d

iv>

element. Unlike the <fptr>, which either directly or indi

rectly

points to content represented in the <fileSec> of the pare

METS document, the <mptr> element points to content

represented by an external METS document. Thus, this elem

ent

allows multiple discrete and separate METS documents

to be

organized at a higher level by a separate METS document.

Element <fptr>

The <fptr> or file pointer element represents digital co

ntent that

manifests its parent <div> element. The content represente

d by

an <fptr> element must consist of integral files or par

ts of files

that are represented by <file> elements in the <fileSec>

. Via its

FILEID attribute, an <fptr> may point directly to a single

integral <file> element that manifests a structural divi

sion.

However, an <fptr> element may also govern an <area>

element, a <par>, or a <seq>, which in turn would point to th

relevant file or files. A child <area> element can poi

nt to part of

a <file> that manifests a division, while the <par> and <s

eq>

elements can point to multiple files or parts of files t

hat together

manifest a division.

Element <par>

The <par> or parallel files element aggregates pointers to

files,

parts of files, and/or sequences of files or parts of files

that must

be played or displayed simultaneously to manifest a block of

digital content represented by an <fptr> element.

Element <smLink>

The Structural Map Link element <smLink> identifies a

hyperlink between two nodes in the structural map. You would

use <smLink>, for instance, to note the existence of hypertex

links between web pages, if you wished to record those links

within METS. NOTE: <smLink> is an empty element. The

location of the <smLink> element to which the <smLink>

element is pointing MUST be stored in the xlink:href attribut

Element <seq>

The sequence of files element <seq> aggregates pointers to

files,

parts of files and/or parallel sets of files or parts of f

iles that

must be played or displayed sequentially to manifest a bloc

k of

digital content.

Element <area>

The area element <area> typically points to content consi

sting of

just a portion or area of a file represented by a <file>

element in

the <fileSec>.

Element <smLinkGrp>

The structMap link group element <smLinkGrp> provides an

implementation of xlink:extendLink, and provides xlink

compliant mechanisms for establishing xlink:arcLink type links

between 2 or more <div> elements in <structMap> element(s

)

occurring within the same METS document or different METS

documents.

Element

The structMap locator link element <smLocatorLink> is of

xlink:type "locator". It provides a means of identifying a <di

element that will participate in one or more of the links

specified

by means of <smArcLink> elements within the same

<smLinkGrp>.

Element <smArcLink>

Element <smArcLink> contained within <smLinkGrp>.

Element <behavior>

A behavior element <behavior> can be used to associate

executable behaviors with content in the METS document.

This

element has an interface definition <interfaceDef> ele

ment that

represents an abstract definition of a set of behaviors

represented

by a particular behavior. A <behavior> element also has a

behavior mechanism <mechanism> element, a module of

executable code that implements and runs the behavior defi

ned

abstractly by the interface definition.

Element <interfaceDef>

The interface definition <interfaceDef> element contai

ns a

pointer to an abstract definition of a single behavior or

a set of

related behaviors that are associated with the content

of a METS

object.

Element <mechanism>

A mechanism element <mechanism> contains a pointer to an

executable code module that implements a set of behaviors

defined by an interface definition.

Element <mdRef>

The metadata reference element <mdRef> element is a

generic

element used throughout the METS schema to provide a pointer

to metadata which resides outside the METS document.

Element <mdWrap>

A metadata wrapper element <mdWrap> provides a wrapper

around metadata embedded within a METS document.

Element <binData>

The binary data wrapper element <binData> is used to contain

Base64 encoded metadata.

Element <xmlData>

The xml data wrapper element <xmlData> is used to contain

XML encoded metadata.

Element <FLocat>

The file location element <FLocat> provides a pointer to

the

location of a content file. It uses the XLink reference

syntax to

provide linking information indicating the actual location of

the

content file, along with other attributes specifying additi

onal

linking information. NOTE: <FLocat> is an empty element. Th

location of the resource pointed to MUST be stored in the

xlink:href attribute.

Element <FContent>

The file content element <FContent> is used to identify

content file contained internally within a METS documen

t. The

content file must be either Base64 encoded and contained wit

hin

the subsidiary <binData> wrapper element, or consist of XML

information and be contained within the subsidiary <xml

Data>

wrapper element.

Element <binData>

A binary data wrapper element <binData> is used to contain a

Base64 encoded file.

Element <xmlData>

An xml data wrapper element <xmlData> is used to contain an

XML encoded file. The content of an <xmlData> element can

in any namespace or in no namespace. As permitted by the XM

Schema Standard, the processContents attribute value for

the

metadata in an <xmlData> element is set to

“

lax

”

. Therefore, if

the source schema and its location are identified by mea

ns of an

xsi:schemaLocation attribute, then an XML processor will

validate the elements for which it can find declarations.

Element <stream>

A component byte stream element <stream> may be compose

of one or more subsidiary streams. An MPEG4 file, for ex

ample,

might contain separate audio and video streams, each of w

hich is

associated with technical metadata. The repeatable <strea

element provides a mechanism to record the existence of

separate data streams within a particular file, and the oppor

tunity

to associate <dmdSec> and <amdSec> with those subsidiary

data streams if desired.

Element <transformFile>

The transform file element <transformFile> provides a

means to

access any subsidiary files listed below a <file> element

indicating the steps required to "unpack" or transform the

subsidiary files. This element is repeatable and might provide

link to a <behavior> in the <behaviorSec> that performs the

transformation.

Table B.3 TEI Header (Version 2.8.0)

(Source: TEI Header

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/HD.html#HD21)

Types of Elements

Definition

Example

titleStmt

(title statement) groups information about the title

of a work and those responsible for its content.

editionStmt

(edition statement) groups information relating to

one edition of a text.

extent

(extent) describes the approximate size of a text

stored on some carrier medium or of some other

object, digital or non-digital, specified in any

convenient units.

publicationStmt

(publication statement) groups information

concerning the publication or distribution of an

electronic or other text.

A publisher or

distributor;Licens

ing conditions;

Identifying

numbers

<filedesc> File Description

A required subelement of the <eadheader> that bundles

much of the bibliographic information about the finding

aid, including its author, title, subtitle, and sponsor (al

l in

the <titlestmt>), as well as the edition, publisher,

publishing series, and related notes (encoded separately).

<profiledesc> Profile Description

An optional subelement of the <eadheader> that bundles

information about the creation of the encoded version of

the finding aid, including the name of the agent, place,

and date of encoding. The <profiledesc> element also

designates the

predominant and minor languages used in the finding aid.

<revisiondesc> Revision

Description

An optional subelement of the <eadheader> for

information about changes or alterations that have be

made to the encoded finding aid. The revisions may be

recorded as part of a <list> or as a series of <change>

elements. Like much of the

<eadheader>, the <revisiondesc> element is modeled on

an element found in the Text Encoding Initiative (TEI)

DTD. The TEI recommends that revisions be numbered

and appear in reverse chronological order, with the most

recent <change> first.

For more EAD Elements: http://www.loc.gov/ead/tglib/element_index.htm

Table B.5 VRA Core (Version 4.0)

(Source: VRA Core 4.0 Element Description

http://www.loc.gov/standards/vracore/VRA_Core4_Element_Description.pdf

)

Types of Elements

Definition

Example

work, collection, or

image

A choice of one of three elements, WORK,

COLLECTION, or IMAGE, defines a VRA 4.0

record as describing a WORK (a built or created

object), a COLLECTION (an aggregate of such

objects), or an IMAGE (a visual surrogate of such

objects.)

agent

The names, appellations, or other identifiers

assigned to an individual, group, or corporate body

that has contributed to the design, creation,

production, manufacture, or alteration of the work

or image.

cultural Context

The name of the culture, people (ethnonym), or

adjectival form of a country name from which a

Work, Collection, or Image originates, or the

cultural context with which the Work, Collection, or

Image has been associated.

date

Date or range of dates associated with the creation,

design, production, presentation, performance,

construction, or alteration, etc. of the work or

image. Dates may be expressed as free text or

numerical.

description

A free-text note about the Work, Collection, or

Image, including comments, description, or

interpretation, that gives additional information not

recorded in other categories.

inscription

All marks or written words added to the object at

the time of production or in its subsequent history,

including signatures, dates, dedications, texts, and

colophons, as well as marks, such as the stamps of

silversmiths, publishers, or printers.

location

The geographic location and/or name of the

repository, building, site, or other entity whose

boundaries include the Work or Image.

Repository

locations;

Creation

locations;

Discovery

locations

material

The substance of which a work or an image is

composed.

measurements

The physical size, shape, scale, dimensions, or

format of the Work or Image.

relation

Terms or phrases describing the identity of the

related work and the relationship between the work

being cataloged and the related work or image. Use

this element to relate work records to other work or

collection records, or image records to work or

collection records.

rights

Information about the copyright status and the rights

holder for a work, collection, or image.

source

A reference to the source of the information

recorded about the work or the image.

stateEdition

The identifying number and/or name assigned to the

state or edition of a work that exists in more than

one form and the placement of that work in the

context of prior or later issuances of multiples of th

same work.

stylePeriod

A defined style, historical period, group, school,

dynasty, movement, etc. whose characteristics are

represented in the Work or Image.

subject

Terms or phrases that describe, identify, or interpret

the Work or Image and what it depicts or expresses.

technique

The production or manufacturing processes,

techniques, and methods incorporated in the

fabrication or alteration of the work or image.

textref

Contains the name of a related textual reference and

any type of unique identifier that text assigns to a

Work or Collection that is independent of any

repository.

title

The title or identifying phrase given to a Work or an

Image.

worktype

Identifies the specific type of WORK,

COLLECTION, or IMAGE being described in the

record.