Digital library infrastructure -- systems Repositories for storing digital resources protect, manage, deliver, and preserve digital resources over time Discovery services for finding digital resources catalogs, portals, full text search services, federated search agents Access management to protect digital resources authentication, profile information, “fewer sign-ons”

Digital library infrastructures -- services Digitizing –facilities, expertise, and on-demand services to convert materials to digital formats Object management –store, protect, and serve digital resources Preservation –maintain availability and/or viability of digital objects over time as technology changes Metadata –create and maintain metadata required to describe, render, manage, and preserve digital objects

Digital library infrastructures -- expertise Metadata –advise on formats and conventions for descriptive, technical, and administrative metadata as used in various communities Digitization –advise on technical formats, good practices, conversion hardware and software, and conversion workfows Intellectual property –advise on copyright and license issues related to digital information, both procured from outside and created within the university

Some areas of overlap with academic IT Institutional repositories –who is responsible for housing, providing access, and preserving the digital assets created within the university? Learning management systems –relationship between “e-reserves” systems and LMS? –can LMS utilize digital objects stored in digital library repositories? –Should course web sites be archived and preserved? Authentication, profiling, “single sign-on” –Pretty obvious….

Some areas of overlap with academic IT Supporting scholars and students in creating digital objects –who provides advice on appropriate formats, metadata, conversion technologies and workflow? Portals –library resources should be configurable and delivered through the same mechanism as any other campus resource Large-scale storage systems –digital libraries generate LOTS of large objects, many of which are archival rather than current service copies