The UCLDC Implementation Project Team is pleased to announce our second release: "Anteater." (Why this name?)
The primary goal of this release was to establish processes for batch-loading files and metadata into the Nuxeo DAMS, and subsequently to begin the work of loading the collections we have obtained so far. We also worked closely with the UCLDC Product Stakeholder Group to refine the scope and requirements of the public interface. Other features and work completed are explained below.
We welcome your feedback on this release. Please send any comments and questions to email@example.com.
Below are the major features of the release, with video demos and links to explore further, where available. For background on the project, please see the Overview of UCLDC Implementation.
NOTE: to more easily browse these notes, we recommend collapsing the side bar menu using the icon in the bottom-left of the page.
First collections loaded into DAMS
One of the objectives of the UCLDC project is to "seed" the DAMS with a selection of existing collections (identified by a POT1 lightning team). We have determined a process for batch-importing these collections, which includes loading and then matching files and metadata records.
Using this process, we have moved forward with loading the first collections into the DAMS. As of the date of this release, we have loaded at least some content--with varying levels of metadata--from four campuses: Davis, Irvine, Merced, and Riverside. A "snapshot" list of the collections in the pipeline is available on the page "DAMS collections in process."
We will be continuing to load existing collections into the DAMS on an ongoing basis; we are on track to have all of the collections on the above list in the DAMS by later this calendar year.
DAMS configured for UCLDC object types, metadata
We also configured the Nuxeo user interface so these options now appear in the platform.
Index up and running with test harvest data
The common index will aggregate UC Libraries collections from the Nuxeo DAMS and a range of distributed platforms such as campus-hosted systems and third-party websites like the Internet Archive. Although we are still determining the best methods for harvesting metadata into the index, we have been able to move forward with building out the index using test data obtained through existing OAI-PMH feeds to target collections.
For this release, we have established a mechanism for triggering a harvest of a collection, started setting up the index and its related API to support the public interface, and experimented with metadata enhancement techniques.
Public interface requirements unpacked
Another major push during this period was to understand, define, and start to prioritize the requirements for the UCLDC public interface, working closely with the UCLDC Product Stakeholder Group. During an all-day meeting with this group in January, we made some key decisions (for example that content harvested from external systems will have a "landing page") and uncovered some key needs and priorities (for example, campus landing pages on the website and a long-term interest in providing curated and/or customized views of content)–learn more. This research has helped set us up to move forward on defining the scope of the UCLDC public website at launch and on developing wireframes for the user interface.
For this release we also identified human resources for interaction design/user experience.
Other work completed
In addition to the more visible features described above, we also made progress in several additional areas:
- Improved the user interface for the Shibboleth campus-picker, for users who log into the Collection Registry or Nuxeo
- Completed Nuxeo training to gain in-depth knowledge of the platform and configuration options/techniques
- Began analysis of the Nuxeo user interface and customization options, to optimize the user experience for campus library staff
- Began mapping out the relationship between the collection registry and the public interface
- Developed an approach towards merging Calisphere and the UCLDC public interface
- Customized the Solr API to meet the metadata schema and some major known public interface requirements
- Streamlined project management and reporting by utilizing Pivotal Tracker
- Fixed a Shibboleth issue for UC Riverside, so staff members can now log into Nuxeo and the Collection Registry
- Discussed terms of service/submission agreements to ensure consistency with other CDL and UC libraries policies