Islandora 2.x Repository Profile: University of Nevada, Las Vegas Special Collections and Archives

Question responses were provided via the Repository Profile Form by Emily Lapworth, Digital Special Collections and Archives Librarian, on November 30, 2023.

Questions

Tool and version, if applicable

Islandora 2.x

Type of archives or special collection library?

University special collections

When and why did you adopt this tool?  What system did it replace (if any)?

The goal was to replace CONTENTdm but also evolve our metadata processed to RDF, and improve flexibility, scalability, and digital preservation capabilities of our DAMS.  After a dedicated application developer was hired in 2017, the task force decided to adopt Islandora because it could be customized to meet all our goals, and it is based in Drupal, which is what our library website uses and what library IT staff are already familiar with. Drupal and Islandora are open-source software with active user communities. UNLV publicly launched its Islandora 2.x site in 2021.

Briefly explain how this tool functions at your institution (e.g. do you only use it for accessioning, or does it fill all the functions from accesioning to public access?)

Currently it is used for public access and storage of digital objects and metadata. A future goal is to develop it to also be used for preservation.

What pre-installation/migration preparations were taken to facilitate implementation of this tool?

UNLV’s application developer contributed to developing the core code of Islandora 2.x starting in 2017, and the initial public release was in 2019. He also developed customizations for UNLV and worked with Special Collections and Archives staff to design the public user interface of our local installation. Librarians audited files, developed a new metadata application profile, remediated metadata, and created ingest spreadsheets to migrate content. Digital files and metadata were migrated to UNLV’s new Islandora DAMS from 2019-2021. Usability testing was done on the system in 2021.

What degree of IT support was needed to implement and migrate into this tool?

High

Is your collection management tool hosted on-site and in-house or off-site by a vendor?

On-site and in-house

Please describe significant post-implementation challenges using the administrative and/or public interfaces.

UNLV’s main challenge was that our lead application developer position that is dedicated to Islandora was vacant for over a year after the public launch. Islandora consists of many different interdependent pieces of software and modules that are updated all the time, so updates and further development work were largely put on hold for over a year, causing some issues with the staff and public interfaces.

Is your institution integrating this tool with other automated request, preservation, or digital asset management systems?

It is integrated with ArchivesSpace to allow display and search of finding aids and agent records alongside digital objects. An automated script updates the Islandora site with any additions, revisions, and deletions made in ArchivesSpace on a regular basis.

In what ways has using this tool been an improvement over your previous tool or finding aid access strategy?

Archival description and digital objects are displayed and searchable on the same website instead of multiple separate sites. It is more flexible and allows for more customization than CONTENTdm.

What is your most favorite feature of this tool?

How customizable it is (specifically, it allowed us to build a unified search interface), and the collaborative user community

What is your least favorite feature of this tool? 

The IT knowledge required to support this system (if you are hosting it in-house)

Lessons Learned, or tip for prospective users? What is your least favorite feature of this tool?

Islandora is an open-source software framework that requires IT support either locally within your institution, or contracting with a vendor. You can implement a more standard or “out of the box” version of Islandora, or, if you have the resources, your DAMS can be highly customized. Either way you also have the opportunity to collaborate with an active user community that shares modules, strategies, and advice.

What features would you want to see added to this tool in the future?

A less static, more dynamic public interface with easier navigability throughout a collection's hierarchy.