Collection Loader

Summary

Directed the end-to-end creation and launch of a new automated migration tool from initial concept to product rollout. 35+ institutions have utilized this tool to publish 10,000+ items, exceeding adoption goals by over 10% and generating over $60,000 in revenue.

0
Institutions
0
Artifacts
0
Revenue

TL;DR

Goal

Create a simple and intuitive tool for libraries and cultural institutions to publish their digital collections for wider reach.

Roles

  • Design sprint facilitator
  • Concept designer
  • Concept test facilitator
  • Visual designer

Process

  • 3 day design sprint
  • Concept test of low fidelity screen designs to encourage candid feedback and open the door for spontaneous suggestions.
  • Usability test of a working prototype, aiming to evaluate usability and measure interest in adopting the tool.
  • Distilled the key elements from the early adopter phase to create visual and interactive design for a viable product.

Design sprint

The core product team spent 3 full days together, focused on problem definition and solution ideation.

Identified

  • Key risks
  • Focus areas
  • Design principles

I synthesized the sprint outputs and developed an initial concept to validate with users.

Core product team

  • Product Manager
  • Product Designer (Myself)
  • UX Researcher
  • 4 Engineers

We consulted relevant experts including a Metadata Librarian, Data Governance Director, Product Marketing Director and VP of Open Collections to inform our direction.

Low fidelity concept test

We presented low fi concepts to participants to encourage candid feedback and open the door for spontaneous suggestions.

The marketing email was crucial for testing. We needed to provide a realistic preview of what our new product to gauge interest.

Starting point

To understand how potential users wanted to begin using the Collection Loader, we showed side-by-side options of two approaches. Would they prefer starting from the overall structure and themes, or focus instead on the media objects and metadata?

This comparative format sparked a valuable dialogue about the merits of each and gave us tangible insights into real user preferences.

User control

Mapping metadata is arguably one of the most important steps in the publishing process.

The system is showing how it interprets the metadata from the user and allows them to make changes.

Another crucial step in the process is to set up how the collection will be presented to scholars. Here we explored what types of tools and context they would like to provide a scholar when visiting their collection

Early adopter program

Twenty five institutions participated in overview sessions, while fifteen institutions trialed the Collection Loader tool.

Despite—and because—the Collection Loader tool being in development throughout this program, participants provided valuable insights that informed product and development priorities.

  • Aligned the product design closer to the needs of the user.
  • Pinpointed critical pre-launch issues for resolution.
  • Validated workflow, design, and opportunities for improvement.
  • Created an FAQ to equip the support and onboarding teams.

“This process is amazing for us. I used to use CONTENTdm and would set it up to upload overnight. I could do the same [with Collection Loader]— load it at the end of day. This works for us! Donors complain: Why isn’t it up? And here I have control.” —Megan, Southwestern University

Launch

30 institutions have utilized our tool to publish 9,867 items, estimated $60,000 in generated revenue