- 1 ICCU’s full name is “Istituto centrale per il catalogo unico delle biblioteche italiane e per le in (...)
1The Activity Area for Manuscript Bibliography, Research and Census (Area di attività per la bibliografia, la documentazione e il censimento dei manoscritti) is a branch of the Central Institute of Cataloguing (ICCU) belonging to the Italian Ministry of Heritage and Culture.1 The goal of this office is to take the census and to catalogue manuscripts held by Italian institutions: medieval manuscripts, early modern and modern manuscripts, literary and private papers of the nineteenth and twentieth centuries, and original handwritten letters.
2The main achievements of this office are:
Manus OnLine, the Italian national catalogue of manuscripts,2 and
BibMan, the national bibliography of manuscripts.3
3Manus OnLine (MOL) is a project managing a relational database accessible through a web-based application. In 2007, this was the first national web-based application devoted to manuscript cataloguing. Italian librarians and researchers can produce manuscript descriptions and publish digital images through MOL using personal computers connected through the Internet to the ICCU main server. Within MOL, manuscript descriptions can be linked to images stored in any digital repository. Moreover, cataloguers share the same authority list of names (Marcuccio 2010; Bagnato, Barbero, and Menna 2009).
4Since all the manuscript descriptions are stored directly in the same central repository, as soon as a description is marked as “published” by the cataloguer, it becomes immediately accessible and searchable through the OPAC.
5At the time of writing (January 2014), MOL contains about 141,000 manuscript descriptions from 270 different libraries and 470 cataloguers are involved in the project. The catalogue will be continuously updated and extended. As the Italian manuscript collections preserve the majority of European manuscripts, MOL contains material of outstanding research importance for all periods and disciplines. Greek manuscripts are catalogued as well, for example those belonging to the Biblioteca Trivulziana of Milan, the Biblioteca Riccardiana in Florence, the Biblioteca Angelica, and the Biblioteca Nazionale Centrale (National Central Library) in Rome. Having been created and developed by the Ministry of Heritage and Culture, MOL is free: cataloguers need only a username and a password to begin their work.
6MOL and the TEI schema share a logical model which is typical of European scientific manuscript cataloguing practices (Petrucci 2001; Rehbein, Sahle, and Schassan 2009; Fischer, Fritze, and Vogeler 2010). Data considered in paleographical and codicological environments, and as a consequence in manuscript cataloguing, are
- the manuscript identifier;
- the physical description;
- the contents (texts);
- the bibliography; and
- names of people and corporations who have any responsibility for the manuscript curation and for texts, and names of places where manuscripts were written.
7In European manuscript cataloguing practice, the manuscript identifier—composed of the name of the place and library where the manuscript is preserved and by an official shelfmark—is necessary to define every single manuscript. This identifier is linked to a single physical description when the manuscript consists of one unit, or to multiple physical descriptions when the manuscript is composite. Each area devoted to the physical description is linked to one or more texts, because several texts can be copied in the same manuscript or part of a manuscript. Names can be linked both to the physical description (to represent, e.g., owners or copyists) and to texts (to represent, e.g., authors or translators). This traditional conceptual data model inspired the organization of data storage in the MOL database in which the identifier and the physical descriptions are considered as two separate entities while texts and names are considered different types of entities. The relationship between the identifier and the physical descriptions in MOL is one-to-n (one-to-many); the relationship between physical descriptions and texts is also one-to-n. The relationship between names (which populate the MOL authority file) and physical descriptions and between names and texts is n-to-n.
8The TEI schema has the same logical structure as MOL. In fact, following the TEI P5 Guidelines (TEI Consortium 2013: 10.2 The Manuscript Description Element), within an element <msDesc>
- the manuscript identifier is marked with <msIdentifier>, which is mandatory in any description;
- the physical description is marked with <physDesc>—optional;
- history is marked with <history>—optional;
- the contents (texts) are marked with <msContents>—optional;
- the bibliography is marked with <msBibl> within <additional>—optional; and
- names can be inserted at different levels within several other elements.
9Moreover, at deep levels the TEI schema contains an almost complete set of tags devoted to manuscript description and cataloguing (Barbero and Smaldone 2000; Burnard 2001; Milanese 2007). This is why on several occasions and with different aims the ICCU adopted the TEI schema to exchange data between different electronic repositories.
10In the past, between 2004 and 2007, when Manus was still a standalone application, the ICCU was able to export TEI XML files from local Manus databases, which were not accessible through the web, and import them into the online public catalogue (Barbero 2004). In 2003, Manus was adopted by the European project Rinascimento Virtuale,4 devoted to the digital publication of Greek palimpsests; on that occasion, the TEI schema was adopted to share manuscript descriptions of palimpsests among all the European partners (Magrini, Pasini, and Arduini 2005). Later, starting in 2007, the ICCU planned and performed harvesting between the CERL Portal, a meta search interface developed by the Consortium of European Research Libraries, and MOL: the ICCU exposes MOL contents on the web, providing OAI-PMH records with light TEI metadata inside, and CERL harvests them.5
11At present, the TEI schema is used in MOL with another very important aim. The ICCU wants to supply data to the institutions which produced them. In fact libraries and research organizations also need to use their own data outside MOL. For example, they need complete data to manage their own online public access catalogues (OPACs) or to populate their local digital libraries.6 Since institutions produce data on their own, they have the right to access all the data they produce; that is why the ICCU needs a suitably rich schema, not only a partial set of metadata. Bibliographical standards are not adequate for structuring manuscript descriptions in their entirety, because they have a quite different logical structure (Daines and Nimer 2012; Barbero 2013).
12In 2012, an export application was developed to export catalogues of manuscript collections from MOL as TEI XML files; moreover, users can download each description from the OPAC in TEI format:
Figure 1: The OPAC of Manus OnLine with the download button
13The aim of this paper is to discuss how the ICCU exports the contents of MOL fields into TEI elements to create valid XML files. An example of a TEI XML file exported from MOL is shown in appendix 1, while a complete list of MOL fields and the corresponding TEI elements follows in appendix 2.
- 7 Censimento Nazionale dei Manoscritti—Descrizione.
14According to TEI P5 Guidelines (TEI Consortium 2013: 2. The TEI Header), at the beginning of each XML file, a <teiHeader> is automatically produced, where a title (Catalogo di manoscritti), the name of the publisher (ICCU), the date of the creation of the XML file, and the name of the person or institution or project which is considered responsible for the intellectual content of the file are inserted. In the <body> of the TEI XML document, a <listBibl> element is nested, in which each manuscript description is encoded within an <msDesc> element. For each <msDesc> an @xml:id attribute is create, whose value corresponds to the CNMD,7 the unique code number identifying each description published by the Italian National Census of Manuscripts.
15The first-child-level elements of <msDesc> defined by the TEI schema, <msIdentifier>, <msContents>, <physDesc>, <history>, and <additional>, appear whenever the MOL database contains the corresponding information. If a manuscript is defined as composite and its parts are described separately in MOL, then the TEI XML document contains as many <msPart> elements as there are codicological sections.
16Within these elements, many other TEI elements are used to create a deeply structured XML manuscript description. In several cases, during the design of the export application, it was clear which TEI elements had to be used in encoding MOL original information. For example, there is no doubt that the name of the library holding a manuscript must be encoded through a <repository> element within <msIdentifier>; the field containing the history of the manuscript, which can be very long in MOL, can be encoded in a <summary> element within the element <history>; the author’s name is inserted in the <author> tag within an <msItem>.
17Several specific highly formalized data have also been encoded as TEI attribute values. For example, the international code identifying libraries, composed of two letters representing a city and four numbers, is encoded as the value of the canonical @key attribute within <institution>, because this code can associate each library with the records of the national database Anagrafe delle biblioteche italiane:8
<institution key="LO0020">Biblioteca comunale Laudense</institution>
18The code identifying a single record inside the MOL authority file of names (composed of CNMN and a number) is encoded as the value of the @key attribute within <name>:
<name key="CNMN0000014152">Alighieri, Dante</name>
19The global @n attribute has been used in <msPart> and <msItem> to encode the numbers of the codicological units and of the texts. These are numbers which are automatically recorded in MOL to order codicological parts and texts in the same sequence as they appear within the original codex:
<title type="elaborato">Divina Commedia. Inferno</title>
<title type="elaborato">Divina Commedia. Purgatorio</title>
<title type="elaborato">Divina Commedia. Paradiso</title>
20The @type attribute has been used on <title>, and four values have been defined to express whether the title is “attested” in the manuscript by the copyist, “added” by a hand different from the main copyist’s hand, “elaborated” by the cataloguer, or “identified” as a published work:
<title type="elaborato">Divina Commedia. Paradiso</title>
<title type="presente"> Seguita la terça Comedia di Dante chiamata Paradiso et capitolo primo</title>
21The @type attribute is also used on <incipit> and <explicit> to distinguish which part of the text begins or ends with those words: the dedication letter, the preface, the first poem of an anthology, the main text, and any other significant part of the text. The ICCU also uses the @defective attribute on the elements <incipit> and <explicit> to specify whether incipit or explicit belongs to an acephal text or if the text is lacking its end:
<incipit type="prefazione" defective="false"> Apuleius Plato ad cives suos Ex pluribus paucas vires herbarum</incipit>
<incipit type="primoTesto" defective="false"> Herba nomine plantago a Graecis dicitur</incipit>
22In some other cases, the XML encoding of information stored in MOL needs to be discussed, because different solutions can be adopted in the export process to create valid TEI documents. Astonishingly, this is the case in the encoding of three types of codicological data which are very common in manuscript descriptions: material, number of folios, and dimensions of the manuscripts.
23In fact there is no consensus on the values of the @material attribute that can be used in the element <supportDesc>. Even if papyrus, parchment, and paper can absolutely be considered the most common materials, together with mixed material manuscript, different solutions have been chosen to express these data through the @material attribute. The TEI P5 Guidelines (Appendix C) suggests "paper", "parch", and "mixed" as values of this attribute, but ultimately the ICCU decided to follow the important European cataloguing projects Manuscriptorium9 and e-Codices10 in using "chart" (paper), "perg", (parchment) and "mixed".
24In describing the number of folios, cataloguers usually need to encode the quantity of guard leaves bound at the beginning of the volume, of folios which constitute the volume proper, and of guard leaves at the end of the volume. These are three simple numbers, but TEI P5 Guidelines (10.7.1.2 Extent) proposes different solutions and different projects have adopted different encoding methods which, of course, will not help them in sharing data.
25The project Manuscriptorium, which describes itself as a “European digital library of written cultural heritage,” uses arabic numerals directly within the <extent> element; if the codex has guard leaves, their number is distinguished through a + (plus sign): <extent>2+30+2</extent>. As all three numerals (separated by plus signs) are expressed only if a manuscript has guard-leaves at both the beginning and the end, and sometimes manuscripts have guard-leaves only at the beginning or only at the end, an automatic procedure cannot distinguish the semantic value of numerals expressed.
26e-Codices, the virtual manuscript library of Switzerland, encodes the quantity of folios through non-structured information within a <measure> element contained in the element <extent>; at the same time a structured version of the same information is given as value of the @n attribute: <extent><measure type="leavesCount" n="114 + 3">114 Bll. + 2 Vor- und 1 Nachsatzbl.</measure></extent>. As @n is a global attribute which should number the element, not express any number contained within the element, probably this solution is not to be recommended.
27As the ICCU needs to preserve the structure of the MOL data model as far as possible, and also the semantic distinction among initial and final guard leaves, in the export process the following solution has been adopted:
<measure type="Guardieiniziali" unit="carte">2</measure>
<measure type="Corpo" unit="carte">30</measure>
<measure type="Guardiefinali" unit="carte">2</measure>
28As with material and number of folios, the size of leaves can also be marked with different elements following the TEI P5 Guidelines (10.7.1.2 Extent): with the elements <dimensions>, <height>, and <width>, or with the element <measure>. Manuscriptorium adopts the first solution:
<height>21 cm</height><width>15 cm</width>
while e-Codices uses an empty <measure> element and, again, an @n attribute: <measure type="pageDimensions" n="24.0 x 17.5 cm / 23.3 x 16.5 cm / 24 x 18 cm"/>. As in MOL, several measurements can be recorded and each of them must be related to a folio number from which size was assessed; in the export application the following solution has been adopted:
<measure n="1" type="height" unit="mm">234</measure> x
<measure n="2" type="width" unit="mm">123</measure>
29Other problems to be discussed are due to MOL contents and data structure. First, each cataloguing area, for example those devoted to material, date, number of folios, and many others, contains a generic field called “Note,” where cataloguers can register annotations in prose about that area. The ICCU decided not to encode all the MOL “Note” fields in XML with the same <note> element, without introducing any distinction, and tried to distinguish the original MOL field represented in each <note> element. For this reason each <note> uses the @n attribute to number the element and the @type attribute to encode the subject of the original “Note” field. For example, annotations about the first area of MOL, devoted to the identification of the manuscript, are marked as <note n="1" type="sez01">, while annotations about the second area, devoted to the form of the manuscript, are marked as <note n="2" type="sez02">.
- 11 According to the TEI schema, pricking and ruling can be encoded in <layout> together with other inf (...)
- 12 According to the TEI schema, lines and columns can be described through numbers (data.count) using (...)
30The <note> element with @n and @type attributes is also used to encode those contents which have an appropriate field in MOL but do not have an appropriate tag in the TEI schema. For example, in MOL there is a specific area devoted to the description of palimpsest folios, which is not considered in the TEI P5 Guidelines; in the TEI XML document, this information is encoded through a <note> element with "palimpsest" as the value of @type: <note n="3" type="palinsesto">. A similar solution has been adopted by the ICCU to encode data about many other subjects: description of missing folios (<note n="9" type="mancanze">), fragments of manuscripts (<note n="10" type="frammenti">), folios derived from printed books (<note n="11" type="partistampa">), pricking (<note n="14" type="foratura">), ruling (<note n="15" type="rigatura">),11 ruled frame (<note n="16" type="specchiorigato">), lines (<note n="17" type="righe">), columns (<note n="18" type="disposizionetesto">),12 and ink (<note n="20" type="inchiostro">). However, even if these data can be encoded in a TEI XML document by creating specific combinations of a generic <note> element with specific attribute values, at least for the data that are commonly recorded in manuscript cataloguing practice (for example pricking, ruling, and ink), the ICCU would recommend the introduction in the TEI schema of new specific elements.
31Other codicological data pertaining to manuscript decoration, music notation, and binding, which are analytically recorded in several MOL fields and are expressed through a specialized lexicon, are exported in TEI XML files within a generic <term> element. As with our use of the <note> element, this encoding also uses @n and @type attributes to mark data derived from different MOL fields and to express in this way the specific semantic area of each <term>. For example, a cataloguer can point out the presence of neumes in a manuscript by putting a flag (yes in the database) in the MOL field “Neumatic notation”; such information is exported in the TEI XML document as <term n="4" type="notazione">neumatica</term>. The presence of clasps can be recorded by putting a flag in the MOL field “Clasps,” which causes an element <term n="14">fermagli</term> to be created in the TEI XML document.
32The Italian standard for manuscripts adopted by MOL also includes original letters. The information about original letters in MOL consists of the following fields related to the physical description:
- type of letter (letter, postcard, picture postcard, business card…),
- presence of envelope,
- presence of typescript part,
- presence of a printed letterhead,
- presence of original signature,
- presence of manuscript notes.
33Such data should be encoded in a <physDesc>, but at present, there are no TEI elements which could be used for this purpose.
34The information about the text of original letters recorded in MOL consists of
- name of sender,
- name of addressee,
- stage of the text (draft, original, copy),
35Such data should be encoded through an <msItem> within <msContents>. The number of folios can be marked with <locus>; the sender can be encoded as an <author> and the addressee as a name with a specific <respStmt>; but at present the ICCU does not know which elements could be used for other fields. Close collaboration among different projects and the TEI Consortium would be essential in order to develop an encoding system for original letters compatible with TEI <msDesc> encoding; for example a new set of tags to be used in the header of correspondence editions could be studied in collaboration by the TEI Manuscripts SIG13 and the TEI Correspondence SIG.14
36Discussing the solutions found by the ICCU with the TEI Consortium could help not only to verify the encoding developed by the ICCU, but also to spread the use of this standard to meet the needs of European manuscript cataloguing.