Power in Partnerships: The Unified Hub

In our introductory post, Power in Partnerships: 3 Models for Sharing a Museum Collections Management System we explored how a creative partnership approach can offer a multitude of benefits, including: bigger buying power, inspired cross-institutional work, and amplified collection discovery. This post will focus on the most integrated version of this approach: a single, shared database. A unified hub.

What is a Unified Hub?

A Unified Hub is the most integrated approach to shared collections management. In this model, multiple institutions operate within a single, centralized database. Instead of each museum maintaining its own local server, negotiating individual software licenses, and hiring dedicated IT support, this partnership shares a unified infrastructure.

The hub at-a-glance is:

• The most integrated partnership approach.
• 2+ institutions within 1 shared database.

Two Flavors of the Unified Hub

A shared database has two flavors. The choice of flavor is dependent upon the robustness of the system to support nuanced permission restrictions and the ability to support different catalog forms and processes.

1. In simpler Collections Management Systems, the data is co-mingled and there’s no ability to apply nuanced restrictions, nor the ability to support different forms for data capture.
2. In more advanced Collections Management Systems, there’s the ability to put partitioned access in place, set up similar but different catalog forms, and support similar but institution-specific processes.

For the latter, it can help to think of it as a professional co-living space for your data: you have your own private room (your data partition), but you share the high-end kitchen and utilities (the server, software, published portal) that might otherwise be too expensive to afford on your own. With a partner, you can afford more when it comes to your Collections Management System (CMS).

The Model in Action: The Danish Natural History Museum Consortium

The gold standard for this model is the Danish Natural History Museum (DiSSCo) consortium. This nationwide initiative utilizes a centralized CMS implementation. This partnership includes a variety of institutional sizes: from massive university institutions to smaller regional sites, all three Denmark natural history museums operate within the same system. By hosting a single web-based instance, the consortium eliminates the need for each museum to have their own CMS. But this isn’t just about convenience or cost-savings; it’s about the global connectivity of their data. Because they are in the same system, their data is automatically “hard-wired” for sharing with international research networks like the Global Biodiversity Information Facility (GBIF). This means that a small regional museum in Denmark has the same digital megaphonic reach as a major national institution.

The Partnership Edge: Why Go Unified?

For the modern museum professional, the benefits of the Unified Hub are transformative:

• Massive IT Cost Savings: By consolidating server hardware and administrative roles into one CMS, institutions can afford more—aka a better system. Or they can choose to redirect their savings toward other areas.
• An Increase in Technical Capacity: This model can significantly increase the technical capacity for each partner museum and improve shared expertise among staff.
• Standardized Data Quality: Operating in a shared environment naturally encourages (and often requires) a unified cataloging protocol. This ensures that data is consistent across the entire network and helps to ensure cross-institutional projects seamless.

The Partnership Challenge: The Social Contract

While the technical benefits are clear, the Unified Hub is as much a social endeavor as a digital one. This model requires:

• A high level of trust with shared data access.
• An agreement on cataloging protocols across all members.

Because you are sharing a digital ecosystem, a mistake in data entry standards at one institution can impact the searchability of the entire hub. Establishing a governance board and developing a shared style guide are often prerequisites for success.

The Unified Hub is a Shared Search Engine for Discovery

The Unified Hub proves that by pooling our resources, we can transform our CMS from a private ledger into a powerful, shared engine for discovery. Instead of islands of information, the hub transforms single databases into a connected archipelago, where resources are shared and discovery is deepened for everyone.