Implementation of Dublin Core at the University of Alberta Libraries
Identifieur interne : 000402 ( Istex/Corpus ); précédent : 000401; suivant : 000403Implementation of Dublin Core at the University of Alberta Libraries
Auteurs : Erika BanskiSource :
- OCLC Systems & Services: International digital library perspectives [ 1065-075X ] ; 2002-09-01.
Abstract
The article describes the application of the Dublin Core metadata scheme for the digital collections, the Alberta Folklore and Local History, housed at the University of Alberta Libraries. It highlights the metadata needs for describing an archival collection, a detailed metadata encoding structure, the metadata authority guidelines, and the use of controlled vocabulary. It concludes that the extended Dublin Core metadata element set derived from this project is also feasible for describing other locally developed digital collections.
Url:
DOI: 10.1108/10650750210439340
Links to Exploration step
ISTEX:6E2B59E77937C46399944FB877D4FD474FD6375DLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">Implementation of Dublin Core at the University of Alberta Libraries</title><author wicri:is="90%"><name sortKey="Banski, Erika" sort="Banski, Erika" uniqKey="Banski E" first="Erika" last="Banski">Erika Banski</name><affiliation><mods:affiliation>Erika Banski is GermanSlavic Librarian and Principal Cataloguer, University of Alberta Libraries, Edmonton, Alberta, Canada.</mods:affiliation></affiliation></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:6E2B59E77937C46399944FB877D4FD474FD6375D</idno><date when="2002" year="2002">2002</date><idno type="doi">10.1108/10650750210439340</idno><idno type="url">https://api.istex.fr/document/6E2B59E77937C46399944FB877D4FD474FD6375D/fulltext/pdf</idno><idno type="wicri:Area/Istex/Corpus">000402</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">Implementation of Dublin Core at the University of Alberta Libraries</title><author wicri:is="90%"><name sortKey="Banski, Erika" sort="Banski, Erika" uniqKey="Banski E" first="Erika" last="Banski">Erika Banski</name><affiliation><mods:affiliation>Erika Banski is GermanSlavic Librarian and Principal Cataloguer, University of Alberta Libraries, Edmonton, Alberta, Canada.</mods:affiliation></affiliation></author></analytic><monogr></monogr><series><title level="j">OCLC Systems & Services: International digital library perspectives</title><idno type="ISSN">1065-075X</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="2002-09-01">2002-09-01</date><biblScope unit="volume">18</biblScope><biblScope unit="issue">3</biblScope><biblScope unit="page" from="130">130</biblScope><biblScope unit="page" to="138">138</biblScope></imprint><idno type="ISSN">1065-075X</idno></series><idno type="istex">6E2B59E77937C46399944FB877D4FD474FD6375D</idno><idno type="DOI">10.1108/10650750210439340</idno><idno type="filenameID">1640180303</idno><idno type="original-pdf">1640180303.pdf</idno><idno type="href">10650750210439340.pdf</idno></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">1065-075X</idno></seriesStmt></fileDesc><profileDesc><textClass></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">The article describes the application of the Dublin Core metadata scheme for the digital collections, the Alberta Folklore and Local History, housed at the University of Alberta Libraries. It highlights the metadata needs for describing an archival collection, a detailed metadata encoding structure, the metadata authority guidelines, and the use of controlled vocabulary. It concludes that the extended Dublin Core metadata element set derived from this project is also feasible for describing other locally developed digital collections.</div></front></TEI><istex><corpusName>emerald</corpusName><author><json:item><name>Erika Banski</name><affiliations><json:string>Erika Banski is GermanSlavic Librarian and Principal Cataloguer, University of Alberta Libraries, Edmonton, Alberta, Canada.</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>Collection management</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Internet</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Library services</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Resources</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>Canada</value></json:item></subject><language><json:string>eng</json:string></language><originalGenre><json:string>case-report</json:string></originalGenre><abstract>The article describes the application of the Dublin Core metadata scheme for the digital collections, the Alberta Folklore and Local History, housed at the University of Alberta Libraries. It highlights the metadata needs for describing an archival collection, a detailed metadata encoding structure, the metadata authority guidelines, and the use of controlled vocabulary. It concludes that the extended Dublin Core metadata element set derived from this project is also feasible for describing other locally developed digital collections.</abstract><qualityIndicators><score>4.891</score><pdfVersion>1.2</pdfVersion><pdfPageSize>610 x 789 pts</pdfPageSize><refBibsNative>true</refBibsNative><keywordCount>6</keywordCount><abstractCharCount>540</abstractCharCount><pdfWordCount>3967</pdfWordCount><pdfCharCount>26707</pdfCharCount><pdfPageCount>9</pdfPageCount><abstractWordCount>77</abstractWordCount></qualityIndicators><title>Implementation of Dublin Core at the University of Alberta Libraries</title><genre><json:string>case-report</json:string></genre><host><volume>18</volume><publisherId><json:string>oclc</json:string></publisherId><pages><last>138</last><first>130</first></pages><issn><json:string>1065-075X</json:string></issn><issue>3</issue><subject><json:item><value>Library & information science</value></json:item><json:item><value>Librarianship/library management</value></json:item><json:item><value>Records management & preservation</value></json:item><json:item><value>Library technology</value></json:item><json:item><value>Information repositories</value></json:item></subject><genre><json:string>journal</json:string></genre><language><json:string>unknown</json:string></language><title>OCLC Systems & Services: International digital library perspectives</title><doi><json:string>10.1108/oclc</json:string></doi></host><publicationDate>2002</publicationDate><copyrightDate>2002</copyrightDate><doi><json:string>10.1108/10650750210439340</json:string></doi><id>6E2B59E77937C46399944FB877D4FD474FD6375D</id><score>0.14075674</score><fulltext><json:item><original>true</original><mimetype>application/pdf</mimetype><extension>pdf</extension><uri>https://api.istex.fr/document/6E2B59E77937C46399944FB877D4FD474FD6375D/fulltext/pdf</uri></json:item><json:item><original>false</original><mimetype>application/zip</mimetype><extension>zip</extension><uri>https://api.istex.fr/document/6E2B59E77937C46399944FB877D4FD474FD6375D/fulltext/zip</uri></json:item><istex:fulltextTEI uri="https://api.istex.fr/document/6E2B59E77937C46399944FB877D4FD474FD6375D/fulltext/tei"><teiHeader><fileDesc><titleStmt><title level="a" type="main" xml:lang="en">Implementation of Dublin Core at the University of Alberta Libraries</title></titleStmt><publicationStmt><authority>ISTEX</authority><publisher>MCB UP Ltd</publisher><availability><p>EMERALD</p></availability><date>2002</date></publicationStmt><sourceDesc><biblStruct type="inbook"><analytic><title level="a" type="main" xml:lang="en">Implementation of Dublin Core at the University of Alberta Libraries</title><author><persName><forename type="first">Erika</forename><surname>Banski</surname></persName><affiliation>Erika Banski is GermanSlavic Librarian and Principal Cataloguer, University of Alberta Libraries, Edmonton, Alberta, Canada.</affiliation></author></analytic><monogr><title level="j">OCLC Systems & Services: International digital library perspectives</title><idno type="pISSN">1065-075X</idno><idno type="DOI">10.1108/oclc</idno><imprint><publisher>MCB UP Ltd</publisher><date type="published" when="2002-09-01"></date><biblScope unit="volume">18</biblScope><biblScope unit="issue">3</biblScope><biblScope unit="page" from="130">130</biblScope><biblScope unit="page" to="138">138</biblScope></imprint></monogr><idno type="istex">6E2B59E77937C46399944FB877D4FD474FD6375D</idno><idno type="DOI">10.1108/10650750210439340</idno><idno type="filenameID">1640180303</idno><idno type="original-pdf">1640180303.pdf</idno><idno type="href">10650750210439340.pdf</idno></biblStruct></sourceDesc></fileDesc><profileDesc><creation><date>2002</date></creation><langUsage><language ident="en">en</language></langUsage><abstract xml:lang="en"><p>The article describes the application of the Dublin Core metadata scheme for the digital collections, the Alberta Folklore and Local History, housed at the University of Alberta Libraries. It highlights the metadata needs for describing an archival collection, a detailed metadata encoding structure, the metadata authority guidelines, and the use of controlled vocabulary. It concludes that the extended Dublin Core metadata element set derived from this project is also feasible for describing other locally developed digital collections.</p></abstract><textClass><keywords scheme="keyword"><list><head>Keywords</head><item><term>Archives</term></item><item><term>Collection management</term></item><item><term>Internet</term></item><item><term>Library services</term></item><item><term>Resources</term></item><item><term>Canada</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-LLM</label><item><term>Librarianship/library management</term></item><label>cat-RMP</label><item><term>Records management & preservation</term></item><label>cat-LTC</label><item><term>Library technology</term></item><label>cat-IREP</label><item><term>Information repositories</term></item></list></keywords></textClass></profileDesc><revisionDesc><change when="2002-09-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/6E2B59E77937C46399944FB877D4FD474FD6375D/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="case-report"><front><journal-meta><journal-id journal-id-type="publisher-id">oclc</journal-id><journal-id journal-id-type="doi">10.1108/oclc</journal-id><journal-title-group><journal-title>OCLC Systems & Services: International digital library perspectives</journal-title></journal-title-group><issn pub-type="ppub">1065-075X</issn><publisher><publisher-name>MCB UP Ltd</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.1108/10650750210439340</article-id><article-id pub-id-type="original-pdf">1640180303.pdf</article-id><article-id pub-id-type="filename">1640180303</article-id><article-categories><subj-group subj-group-type="type-of-publication"><compound-subject><compound-subject-part content-type="code">case-report</compound-subject-part><compound-subject-part content-type="label">Case study</compound-subject-part></compound-subject></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-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><compound-subject><compound-subject-part content-type="code">cat-RMP</compound-subject-part><compound-subject-part content-type="label">Records management & preservation</compound-subject-part></compound-subject><subj-group><compound-subject><compound-subject-part content-type="code">cat-IREP</compound-subject-part><compound-subject-part content-type="label">Information repositories</compound-subject-part></compound-subject></subj-group></subj-group></subj-group></article-categories><title-group><article-title>Implementation of Dublin Core at the University of Alberta Libraries</article-title></title-group><contrib-group><contrib contrib-type="author"><string-name><given-names>Erika</given-names> <surname>Banski</surname></string-name><aff>Erika Banski is German/Slavic Librarian and Principal Cataloguer, University of Alberta Libraries, Edmonton, Alberta, Canada.</aff></contrib></contrib-group><pub-date pub-type="ppub"><day>01</day><month>09</month><year>2002</year></pub-date><volume>18</volume><issue>3</issue><fpage>130</fpage><lpage>138</lpage><permissions><copyright-statement>© MCB UP Limited</copyright-statement><copyright-year>2002</copyright-year><license license-type="publisher"><license-p></license-p></license></permissions><self-uri content-type="pdf" xlink:href="10650750210439340.pdf"></self-uri><abstract><p>The article describes the application of the Dublin Core metadata scheme for the digital collections, the <italic>Alberta Folklore and Local History</italic>, housed at the University of Alberta Libraries. It highlights the metadata needs for describing an archival collection, a detailed metadata encoding structure, the metadata authority guidelines, and the use of controlled vocabulary. It concludes that the extended Dublin Core metadata element set derived from this project is also feasible for describing other locally developed digital collections.</p></abstract><kwd-group><kwd>Archives</kwd><x>, </x><kwd>Collection management</kwd><x>, </x><kwd>Internet</kwd><x>, </x><kwd>Library services</kwd><x>, </x><kwd>Resources</kwd><x>, </x><kwd>Canada</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>The University of Alberta Libraries (UAL) Web portal is a dynamic Web site supported by a number of underlying databases. Currently, two metadata standards are used in these databases to provide access to UAL holdings in electronic format: the traditional MARC standard and the non‐traditional Dublin Core (DC) standard. Digital resources belonging to other parties, including licensed bibliographic and full‐text databases, e‐journals, e‐books, and other Internet resources, are catalogued in MARC format in the OPAC. The digital collections developed locally and made available for public use through the UAL Web portal are described using DC metadata elements. This article explores the application of the extended DC standard on the <italic>Alberta Folklore and Local History</italic> (AFLH) digital collection.</p><p>Digitization of the AFLH collection started in April, 2000, as part of the <italic>Our Future, Our Past: the Alberta Heritage Digitization Project</italic> (<ext-link ext-link-type="uri" xlink:href="http://ahdp.lib.ucalgary.ca/home.htm">http://ahdp.lib.ucalgary.ca/home.htm</ext-link>). Because it was the first project of its kind conducted by the UAL, the project team, called the DRG (Digital Resources Group), faced many challenges. The DRG group consisted of librarians and library associates from various units of the UAL, including the Humanities and Social Sciences Library, the Information Technology Services unit, the Data Library, and the Bibliographic Services department. The pioneering work that the author engaged in focused on evaluating and selecting a metadata standard, defining the working template, and compiling metadata authority guidelines.</p><p>It must be admitted that leaving behind the familiar world of MARC, AACR2 and LC authorities was both challenging and exciting. As it turned out, the lessons learned in the “old world” helped to overcome the difficulties of the new one, by providing a knowledge base for making the right decisions. Furthermore, certain established principles and rules also proved to be transferable. Altogether, in our opinion, this link between old and new will enhance interoperability between traditional and non‐traditional metadata.</p></sec><sec><title>The AFLH collection</title><p>The AFLH collection is an archive housed in the Bruce Peel Special Collections Library at the University of Alberta. It is a major resource on the history of Alberta, and contains historical documents collected by the University of Alberta in the mid‐1940s through the Alberta Folklore and Local History Project led by Robert E. Gard. The collection basically consists of 992 files containing a variety of items such as anecdotes, essays, poetry, tall tales, personal reminiscences of Alberta pioneers, school histories and yearbooks, photographs, correspondence, play and radio scripts, newspaper clippings, and excerpts of stories from published documents. Physically, the collection spans approximately six linear meters.</p></sec><sec><title>The project</title><p>The main goal of the project was to launch the UAL’s digital collections initiative. This initiative aims to digitize unique materials in the library’s collection and provide free access to them via the Internet. The project also represents the first major contribution of the UAL to the <italic>Our Future, Our Past: The Alberta Heritage Digitization Project</italic>.</p><p>The project was conducted in several phases. In the first phase, the original AFLH collection was accessioned and inventoried, and a finding aid was compiled. We used the results of this first phase to develop <italic>A Guide to The Alberta Folklore and Local History Collection</italic> (Banski and Russell, 2001), which significantly enhanced access to the original collection. The accession numbers and the inventory enabled the second phase of the project, the digitization project, to proceed. This second phase included scanning the archival files, selecting database software to store metadata, creating metadata, and preserving the master copy of the digital object on CD‐ROMs. The third phase focused on three processes: converting the scanned versions of digital objects into an image format for public access, creating thumbnails of the first pages of the digital objects, and establishing links from the metadata records to the digital objects. The fourth phase, where we are now, includes finalizing the public access interface, cleaning up errors, and proofreading metadata.</p><p>The goal of the digitization project was to provide free online access to this unique collection to university staff and students, researchers, genealogists, local historians, cultural heritage groups, K‐12 teachers and students, and everyone else who is interested in Alberta’s history and cultural heritage. Preservation in electronic format was a secondary goal of the project. The digital collection contains most but not all of the documents included in the original archive. Items for which copyright could not be obtained were excluded, and so were documents with closed access. Examples of closed access items are some items in the photographs series and the entire AFLH project correspondence series.</p><p>The decisions we made regarding metadata were influenced by the fact that the files in the digital collection were all image files. Ideally, we would have made the textual documents accessible in two formats, image and text, but neither OCR nor re‐typing of documents was an option due to time limits and financial constraints. The text versions of the documents would have been used for full‐text searching of the collection. The lack of full‐text searchability required detailed, rich metadata in order to provide an optimal number of access points to this collection’s contents.</p></sec><sec><title>Metadata for archival collections</title><p>The first challenge of the project was to decide how to best describe an archival collection in digital format. Traditionally, archivists assign accession numbers to a specific collection to preserve the original sequence of the material, and then create a finding aid that follows the hierarchical relationships of the collection. A finding aid normally describes the content and intellectual organization of an archival collection or fonds. It starts with the top level of the hierarchy, then descends to the second or the series level, and then to the third level, which most often is the files level. In certain cases, the description may even extend to the fourth, or item level.</p><p>Following this practice, we first accessioned the collection and compiled the AFLH finding aid based on the <italic>Rules for Archival Description</italic> (1996). We then created metadata that corresponded to the lowest level descriptions in the finding aid, which in most series are the file level descriptions. For selected series only, the accession numbers were assigned to items rather than to files, and the finding aid descriptions as well as the corresponding metadata were also at the item level. The Photographs and the Notebooks series are two examples of item level accessioning and description (see example in Appendix 1).</p></sec><sec><title>Metadata standard</title><p>The next step was to select a metadata scheme and establish the structure and fields of the metadata records. We looked at various standards, including encoded archival description (EAD), text encoding initiative (TEI), DC and MARC. We decided to use the DC metadata scheme for several reasons:</p><list list-type="order"><list-item><label>1. </label><p>(1) It is simple enough to be used by project staff not trained as cataloguers.</p></list-item><list-item><label>2. </label><p>(2) It is interoperable with MARC. OCLC implemented it successfully in the CORC project, mapping DC elements to MARC fields. A few commercial vendors of integrated library systems have already started to support DC crosswalks for their MARC‐based products.</p></list-item><list-item><label>3. </label><p>(3) It can facilitate the implementation of the one‐stop searching concept. UAL is a member of the Alberta Library consortium, which selected OCLC’s SiteSearch for its public access interface. This interface already supports DC. OCLC has also successfully implemented DC in the CORC project and is mapping DC elements to MARC fields.</p></list-item><list-item><label>4. </label><p>(4) It has become a trend that more and more digital libraries are using non‐traditional metadata standards (i.e. non‐MARC) to describe their digital collections. Although DC is an emerging standard, it in fact has the strongest support from the library community in terms of non‐traditional metadata.</p></list-item></list></sec><sec><title>Metadata software and metadata record structure</title><p>Microsoft Access database software was used to create, store, and maintain the metadata elements for describing the AFLH collection. A link field was included that contains data associated with the location of the digital object being described. Because Access provides the ability to create a data input template and relational tables, data entry becomes easy and consistency can be maintained. Controlled vocabulary lists of personal names, and topical and geographical subject headings were compiled using relational tables. Access also comes with a mechanism to build Web interfaces. We developed a metadata workform to allow staff to access the database to create and edit records via the Web.</p><p>Following the organization structure of our finding aid, each metadata record describes the digital representation of an archival file, or in certain series, an item in the collection. The project team members who scanned the material created the metadata records with “item(s) in hand.” This basic cataloguing principle in our case meant that they described the archival file or item being scanned in one part of the record, and then the digital object that resulted from the scanning process in the next part of the record. Thus, the first part of the metadata record is descriptive, consisting of mainly bibliographic information pertaining to the original object. The second part describes the digitized version of the original object, focusing on file size, file format, and image resolution. The elements of a metadata record are listed in <xref ref-type="fig" rid="F_1640180303001">Table I</xref>. The record is divided into two sections: the descriptive metadata section consists of elements for recording bibliographic information while the administrative metadata section consists of technical information relating to the scanning process and the resulting image files.</p><sec><title>Descriptive metadata</title><p>Most descriptive elements used are qualified DC elements. Local qualifiers were added either for clarity or because of the need to repeat the same element in one of the sections. For example, Coverage has two occurrences, Coverage.Geographic and Coverage.Time. The qualifiers Geographic and Time were used because the DC qualifiers Spatial and Temporal were not established at the time. Another example is the Source element, where three different values are used. They are: Source.Collection, Source.Series, and Source.Publication. The first two pertain to various levels of description, while the third occurrence has a value for the type of published documents, for example, newspaper clippings or excerpts.</p><p>The accession number element was locally defined. The number for the original AFLH collection is 96‐93, assigned by the Public Archives of Canada in the <italic>Union List of Manuscripts in Canadian Repositories</italic> (Gordon, 1975). Its format consists of two segments separated by a hyphen. The 96 is the number for the Bruce Peel Special Collections Library, while the 93 indicates that this archive was the 93rd manuscript collection acquired by this library. The range for this collection is 96‐93‐1 through 96‐93‐992, where the third part of the number is unique to each individual archival file.</p></sec><sec><title>Administrative metadata</title><p>Because two versions of each digital object were created, the encoding process became more complex. The first version was done in high resolution TIFF format for preservation purposes. These master copies were stored on CD‐ROMs and archived in a climate‐controlled vault. The second version was derived through a batch conversion of all TIFF files to lower resolution JPEG files, intended for public access.</p></sec><sec><title>File naming for digital objects</title><p>Naming of digital files is often an issue of concern to the Internet community. This is because almost every digital object consists of numerous image files. As a rule, one image file corresponds to one page of the original document. Only in the case of photographs did we have one image file representing the entire original document. Regarding the number of characters in the file name, we decided to use the “eight plus three” file naming convention in order to accommodate older MS‐DOS systems (up to eight characters for the file name and three for the file type extension.) We also wanted to have a recognizable link between the name of each digital file and the corresponding part of the original document. To achieve this, we used the accession number of the original document. We incorporated the third element of every accession number (mentioned earlier) and the sequence in the file name. <xref ref-type="fig" rid="F_1640180303002">Table II</xref> is the file naming scheme used for our project.</p></sec><sec><title>Metadata elements repeated with different qualifiers</title><p>Some elements, such as date, publisher, and rights, are used in both the descriptive and the administrative sections. These elements use different qualifiers for different purposes. For example, the value of the Date.Created element refers to the original document’s creation date, while the value of the Date.Digitized element refers to the digital archival object’s creation date. Also, it is common for access to some files to be restricted in an archival collection. We used the Rights.Access field, which contains a value of “Open” or “Closed” to store such information. When “Closed” is used, no link will be provided from the metadata to the digital object. The second occurrence of the Rights field, Rights.Copyright, is in the administrative section to indicate the copyright holder. The default value of this field is “2000 University of Alberta Libraries,” indicating that the library holds copyright for the digital object.</p></sec><sec><title>Metadata elements with more than one value</title><p>Unlike MARC records, the number of elements (or fields) in each metadata record is fixed in the AFLH database. The Access template that was developed for data entry does not allow addition or deletion of elements. In many records where more than one value had to be entered for each element, these different values were entered in the same field with delimiters. Examples of such cases include instances where there is more than one name entry in the Creator and Contributor field, or multiple subjects in the Subject field. In addition, empty elements cannot be deleted. </p><p>We developed guidelines for deploying metadata in order to ensure consistency and interoperability among metadata records internal to the AFLH database, as well as externally in various UAL digital collections</p><p>It remains to be seen how these features may affect interoperability in the future. However, we missed MARC’s flexibility, which allows an unlimited number of added entry fields and subject fields, and excludes empty fields.</p></sec><sec><title>Metadata authority guidelines</title><p>Currently, there are no prescribed rules and methods available to the library community for deploying DC metadata elements, other than best practices. We relied on the Dublin Core Metadata Initiative documentation available at <ext-link ext-link-type="uri" xlink:href="http://dublincore.org/,andonitsmorerecentlydeveloped">http://dublincore.org/, and on its more recently developed</ext-link> DC Library Application Profile section (<ext-link ext-link-type="uri" xlink:href="http://dublincore.org/documents/library-application-profile/">http://dublincore.org/documents/library‐application‐profile/</ext-link>). Furthermore, we used the OCLC‐CORC documentation (<ext-link ext-link-type="uri" xlink:href="http://www.oclc.org/corc/">http://www.oclc.org/corc/</ext-link>) while we were participating in the CORC founder’s phase, as well as information provided via the Web by libraries and other institutions that had already implemented digital libraries, such as the Cornell Digital Library.</p><p>However, the lack of rules and rule interpretations also makes the use of DC simpler and easier for local applications. Since every collection has unique features, and every institution has specific needs, the DC metadata scheme can be used as the basic set and be extended with locally defined elements to express the uniqueness of a collection. The user may also choose to follow an existing standard for cataloguing or archival description to regulate data entry. Institutions can develop customized metadata sets and decide how to populate them and what values to use to represent specifics.</p><p>We developed guidelines for deploying metadata in order to ensure consistency and interoperability among metadata records internal to the AFLH database, as well as externally in various UAL digital collections (from <ext-link ext-link-type="uri" xlink:href="http://folklore.library.ualberta.ca/About.cfm">http://folklore.library.ualberta.ca/About.cfm</ext-link>, select the Documentation link, then select Metadata Authority Guidelines). These guidelines resemble a very simple version of a cataloguing procedures manual. For every element of a metadata record, the guidelines provide a definition within the context of AFLH and encoding instructions for source of information, form of entry, cataloguing standards and rules, and use of controlled vocabulary. For personal and corporate name entries, for example, the guidelines refer to RAD and AACR2 rules. For the language codes and date form, the ISO standards recommended by DCMI (Dublin Core Metadata Initiative), ISO639, and ISO8601 were used. An example of a complete record was also included in the Guidelines for quick reference. Appendix 2 at the end of this article provides an example of a metadata record viewed through the public access interface.</p></sec></sec><sec><title>Controlled vocabulary</title><p>Controlled vocabulary allows inter‐ and intra‐index consistency and enables interoperability in terms of cross‐database searching. LCSH (Library of Congress subject headings) and LC authority records are the first choice for name and subject entries. However, in some instances, the <italic>Provincial Archives of Alberta Subject Headings</italic> (1992) were used. We decided to use it when neither LCSH nor CSH (Canadian subject headings) (Schweitzer, 1992) provided a subject heading specific to local Alberta; for example, in the case of “Campbell School District, Alberta – History – School yearbooks.” </p><p>AFLH is the first digital collection implemented with DC by UAL … Our experience with DC shows that this metadata standard is the right choice for UAL digital applications</p><p>The AFLH database’s public interface allows the user to both browse and search all metadata elements with controlled vocabulary:</p><list list-type="bullet"><list-item><label>• </label><p>Creator;</p></list-item><list-item><label>• </label><p>Contributor;</p></list-item><list-item><label>• </label><p>Coverage.Geographic; and</p></list-item><list-item><label>• </label><p>Subject.</p></list-item></list><p>For these fields, relational indexes (i.e. tables) were developed. Each index was built using a pull‐down menu in its corresponding database field. This allowed the metadata creator to click on a relevant term and create a link to it from the record. The benefits were three‐fold:</p><list list-type="order"><list-item><label>1. </label><p>(1) allowing faster data entry;</p></list-item><list-item><label>2. </label><p>(2) ensuring consistency; and</p></list-item><list-item><label>3. </label><p>(3) providing a means for easy record maintenance.</p></list-item></list><p>The metadata elements without controlled vocabulary use were not indexed, so they are searchable but not browsable through the public interface.</p><p>Controlled vocabulary lists for certain metadata elements were developed locally to describe attributes specific to this collection. Examples are Type.Genre and Source.Series. The Type.Genre element includes, among others, biographies, diaries, obituaries, and personal reminiscences. This field was also indexed and allows for browsing. The Source.Series element served to identify the series to which the archival file belongs, and to establish links among all archival files at this higher level in the hierarchy. The values in Source.Series can be described as a controlled vocabulary list, because they consist of all series titles in the collection (series are listed at the second level of archival description, see Appendix 1).</p></sec><sec><title>Public interface and Web portal</title><p>A Web‐based interface called <italic>Prairie Provinces</italic> (<ext-link ext-link-type="uri" xlink:href="http://peel.library.ualberta.ca/index_english.cfm">http://peel.library.ualberta.ca/index_english.cfm</ext-link>) provides access to all UAL digital collections. It was developed using Cold Fusion and is available in both English and French at <ext-link ext-link-type="uri" xlink:href="http://peel.library.ualberta.ca/">http://peel.library.ualberta.ca/</ext-link>. The architecture of this Web site includes separate MS Access‐based databases for each collection. Each record contains links to the relevant digital object consisting of one or more image files.</p><p>AFLH is one of the collections available through this portal. The user can search or browse the collection, view the digital objects, and navigate through them. Other features such as adding items to a “shopping cart” and printing or downloading selected items are available. The portal also provides links to online finding aids and documentation for projects.</p></sec><sec><title>Conclusion</title><p>AFLH is the first digital collection implemented with DC by UAL. The core metadata set developed for this project has since been used for the digital projects that followed. Our experience with DC shows that this metadata standard is the right choice for UAL digital applications, because it provides a means to accommodate the common attributes of each collection. Also, its extensibility allows the inclusion of locally developed elements that express the unique features of each collection.</p><p>Two metadata standards are currently used to support the discovery of and access to electronic collections through the UAL Web portal. One is the MARC standard, which supports the OPAC, and the other is the DC standard for local digital collections. Both standards share numerous common principles and rules and complement each other with their unique features. Records encoded with these two standards currently coexist on our Web portal.</p><p>The final goal of the UAL Web portal developers is to implement a one‐stop search and viewing interface for all electronic resources. To achieve this goal, we are looking at two possible options:</p><list list-type="order"><list-item><label>1. </label><p>(1) integrating metadata from all databases into one integrated library system that supports multiple metadata standards; or</p></list-item><list-item><label>2. </label><p>(2) implementing a one‐stop search interface able to execute simultaneous searches of various databases and metadata standards</p></list-item></list></sec><sec><fig position="float" id="F_1640180303001"><label><bold>Table I<x> </x></bold></label><caption><p>List of metadata elements</p></caption><graphic xlink:href="1640180303001.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180303002"><label><bold>Table II<x> </x></bold></label><caption><p>Image file naming scheme</p></caption><graphic xlink:href="1640180303002.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180303003"><label><bold>Table AI<x> </x></bold></label><caption><p>Hierarchical description of archival collections</p></caption><graphic xlink:href="1640180303003.tif"></graphic></fig></sec><sec><fig position="float" id="F_1640180303004"><label><bold>Figure A1<x> </x></bold></label><caption><p>Example of a metadata record. Alberta Folklore and Local History Collection</p></caption><graphic xlink:href="1640180303004.tif"></graphic></fig></sec></body><back><ref-list><title>References</title><ref id="B1"><mixed-citation><person-group person-group-type="editor"><string-name><surname>Banski</surname>, <given-names>E.</given-names></string-name></person-group> and <person-group person-group-type="editor"><string-name><surname>Rusell</surname>, <given-names>F.</given-names></string-name></person-group> (Ed.) (<year>2001</year>), <source><italic>A Guide to the Alberta Folklore and Local History Collection</italic></source>, in <person-group person-group-type="editor"><string-name><surname>MacKeen</surname>, <given-names>J.</given-names></string-name></person-group> (Comp.), <publisher-name>University of Alberta Libraries</publisher-name>, <publisher-loc>Edmonton, Canada.</publisher-loc></mixed-citation></ref><ref id="B2"><mixed-citation><person-group person-group-type="editor"><string-name><surname>Gordon</surname>, <given-names>R.</given-names></string-name></person-group> (Ed.) (<year>1975</year>), <source><italic>Union List of Manuscripts in Canadian Repositories = Catalogue Collectif des Manuscrits des Archives Canadiennes</italic></source>, <edition>revised ed.</edition>, <publisher-name>Public Archives Canada</publisher-name>, <publisher-loc>Ottawa, Canada.</publisher-loc></mixed-citation></ref><ref id="B3"><mixed-citation><person-group person-group-type="author"><string-name>Provincial Archives of Alberta</string-name></person-group> (<year>1992</year>), <source><italic>Provincial Archives of Alberta Subject Headings</italic></source>, <publisher-name>Alberta Culture, Provincial Archives of Alberta</publisher-name>, <publisher-loc>Edmonton, Canada.</publisher-loc></mixed-citation></ref><ref id="B4"><mixed-citation><source><italic>Rules for Archival Description</italic></source> (<year>1996</year>), <source><italic>Rules for Archival Description</italic></source>, <edition>revised ed.</edition>, <publisher-name>Bureau of Canadian Archivists</publisher-name>, <publisher-loc>Ottawa, Canada.</publisher-loc></mixed-citation></ref><ref id="B5"><mixed-citation><person-group person-group-type="editor"><string-name><surname>Schweitzer</surname>, <given-names>A.</given-names></string-name></person-group> (Ed.) (<year>1992</year>), <source><italic>Canadian Subject Headings</italic></source>, <publisher-name>National Library of Canada</publisher-name>, <publisher-loc>Ottawa, Canada</publisher-loc>.</mixed-citation></ref></ref-list><ref-list><title>Further reading</title><ref id="B6"><mixed-citation><person-group person-group-type="author"><string-name><surname>Van Ballegooie</surname>, <given-names>M.</given-names></string-name></person-group> (<year>2001</year>), “<article-title><italic>Metadata for archival collections: the University of Toronto’s ’barren lands’ project</italic></article-title>”, <source><italic>RLG DigiNews</italic></source>, Vol. <volume>5</volume> No. <issue>4</issue>, available at: <ext-link ext-link-type="uri" xlink:href="http://www.rlg.org/preserv/diginews/diginews5-4.html">http://www.rlg.org/preserv/diginews/diginews5‐4.html</ext-link> (accessed 16 October 2001).</mixed-citation></ref></ref-list><app-group><app><title>Appendix 1</title><p><xref ref-type="fig" rid="F_1640180303003">Table AI</xref></p></app><app><title>Appendix 2</title><p><xref ref-type="fig" rid="F_1640180303004">Figure A1</xref></p><sec><title>Metadata</title><p><italic>Title:</italic> Omand Family</p><p><italic>Contributor:</italic> Robert E. Gard</p><p><italic>Contents:</italic> Story by Betty Bicknell, [194‐]. Typescript, 5 leaves.</p><p><italic>Date Created:</italic> [194‐]</p><p><italic>Genre:</italic> Short Stories</p><p><italic>Coverage Time:</italic></p><p><italic>Language:</italic> English</p><p><italic>Source Collection:</italic> Alberta Folklore and Local History Collection</p><p><italic>Source Series:</italic> Notebooks</p><p><italic>Source Publication:</italic></p><p><italic>Accession No:</italic> 96‐93‐799</p><p><italic>Rights Access:</italic> Open</p><p><italic>Creators or Authors</italic></p><p>Bicknell, Betty</p><p><italic>Geographic Name</italic></p><p>Edmonton, Alberta</p><p><italic>Subject Headings</italic></p><p>Edmonton, Alberta – History</p><p>Frontier and pioneer life – Alberta</p><p>Omand Family</p><p>Women’s writings</p></sec><sec><title>Implications for practitioners</title><p>This summary has been provided to allow a rapid appreciation of the significance of the content of this article. Browsers may then choose to read the article in toto, to derive full benefit from the author’s work.</p><p>The Alberta Folklore and Local History collection is a major resource on the history of the province.</p><p>At the University of Alberta (UAL), a digitization project was created with the aim of giving all users free online access to this unique collection of historical documents collected by UAL during the mid 1940s.</p><p>Detailed and rich metadata would be needed to provide the best possible access points for the collection’s contents. The Digital Resources Group of librarians and library associates, who were charged with the digitization project, had first to decide how to best describe an archival collection in digital format, using a mixture of traditional and innovative approaches.</p><p>The group then faced a decision over which metadata scheme should be applied to the collection. Among metadata standards for the World Wide Web, Dublin Core (DC) is acknowledged as a pioneer in simple content description. That put it in the frame and it prevailed over various standards including Encoded Archival Description (EAD) and MARC.</p><p>Factors taken into account included simplicity for use by project staff not trained as catalogers and its interoperability with MARC. A further consideration was the growing trend for digital libraries to use non‐traditional metadata standards.</p><p>Microsoft Access database software was used to create, store and maintain metadata elements for describing the collection. Development of a metadata workform allowed staff to access the database and create and edit records via the Web.</p><p>Basic cataloging principles informed much of the work, with the first part of the metadata record descriptive and the second describing the digitized version of the original object, focusing on file size, file format and image resolution. Within the former, most descriptive elements used are qualified DC, with local qualifiers added for clarity or to avoid confusion where elements occur more than once.</p><p>In dealing with metadata elements with more than one value, the writer acknowledges that DC lacked the flexibility that enabled MARC to allow an unlimited number of added entry fields and subject fields.</p><p>Furthermore, there are no prescribed rules and methods for deploying DC metadata elements. The project team found assistance from several Web sources, including the Dublin Core Metadata Initiative and OCLC‐CORC documentation.</p><p>There was, however, a plus side to the lack of rules and rule interpretations: simplicity and easier local applications.</p><p>Guidelines on metadata deployment were developed to ensure consistency and interoperability, and the same principle informed local creation of controlled vocabulary lists.</p><p>Prairie Provinces, a Web‐based interface available in English and French, now provides access to all UAL digital collections. Among those collections, Alberta Folklore and Local History is the first digital collection implemented with DC.</p><p>The project team is convinced that the choice of metadata standard was the right one. Within each collection, DC can accommodate common attributes</p><p>while also allowing inclusion of locally developed elements that express unique features.</p><p>DC has now joined MARC in supporting discovery of and access to UAL electronic collections. Web portal developers are now looking at ways to implement a one‐stop search and viewing interface for all electronic resources.</p><p>(Précis suppplied to MCB UP Limited by consultants.)</p></sec></app></app-group></back></article></istex:document></istex:metadataXml><mods version="3.6"><titleInfo lang="en"><title>Implementation of Dublin Core at the University of Alberta Libraries</title></titleInfo><titleInfo type="alternative" lang="en" contentType="CDATA"><title>Implementation of Dublin Core at the University of Alberta Libraries</title></titleInfo><name type="personal"><namePart type="given">Erika</namePart><namePart type="family">Banski</namePart><affiliation>Erika Banski is GermanSlavic Librarian and Principal Cataloguer, University of Alberta Libraries, Edmonton, Alberta, Canada.</affiliation></name><typeOfResource>text</typeOfResource><genre type="case-report" displayLabel="case-report"></genre><originInfo><publisher>MCB UP Ltd</publisher><dateIssued encoding="w3cdtf">2002-09-01</dateIssued><copyrightDate encoding="w3cdtf">2002</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 article describes the application of the Dublin Core metadata scheme for the digital collections, the Alberta Folklore and Local History, housed at the University of Alberta Libraries. It highlights the metadata needs for describing an archival collection, a detailed metadata encoding structure, the metadata authority guidelines, and the use of controlled vocabulary. It concludes that the extended Dublin Core metadata element set derived from this project is also feasible for describing other locally developed digital collections.</abstract><subject><genre>keywords</genre><topic>Archives</topic><topic>Collection management</topic><topic>Internet</topic><topic>Library services</topic><topic>Resources</topic><topic>Canada</topic></subject><relatedItem type="host"><titleInfo><title>OCLC Systems & Services: International digital library perspectives</title></titleInfo><genre type="journal">journal</genre><subject><genre>Emerald Subject Group</genre><topic authority="SubjectCodesPrimary" authorityURI="cat-LISC">Library & information science</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LLM">Librarianship/library management</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-RMP">Records management & preservation</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-LTC">Library technology</topic><topic authority="SubjectCodesSecondary" authorityURI="cat-IREP">Information repositories</topic></subject><identifier type="ISSN">1065-075X</identifier><identifier type="PublisherID">oclc</identifier><identifier type="DOI">10.1108/oclc</identifier><part><date>2002</date><detail type="volume"><caption>vol.</caption><number>18</number></detail><detail type="issue"><caption>no.</caption><number>3</number></detail><extent unit="pages"><start>130</start><end>138</end></extent></part></relatedItem><identifier type="istex">6E2B59E77937C46399944FB877D4FD474FD6375D</identifier><identifier type="DOI">10.1108/10650750210439340</identifier><identifier type="filenameID">1640180303</identifier><identifier type="original-pdf">1640180303.pdf</identifier><identifier type="href">10650750210439340.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 000402 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000402 | 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:6E2B59E77937C46399944FB877D4FD474FD6375D
|texte= Implementation of Dublin Core at the University of Alberta Libraries
}}
| This area was generated with Dilib version V0.6.31. |  |