UC Libraries Digital Preservation Repository Timeline

I. Development Phase (Through Early September 2004)

1. Focus is on core digital preservation repository functions: ingest, administration, access.
2. Policy development occurs parallel to software development.
3. Documentation is being developed for internal California Digital Library use and for users.

II. CDL Pilot Phase (September-December 2004)

1. Core development of digital preservation repository will be complete and ready to test in September. The CDL will test the functions and documentation of the digital preservation repository by ingesting master images from the Local History Resource Project. During this phase, enhancements to the system will be evaluated, prioritized, scheduled, and implemented. Hardware installation will be completed.
2. Additional policies and documentation will be developed, including correlation with the new CDL digital object standard, which is slated for release in spring 2005.
3. Materials will be developed to enable campuses to add their own Java layer to the repository if they choose to do so.
4. Needs assessment, presentations, and training will take place for UC Davis, UC Irvine, UC Merced, UC Riverside, UC Santa Barbara, and UC Santa Cruz.
5. UC Berkeley, UC San Francisco, UC San Diego, and UCLA will be given training so they can begin depositing content in the digital preservation repository as a small pilot phase starting in January.

III. Campus Assessment and Pilot Use Phase (January 1-March 17, 2005)

1. Four pilot phase campuses will begin to use the digital preservation repository, providing the CDL with feedback on system and supporting documentation. The CDL will evaluate and prioritize suggested software and documentation enhancements, then scheduling and implementing changes.
2. Six second-phase campuses will receive training to enable them to deposit content starting in March. Outreach and education will continue on all 10 campuses. Communication plans will be developed for release in March.
3. Additional policies and documentation will continue to be developed. Feedback about existing policies and documentation will be collected from the campuses, with revisions evaluated and made accordingly.

IV. Full Rollout (March 2005 forward)

1. Input will continue to be collected from all participating campuses. Software, documentation, and policy changes will be evaluated and scheduled as needed.
2. Feedback from the continued implementation of policies will be gathered and assessed.
3. Education and outreach will continue within UC and to the wider digital library community.