1. Trove Tufts Digital Image Library
Good Morning. I’m going to talk for a few minutes about Tufts Trove Digital Image Library, the Hydra Head we built to support the teaching and research needs of students and faculty in the School of Arts and Sciences and Engineering at Tufts University.
Hydra Connect 2016 Boston

2. Trove Process Ingest of images via MIRA Trove Features Demo
I’ll briefly go through the process of how we got to the point of developing a Hydra Head for Images, talk about the ingest process, Trove features, and if it all works, run through a short demo.

3. Trove - Collaboration
Trove was a collaboration of Tufts Department of Art and Art History, the Educational Technology Services Dept. (ETS), Digital Collections and Archives (DCA) and Tisch Library to create an interface to display images for study and teaching purposes.
Fundingwas secured in FY2014 and we partnered with Data Curation Experts for software development.
We modeled our concept on the functionality that was available Northwestern’s Digital Image Library

4. Tufts approach is to have a single administrative Hydra Head where library and archives staff can ingest objects into a single Fedora repository, manage metadata and control display of content in user facing Hydra Heads. Trove is a Hydra Head that manages the Dept. of Art and Art History images and Course Collections. The interface is accessible via LDAP authentication.

5. Batch Ingest into MIRA…
… Or, assembling your metadata for quality, accuracy, and timeliness
Trove went live in December 2014, just ahead of the spring 2015 semester. The Art and Art History Department needed metadata for over 1,000 slides. The plan we came up with, was that images would be provided on a rolling basis, and we would attempt to stay ahead of the class lecture schedule by 2 to 3 weeks
We needed a way to create original metadata for significant numbers of images and achieve a high degree of quality and accuracy and provide timely access
"Ford assembly line " by Unknown - image. Licensed under Public Domain via Wikimedia Commons -

6. Images viewable in Trove are ingested via our administrative interface, MIRA

7. The Solution
Our Metadata Librarian, Alex May created a workflow solution that broke metadata creation into small parts, utilizing the expertise of staff in the Dept. of Art and Art History and Metadata Services in the library.
Ingest accomplished in Three ways: Single Item Creation, Template batch ingest (new in 2014), XML batch ingest (new in 2014)
Our process involved having
Visual Resource Manager vet the content for use in classes
Her process was to select images, optimize them, input accession numbers into Excel spreadsheets and distribute to Art and Art History Students
Who fill basic metadata fields, and provide key words for subject analysis
The images and spreadsheets were then sent to metadata staff in the library to review spreadsheets, and provide subject analysis and QA

8. The Solution
Metadata librarian transformed the completed spreadsheets into Dublin Core
Using xslt to create DC records
Creates an internal audit log
He ran scripts to ensure that the Records were ISBD compliant, and also provided additional levels of QA, like checking for spelling of common words, and checking the subject terminology was is in the correct format.
He took the XML files to ingest into Fedora via MIRA for Display in Trove

9. A Successfully ingested batch
This Workflow was able to play to the strengths of Art and Art History Students, the library metadata staff, and took advantage of scripting routines that could enforce consistency in spelling, punctuation and metadata display.
The end result was that we met the needs of Art and Art History without straining the resources of either department
Over 1,200 images had original metadata created and were ingested in a 5 month period

10. So here’s the entry page to Trove
So here’s the entry page to Trove. The features our users wanted was the ability to create course and personal collections

11. The ability to create a hierarchy or nesting of collections, and the ability to drag and drop images into a collection.

12. They also wanted the ability to display images in a list view

13. Display a list or gallery view

14. Ability to edit collections – to reorder images within a collection and to remove images from a collection

15. And have the ability to copy or download a collection for study and teaching using powerpoint or pdf formats

16. DEMO

17. Thank You! Alicia Morris alicia.morris@tufts.edu