Yale VITAL/FEDORA Repository IAC Update 30 Oct 2006 Audrey Novak, Head IS&P, ILTS

Presentation Outline Why a Repository? Status of VITAL agreement VItal Network of ExpertS (VINES) Update on planning Repository examples

Why A Repository? Identified Need: IAC report on digital repositories: Identified the need to “ find homes for digital collection that have proliferated throughout campus and for which the Library has been given or must take stewardship responsibility in order to organize and provide access to digital collection to ensure infrastructure for long-term preservation. Rescue Repository and Digital Preservation Committee: Foresee a permanent preservation environment within three years, i.e., by 2008

Why A Repository? Identified Need, continued: VITAL Research Project: Recognized the establishment of a trusted repository and long-term digital preservation as key requirements in the design of our information architecture. DPIP: Cited the need for a robust library repository that is capable of accepting material in multiple formats (images, full text, audio, video, data sets, etc) and achieving global integration of available resources.

Why A Repository? Abundant Content: AMEEL Collections Collaborative DPIP ERA Project Finding Aids migration OAI projects Rescue Repository migration Social Science Data Set migration Teaching and learning initiatives (Sakai classesV2, Davis) Yale Daily News Yale Indian Papers More ….

Why A Repository? Intrastructure & New Services: Managed, secure content Customized presentation Searchable full-text content Display of high resolution imagery, multi-page documents and specialized data formats Persistent, citable access Integration with other environments and functions (classesV2, federated searching, University and departmental portals) Digital Preservation Content repurposing  Aggregation, knowledge integration, transformation More …

Why A Repository? For Our Readers: Increased consistency in presentation and cataloging within the repository will make it easier for readers to navigate within our services and find resources. Increased integration within the repository will make it easier for readers to discover resources across collections. Persistent identifiers will give readers the ability to use lasting citations. The presentation of multiple formats (images, full text, audio, video, multi-page documents, data sets, etc.) will enrich readers ’ experience by making available a fuller body of resources for teaching, learning and research. Integration with other environments and functions such as classesV2, federated searching, University and departmental portals will make library services available to faculty and students when they need it and where they need it to support teaching and learning.

Why a Repository? For Our Readers, continued: Beyond content, i.e., beyond collections this repository, and specifically this architecture will position YUL to respond to key themes emerging in the e-teaching/learning/research environment. Those themes are: Services (not packaged applications) Architecture of participation Remix/transform data sources Harness collective intelligence  (Sandy Payette,

Why a Repostiory? Identified Need Abundant content Improved infrastructure and new services Better meet and anticipate our readers ’ needs for teaching, learning and research

Agreement Status Review by University General Counsel concluded last week Next: Review by Procurement and negotiation of changes with VTLS Signatures – first half of November

VItal Network of ExpertS (VINES) Creative and pioneering recasting of the library/vendor relationship. Development collaboration Empowers us to define the development path of VITAL Membership includes paid customers, integrated solution partners, e.g., FEDORA Project, and leading thinkers and organizations in this field Taskforces are the engines for VINES initiatives 40 VTLS development hours (approx. 100 staff hrs.) Option to purchase additional development time Ease burden of making hard choices among the many priorities that vie for local technology resources

Update on Planning Dual challenges Steep learning curve Urgent demand for immediate yet complex solutions Repository Service Structure Charges Membership

Repository Service WORKING GROUP Project Management Team VINES Project Task Force Project Team

Operational Plan Implementation broad strokes: Knowledge transfer, project preparation, requirements refinement, discussion throughout YUL Configure and refine VITAL/Fedora Establish public jumpstart service (a generic service with basic repository functions and a basic support structure, intended for use by broadly for any collection for resource management, search and retrieval) Development process (driven by individual collection needs): Iterative process of establish requirements, project analysis, design, development & implementation, testing, deployment, support, review, update best practices.

Q&A