At the 2013 Museums and the Web conference I gave talk entitledÂ Open systems, loosely coupled: Creating an integrated museum eCommerce system for the MCAÂ which is about how we delivered an integrated eCommerce system for the Museum of Contemporary Art Australia.
Open systems, loosely coupled: Creating an integrated museum eCommerce system for the MCA
In 2011/12 the Museum of Contemporary Art Australia (MCA) underwent a AUD$53 million redevelopment.Â The building works included the refurbishment of all galleries and offices, the addition of a new 5-story wing and two new rooftop venues. While the physical building was closed for redevelopment, from August 2011 to March 2012, the Museumâ€™s digital systems were also being refurbished and, in many cases, totally replaced.
The MCA took this opportunity to look at its digital systems in a holistic manner. These included suppliers and technologies used for ticketing, store point-of-sale, customer relationship management (CRM), membership and donations, as well as the MCA website (http://www.mca.com.au). InÂ parallelÂ to this review, the Museum sought to integrate certain web based systems with a new museum-wide wireless network, new digitalÂ interpretationÂ smartphone app and new internal IT infrastructure.
This paper outlines how an entirely new eCommerce framework was built using open web APIs to connect systems for ticketing, store, philanthropy, membership, CRM and the WiFi network. In this solution a selection of loosely coupled best-of-breed systems â€“ connected via open APIs â€“ was attempted instead of an all-in-one solution or an in-house build. I will describe the approach taken, the challenges faced and lessons learned.
In 2011 the MCAâ€™s website turned 6 years old, which made it older than both Twitter and the iPhone. Web technology had progressed considerably since 2005, as had the visual identity of the Museum, so it made sense to rebuilt rather than refresh the website. At the time, the MCA had no online store to support its successful onsite store. There was no online membership and limitedÂ facilitiesÂ for online donations. The Museum is free to attend, however there was no online ticketing for public programs. At the time Raiserâ€™s Edge from Blackbaud was used as a CRM for donors, members and partners (https://www.blackbaud.com/fundraising-crm/raisers-edge-donor-management), however this required a series of manual steps to create each new member and membership data could not be connected to any other system without further manual steps.
The MCA engaged the Interaction Consortium (http://interaction.net.au/)Â to build the new website and began looking for an eCommerce solution that could support a set of needs that are very common in cultural organisations:
- Online store
- Online membership
- Online public program ticketing
- Online donations
- CRM integration
- Integration of these systems with onsite physical technologies such as store point-of-sale, event ticket validation and access to membershipÂ privileges
The Interaction Consortium was selected for the project, in large part, because they would be utilising and improving upon the GLAMkit web toolkit that has been especially designed for the galleries, libraries, archives and museums sector (http://glamkit.org/). Further, they committed to making the resultant code available as an open source project, an initiative that the MCA strongly supports.
A number of Australian, European and North American â€œall in oneâ€ solutions were investigated, however none that were available in the Australian market met the MCAâ€™s modest requirements at a reasonable cost. A different approach was required.
There are a wide variety of solutions to each of these individual requirements. Using membership support and integration as a crucible through which each potential provider was viewed, all systems that did not have an open API, or who were unwilling to open up APIs they did have, were struck off the list. Only systems that could communicate with others made the cut. This immediately removed Raiserâ€™s Edge and the storeâ€™sÂ incumbent point-of-sale system from the planning process.
The key membership technology we selected was eTapestry. eTapestry was chosen because it has a stable, documented and open API for adding and alteringÂ constituentÂ records, as well as a query language that is available via the API. This means that we are able to retrieve a list of active members, or to get a list of new members, which can be used to notify other providers. Further, if memberships were created by other providers we would be able to add them to the master database. As eTapestry is a web-based system, it easy for it to supply membership signup and various donation pages in the visual style of the MCAâ€™s main website (https://app.etapestry.com/bbphosted/nl_mca/MembershipForm.html).
We selected a New Zealand based eStore and in-store point-of-sale solution from Circle Software (http://www.circlesoft.net/) to run the MCA StoreÂ (http://store.mca.com.au/). Circle Software was selected because they could integrate with our system and their point of sale software wasÂ intuitiveÂ and mature.
The Australian online and onsite ticketing company Oztix (http://oztix.com.au) was chosen as their venue ticket scanning technology can scan MCA issued tickets, MCA membership cards and tickets issued by other providers. Also Oztix commited to implement a bespoke two-way membership integration and to expose the event API to the MCAâ€™s GLAMkit CMS (https://tickets.mca.com.au/). This API was used to integrate the MCAâ€™s event listing with the Oztix event ticket pages. MCA staff can create an event in the GLAMkit CMS just once, specifying single or multiple occurrences, price, capacity and other parameters. They can then choose to send that event to Oztix and that event will be created by the API. MCA public programs staff can decide when theyâ€™re ready to make it available for sale using the Oztix CMS. The API constantly monitors Oztix event listing RSS for new MCA events and automatically links the two events when itâ€™s made active.
We were able toÂ achieveÂ the initial goal of a group of integrated systems that passed key user data between them across multiple axes. Itâ€™s also important that certain data can originate in different places. For example, someone booking tickets to an event or a workshop can buy a membership and book membership price tickets in the same transaction. The ticketing system inserts a new membership into eTapestry, theÂ PhilanthropyÂ and Membership team is notified and sends out a membership pack and GLAMkit picks up the new membership and creates a memberâ€™s account in the eStore. Within 15 minutes of a new membership being purchased online, all providers have been notified and the new member has been emailed their store and ticketing login credentials.
This approach was used throughout the build process for the main MCA website and was very successful. The user stories for the website were generated at the end of a series of workshops, UX sessions and one-on-one interviews. In addition, I undertook a series of interviews with members of the Store, Marketing, Philanthropy/Development, IT, Public Programs and Finance departments to understand their ecommerce needs and dependencies. In collaboration with Interaction Consortium, the MCA crafted user stories in the style; â€œas a user, I can buy a membership online and then access membership events and membership discounts for tickets, on the eStore and at the MCA Store within an hourâ€.
I used these stories as a way of judging potential vendors. The vendor selection process took a period of months, as the different options were tested and contracts negotiated. Interaction Consortium, Circle Software and Oztix were all happy with a user story approach to the integration of their systems.
The loosely-coupled approach means that any of the system, with varying degrees of difficulty, can be unbolted and a new provider bolted on without affecting the other systems or the overall user experience. This isÂ especiallyÂ important in the often cash strapped museum sector.
The user experience
We decided early on that Oztix would host the online ticket outlet and that Circle Software would host the eStore, such that they could manage upgrades and meet uptime SLAs. To make the transition clear to the user, we devised a different header and background treatment for the affiliate sites.
When a user clicks â€œBuy tickets hereâ€ they are taken to page with the same font and the same visual style, however the background changes from an image from within the MCA to a stylised composite image, the header changes to one that offers a â€œback to the MCAâ€ link in place of the normal page header andÂ MCA TicketsÂ page branding is added.
Due to the refurbishment of the Museum of Contemporary Art the MCA Store was closed and the Museum was not actively promoting membership. This made it easier to convince the Store and Philanthropy departments to embrace the changes that affected them directly. Despite this, there were still significant challenges.
- Migrating data from Raiserâ€™s Edge to eTapestry was very difficult. Some of the data in Raiserâ€™s Edge was old and incomplete making the migration process difficult. Blackbaud, providers of Raiserâ€™s Edge and eTapestry, were engaged to manage the migration process and made some initial miscalculations that also slowed the migration process.
- Financial reporting for government audited institutions is already an ordeal without the addition of a number of new systems and payment pathways. Getting the reporting right for ticketing and the store has been one of the most difficult, expensive and time consuming parts of the whole process for the MCA.
- Some staff do not like change, especially when it might mean more work for them. In these cases itâ€™s important to explain the whole project and their part within it and to reiterate the importance of the visitor experience, rather than appearing to force them to change without contextualising their work.
- The ticket scanning system that we used is designed for single entry/single event venues, the MCA was the first cultural institution to use Oztix and as such there were difficulties in tailoring the Oztix ticket scanning system for multiple concurrent events and single events (such as paid exhibitions) in multiple galleries. The benefit of this system, however, is being able to see the analytics of what tickets are being bought online and in person, as well as when these tickets are being scanned at the Museum.
- Integrating disparate systems that are managed and, crucially, paid for by different departments can be challenging. During the installation and migration process, the Digital Media department took ownership of all the vendor relationships and all technologies, in collaboration with the IT department when needed. Once the technology was bedded in, the ownership was returned to the individual department.
The lessons learnt
Wholesale changes, such as the ones described here, can be difficult to negotiate in an institution with established departments, occasionally with competing goals. Although this exact model isnâ€™t appropriate in all circumstances, or for all institutions, here are few key lessons that we learnt during this project. These should act as reference points for other individuals and institutions with the same objectives.
- Establish clear goals at the outset. We worked hard to get institutional buy-in to these goals, and not particular technologies or providers, from the key departments and other stakeholders. This helped negotiate changes to staff systems or workflows.
- Keep the visitor experience at the core of the change. This allows you to explain to departments or staff that in order to reach the agreed goal or to give visitors a particular experience that they will need to spend time, money or resources on the incoming system.
- Acknowledge that you have two key audiences; museum visitors (physical and digital) and museum staff. In doing so, we avoided solutions that only benefits one group.
- Offer complimentary products in different systems were possible. For example the MCA offers a membership package and membership priced tickets or store items in a single transaction.
- If you are moving a user from one web platform to another, try to do it seamlessly while making it clear they have been moved. Further, provide a way back to the site at the end of their purchase path.
- We were always wary of providers who were unwilling to update, describe, add to or alter their systems. We felt that if we had to build lots of scaffolding around their technology in order to use it, itâ€™s not the right solution.
- Include API stability, maintenance and uptime requirements in your contracts with suppliers.
- Include analytics from the very first day and measure the success/failure of each new or altered technology. This is very helpful when it comes toÂ justifyingÂ the changes to the sceptical.
- We clearly articulated the whole projectâ€™s goals to each provider so they could see how their part fits into the whole. As they know their domain well they often had innovative ideas or useful experiences to add.
- We decided to not build too much in house. A museum is not a ticketing company. Leave the ticketing innovation to companies whose sole purpose is to deliver ticketing. Instead, we focused on creating compelling experiences for our audiences.
- Donâ€™t underestimate how hard it can be and how long it can take and set expectations accordingly.
- Lastly, have high expectations. Be prepared to replace under-performing technologies or partners. One of the strengths of this approach is that elements of overall solution can be replaced if necessary.
Further integration possibilities remain, for example we would like to record every ticket and store purchase members and donors make against their eTapestry account to help us better understand and serve their interests.
We would like to provide tools and support for smaller institutions who are struggling with out-dated or dysfunctional eCommerce solutions. This paper is part of that process, as is the open source approach to GLAMkit taken by Interaction Consortium. The MCA website forms part of the core part of the initial version of the GLAMkit CMS.
In January 2013, with the support and encouragement of the Museum of Contemporary Art Australia, weâ€™ll release the code forÂ www.mca.com.auÂ â€“ minus the MCA-specific parts â€“ as version 0.1 of the free, open-source GLAMkitÂ CMS, for anyone to install, use, or contribute to.
Turner, G. (2013)Â GLAMkit rebooted.Â Last updated January 4, 2013. Consulted January 28, 2013. AvailableÂ http://glamkit.com/blog/2013/reboot/