This page presents a summary of work completed during the UCLDC implementation project, July 2013 - September 2015, plus key "historic" pages and information.


The UCLDC Project resulted from several years of planning across the UC Libraries. The planning process began in 2009 with the cross-campus Digital Libraries Services Task Force (DLSTF), which articulated a vision. A subsequent task force (DLSTF2) continued the work of scoping a digital collection service and formulating a plan for how to get there. Finally, Next Generation Technical Services (NGTS) Power of Three Group One (POT1) coordinated several “lightning teams” focused on various aspects of implementation. Two lightning teams in particular most directly shaped the direction of the service and the technologies implemented: LT1A (which drafted requirements for a systemwide DAMS), and LT1C (which put forth a technical model and selected Nuxeo as the "first step towards a systemwide digital asset management system strategy").


The UCLDC project team comprised staff members at CDL and UC Berkeley's Research IT unit. See complete list. The project team reported to SAG2 and obtained additional input from a Project Stakeholders Group. Many campus collaborators also worked on aspects of the project such as the migration and harvest of collections, and provided constant feedback and ideas. Thank you to everyone who helped us realize the vision of building a shared service for managing, aggregating, and surfacing digital collections.

Timeline and Deliverables

The UCLDC Implementation Project began in the summer of 2013, and concluded in September 2015 with the public launch of the Calisphere BETA site. 

Key project deliverables included the following:

Source code for all of the above is available at the UCLDC github repository.

For a detailed list of lightning team 1A requirements met by the project, please click here to download.

Content by the Numbers

The project resulted in the successful migration of many collections into the DAMS, as well as a significant growth in the amount of content aggregated and shared with the public.

Releases and Reports

Project development work was staged as a series of releases (approximately quarterly); releases were named after UC campus mascots/nicknames.

Workspaces charted out the plan, and release notes summarized the work completed. Status reports were provided to SAG2 at first according to project sprints and later monthly or as requested.

Date of releaseRelease nameDocumentsSAG2 Status Reports
2013 - June(Project planning)

Weekly tasks completed

2013 - NovemberAggie


Release Notes

8/22/13 - 9/11/13

9/12/13 - 10/2/13

10/3/13 - 10/23/13

2014 - MarchAnteater


Release Notes

10/24/13 - 11/19/13

11/20/13 - 12/11/13

12/12/13 - 1/15/14

1/15/14 - 2/3/14

2/3/14 - 2/28/14

2014 - JulyBanana Slug


Release Notes

3/3/14 - 3/21/14

3/24/14 - 4/11/14

4/14/14 - 5/2/14

5/5/14 - 5/23/14

5/27/14 - 6/20/14

2014 - SeptemberBear


Release Notes

July 2014

August 2014

September 2014

2015 - DecemberBobcat


Release Notes

October 2014

November 2014

December 2014

2015 - JanuaryBruin


Release Notes

2015 - MarchCaduceus


Release Notes

February 2015

March 2015

2015 - MayGaucho


Release Notes

April-May 2015

2015 - JulyHighlander (Calisphere beta soft launch)


Release Notes

June 2015

2015 - SeptemberTriton (Calisphere beta public launch)


Release Notes

July 2015