This documents an additional TEI element which may be used to encode rich textual descriptions of manuscript material of any kind.
Primary application areas...
References and sources...
This description assumes the availability of a number of standard TEI elements. All such elements are signalled in the body of this document with the phrase ``(standard TEI element''). For convenience, an additional section (2 ) lists brief characteristics of all those elements and their constituents.
An <msDescription> element may reasonably appear either within the body or the header of a TEI conformant document. In the former case, where the document being encoded is essentially a collection of manuscript descriptions, the <msDescription> element may be placed anywhere that a paragraph might appear. In the latter case, where the description forms part of the metadata to be associated with a digital representation of some manuscript original, whether as a transcription, as a collection of digital images, or as some combination of the two, then the <msDescription> may appear within the <sourceDesc> element of the header.
The <msDescription> element has eight components, of which only the first is mandatory. They are listed here, and discussed in the associated section below.
|<msIdentifier>||groups information that identifies a ms or ms fragment; mandatory; 1.2|
|<msDocket>||contains a name or description for the manuscript supplied by the cataloguer for use as a running heading.|
|<msSummary>||a short summary catalogue record containing author, title, date, and notes only; may be used as an alternative to more detailed cataloguing; 1.4|
|<mscontents>||an itemised list of the intellectual contents of a ms or ms part, with bibliographic descriptions etc. as appropriate; 1.5|
|<physDesc>||groups information providing a detailed descriptions of all physical aspects of the ms or ms part (e.g. its material, script, component parts, illustration, binding etc.1.6|
|<history>||summarizes the known history of a ms or ms part: its origin and provenance 1.7|
|<additional>||groups other related information about a manuscript, in particular, administrative information relating to its current location, additional materials associated with it, etc. 1.8|
|<msPart>||contains a nested description for a manuscript fragment which is now regarded as forming part of the ms being described, although physically distinct 1.9|
In addition to the global attributes rend, id, lang etc. available to all TEI elements, the <msDescription> element carries a special purpose status attribute which defines the compositional status of the manuscript being described , i.e. whether it is a complete unitary object, a composite of fragments, or an isolated group of fragments. In summary:
|<msDescription>||contains a description of a single identifiable manuscript or manuscript part|
|status||specifies the compositional status of a manuscript or manuscript part|
|uni||unitary: the manuscript is a complete entity which exists as a single fragment|
|compo||composite: the manuscript is a complete entity comprising multiple fragments|
|frag||fragmentary: the manuscript is an incomplete assemblage of one or more fragments|
|unknown||unknown or unstated|
Here is a very simple example of a complete manuscript description:
<msDescription> <msIdentifier> <city>Oxford</city> <repository>Bodleian Library</repository> <idNo type="Bod">Rawlinson Poet. 149</idNo> </msIdentifier> <msDocket> The Canterbury Tales </msDocket> </msDescription>
Here is a slightly more ambitious description for the same manuscript, using elements described in more detail in the following sections.
<!-- to be supplied-->
The formal definition for the <msDescription> element is as follows:
<!ELEMENT msDescription - - (msIdentifier, msDocket?, msSummary?, msContents?, physDesc?, history?, additional?, msPart*)>
The primary purpose of manuscript description is to provide an unambiguous means of identification for particular manuscript items within a collection. The <msIdentifier> element is provided for this purpose.
|<msIdentifier>||contains the information required to identify a given manuscript or manuscript part uniquely within its holding institution.|
A manuscript identifier typically has two parts, the first being its location, and the second the name used for it within that location. The location may be specified as a collection, located within a repository, forming part of an institution whose primary geographic location is within a city, itself located within a region or country, or both. A manuscript may have alternative identifiers additional to the one currently used, including informal names or old shelfmarks which are retained even after they have been officially superceded.
The following elements are available within <msIdentifier> to identify the physical location of a manuscript:
|<country>||contains the name of a geo-political unit larger than or administratively superior to a <region> (standard TEI element)|
|<region>||contains the name of a smaller geo-political unit, intermediate between <country> and <settlement> (standard TEI element)|
|<settlement>||contains the name of the smallest component of a placename expressed as a hierarchy of geo-political or administrative units (standard TEI element)|
|<institution>||contains the institutional name of an organization, such as a University or Library, within which a manuscript repository is located.|
|<repository>||contains the name of a repository (a physical building) within which manuscripts are stored, forming part of an institution.|
|<collection>||contains the name of a collection of manuscripts, not necessarily located within a single repository.|
These elements are all structurally equivalent to the standard TEI <name> element with an appropriate value for its type attribute; however the use of this `syntactic sugar' enables the model for <msIdentifier> to be constrained rather more tightly than would otherwise be possible. Specifically, only one of each of the elements listed above may appear; if present, they must appear in the order given; and all of them except for the <settlement> and <repository> element may be omitted.
The standard TEI element <idNo> should be used to supply an identifying name or number for a manuscript, such as a shelfmark. In addition, or alternatively, any number of <altName> elements may be used to supply alternative names for the manuscript:
|<idNo>||supplies any number used to identify a bibliographic item (standard TEI element)|
|<altName>||contains an alternative name or identifier for a manuscript, such as a former catalogue number or a nickname.|
At least an <idNo> element must be supplied.
Here is a simple example:
<msIdentifier> <settlement>San Marino</settlement> <repository>Huntington Library</repository> <idNo>El. 26 C. 9</idNo> </msIdentifier>
Here is a somewhat over explicit example:
<msIdentifier <country>UK</country> <region>Oxfordshire</region> <settlement>Oxford</settlement> <institution>The University of Oxford</institution> <repository>Bodleian Library</repository> <collection>Rawlinson</collection> <idNo type="BOD">Rawlinson MS poet. 149</idNo> <altname type="nick">Peter's favourite manuscript</altName> </msIdentifier>
The <msIdentifier> element and its constituents are formally defined as follows:
<!ELEMENT - - (country?, region?, settlement, institution?, repository, collection?, idNo, altName* )> <!ELEMENT country %om (#PCDATA) > <!ELEMENT region %om (#PCDATA) > <!ELEMENT settlement %om (#PCDATA) > <!ELEMENT institution %om (#PCDATA) > <!ELEMENT repository %om (#PCDATA) > <!ELEMENT collection %om (#PCDATA) > <!ELEMENT altName %om (#PCDATA) >
It is common practice to prefix a full manuscript description with a brief prose characterization, title, or description, summarizing the whole of the manuscript, which may be used as a kind of `supplied title' or heading. A special purpose <msDocket> element is provided for this purpose, which may be used as an alternative to a supplied title within the <msSummary> or <msContents> elements.
Here is an example of the use of this element:
<msDocket> The Ellesmere Chaucer </msDocket>
This element is formally defined as follows:
Manuscript cataloguing practices vary widely, not only in the scope of the information included, but also in the amount of detail which it is feasible or desirable to record for each item. Particularly when handling legacy data, there is a frequent demand for some kind of `minimal' level record, whether as an end in itself or as an initial stage in the creation of a more complete record.
It is possible for any project to select freely from the detailed provisions described in this chapter in order to create a subset tailored to its own needs, which can then later be expanded as appropriate. The DTD described here is designed precisely to facilitate such incremental enrichment. However, there is also a frequently voiced desire for some specific recommendation concerning the minimum practical level of detail to be recorded. The <msSummary> element is provided to meet this need, and that for rapid conversion of legacy data.
The <msSummary> element should not be used simply to hold short summary title, `docket', or `tombstone' specifying a supplied title or heading applicable to the whole of a manuscript: the <docket> element (1.3 ) is provided for this purpose.
Where more detail is required than can be accomodated by the <msSummary> element, it should not be used; indeed, good practice may suggest the removal of this element from the record when more detailed information has been included in the remainder of the manuscript description.
The <msSummary> element and its constituents provide for the inclusion of the following information in a structured form:
|<author>||identifies the primary author of a manuscript (standard TEI element)|
|<title>||supplies a title or brief description of a manuscript (standard TEI element)|
|<origPlace>||contains any form of place name, used to identify the place of origin for a manuscript or manuscript part.|
|<origDate>||contains any form of date, used to identify the date of origin for a manuscript or manuscript part.|
|<langUsage>||describes languages used within a ms (standard TEI element)|
|<note>||contains any additional descriptive information about a manuscript (standard TEI element)|
The constituents of a <msSummary> must be supplied in the order prescribed above. Only the <author><, ><title> and <note> elements may be repeated.
Here is a simple example:
<msSummary> <author>Domenico Cavalca</author> <title>Vite dei santi padri</title> <origPlace>trans. Naples</origPlace> <origDate>1474</origDate> </msSummary>
The <msSummary> element is formally defined as follows:
<!ELEMENT msSummary - - (author*, title*, origPlace?, origDate?, langUsage?, note*)>
The <msContents> element is used to describe the intellectual content of a manuscript or manuscript part. It comprises either a series of informal prose paragraphs or a series of more structured <msItem> elements, each of which provides a more detailed description of a single item contained within the manuscript.
In the simplest case, only a brief description may be provided, as in the following example:
<msContents> <p>A collection of Lollard sermons</p> </msContents>
This description may of course be expanded to include any of the TEI elements generally available within a <p> element, such as <bibl> to mark bibliographic descriptions, or <list> for a list. More usually however, each individual work within a manuscript will be given its own description, using the <msItem> element described in the next section, as in the following example:
<msContents> <msItem n="1"><title>An ABC</title>: <range>fols. 5r -7v</range> (<bibl><title>IMEV</title> <biblScope>239</biblScope></bibl>)</msItem> <msItem n="2"><title lang="FRA">Lenvoy de Chaucer a Scogan</title>: <range>fols. 7v -8v</range> (<bibl><title>IMEV</title> <biblScope>3747</biblScope></bibl>)</msItem> <msItem n="3"><title>Truth</title>: <range>fol. 8v</range> (<bibl><title>IMEV</title> <biblScope>809</biblScope></bibl>)</msItem> <msItem n="4"><title>Birds Praise of Love</title>: <range>fols. 8v -10v</range> (<bibl><title>IMEV</title> <biblScope>1506</biblScope></bibl>)</msItem> <msItem n="5"><title lang="LAT">De amico ad amica</title> and <title lang="LAT">Responcio</title>: <range>fols. 10v -11v</range> (<bibl><title>IMEV</title> <biblScope>16 & 19</biblScope></bibl>)</msItem> <msItem n="6"><title>Troilus and Criseyde</title>: <range>fols. 14r -126v</range> (Bk. 1:71-Bk. 5:1701, with additional losses due to mutilation throughout)</msItem> </msContents>
Any combination of the elements described in this section may be used to record information about individual items within the intellectual content of a manuscript or manuscript part. Each discrete item should be encoded within a distinct <msItem> element:
|<msItem>||describes an individual work or item within the intellectual content of a manuscript or manuscript part.|
A <msItem> element may simply contain running text with no further tagging; more usually, however, it will contain additional identifiable components. A number of standard TEI elements are available; these have the same definitions and significance as elsewhere in the TEI scheme:
|<author>||supplies the name of an author|
|<respStmt>||supplies a name and description for anyone other than an author credited with intellectual responsibility for some aspect of a work (e.g. an illustrator)|
|<title>||supplies a title for the work|
|<langUsage>||lists the languages used within a work|
|<q>||contains text quoted from the manuscript|
|<bibl>||contains a conventional bibliographic description, for example of a modern edition|
Any combination of these elements with the following additional manuscript-specific elements is permitted:
|<abstract>||contains a prose summary or abstract of the contents of one manuscript item.|
|<colophon>||contains the text of any colophon attached to a particular manuscript item.|
|<incipit>||contains the text of any incipit attached to a particular manuscript item.|
|<explicit>||contains the text of any explicit attached to a particular manuscript item.|
|<rubric>||contains the text of any rubric attached to and preceding a particular manuscript item.|
|<finalRubric>||contains the text of any finalRubric attached to and following a particular manuscript item.|
Finally, a special purpose <locus> element is provided to specify the location in the manuscript occupied by the element within which it appears. Locations are conventionally specified as a sequence of folio numbers, but may also be a discontinuous list, or a combination of the two. This specification should be given as the content of the <locus> element. It may also be specified in a normalised form using special purpose attributes on the <locus> element. To avoid ambiguity, a <locus> element should be the first component element of the item whose location is being specified, and it should not normally be repeated within that element.
|<locus>||defines a location within a manuscript or manuscript part, usually as a (possibly discontinuous) sequence of folio references.|
|from||specifies the starting point of the location in a normalised form|
|to||specifies the end-point of the location in a normalized form|
|supplied||indicates whether the foliation used to define the locus was supplied by the cataloguer or is that used in the manuscript itself|
|yes||the foliation is supplied by the cataloguer|
|no||the foliation is as given in the manuscript|
|targets||supplies identifiers of associated page images|
Each element within <msItem> has the same substructure, in which (following an optional <locus> element) any combination of phrase-level elements and plain text may appear, except for <abstract> which contains one or more paragraphs of text.
Here is a simple example, for a manuscript containing a single item:
<msContents> <msItem><locus>f. 1-223</locus> <author>Radulphus Flaviacensis</author> <title>Expositio super Leviticum </title> cf. <bibl>Stegmüller, RB 7093</bibl> <incipit><locus>f. 1</locus> Forte Hervei monachi</incipit> <explicit><locus>f. 223v</locus> Benedictio salis et aquae</explicit> </msItem> </msContents>
Note that a manuscript item may itself contain further nested items, for example where a title is supplied for a group of works each of which is also titled, as in the following example:
<!-- to be supplied -->
The <msContents> element and its constituents are formally defined as follows:
<!ELEMENT msContents - - (p+|msItem+)> <!ELEMENT msItem - - (locus?, (#PCDATA|author|respStmt|title |rubric|incipit|explicit|colophon|finalRubric|langUsage |q|bibl|abstract|msItem )* )> <!ELEMENT abstract - - (locus?, %phrase.seq;) > <!ELEMENT rubric - - (locus?, %phrase.seq;) > <!ELEMENT incipit - - (locus?, %phrase.seq;) > <!ELEMENT explicit - - (locus?, %phrase.seq;) > <!ELEMENT colophon - - (locus?, %phrase.seq;) > <!ELEMENT finalrubric - - (locus?, %phrase.seq;) >
The <physDesc> element is used as a container element for a description of the various physical elements of a manuscript or manuscript part. The element is not designed to contain prose description directly, but is meant instead to "wrap" the various other elements within <physDesc>, each of which covers a different aspect of the physical characteristics of the manuscript.
The major elements which are subsidiary to <physDesc> are:
|<form>||contains a description of the physcial format of the manuscript item.|
|<support>||contains a description of material upon which writing is done.|
|<extent>||(standard TEI element)|
|<layout>||contains a description of ruling technique and layout.|
|<script>||contains description of script used.|
|<music>||contains description of type of musical notation.|
|<decoration>||contains a either a prose description of the decoration of a manuscript; or is a grouping device for one or more items contained by decoNote.|
|<binding>||contains description of binding, i.e. type of covering, boards, etc.|
|<collation>||contains a description of how the leaves or bifolia are arranged.|
|<paratext>||contains a description of items which aid the reader, such as foliation, pagination, column numbers, running heads, etc..|
Elements which are available within <collation> are:
|<formula>||(standard TEI element)|
The formal definition for the <physDesc> element and its constituents are as follows:
<!ELEMENT physDesc %om (form|support|extent|layout|script|music|decoration| binding|collation|paratext|correction)* <!ELEMENT form %om (%paraContent;) > <!ELEMENT support %om (%paraContent;) > <!ELEMENT layout %om (p+) > <!ATTLIST layout columns CDATA #IMPLIED lines CDATA #IMPLIED > <!ELEMENT script %om (handlist?, p+) > <!ELEMENT hand %om EMPTY > <!ATTLIST hand id ID #IMPLIED n CDATA #IMPLIED rend CDATA #IMPLIED hand CDATA #IMPLIED scribe CDATA #IMPLIED style CDATA #IMPLIED lang CDATA #IMPLIED ink CDATA #IMPLIED character CDATA #IMPLIED first CDATA #IMPLIED resp CDATA #IMPLIED TEIform CDATA 'hand' > <!ELEMENT music %om (p+) > <!ELEMENT decoration %om ((p|decoNote)+) > <!ELEMENT decoNote %om ((p)+) > <!ATTLIST decoNote type (miniature|initial|border|secondary|diagram|generic|unk|na) "na" subtype CDATA #IMPLIED size CDATA #IMPLIED technique CDATA #IMPLIED quality CDATA #IMPLIED figurative (yes|no|unstated) "unstated" > <!ELEMENT binding %om (p+)> <!ATTLIST binding date CDATA #IMPLIED contemporary (yes|no|unknown) unknown> <!ELEMENT collation %om ((p|formula|catchwords|signatures)+)> <!ELEMENT catchwords %om (p+) > <!ELEMENT signatures %om (p+) > <!ELEMENT paratext %om (p+) >
The following elements are used to record information about the history of a manuscript:
|<history>||groups elements describing the full history of a manuscript or manuscript part.|
|<origin>||contains any descriptive or other information concerning the origin of a manuscript or manuscript part.|
|<provenance>||contains any descriptive or other information concerning a single identifiable episode during the history of a manuscript or manuscript part, after its creation but before its acquisition.|
|<acquisition>||contains any descriptive or other information concerning the process by which a ms or ms part entered the holding institution.|
The three components of the <history> element all have the same substructure, consisting of one or more paragraphs marked as <p> elements. Each of these three elements is also a member of the datable attribute class, and thus also carries the following optional attributes:
|notBefore||specifies the earliest possible date for the information in the associated element|
|notAfter||specifies the latest possible date for the information in the associated element|
|certainty||specifies the degree of confidence associated with the dating specified by the other attributes|
|high||the dating is generally believed to be correct|
|medium||there is some doubt as to the reliability of the dating|
|low||the dating is controversial|
|evidence||specifies the kind of evidence for the dating supplied by the other attributes|
|internal||the dating is based on evidence internal to the ms )(e.g. an inscription)|
|external||the dating is based on evidence external to the ms (e.g. a reference to the ms in some other datable context)|
|conjecture||the dating is based on conjecture, as further discussed within the associated element.|
The history of a manuscript should normally be presented in the order implied by the above description. Information about the origins of the element (including any discussion of its sources) should be given as one or more paragraphs contained by a single <origin> element; any available information or discussion of distinct stages in the history of the manuscript before its arrival in its current location should be included as paragraphs within one or more <provenance> elements following this. Finally, any information specific to the means by which the manuscript was acquired by its present owners should be given as paragraphs within the <acquisition> element.
Here is a simple example of the use of this element:
<!-- to be supplied -->
The <history> element and its immediate component elements are formally defined as follows:
<!ELEMENT history - - (p+ | (origin?,provenance*,acquisition?)) > <!ELEMENT origin - - (p+) > <!ATTLIST origin %a.datable; > <!ELEMENT provenance - - (p+) > <!ATTLIST provenance %a.datable; > <!ELEMENT acquisition - - (p+) > <!ATTLIST acquisition %a.datable; >
Four categories of additional information are provided for by the scheme described here, grouped together within the <additional> element described in this section.
|<additional>||groups additional information relating to the modern bibliography for a manuscript, its current curatorial status, and and other associated materials.|
|<listBibl>||lists bibliographic descriptions of publications relating to the manuscript (standard TEI element)|
|<adminInfo>||groups administrative information relating to the present custody of the manuscript, and also to the record description itself.|
|<surrogates>||contains information about any digital or photographic representations of the manuscript being described which may exist in the holding institution or elsewhere.|
|<accMat>||contains details of any significant additional material which may be closely associated with the manuscript being described, such as non-contemporaneous documents or fragments bound in with the manuscript at some earlier historical periods. .|
None of the constituent elements of <additional> is required. If any is supplied, it may appear once only; furthermore, the order in which elements are supplied should be as specified above.
The <additional> element is formally defined as follows:
<!ELEMENT additional %om (listBibl?, adminInfo?, surrogates?, accMat?)>
A variety of information relating to the curation and management of a manuscript may be recorded as simple prose narrative tagged using the standard <p> element, optionally grouped within one or more of the following specialised elements:
|<recordHist>||provides information about the source and revision status of the parent manuscript description itself.|
|<custHist>||contains a description of a manuscript's custodial history, either as running prose or as a series of dated custodial events.|
|<availability>||describes any constraints or restrictions concerning access to the manuscript (standard TEI element)|
The <recordHist> element, if supplied, must contain a <source> element, followed by an optional series of <change> elements. The latter are standard TEI elements, which may also appear within the <revisionDesc> element of the standard TEI Header; their use here is intended to signal the similarity of function between the two container elements. Where the TEI Header should be used to document the revision history of the whole electronic file to which it is prefixed, the <recordHist> element may be used to document changes at a lower level, relating to the individual record.
The <source> element is used to document the primary source of information for the catalogue record containing it, in a similar way to the standard TEI <sourceDesc> element within a TEI Header. If the record is a new one, it may simply contain a <p> element as in the following example:
<source><p>No source: this is an original record</p></source>
More usually however the record will be derived from some previously existing catalogue, which may be specified using the standard TEI <bibl> element, as in the following example:
<source><p>Information transcribed from <bibl><title>IMEV</title><biblScope>1234</biblScope></bibl> </p></source>
If, as is likely, a full bibliographic description of the source from which cataloguing information was taken has already been given in the <listBibl> element within the current <additional> element, then it need not be repeated here. Instead, it should be referenced using the standard TEI <ref> element, as in the following example:
<additional> <listBibl> <bibl id="IMEV123"> <title>Index of Medieval Verse</title> <!-- other bibliographic details for IMEV here --> <biblScope>123</biblScope> </bibl> <!-- other bibliographic records relating to this ms here --> </listBibl> <recordHist> <source><p>Information transcribed from <ref target="IMEV123">IMEV 123</ref> </p></source> <!-- ... --> </recordHist>
The <custHist> record is used to describe the custodial history of a manuscript, recording any significant events noted during the period that it has been located within the cataloguing institution. It may contain either a series of paragraphs tagged with the standard TEI <p> element, or a series of paired <date> and <custEvent> elements, each describing a distinct incident or event, further specified by a type attribute.
|<date>||specifies the date of a custodial event (standard TEI element)|
|<custEvent>||describes a single event during the custodial history of a manuscript or manuscript .|
|type||specifies the type of event, for example conservation, photography, exhibition, etc.|
The <adminInfo> element and its immediate component elements are formally defined as follows:
<!ELEMENT adminInfo %om (p+ | (recordHist|availability|custodialHist)+)> <!ELEMENT recordHist %om (source, change*) > <!ELEMENT source %om (p+) > <!ELEMENT custHist %om (p+ | (date,custEvent)+) > <!ELEMENT custEvent %om (p+)> <!ATTLIST custEvent TYPE CDATA #IMPLIED >
The <surrogates> element is provided to enable cataloguers to provide information about any digital or photographic representations of the manuscript which may exist within the holding institution or elsewhere. Where such representations exist within published works, they will normally be documented within the <listBibl> element within the <additional> element. However, it is often also convenient to record information such as negative numbers, digital identifiers etc. for unpublished collections of manuscript images maintained within the holding institution, as well as to provide more detailed descriptive information about the surrogate itself,
At a later version, the content of the <surrogates> element is likely to be expanded to include elements more specifically intended to provide detailed information such as technical details of the process by which a digital or photographic image was made. At present, this and other information should be recorded simply as prose paragraphs, as in the following example:
<!-- to be supplied -->
The <surrogates> element is formally defined as follows:
<!ELEMENT surrogates - - (p+)>
The circumstance commonly arises where a manuscript has additional material, not originally part of the manuscript, which is bound with it or otherwise accompanying the manuscript. In the cases where this is clearly a distinct manuscript, the whole manuscript should be treated as a composite manuscript and the additional matter described in a separate <msPart> (see 1.9 below). However, there are cases where the additional matter is not self-evidently a distinct manuscript: it might be an important set of notes by a later scholar or owner, or it might be a file of correspondence relating to the manuscript. The <accMat> element is provided as a holder for this kind of information, as in the following example, describing a note by the Icelandic manuscript collector rni Magnsson which has been bound with the manuscript:
<accMat> <p>A slip in Árni Magnúe;sson's hand has been stuck to the pastedown on the inside front cover; the text reads:<q>Þidreks Søgu þessa hefi eg feiged af Sekreterer Wielandt Anno 171 5 i Kaupmanna høfn. Hun er, sem eg sie, Copia af Austfirda bókinni (Eidagás) en<expan>n</expan> ecki progenies Brædratungu bokarinnar. Og er þar fyrer eigi i allan<expan>n</expan> máta samhlioda þ<expan>eir</expan>re er Sr Jon Erlendz son hefer ritad fyrer Mag. Bryniolf. Þesse Þidreks Saga mun vera komin fra Sr Vigfuse á Helgafelle.</q></p> </accMat>
The formal definition for the <accMat> element is as follows:
<!ELEMENT accMat - - (p+)>
It is frequently the case that an item catalogued as if it were a single object is in fact a composite made up of several different and originally distinct manuscripts or manuscript fragments. Each such component should be recorded using a distinct <msPart> element, embedded within the <msDescription> element for the composite:
|<msPart>||contains information about an originally distinct manuscript or manuscript fragment now forming part of a composite manuscript.|
Each component of a composite manuscript may have its own content, physical description, history, etc. It may have been given a distinct manuscript identifier which it would be desirable to maintain. And finally, it is not impossible that a composite be made from previously-existing composites. For all these reasons, the <msPart> element used to record information about an individual constituent of a composite manuscript has an almost identical structure to that of a <msdescription> proper. The only differences are :
Here is a simple example of a composite manuscript, in which there are two discrete components:
<msDescription> <msIdentifier> <!-- identifying information for the whole manuscript --> </msIdentifier> <msSummary> <!-- short description of the whole manuscript --> </msSummary> <msPart> <physDesc> <!-- physical description of the first component part --> </physDesc> <msContent> <!-- intellectual content of first component part --> </msContent> </mspart> <msPart> <physDesc> <!-- physical description of the second component part --> </physDesc> <msContent> <!-- intellectual content of second component part --> </msContent> </mspart> </msDescription>
The <msPart> element is formally defined as follows:
<!ELEMENT - - (msIdentifier?, msContents?, physDesc?, history?, additional?, msPart*)>