|
Metadata Home > Metadata
Mappings > TEI to UVa Metadata Mapping
Content Standard at:
http://www.tei-c.org/P4X/
P4 DTD at:
http://www.tei-c.org/P4X/DTD/
UVa Fedora TEI Content Model
Example in Native Format
Every TEI-conformant text must include a set of descriptions. The set is
known as the TEI header, tagged <teiHeader>, and it has four major parts:
- a file description, tagged <fileDesc>, containing information
about the e-text file itself.
- a source description tagged <source text>, containing information
about the original print text.
- an encoding description, tagged <encodingDesc>, which allows
for detailed description of whether (or how) the text was normalized during
transcription, how the encoder resolved ambiguities in the source, what
levels of encoding or analysis were applied, and similar matters.
- a text profile, tagged <profileDesc> containing classifactory
and contextual information about the text, such as its subject matter, the
situation in which it was produced, the individuals described by or participating
in producing it, and so forth.
- a revision history, tagged <revisionDesc>, which allows the
encoder to provide a history of changes made during the development of the
e-text. The revision history is important for version control and for resolving
questions about the history of a file.
Generally, much of the information concerning the source of a TEI e-text
can be found within the TEI <sourceDesc> element and is mapped to the top level <descmeta>
element. In most cases, information contained within the TEI <fileDesc>
is mapped to <descmeta><surrogate>. Both are considered descriptive metadata. The Administrative metadata (UVa AdminMeta) is drawn from the xml declarations at the top of the TEI file.
TEI <revisionDesc> and <encodingDesc> elements are considered
administrative metadata.
UVa DescMeta-TEI map (Excel document)
UVa DescMeta-TEI map (PDF document)
UVa AdminMeta-TEI map (Excel document)
UVa AdminMeta-TEI map (PDF document)
|
