If you are responsible for ensuring that solutions are a suitable technology fit for your museum you have to worry many things that some of your colleagues don't. Perhaps one of them sent you here to check out yet another service they are interested in using and to evaluate if it's a good fit for you, your museum and your over-stretched team (if you're lucky enough to have one). This page aims to give you the information you need to assess The Museum Platform from an IT perspective. So here's what you need to know:
That all being said, whilst you don’t need to run any of this, you do need to know that TMP is built and hosted on super-solid foundations, so here you can read about the software architecture and roles along with the full stack and the hosting arrangements for both the website and the back-end systems.
TMP is built in WordPress, the world's most popular content management system, which we keep bang up to date (currently 5.3.2), along with a set of plugins and themes that we have built ourselves or carefully chosen and tested. The other key parts of the stack are:
The true power behind the Collections module comes from Knowledge Integration's CIIM software. CIIM is widely used to organise, manipulate and enrich varied museum and archive data and media. It is enterprise-level software, highly customised to each client, which can bring together data from many sources, align and enrich it and prepare it for many end uses.
The CIIM is a mature Java application, built on established open source technology, which mainly sits behind the scenes, talking with WordPress. However it also supports various public APIs (you can choose whether or not to include your content in these).
Help us to make this page more useful: if you still have questions please don't hesitate to get in touch and we will do our best to answer (and to improve the information here).