The purpose of a museum online presence is to deliver engaging, educational, and enjoyable content to its audience. Now, with COVID-19, we’ve learned a museum’s online presence may at times be the only way to connect with an audience and deliver value.
The front-end portal to a museum CMS was already considered a major tool to support museum operations, and we’re now realizing (if we hadn’t already) how powerful and important that tool can be—especially when it’s our only tool. With this in mind, we need to consider the different ways a museum CMS front-end is offered, assess whether your front-end portal is working for your museum, and become familiar with the benefits of a fully integrated portal.
Museum CMS Front-end Portal Miniseries
This three-part miniseries will review: 1. The different ways a front-end museum CMS portal is delivered; 2. The cost involved when working with two separate platforms or an “add on” front-end portal; and 3. The benefits of investing in one museum CMS with a fully integrated front and back-end.
The Three Ways a Museum CMS Front-end Can Exist:
As the museum CMS has evolved, so has the way a museum provides external user access to its collections within a CMS. This is otherwise known as the museum front-end, or front-end portal. In the early days of digital museum CMS creation, it was more common to see CMS platforms provide a back-end platform only—forcing museums to either create their own front-end or pay a second vendor to do so. Presently, we more commonly see CMS platforms offer a front-end either as an add on or as an equally invested feature of the whole museum CMS platform.
To summarize, here are the three ways a museum CMS front-end can exist:
- As a completely separate platform from the museum CMS back-end.
- As an “add on” to the existing CMS platform.
- As an equally invested in part of the museum CMS.
1. Two Separate Platforms
Option 1 leaves museum staff on their own to figure out how to provide and maintain a front-end for the museum CMS. The museum will either need a knowledgeable staff member or hire an outside consultant to create the custom code needed to link the front and back-end together. This option requires the investment and maintenance of two separate platforms and increases the workload on staff to push the collections content from one platform (the back-end) to the other (the front-end).
2. As an “Add on” to the Platform
Option 2 is a museum CMS that can provide a front-end portal as an “add on” feature. The optional add doesn’t typically receive the same amount of investment as the back-end which means it’s not nearly as competitive among other CMS front-ends on the market. This option eliminates the need for two platforms, but it fails to provide a tool that can meet staff and user expectations. The museum may save some money and decrease staff labor by moving from two platforms to one, but the quality available for this option will leave a lot to be desired. Staff will have to work extra hard to create customized workarounds in an effort to tweak the front-end into something more acceptable. In the end, this option can cost more money and staff time than having a fully integrated and invested in front-end portal. Which leads us to option number 3…
To learn more about digital user expectations please see my previous posts on Lucidea’s Think Clearly Blog: The Top 4 Things a Museum Needs to Know About the Digital Visitor, and Museum Digital Collections User Types & Expectations
3. A Fully Invested-in and Integrated Front-end Portal as Part of the Museum CMS
Option 3 is a museum CMS that comes with an integrated front-end portal. This portal is fully integrated and has received a substantial amount of investment to make it dynamic, engaging, and visually appealing. While this option can cost more money upfront, it makes up for it by not requiring additional staff labor to support either two separate platforms (option 1) or a platform with a sad front-end portal (option 2).
Seamless integration of a CMS front-end portal is becoming an expected mechanic of any CMS platform. Fully integrated portals offer benefits for the museum, staff, and digital visitors—and should definitely be considered over other options when at all possible.
If your museum is embarking on a the search for a new museum CMS please check out the following posts on Lucidea’s Think Clearly Blog: 3 Things to Look for When Choosing a Museum Collections Management System, How to Begin Your Search for the Right Museum CMS, How to Form a Museum CMS Procurement Team, How to Test, Vet, and Purchase a New Museum CMS, and How to Identify Specifications for a New CMS. And don’t forget to grab your free e-copy of my book: How to Select, Buy, and Use a Museum CMS.
Rachael Cristine Woody
Expert Rachael Cristine Woody advises on museum strategies, collections management, and grant writing for a wide variety of clients. Register here for the next webinar in Rachael’s series on Collections Management System Essentials for Impact on 11/25/20, where she’ll expand on the benefits of museum CMS front-end/back-end integration. Learn about Lucidea’s Argus solution for integrated museum collections management.
For each museum digitization project, research and identify equipment and software tools, outline and commit to standards, keep end result(s) in mind
Digitization standards for file resolution and formats should be intentionally thought of and committed to prior to any museum digitization project.
Before a museum collections digitization project, assess what types of items you have and therefore, what digitization tools you need.
The second post in a series on the Harryhausen Titan of Cinema Experience analyzing the specific pivot to an online virtual exhibition during COVID