🛈 Wiki Tips

(1) Is your name in Wiki displaying only your last name? Or is your name in Wiki displaying as you user account id? Need to update your name in Wiki so colleagues can find you? Want to upload a photo? See Personal Settings in the updated FAQ in Wiki Help.
(2) Can't find a user to add to your wiki space? See what you can do when User cannot be found via search .
Child pages
  • Bear (Fall 2014) Release Notes

This is a public wiki space. All contents are publicly accessible unless page restrictions are in place.

Skip to end of metadata
Go to start of metadata
(info) To more easily browse these notes, collapse the side bar using the << icon in the bottom-left of the page.


Want the 3-minute rundown? Watch the video summary:

Major Release Features and Accomplishments

1. DAMS upgrades

Since releasing the shared Nuxeo DAMS in July of this year, we've continued to improve the interface and functionality of the system. In some cases, we were already aware of and planing the upgrades, but in others, we were alerted to issues by campus partners. We responded by making the following improvements to the DAMS:

  • Enhanced the 'Description' metadata field. It is now repeatable, and it carries an accompanying 'Type' field which campus partners can use to qualify the description.

  • Added 'Extent' and 'Transcription' metadata fields, which campus partners can use to further describe their objects.

  • Enhanced Nuxeo's Bulk Edit functionality so it relates to the UCLDC metadata model–meaning campus partners can now add or change metadata for any field(s) across a large quantity of objects.

  • Enhanced Nuxeo's Faceted Search so it relates to the UCLDC metadata model–meaning campus partners can now hone their searches on specific metadata fields and folders.

  • Enhanced Nuxeo's Advanced Search so it relates to the UCLDC metadata model–meaning campus partners can now perform advanced searches on any field in the model.

2. Training and consultation with DAMS users

During this release cycle, we provided training and consultation to librarians. We traveled to six campuses, where we presented the project to all interested stakeholders, and then held a more in-depth "deep dive" for staff who will be using the DAMS. These sessions were designed to familiarize staff with the system and to kick-start the process of identifying additional issues and feature requests. We challenged each campus to start building at least one collection (objects and metadata) in the system, so we can continue to refine and improve it. This will be our focus in future releases.

3. First collections harvested

As of this release, we have preliminary but operational harvest feeds going for two platforms–the Nuxeo DAMS and UCLA's Islandora platform–and have started working with UC San Diego to obtain data from their repository. The harvest is not only grabbing metadata, but also images (for image objects). This will allow visitors to the new Calisphere site to see representations of both hosted and harvested content in the same interface; for example, they can browse thumbnails for all the content retrieved in a given search, without regard to where the object is actually hosted. (Users will ultimately be referred to the local hosting platform to interact with and obtain information about a harvested object.)

4. A prototype of the public interface

A major focus of the Bear release was to turn our ideas about the UCLDC technical stack into reality. We developed an initial prototype of the public interface to test our model and start to identify the specific technologies we'll be employing to actually build the new Calisphere site. For example, we identified an "image viewer" we'll use to display image-type objects in the new site. The prototype is also showing data in the index that has been harvested. In short, the prototype is our first step towards fully realizing the vision of aggregating and displaying the UC Libraries Digital Collection.

5. Graphic design direction

In August, the UCLDC team began working with a graphic designer to revamp the look and feel of the Calisphere site and apply styles to the new wireframes. We have decided on the major "design direction," which includes logo revisions, colors, and general design decisions that will be integrated throughout the site. A sneak peak of the new homepage and some other design elements are shown in the video, above.

Other work completed

In addition to the more visible features described above, we made progress in several other areas:

  • Continued loading retrospective collections into the DAMS (4 more collections added in this period)
  • Conferred with UC Santa Cruz on the development of an Omeka plug-in that pulls in Nuxeo objects
  • Developed an initial strategy for a workflow for sending objects from the DAMS to Merritt, in consultation with UC3
  • Rebuilt the common Solr index with updated collection information and technical enhancements
  • Identified priority needed improvements to the Collection Registry
  • Altered the display of entries in the Collection Registry to better show the scope of collections in the UCLDC
  • Completed all desktop wireframes for the public interface
  • Created initial documentation for use of the Solr API, using queries performed for the prototype
  • Determined a plan and process for the first activities involved in developing the site, in consultation with CDL Web Production
  • Began initial thinking about the transition from the current Calisphere to the new site, after launch (including planning around moving to Amazon Web Services for data hosting and creation of an inventory of Calisphere content)
  • Investigated use of the IIIF standard for serving up images on the new site and began installation of a compliant image server
  • Expanded the reach of the project to a wider group of UC Libraries stakeholders through presentations at campus visits


We welcome your feedback on this release. Please send any comments and questions to ucldc@ucop.edu.