320 likes | 331 Views
Automated building blocks for digital libraries to create, manage, and present high-quality collections, encouraging customization and interactivity. Learn about the CDL Common Framework and its applications.
E N D
Digital library building blocks: Empowering libraries in an increasingly competitive online information space Daniel Greenstein and Peter Brantley California Digital Library Presentation to CNI, April 5, 2005
Lowering the costs involved in building high-quality trusted collections… with a suite of web-accessible services that libraries and other information organizations can use to • create and gather collection content that their users require • organize and present that content in ways and with tools that meet their users’ needs • manage the content persistently over the longer term
Encouraging with guidelines tools, and support services, the production of persistent and interoperable digital content
Automating incorporation of that content into access services and digital persistent repositories
Enabling customization and interactivity with authoring, editing, exhibit-building, and export tools To be supplied…
Some use cases for digital library building blocks • A public library [historical society/museum/academic department] wants to digitally reformat selected materials from its special collections, publishing them to the web via a local service and integrating them into one or more larger collections • A government agency [academic institution/university or society publisher or press] wants to enable staff [faculty/authors] to “publish” papers, monographs, journals, etc to the web in an orderly manner • A research organization [library/archive/historical society] wants selectively to capture, organize, and manage selected web-based materials that are critical to the organization/users it serves • A curriculum development specialist [museum curator/academic publisher] wants to wrap a variety of primary sources, all of them available in digital form, in a narrative web, presenting them to end users as learning materials [exhibits/textbooks] with a variety of interactive features
CDL Common Framework • The CDL Common Framework - • Is a philosophy governing software development • … a conceptual design for digital library services • … a specific technical architecture • … a set of developed services • … growing number of applications
CF Philosophy • Composite, modular, lightweight are good words • Design and implement quickly • Reduce need for app-specific kludges • Make replacement and enhancement easy • Encourage staff training, development • Perfection is not allowed
CF Conceptual Design • Elemental services conceptualization • E.g.: “search”, “AuthZ”, “admin”, “harvest” • Applications independent of services • Design to enable build, rebuild apps • New app « reuse existing services (or minor mods) • Services change, apps version
CF Technical Architecture • Common development environment • Web services based (XML, Java) • Preserve generic design in specification • Cleanly separate API (interface) layer • Services agnostic on system vs. user interaction • Externalize data mods to XSLT when possible
CF Services • CDL has defined and prioritized services • Preservation repository first CF application • Services such as ingest, search, view, admin built • Design review with campuses inits change reqs • CF permits very rapid change/build cycles
CF Applications • Applications are released products • Comprised of packaged (or suites of) services • Preservation repository (DPR) • eXtended Browse Framework (XBF) • Product evolution yields new services