6. Digital Library/Preservation

Anne Kenney

Pat Court, John Saylor, George Kozak, Peter MacDonald, Peter Hirtle

6.1 System should support . . .

Web interface to display full text resources (text files, digital images, numeric data, multi-media) and provide text-only capability for low-end CPUs/monitors.
hot-link pointer from bibliographic records to finding aids and directly to full-text resources produced by Cornell or those from outside sources.
links between associated text, image, and multimedia files. Links should exist, for example, between a bitmapped image of a page, the page as text after being converted by an OCR engine, and annotations of the image/text made by students, faculty, or the public.
migration of link information connecting bibliographic records to other resources or linking related full-text resources, must be transferable into an open, standard, database environment. In other words, no proprietary links will be allowed unless there is a method for exporting the link data into a different, open environment.
"intuitive" access to online journals, monographs, and other resources.
access to Z39.50 compliant full text resources.
intra-institution and inter-institutional database search and retrieval capability. This would be from Cornell's LMS to other repositories of full text materials, including consortially developed digital collections.
use of sophisticated searching, retrieval, and display options specific to individual full text sources. LMS should allow for local tailoring of indexes and display of search results.
variety of application capabilities to enable end user to display and use full text sources in manner appropriate to their research needs and computing/networking environment (including processing software, image viewing software, etc.).
back and forth links between LMS and full text resources.
contextual/directional references in all LMS windows/levels.
history of search capability; replicable searching strategies.
data manipulation capability
print and downloading capability and support
batch search and retrieval.
user feedback capability
authentication, copyright and other use rights management system, and financial accounting systems
reporting on full-text resources and use (LMS must be capable of generating statistical and error reports for delivery of full text resources, including tracking of copyright and restrictions on access, site licensing agreements, queuing of material for retrospective conversion, archiving status of full text sources, ability to distinguish parts of a collection with full text delivery capabilities
preview capability for digital resources, i.e., a test system for staff use only.
interface with scanning hardware/software, file management system running on high performance network and interface with server software storage and retrieval of material based on use (e.g., HMS capability with caching of high use items)

Back to LMS Committee Page | StaffWeb Index

ark

rev. 7/24/97 dih