Serveur d'exploration sur la TEI

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

Encoded archival description EAD conversion a methodological proposal

Identifieur interne : 000379 ( Istex/Corpus ); précédent : 000378; suivant : 000380

Encoded archival description EAD conversion a methodological proposal

Auteurs : Eduardo Peis ; Flix De Moya ; J. Carlos Fernndezmolina

Source :

RBID : ISTEX:0812C84ADDFA7954CAC853D5E947F16DEB386E4C

Abstract

The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language SGML, document type definition DTD for archival description known as encoded archival description EAD is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.

Url:
DOI: 10.1108/07378830010360455

Links to Exploration step

ISTEX:0812C84ADDFA7954CAC853D5E947F16DEB386E4C

Le document en format XML

<record>
<TEI wicri:istexFullTextTei="biblStruct">
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">Encoded archival description EAD conversion a methodological proposal</title>
<author>
<name sortKey="Peis, Eduardo" sort="Peis, Eduardo" uniqKey="Peis E" first="Eduardo" last="Peis">Eduardo Peis</name>
<affiliation>
<mods:affiliation>Eduardo Peis is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="De Moya, Flix" sort="De Moya, Flix" uniqKey="De Moya F" first="Flix" last="De Moya">Flix De Moya</name>
<affiliation>
<mods:affiliation>Flix de Moya is Dean, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Carlos Fernndezmolina, J" sort="Carlos Fernndezmolina, J" uniqKey="Carlos Fernndezmolina J" first="J." last="Carlos Fernndezmolina">J. Carlos Fernndezmolina</name>
<affiliation>
<mods:affiliation>J. Carlos FernndezMolina is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</mods:affiliation>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:0812C84ADDFA7954CAC853D5E947F16DEB386E4C</idno>
<date when="2000" year="2000">2000</date>
<idno type="doi">10.1108/07378830010360455</idno>
<idno type="url">https://api.istex.fr/document/0812C84ADDFA7954CAC853D5E947F16DEB386E4C/fulltext/pdf</idno>
<idno type="wicri:Area/Istex/Corpus">000379</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title level="a" type="main" xml:lang="en">Encoded archival description EAD conversion a methodological proposal</title>
<author>
<name sortKey="Peis, Eduardo" sort="Peis, Eduardo" uniqKey="Peis E" first="Eduardo" last="Peis">Eduardo Peis</name>
<affiliation>
<mods:affiliation>Eduardo Peis is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="De Moya, Flix" sort="De Moya, Flix" uniqKey="De Moya F" first="Flix" last="De Moya">Flix De Moya</name>
<affiliation>
<mods:affiliation>Flix de Moya is Dean, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Carlos Fernndezmolina, J" sort="Carlos Fernndezmolina, J" uniqKey="Carlos Fernndezmolina J" first="J." last="Carlos Fernndezmolina">J. Carlos Fernndezmolina</name>
<affiliation>
<mods:affiliation>J. Carlos FernndezMolina is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</mods:affiliation>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series>
<title level="j">Library Hi Tech</title>
<idno type="ISSN">0737-8831</idno>
<imprint>
<publisher>MCB UP Ltd</publisher>
<date type="published" when="2000-12-01">2000-12-01</date>
<biblScope unit="volume">18</biblScope>
<biblScope unit="issue">4</biblScope>
<biblScope unit="page" from="360">360</biblScope>
<biblScope unit="page" to="368">368</biblScope>
</imprint>
<idno type="ISSN">0737-8831</idno>
</series>
<idno type="istex">0812C84ADDFA7954CAC853D5E947F16DEB386E4C</idno>
<idno type="DOI">10.1108/07378830010360455</idno>
<idno type="filenameID">2380180405</idno>
<idno type="original-pdf">2380180405.pdf</idno>
<idno type="href">07378830010360455.pdf</idno>
</biblStruct>
</sourceDesc>
<seriesStmt>
<idno type="ISSN">0737-8831</idno>
</seriesStmt>
</fileDesc>
<profileDesc>
<textClass></textClass>
<langUsage>
<language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language SGML, document type definition DTD for archival description known as encoded archival description EAD is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.</div>
</front>
</TEI>
<istex>
<corpusName>emerald</corpusName>
<author>
<json:item>
<name>Eduardo Peis</name>
<affiliations>
<json:string>Eduardo Peis is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</json:string>
</affiliations>
</json:item>
<json:item>
<name>Flix de Moya</name>
<affiliations>
<json:string>Flix de Moya is Dean, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</json:string>
</affiliations>
</json:item>
<json:item>
<name>J. Carlos FernndezMolina</name>
<affiliations>
<json:string>J. Carlos FernndezMolina is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</json:string>
</affiliations>
</json:item>
</author>
<subject>
<json:item>
<lang>
<json:string>eng</json:string>
</lang>
<value>Archives</value>
</json:item>
<json:item>
<lang>
<json:string>eng</json:string>
</lang>
<value>Standard Generalized Markup Language</value>
</json:item>
<json:item>
<lang>
<json:string>eng</json:string>
</lang>
<value>Spain</value>
</json:item>
</subject>
<language>
<json:string>eng</json:string>
</language>
<originalGenre>
<json:string>e-technical-paper</json:string>
</originalGenre>
<abstract>The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language SGML, document type definition DTD for archival description known as encoded archival description EAD is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.</abstract>
<qualityIndicators>
<score>4.646</score>
<pdfVersion>1.3</pdfVersion>
<pdfPageSize>610 x 789 pts</pdfPageSize>
<refBibsNative>true</refBibsNative>
<keywordCount>3</keywordCount>
<abstractCharCount>579</abstractCharCount>
<pdfWordCount>3650</pdfWordCount>
<pdfCharCount>24647</pdfCharCount>
<pdfPageCount>9</pdfPageCount>
<abstractWordCount>83</abstractWordCount>
</qualityIndicators>
<title>Encoded archival description EAD conversion a methodological proposal</title>
<genre>
<json:string>other</json:string>
</genre>
<host>
<volume>18</volume>
<publisherId>
<json:string>lht</json:string>
</publisherId>
<pages>
<last>368</last>
<first>360</first>
</pages>
<issn>
<json:string>0737-8831</json:string>
</issn>
<issue>4</issue>
<subject>
<json:item>
<value>Information & knowledge management</value>
</json:item>
<json:item>
<value>Information & communications technology</value>
</json:item>
<json:item>
<value>Internet</value>
</json:item>
<json:item>
<value>Library & information science</value>
</json:item>
<json:item>
<value>Information behaviour & retrieval</value>
</json:item>
<json:item>
<value>Librarianship/library management</value>
</json:item>
<json:item>
<value>Information user studies</value>
</json:item>
<json:item>
<value>Metadata</value>
</json:item>
<json:item>
<value>Library technology</value>
</json:item>
</subject>
<genre>
<json:string>journal</json:string>
</genre>
<language>
<json:string>unknown</json:string>
</language>
<title>Library Hi Tech</title>
<doi>
<json:string>10.1108/lht</json:string>
</doi>
</host>
<publicationDate>2000</publicationDate>
<copyrightDate>2000</copyrightDate>
<doi>
<json:string>10.1108/07378830010360455</json:string>
</doi>
<id>0812C84ADDFA7954CAC853D5E947F16DEB386E4C</id>
<score>0.14281934</score>
<fulltext>
<json:item>
<original>true</original>
<mimetype>application/pdf</mimetype>
<extension>pdf</extension>
<uri>https://api.istex.fr/document/0812C84ADDFA7954CAC853D5E947F16DEB386E4C/fulltext/pdf</uri>
</json:item>
<json:item>
<original>false</original>
<mimetype>application/zip</mimetype>
<extension>zip</extension>
<uri>https://api.istex.fr/document/0812C84ADDFA7954CAC853D5E947F16DEB386E4C/fulltext/zip</uri>
</json:item>
<istex:fulltextTEI uri="https://api.istex.fr/document/0812C84ADDFA7954CAC853D5E947F16DEB386E4C/fulltext/tei">
<teiHeader>
<fileDesc>
<titleStmt>
<title level="a" type="main" xml:lang="en">Encoded archival description EAD conversion a methodological proposal</title>
</titleStmt>
<publicationStmt>
<authority>ISTEX</authority>
<publisher>MCB UP Ltd</publisher>
<availability>
<p>EMERALD</p>
</availability>
<date>2000</date>
</publicationStmt>
<sourceDesc>
<biblStruct type="inbook">
<analytic>
<title level="a" type="main" xml:lang="en">Encoded archival description EAD conversion a methodological proposal</title>
<author>
<persName>
<forename type="first">Eduardo</forename>
<surname>Peis</surname>
</persName>
<affiliation>Eduardo Peis is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</affiliation>
</author>
<author>
<persName>
<forename type="first">Flix</forename>
<surname>de Moya</surname>
</persName>
<affiliation>Flix de Moya is Dean, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</affiliation>
</author>
<author>
<persName>
<forename type="first">J.</forename>
<surname>Carlos FernndezMolina</surname>
</persName>
<affiliation>J. Carlos FernndezMolina is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</affiliation>
</author>
</analytic>
<monogr>
<title level="j">Library Hi Tech</title>
<idno type="pISSN">0737-8831</idno>
<idno type="DOI">10.1108/lht</idno>
<imprint>
<publisher>MCB UP Ltd</publisher>
<date type="published" when="2000-12-01"></date>
<biblScope unit="volume">18</biblScope>
<biblScope unit="issue">4</biblScope>
<biblScope unit="page" from="360">360</biblScope>
<biblScope unit="page" to="368">368</biblScope>
</imprint>
</monogr>
<idno type="istex">0812C84ADDFA7954CAC853D5E947F16DEB386E4C</idno>
<idno type="DOI">10.1108/07378830010360455</idno>
<idno type="filenameID">2380180405</idno>
<idno type="original-pdf">2380180405.pdf</idno>
<idno type="href">07378830010360455.pdf</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<creation>
<date>2000</date>
</creation>
<langUsage>
<language ident="en">en</language>
</langUsage>
<abstract xml:lang="en">
<p>The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language SGML, document type definition DTD for archival description known as encoded archival description EAD is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.</p>
</abstract>
<textClass>
<keywords scheme="keyword">
<list>
<head>Keywords</head>
<item>
<term>Archives</term>
</item>
<item>
<term>Standard Generalized Markup Language</term>
</item>
<item>
<term>Spain</term>
</item>
</list>
</keywords>
</textClass>
<textClass>
<keywords scheme="Emerald Subject Group">
<list>
<label>cat-IKM</label>
<item>
<term>Information & knowledge management</term>
</item>
<label>cat-ICT</label>
<item>
<term>Information & communications technology</term>
</item>
<label>cat-INT</label>
<item>
<term>Internet</term>
</item>
</list>
</keywords>
</textClass>
<textClass>
<keywords scheme="Emerald Subject Group">
<list>
<label>cat-LISC</label>
<item>
<term>Library & information science</term>
</item>
<label>cat-IBRT</label>
<item>
<term>Information behaviour & retrieval</term>
</item>
<label>cat-LLM</label>
<item>
<term>Librarianship/library management</term>
</item>
<label>cat-IUS</label>
<item>
<term>Information user studies</term>
</item>
<label>cat-MTD</label>
<item>
<term>Metadata</term>
</item>
<label>cat-LTC</label>
<item>
<term>Library technology</term>
</item>
</list>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change when="2000-12-01">Published</change>
</revisionDesc>
</teiHeader>
</istex:fulltextTEI>
<json:item>
<original>false</original>
<mimetype>text/plain</mimetype>
<extension>txt</extension>
<uri>https://api.istex.fr/document/0812C84ADDFA7954CAC853D5E947F16DEB386E4C/fulltext/txt</uri>
</json:item>
</fulltext>
<metadata>
<istex:metadataXml wicri:clean="corpus emerald not found" wicri:toSee="no header">
<istex:xmlDeclaration>version="1.0" encoding="UTF-8"</istex:xmlDeclaration>
<istex:document><!-- Auto generated NISO JATS XML created by Atypon out of MCB DTD source files. Do Not Edit! -->
<article dtd-version="1.0" xml:lang="en" article-type="e-technical-paper">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">lht</journal-id>
<journal-id journal-id-type="doi">10.1108/lht</journal-id>
<journal-title-group>
<journal-title>Library Hi Tech</journal-title>
</journal-title-group>
<issn pub-type="ppub">0737-8831</issn>
<publisher>
<publisher-name>MCB UP Ltd</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.1108/07378830010360455</article-id>
<article-id pub-id-type="original-pdf">2380180405.pdf</article-id>
<article-id pub-id-type="filename">2380180405</article-id>
<article-categories>
<subj-group subj-group-type="type-of-publication">
<compound-subject>
<compound-subject-part content-type="code">e-technical-paper</compound-subject-part>
<compound-subject-part content-type="label">Technical paper</compound-subject-part>
</compound-subject>
</subj-group>
<subj-group subj-group-type="subject">
<compound-subject>
<compound-subject-part content-type="code">cat-IKM</compound-subject-part>
<compound-subject-part content-type="label">Information & knowledge management</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-ICT</compound-subject-part>
<compound-subject-part content-type="label">Information & communications technology</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-INT</compound-subject-part>
<compound-subject-part content-type="label">Internet</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="subject">
<compound-subject>
<compound-subject-part content-type="code">cat-LISC</compound-subject-part>
<compound-subject-part content-type="label">Library & information science</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-IBRT</compound-subject-part>
<compound-subject-part content-type="label">Information behaviour & retrieval</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-IUS</compound-subject-part>
<compound-subject-part content-type="label">Information user studies</compound-subject-part>
</compound-subject>
<compound-subject>
<compound-subject-part content-type="code">cat-MTD</compound-subject-part>
<compound-subject-part content-type="label">Metadata</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-LLM</compound-subject-part>
<compound-subject-part content-type="label">Librarianship/library management</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-LTC</compound-subject-part>
<compound-subject-part content-type="label">Library technology</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Encoded archival description (EAD) conversion: a methodological proposal</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<string-name>
<given-names>Eduardo</given-names>
<surname>Peis</surname>
</string-name>
<aff>Eduardo Peis is Professor, at the Facultad de Biblioteconomía y Documentación, Universidad de Granada, Granada, Spain.</aff>
</contrib>
<contrib contrib-type="author">
<string-name>
<given-names>Félix</given-names>
<surname>de Moya</surname>
</string-name>
<aff>Félix de Moya is Dean, at the Facultad de Biblioteconomía y Documentación, Universidad de Granada, Granada, Spain.</aff>
</contrib>
<contrib contrib-type="author">
<string-name>
<given-names>J.</given-names>
<surname>Carlos Fernández‐Molina</surname>
</string-name>
<aff>J. Carlos Fernández‐Molina is Professor, at the Facultad de Biblioteconomía y Documentación, Universidad de Granada, Granada, Spain. </aff>
</contrib>
</contrib-group>
<pub-date pub-type="ppub">
<day>01</day>
<month>12</month>
<year>2000</year>
</pub-date>
<volume>18</volume>
<issue>4</issue>
<fpage>360</fpage>
<lpage>368</lpage>
<permissions>
<copyright-statement>© MCB UP Limited</copyright-statement>
<copyright-year>2000</copyright-year>
<license license-type="publisher">
<license-p></license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="07378830010360455.pdf"></self-uri>
<abstract>
<p>The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language (SGML), document type definition (DTD) for archival description known as encoded archival description (EAD) is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version. </p>
</abstract>
<kwd-group>
<kwd>Archives</kwd>
<x>, </x>
<kwd>Standard Generalized Mark‐up Language</kwd>
<x>, </x>
<kwd>Spain</kwd>
</kwd-group>
<custom-meta-group>
<custom-meta>
<meta-name>peer-reviewed</meta-name>
<meta-value>no</meta-value>
</custom-meta>
<custom-meta>
<meta-name>academic-content</meta-name>
<meta-value>yes</meta-value>
</custom-meta>
<custom-meta>
<meta-name>rightslink</meta-name>
<meta-value>included</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec>
<title>Introduction</title>
<p>Informational services should be re‐examined regularly to make sure that all types of materials and electronic formats are used, and that integrated access to informational sources – even external ones – can be offered. It is not a matter of starting from square one, as Croft (1995) would say, when referring to the current lines of research in information retrieval (IR), but rather of reorienting efforts.</p>
<p>This need to adapt is even more crucial in the case of archives, because of their special characteristics, and the scarcity of standards, economic resources and administrative resources.</p>
<p>If archives adjusted to the new technological possibilities, they might be exemplary in making efficient use of resources and increasing the degree of use of the information. One key step on this road to adaptation is the design of structured finding aids that would facilitate Web diffusion of archival information, as well as the re‐utilization of this material in the form of varied information objects.</p>
<p>The special features of archival material make it necessary to develop such systems with consideration of the following aims, to: </p>
<list list-type="bullet">
<list-item>
<label></label>
<p>present in an extensive and interrelated sense, the descriptive information normally contained in finding aids;</p>
</list-item>
<list-item>
<label></label>
<p>preserve the hierarchical relations that exist among the levels of description;</p>
</list-item>
<list-item>
<label></label>
<p>represent the descriptive information that is “inherited” from one level to another;</p>
</list-item>
<list-item>
<label></label>
<p>“browse” through a hierarchical information architecture; and</p>
</list-item>
<list-item>
<label></label>
<p>index and retrieve specific elements[1].</p>
</list-item>
</list>
<p>These needs can be satisfied by creating a digital version of the finding aids, and encoding the structured descriptive information with a mark‐up language that conforms to international standards.</p>
<p>Library systems are beginning to use Standard Generalized Markup Language (SGML) for importing/exporting information in an electronic format, and for creating databases that allow the inclusion of information in multiple formats (Corthouts and Philips, 1996). SGML allows the logical structure of electronic documents to be represented explicitly and rigorously, in an unequivocal and independent form that is internationally recognized, regardless of applications and systems (International Organization for Standardization, 1986).</p>
<p>By means of marks, SGML describes the structural components of an electronic document, identifying each part according to its purpose in the given text or context[2]. Because SGML is a means to describe a language formally, it is known as a meta‐language.</p>
<p>The structured information is “analyzed” in the sense that it is divided into component parts, which in turn have components, and so on. If the components can be identified, then they can be processed as well. At present SGML is, for many reasons, the best option for conceptually codifying a document’s structural units in the broadest sense. First, it is a generalized public standard, independent of manufacturers and distributors, which ensures its permanence. Second, it does not impose a fixed set of components: the structures can be defined by the user, under the concept of “document type”. Therefore, it is remarkably flexible and consistent, adapting to whatever alphabetical system may have been used to write the text. Finally, it breaks down the structure of the presentation, as it is a descriptive rather than procedural codification. For these reasons, more and more applications are using SGML as a basic tool[3].</p>
<p>It is easy to understand why the first attempt to apply a standardized code to instruments of archival description – initiated by the University of California at Berkeley and directed by Daniel Pitti – selected SGML as the ideal technique for carrying out such a codification.</p>
<p>This project designed a document type definition (DTD) to describe a class of documents which consists of an optional title page, the description of a unit of archival material, and appendixes, which are also optional. The title page could include varied elements such as the identification of the repository, or the type of descriptive tool. The descriptive component, in agreement with the DTD, would offer a brief description of the unit (using markable elements analogous to those employed in a MARC cataloging record), a broader narrative description of the unit plus any of its separate parts (including markable elements such as title, dates, scope and contents) and a formatted list of the parts that contain that unit (Gilliland‐Swetland, 1996).</p>
<p>We can no longer conceive an “up‐to‐date” informational service without taking into account the World Wide Web. HTML (or its foreseeable variations) is not adequate for extracting many of the hypertext or hypermedia possibilities of the Web. With SGML these possibilities are greatly increased, but precisely for this reason, their Web implementation is costly to say the very least (and may be simply impossible). Because of this, a set of subsidiary standards is being developed under the auspices of the W3C: Extensible Markup Language, or XML[4]. It has “complementary” specifications in the form of Extensible Style Language (XSL) and Xlink (XML linking language) to enhance SGML potential while allowing the distribution of informational products over the Web. </p>
<p>The current EAD model (version 1.0) offers the option of using XML. It is possible to activate/de‐activate the variant sections SGML/XML option using the SGML feature called “marked sections”.</p>
<p>Despite the apparent advantages of applying this model, many archival systems can run into formidable difficulties in converting the finding aids from paper to digital form, because of having to adjust the information components of these tools to an EAD structural mode. The most obvious solution would be to key in all the data again, following the DTD EAD, but this may not be feasible in view of the – usually – enormous volume of such finding aids. The objective of our study was to confirm the viability of conversion through the development of a pilot
<italic>ad hoc</italic>
system, and to show that the process can confer an added value.</p>
<p>SGML conversion normally implies the construction of a bridge between the world of the printed document or word processor (in which the logical structure is visually perceived by the reader) and the “intelligent” document (in which the logical structure is explicitly codified). In effect, SGML encodes the logical structure; yet in most documents this structure is expressed visually, not by means of well defined marks. When converting to SGML, the implicit structure must be made explicit (Severson, 1995).</p>
<p>Therefore, in general terms, our proposal consists of an analysis of the SGML model to which conversion is intended, focusing on the DTD EAD and the documents that are going to be converted (finding aids). This approach allows the process to be arranged as a production line. As we shall see, nearly all this line can be automated with an appropriate strategy and proper software tools.</p>
</sec>
<sec>
<title>Methodology</title>
<p>If we bear in mind the variety of situations involving archival informational services, the advantages of designing a modular method become apparent. Our approach involves three separate stages:</p>
<list list-type="order">
<list-item>
<label>1. </label>
<p>(1) previous analysis;</p>
</list-item>
<list-item>
<label>2. </label>
<p>(2) capture/conversion; and</p>
</list-item>
<list-item>
<label>3. </label>
<p>(3) translation/organization.</p>
</list-item>
</list>
<p>The first methodological stage may be the most important one. The initial analysis must contemplate both the DTD EAD and the descriptive instrument
<italic>per se</italic>
. The purpose of these preliminary analyses is threefold, to: </p>
<list list-type="order">
<list-item>
<label>1. </label>
<p>(1) corroborate the adequacy of the SGML model to the descriptive instrument that is to be labeled;</p>
</list-item>
<list-item>
<label>2. </label>
<p>(2) study the possible structural correspondence to find those informational elements that are not presented in the “traditional” finding aid model and will have to be added “manually”; and </p>
</list-item>
<list-item>
<label>3. </label>
<p>(3) discover the physical and logical characteristics of the format of the “source” document that will automatically allow SGML labeling. </p>
</list-item>
</list>
<p>These initial assessments will also enable us to make important methodological decisions with respect to the possibilities of application of the model, such as the type of description (in depth, analytical or combined) that best reflects the scope of the information to be converted.</p>
<p>We must be familiar with EAD to be certain that it works for the task at hand. The DTD EAD (Pitti, 1999) was designed to reflect the inherent hierarchy of the collections, in conjunction with the intellectual organization that archivists impose with their descriptive practices. Archival description is regulated by the International Standard Archival Description‐General (ISAD‐G). The ISAD‐G (International Council on Archives, 1994), developed by the International Council on Archives, can be considered the semantic and syntactic intellectual foundation of archival description. EAD, then, would be the standardized communication format, the formal part of that intellectual structure. From this standpoint, EAD is based on ISAD‐G.</p>
<p>The EAD model contains two types of elements: </p>
<list list-type="order">
<list-item>
<label>1. </label>
<p>(1) those that encode specific points in the description of component parts of either the finding aids or the original materials (i.e. the descriptive elements); and </p>
</list-item>
<list-item>
<label>2. </label>
<p>(2) those that could encode any characteristic of the document (i.e. the generic elements).</p>
</list-item>
</list>
<p>The latter are, however, generally included among the descriptive elements.</p>
<p>EAD uses the term “finding aid” to refer to any hierarchical tool that has been codified using EAD, and that allows either the record‐creator or the user to access the materials that are being described.</p>
<p>At a very basic level, a finding aid that is codified using EAD will have three segments:</p>
<list list-type="order">
<list-item>
<label>1. </label>
<p>(1) one that provides information about the finding aid itself, such as its title, the name of its compiler, and date of compilation ();</p>
</list-item>
<list-item>
<label>2. </label>
<p>(2) a second component that includes the preliminary matters necessary for the formal publication of the description (); and</p>
</list-item>
<list-item>
<label>3. </label>
<p>(3) a third that provides the description of the archival material itself, in addition to related contextual and administrative information ().</p>
</list-item>
</list>
<p>The , which is based on the “header” element of the SGML Text Encoding Initiative (TEI) model[5], uses four sub‐elements – , , and – to capture or contain most of the information that is normally recorded about the creation, publication and use of a “finding aid document”. Additional information about this document that does not fit the TEI model can be included in the element, which in turn includes the and
elements and reflects details of an introductory sort (e.g. preface or introduction) that are needed for the formal publication of the finding aid.</p>
<p>In the element, two types of information may be presented under two main sub‐elements. The (“archival description”) element, which can be considered as the fundamental component of EAD, presents hierarchically organized information that describes a unit of records (or papers) together with their component parts (or divisions). In addition, has several “high level” descriptive categories that serve as “containers” for more specific descriptive components.</p>
<p>The most important of the high level elements is , or descriptive identification, which will contain those elements needed to identify the title, creator, date of creation, and volume. The element “additional descriptive data”, or , contains supplementary, optional information that does not directly describe the records, yet facilitates their use by researchers (for example, a bibliography). also contains an element that provides a detailed analysis of the collection materials: or description of subordinate components. The element has a repeatable element, (component), which may include all the descriptive elements that appear in . In this way, can be subdivided into other ’s until arriving at the simplest elements that make up the record pool.</p>
<p>Whatever attribute or value is used to describe material on one level is automatically “inherited” by the elements at subordinated levels, unless the EAD specifies otherwise.</p>
<p>The attributes reflect defined properties of an element, and can take on different values, depending on the context in which they appear. In order to set up one or more attributes, a codifier should include the name of the attribute (using the same angle‐brackets “<>” that are used to define mark‐up labels) and its value.</p>
<p>The point of this first phase, in general terms, is that all the information contained in a traditional finding aid can be structured using the elements that constitute the EAD.</p>
<p>For archives with electronic finding aids, the process of converting to EAD is not terribly time‐consuming, though it is somewhat complex. The macro functions of text processors or design‐conversion scripts may be used to relate the content of the elements pertaining to the database records with the corresponding elements of the SGML model, by inserting the proper labels. Those finding aids that do not exist in an electronic format must be previously converted, either by recreating the finding aid or by using optical character recognition (OCR) technology.</p>
<p>In either digital or printed form the inconsistencies of formatting, or even individual descriptive idiosyncrasies, may complicate the conversion process. For this reason, there is an essential second stage: the formal analysis of the information object to be converted. The application of uniform formatting characteristics (including tabulation, spaces, and regular columns) leads to the automatic identification of the different information elements, thereby permitting them to be labeled.</p>
<p>The next step is the process of capture and conversion. Capture by scanning implies OCR processing. In this scenario, the inconsistencies of formatting we mentioned earlier are further complicated by the omnipresent OCR errors. This calls for double OCR processing: first, for the elimination of errors and proper identification of the formatting characteristics that will discriminate the structural elements, and secondly, for the proper configuration of the OCR software (using, for example, the capacity for manually creating “zones”). In this way, those features of the format that will be crucial for their later conversion can be saved.</p>
<p>Our proposal treats this second methodological phase as an intermediate stage, since it includes the use of a non‐proprietary application for SGML conversion, such as Rainbow Maker[6]. This program uses information on a paragraph or character basis, or even on the basis of common attributes that are not style‐dependent, in order to insert labels (in this case Rainbow labels) to set off and indicate the relevant chains of text. Although Rainbow is itself an SGML format (a DTD, to be more specific), it is not appropriate for the permanent representation of data, because it only reflects that structure or content identification that is given in the original document.</p>
<p>Engaging in this intermediate step instead of directly using a programming aid for conversion may be more time‐consuming in the short term. However, in the mid‐term, it provides dual benefits. On the one hand, we now have an intermediary SGML file that can be used, after applying conversion routines, to generate multiple informational objects; and on the other hand, its use of common characteristics will simplify the production of specifications applicable to more than one finding aid, thereby enhancing the automation process. Although using a database with Rainbow files requires more space for memory, it affords the benefit of “pivot” files that allow the direct unfiltered conversion of SGML to XML, or the placing of already processed descriptive information on to an ISAD‐G style‐sheet. Moreover, indexing, organizational and selection routines may be re‐utilized, requiring only slight adaptations.</p>
<p>The final phase consists of designing scripts for translating Rainbow to EAD and, finally, organizing the SGML labels. The end step allows us to connect all the informational components necessary for obtaining the complete archival product.</p>
</sec>
<sec>
<title>Results</title>
<p>We chose a printed inventory to test our proposal: the stock of the Archives of the Infante don Gabriel de Borbon (Mut, 1985), a work of high quality printing, relatively simple description, and very manageable volume.</p>
<p>The process is semi‐automatic. It requires the manual introduction of any information needed for the SGML document that is not found in the source document. This involves using two files, one that will be considered an internal entity (the file designated as “plantilla”) and another that is an external entity or system entity (the “maestro” file). For example, the explanations of system (content‐type, content‐ID, and content description), the EAD clarification (in this case, DTD version 1.0), and the entity references are made from the “plantilla” file to the “maestro” system file using the SGML aid “system entity reference”. The “plantilla” file should also hold the information contained in the elements and . Also, before processing, it is necessary to configure the attributes in order to match the EAD declarations.</p>
<p>In applying attributes, we naturally take advantage of the so‐called “default” values. Default values are automatically given by the system if the encoder of the finding aid does not specify an alternative value. For example, within the element, which indicates to the computer that the document is encoded in EAD, there is an attribute called audience. It indicates whether the contents of the encoded document are of free public access, or private and restricted. If the coder does not specify “private”, the system automatically interprets the attribute as public. A different example would be the manual manipulation of an attribute such as type, which can affect elements like or . For instance, may be configured to have a value “analyticover”, indicating to the processor that the description of component parts is presented in the form of a summary.</p>
<p>For our trial, notes were defined on the basis of their location. All the elements that could be used in a great number of other elements were defined generically, but their state (that is, “required/not required”, “repeatable/not repeatable”) was determined by the element in which each was included.</p>
<p>This configuration of information was also included in the “maestro” file. The use of a master file makes processing easier by saving space and increasing the automatic component of the process, as redundancies are avoided. The other file, “plantilla”, features an identifier (ID) that was used as a pointer to connect the information with the product of conversion process. This procedure facilitates handling the files.</p>
<p>Part of the content of the “maestro” file of our trial can be seen in
<xref ref-type="fig" rid="F_2380180405001">Figure 1</xref>
.</p>
<p>The capture and OCR processing of the paper finding aid comprises a series of files. Each file contains text in Rich Text Format (RTF) and holds information about the existence of fonts (bold and cursive), as well as a precise representation of the page layout (including tabs and blank lines).
<xref ref-type="fig" rid="F_2380180405002">Figure 2</xref>
offers an example.</p>
<p>Rainbow Makers uses the information regarding the format and logic of the processed documents contained in these files to insert the Rainbow DTD labels, and the product is then placed in a single file. The part of the Rainbow file corresponding to the above example, then, is shown in
<xref ref-type="fig" rid="F_2380180405003">Figure 3</xref>
. Some spaces and tabs were introduced to make the sample easier to read.</p>
<p>Using language aids from the Practical Extraction and Report Language programming (perl)[7], we proceeded to translate the Rainbow labels to EAD labels in “object by object” fashion, principally using character level format (CLF) and location information (WPLOC). After that, these objects were organized according to the document type. The perl aid was used to match chains against a “pattern” document. Once saved, the resulting file is connected to the essential data contained in the “plantilla” file, again producing a single file. The EAD document model corresponding to the proposed example, in an abbreviated form, is given in
<xref ref-type="fig" rid="F_2380180405004">Figure 4</xref>
.</p>
<p>This document instance, or any other obtained through the same procedure, can be validated against its DTD using an SGML/XML parser, in our case James Clark’s “XP”[8].</p>
</sec>
<sec>
<title>Conclusions</title>
<p>The use of SGML is presented as a reasonable choice for information services, because it allows proper electronic processing, and is not overly complicated. It is well suited to the rigorous logical structure of bibliographic descriptions, in addition to text. It also allows flexibility in the inclusion of both MARC and non‐MARC descriptive elements, and permits the interconnection of multiple information objects. Moreover, SGML addresses the problem of special characters through the technique of entity references, and it controls the quality of the input through the features of the parser. On the other hand, the separation of the structure of the document from its particular style of representation makes it possible to use SGML documents for a variety of purposes (e.g. in a Web environment, or in CD‐ROM databases), and with different end‐user formats (e.g. HTML, private formats, or markup languages specifically oriented to printed copies, such as RTF, LaTeX, or Post‐Script).</p>
<p>SGML encoding of archival descriptive elements – accessible either locally or online – simplifies, improves and expands access to archival collections, making it possible to connect catalog records with finding aids. It also allows keyword searches in connected sets of finding aids, thus enabling the retrieval of information that would otherwise remain hidden.</p>
<p>EAD constitutes an ideal DTD SGML for representing the structure of the archival description elements, since it not only describes the physical and intellectual constituents of the documents, but also preserves the hierarchical relationships between these elements. This permits “browsing” over levels of description, without duplicating information. The fact that it fully complies with international standards for artificial description, such as the International Standard Archival Description (ISAD) and other standards and formats, such as MARC, serves as a guarantee of its versatility.</p>
<p>On the basis of our results, we can affirm that it is possible to develop a method that allows a semi‐automatic conversion of paper finding aids into EAD, using technology now in wide use. The use of SGML as a key part of the proposed method allows the use of intermediary products of the conversion process, thus maximizing the yield of the given resources. The simplicity of the SGML file and the versatility of the possible indexing routines facilitate the use of advanced retrieval methods.</p>
<p>Even though SGML is highly complex, it may be transformed into XML. One strategy for making optimal use of archival resources is to have multiple databases with a variety of information objects (e.g. descriptive information, contextual information, or digital images). The information could be almost instantly converted, putting multiple presentation options at our disposal via the XSL specification, including an effective means for the creation of hyperlinks using the XML Link specification.</p>
</sec>
<sec>
<title>Notes</title>
<list list-type="order">
<list-item>
<label>1. </label>
<p>1 Development of the Encoded Archival Description Document Type Definition, available:
<ext-link ext-link-type="uri" xlink:href="http://www.loc.gov/ead/eadback.html">http://www.loc.gov/ead/eadback.html</ext-link>
</p>
</list-item>
<list-item>
<label>2. </label>
<p>2 Sperberg‐Mc Queen, C.M. and Burnard, L., A Gentle Introduction to SGML, available:
<ext-link ext-link-type="uri" xlink:href="http://www-tei.uic.edu/orgs/tei/sgml/teip3sg/SG.htm">http://www‐tei.uic.edu/orgs/tei/sgml/teip3sg/SG.htm</ext-link>
</p>
</list-item>
<list-item>
<label>3. </label>
<p>3 Cover, R., The SGML/XML Web Page, available:
<ext-link ext-link-type="uri" xlink:href="http://www.oasis-public.com/cover">http://www.oasis‐public.com/cover</ext-link>
</p>
</list-item>
<list-item>
<label>4. </label>
<p>4 W3Consortium, XML WP, available:
<ext-link ext-link-type="uri" xlink:href="http://www.w3.org/xml">http://www.w3.org/xml</ext-link>
</p>
</list-item>
<list-item>
<label>5. </label>
<p>5 TEI Guidelines for Electronic Text Encoding and Interchange (P3), available:
<ext-link ext-link-type="uri" xlink:href="http://etext.virginia.edu/TEI.html">http://etext.virginia.edu/TEI.html</ext-link>
</p>
</list-item>
<list-item>
<label>6. </label>
<p>6 Sklar, D., “Accelerating conversion to SGML via the Rainbow format”, Electronic Book Technologies EBT, available:
<ext-link ext-link-type="uri" xlink:href="http://ftp.sunet.se/pub/text-processing/sgml/Rainbow/Rainbow.why">http://ftp.sunet.se/pub/text‐processing/ sgml/Rainbow/Rainbow.why</ext-link>
</p>
</list-item>
<list-item>
<label>7. </label>
<p>7 Practical Extraction and Report Language (perl), available:
<ext-link ext-link-type="uri" xlink:href="http://www.bme.unc.edu/facilities/software/perl/perlIndex.html">http://www.bme.unc.edu/facilities/software/perl/perlIndex.html</ext-link>
</p>
</list-item>
<list-item>
<label>8. </label>
<p>8 XP – James Clark’s XML parser in Java. Version 0.4 available:
<ext-link ext-link-type="uri" xlink:href="http://www.jclark.com/xml/xp/index.html">http://www.jclark.com/xml/xp/index.html</ext-link>
</p>
</list-item>
</list>
</sec>
<sec>
<fig position="float" id="F_2380180405001">
<label>
<bold>Figure 1
<x> </x>
</bold>
</label>
<caption>
<p>Sample of Maestro file</p>
</caption>
<graphic xlink:href="2380180405001.tif"></graphic>
</fig>
</sec>
<sec>
<fig position="float" id="F_2380180405002">
<label>
<bold>Figure 2
<x> </x>
</bold>
</label>
<caption>
<p>Sample of the printed inventory</p>
</caption>
<graphic xlink:href="2380180405002.tif"></graphic>
</fig>
</sec>
<sec>
<fig position="float" id="F_2380180405003">
<label>
<bold>Figure 3
<x> </x>
</bold>
</label>
<caption>
<p>After Rainbow DTD processing</p>
</caption>
<graphic xlink:href="2380180405003.tif"></graphic>
</fig>
</sec>
<sec>
<fig position="float" id="F_2380180405004">
<label>
<bold>Figure 4
<x> </x>
</bold>
</label>
<caption>
<p>Corresponding EAD document</p>
</caption>
<graphic xlink:href="2380180405004.tif"></graphic>
</fig>
</sec>
</body>
<back>
<ref-list>
<title>References</title>
<ref id="B1">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Corthouts</surname>
,
<given-names>J.</given-names>
</string-name>
</person-group>
and
<person-group person-group-type="author">
<string-name>
<surname>Philips</surname>
,
<given-names>R.</given-names>
</string-name>
</person-group>
(
<year>1996</year>
), “
<article-title>
<italic>SGML: a librarian’s perception</italic>
</article-title>
”,
<source>
<italic>The Electronic Library</italic>
</source>
, Vol.
<volume>14</volume>
No.
<issue>2</issue>
, pp.
<fpage>101</fpage>
<x></x>
<lpage>10.</lpage>
</mixed-citation>
</ref>
<ref id="B2">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Croft</surname>
,
<given-names>W.B.</given-names>
</string-name>
</person-group>
(
<year>1995</year>
), “
<article-title>
<italic>What do people want from information retrieval?: (The top 10 research issues for companies that use and sell IR systems)</italic>
</article-title>
”,
<source>
<italic>D‐Lib Magazine</italic>
</source>
, Vol.
<volume>1</volume>
No.
<issue>6</issue>
, available:
<ext-link ext-link-type="uri" xlink:href="http://www.dlib.org/dlib/november95/11croft.html">http://www.dlib.org/dlib/november95/11croft.html</ext-link>
</mixed-citation>
</ref>
<ref id="B3">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Gilliland‐Swetland</surname>
,
<given-names>A.J.</given-names>
</string-name>
</person-group>
(
<year>1996</year>
),
<source>
<italic>Encoded Archival Description Document Type Definition (DTD). Applications Guidelines Technical Document No. 1</italic>
</source>
,
<publisher-loc>Library of Congress and Society of American Archivist, Washington, DC</publisher-loc>
, available:
<ext-link ext-link-type="uri" xlink:href="http://www.loc.gov/ead/">http://www.loc.gov/ead/</ext-link>
</mixed-citation>
</ref>
<ref id="B4">
<mixed-citation>
<person-group person-group-type="author">
<string-name>International Council on Archives</string-name>
</person-group>
(
<year>1994</year>
),
<source>
<italic>ISAD(G): General International Standard Archival Description</italic>
</source>
, Adopted by the Ad Hoc Commission on Descriptive Standards, Stockholm, Sweden, 21‐23 January 1993,
<publisher-loc>International Council on Archives, Ottawa, Ontario</publisher-loc>
, available:
<ext-link ext-link-type="uri" xlink:href="http://www.archives.ca/ica/cds/isad">http://www.archives.ca/ica/cds/isad</ext-link>
(g)e.wp</mixed-citation>
</ref>
<ref id="B5">
<mixed-citation>
<person-group person-group-type="author">
<string-name>International Organization for Standardization</string-name>
</person-group>
(
<year>1986</year>
),
<source>
<italic>ISO 8879‐1986 (E), Information Processing – Text and Office Systems – Standard Generalized Markup Language (SGML)</italic>
</source>
,
<publisher-loc>International Organization for Standardization, Geneva.</publisher-loc>
</mixed-citation>
</ref>
<ref id="B6">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Mut</surname>
,
<given-names>A.</given-names>
</string-name>
</person-group>
(
<year>1985</year>
),
<source>
<italic>Inventario del archivo del Infante don Gabriel de Borbón</italic>
</source>
, Dirección General de Bellas Artes y Archivos,
<publisher-loc>Ministerio de Cultura, Madrid</publisher-loc>
, p.
<fpage>49.</fpage>
</mixed-citation>
</ref>
<ref id="B7">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Pitti</surname>
,
<given-names>D.V.</given-names>
</string-name>
</person-group>
(
<year>1999</year>
), “
<article-title>
<italic>Encoded archival description. An introduction and overview</italic>
</article-title>
”,
<source>
<italic>D‐Lib Magazine</italic>
</source>
, Vol.
<volume>5</volume>
No.
<issue>11</issue>
, available:
<ext-link ext-link-type="uri" xlink:href="http://www.dlib.org/dlib/november99/11pitti.html">http://www.dlib.org/dlib/november99/11pitti.html</ext-link>
</mixed-citation>
</ref>
<ref id="B8">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Severson</surname>
,
<given-names>E.</given-names>
</string-name>
</person-group>
(
<year>1995</year>
), “
<article-title>
<italic>The art of SGML conversion: eating your vegetables and enjoying dessert</italic>
</article-title>
”, available:
<ext-link ext-link-type="uri" xlink:href="http://www.oasis-open.org/cover/seversonVeg.html">http://www.oasis‐open.org/cover/seversonVeg.html</ext-link>
(mirror copy).</mixed-citation>
</ref>
</ref-list>
</back>
</article>
</istex:document>
</istex:metadataXml>
<mods version="3.6">
<titleInfo lang="en">
<title>Encoded archival description EAD conversion a methodological proposal</title>
</titleInfo>
<titleInfo type="alternative" lang="en" contentType="CDATA">
<title>Encoded archival description EAD conversion a methodological proposal</title>
</titleInfo>
<name type="personal">
<namePart type="given">Eduardo</namePart>
<namePart type="family">Peis</namePart>
<affiliation>Eduardo Peis is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Flix</namePart>
<namePart type="family">de Moya</namePart>
<affiliation>Flix de Moya is Dean, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">J.</namePart>
<namePart type="family">Carlos FernndezMolina</namePart>
<affiliation>J. Carlos FernndezMolina is Professor, at the Facultad de Biblioteconoma y Documentacin, Universidad de Granada, Granada, Spain.</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<typeOfResource>text</typeOfResource>
<genre type="other" displayLabel="e-technical-paper"></genre>
<originInfo>
<publisher>MCB UP Ltd</publisher>
<dateIssued encoding="w3cdtf">2000-12-01</dateIssued>
<copyrightDate encoding="w3cdtf">2000</copyrightDate>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
<languageTerm type="code" authority="rfc3066">en</languageTerm>
</language>
<physicalDescription>
<internetMediaType>text/html</internetMediaType>
</physicalDescription>
<abstract lang="en">The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language SGML, document type definition DTD for archival description known as encoded archival description EAD is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.</abstract>
<subject>
<genre>keywords</genre>
<topic>Archives</topic>
<topic>Standard Generalized Markup Language</topic>
<topic>Spain</topic>
</subject>
<relatedItem type="host">
<titleInfo>
<title>Library Hi Tech</title>
</titleInfo>
<genre type="journal">journal</genre>
<subject>
<genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-IKM">Information & knowledge management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-ICT">Information & communications technology</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-INT">Internet</topic>
</subject>
<subject>
<genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-LISC">Library & information science</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-IBRT">Information behaviour & retrieval</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-LLM">Librarianship/library management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-IUS">Information user studies</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-MTD">Metadata</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-LTC">Library technology</topic>
</subject>
<identifier type="ISSN">0737-8831</identifier>
<identifier type="PublisherID">lht</identifier>
<identifier type="DOI">10.1108/lht</identifier>
<part>
<date>2000</date>
<detail type="volume">
<caption>vol.</caption>
<number>18</number>
</detail>
<detail type="issue">
<caption>no.</caption>
<number>4</number>
</detail>
<extent unit="pages">
<start>360</start>
<end>368</end>
</extent>
</part>
</relatedItem>
<identifier type="istex">0812C84ADDFA7954CAC853D5E947F16DEB386E4C</identifier>
<identifier type="DOI">10.1108/07378830010360455</identifier>
<identifier type="filenameID">2380180405</identifier>
<identifier type="original-pdf">2380180405.pdf</identifier>
<identifier type="href">07378830010360455.pdf</identifier>
<accessCondition type="use and reproduction" contentType="copyright">© MCB UP Limited</accessCondition>
<recordInfo>
<recordContentSource>EMERALD</recordContentSource>
</recordInfo>
</mods>
</metadata>
<serie></serie>
</istex>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Ticri/explor/TeiVM2/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000379 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000379 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Wicri/Ticri
   |area=    TeiVM2
   |flux=    Istex
   |étape=   Corpus
   |type=    RBID
   |clé=     ISTEX:0812C84ADDFA7954CAC853D5E947F16DEB386E4C
   |texte=   Encoded archival description EAD conversion a methodological proposal
}}

Wicri

This area was generated with Dilib version V0.6.31.
Data generation: Mon Oct 30 21:59:18 2017. Site generation: Sun Feb 11 23:16:06 2024