Mounting a Finding Aids Collection
From DLXS Documentation
Mounting a Finding Aids Collection
These instructions assume that you have already encoded your finding aids files in the XML-based EAD 2002 DTD. Only you, after looking at your texts and your encoding practices, can do the intellectual work required to encode your finding aids in XML using the EAD 2002 DTD. While DLPS does not have any quick and easy tools for this stage of data preparation, we do have a recommended model: the Bentley Historical Library. The more similar your data and setup is to the Bentley’s, the easier is will be to integrate your finding aids collection with DLXS. DLXS does not support the process of creating new finding aids files: how you do this is you to you. The Bentley Historical Library, however, provides a discussion of some specific tools and a workflow process you might use to create these files. See X section. [again, refer to Bentley doc?]
This topic includes the following sections:
• Findaid Class and Behaviors Overview • Setting Up the Collection: Practical Issues • Preparing Data and Directories • Building the Index with XPAT • Working with Fabricated Regions in FindaidClass • Mounting the Collection Online • Linking from Finding Aids Using the ID Resolver • Using Findaid Class Graphics Files • Findaid Class Processing Instructions
Findaid Class and Behaviors Overview
The Findaid Class consists of EAD2002-encoded Finding Aids. You can learn more about the ead2002 DTD and ead2002 in general at the Library of Congress ead2002 web site. The Findaid Class relies on a single XML Document Type Definition (DTD) file to deliver all collections in the class. This file is essentially identical to the ead2002 DTD with one extra wrapping element added. DLXS then uses XPAT to index the XML and the Findaid Class middleware makes it possible for users to search the resources on the web. The behavior of the Finding Aids Class is similar in many ways to that of Text Class. Access minimally includes full-text searching across collections or within a particular collection of Finding Aids, viewing Finding Aids in a variety of display formats, and the creation of personal collections (a “bookbag”) of Finding Aids. The general characteristics of the Finding Aids class are the following: • Allows search and retrieval of ead2002-endcoded Finding Aids and portions thereof • Allows searching across multiple collections of Finding Aids simultaneously • Allows searching of each collection independently • Allows bookmarking of individual Finding Aids • Requires minimal administrative data • Uses a single data model and shared middleware for all collections in the system • Permits access restrictions at the collection level The Finding Aids class provides no functionality for creating and managing electronic texts in SGML. Findaid Class Behaviors The Findaid Class is typically used for either campus or public access. Its behaviors include the following: • Cross-collection searching in any combination of collections • Selection of collections • Collection-specific searching • Collection-specific browsing of • Simple and Boolean searching • Searching within a user-selected Finding Aid • Ability to review and revise previous searches • Viewing of sections of a Finding Aid or the full text in HTML, and display in context of search terms found • Ability to select particular Finding Aids for saving in a session-based personal collection, or bookbag, and to download or email these • Keeping a record of user search history during a session Representative Resources Bentley Historical Library Finding Aids [case study—can we use more directly?] University of Michigan Special Collections Finding Aids
