Last updated 2003-03-04 09:40:22 EST
Doc Title Basic Overview of the Bibliographic Class
Author 1 Hagedorn, Kat
CVS Revision $Revision: 1.6 $
Basic Overview of the Bibliographic Class

The Bibliographic Class includes a range of descriptive metadata, from the minimal (cf. Wing) to the expansive (cf. MARC records or information extracted from the TEI Header). Entities in this class have a relatively flat structure (i.e., no nesting) and a high degree of relational organization in the way that they use controlled vocabularies or name authorities. Most instances within the Bibliographic Class are collections of bibliographic citations, but may also be collections of entries describing entities other than books or journal articles (e.g., coins, photographs, ostraca, or other objects). The primary behaviors of the class are relatively limited, focusing primarily on searching, display, and management (e.g., collecting together citations of primary interest from a much larger collection of valid citations). Entities in the Bibliographic Class are typically displayed as brief citations or more expansive citations, with and without field labels, and in different formats suitable for different purposes (e.g., downloading). While issues such as display are simple compared to texts, users have come to expect more sophisticated methods for navigating and managing large numbers of results, e.g., sorting on different indexes, or using a "shopping cart" model of collecting the information together for subsequent uses. For more information on the range of bibliographic resources supported by this Class, as well as "tensions" implicit in the Class's definition, please see Representative Resources.

The DLXS Bibliographic Class was not intended to replace robust, large-scale bibliographic systems like the library catalog, but to accomplish resource discovery across a large body of bibliographic information managed outside of large integrated library systems. Implementation is relatively simple and therefore extremely cost-effective (typically more cost-effective than a similar implementation in an integrated library system), and because of this the DLXS Bibliographic Class may have continuing value as a cost-effective system for databases like Wing or the indexes to the London Times and New York Times. Nevertheless, we believe that the opportunity for much tighter integration of full text resources and the library management systems may make many applications of the DLXS Bibliographic Class obsolete.

Related Resources

  1. Bibliographic Class DTD
  2. Representative Resources
  3. Testing Procedures
  4. References: No publications have been written about use of the Bibliographic Class.

Notes on Nomenclature:

Bibliographic indexes are referred to as "collections" for the sake of convenience. A bibliographic index, or collection, consists of all bibliographic fields in SGML or XML format, conforming to the bib.dtd.
We use the term field to describe any bounded and named area of searchable information in a bibliographic collection. Most will correspond to elements in the SGML or XML DTD (e.g., the YR element, used for date information), but fields may also correspond to a searchable attribute, tag, or some "synthetic" body of information such as a subset of elements containing specific information. In XPAT syntax, a field is referred to as a region.
We use the term index to describe any machine-built searchable indexes created by xpatbld, including xpatbld's word and phrase indexes and its "region" indexes (i.e., for searching SGML/XML elements and attributes as containers of information; see Field, above).

Planned Additions and Enhancements to the Bibliographic Class

Bibliographic Class enhancements and additions include:

  1. Word wheel: The word wheel functionality currently available in TextClass will be incorporated in a subsequent release of the Bibliographic Class.
  2. Search by most recent records: This has been implemented for the Bibliography of Asian Studies and may be added in a future release.
  3. Open Archives harvesting capability: Support for the Open Archives harvesting routines has been implemented in the broker.