Transmedia

Wezit, not your typical CMS

As part of the digital era in which we live, you might have read about many CMS for museums, galleries, government archives, heritage sites, libraries, film archives, corporations, private collectors, universities, national parks, religious institutions and many more.

As it is logical in today's world, these collection management systems allow organizations of different sizes, industries, whether in the private or public sectors to track their assets and efficiently manage either events, exhibits and any loans made to another entity.

This approachalthough useful and pragmatic, loses an "emotional" part inherent to all humans manner of communicatingWhat we try to do at Wezitis going a little bit further than arranging a collection; in a certain way we see it more as an architecture of experiences.   

What we allow to convene with all the technical back office portion, is to create an experience: before, during and after the visit. Wezit has an open API, meaning that existing software components can interact. With this said, many technical options are available - those are indeed endless, and can be catered to your organization's needs.

© Nantes Métropole - Musée d’arts de Nantes - Photographie : M. Roynard

However, if your organization already has a collection management system in place, the beauty of Wezit relies on how it can communicate with the existing collection management systems.  

A real case example was the recently opened Museum of Fine Arts Nantes located in France, with a real-time location update of artworks on all the museum’s devices from touch-tables to mobile apps... like magic!

The update of the artwork location, along with the information provided, such as author, title, and date, following the Dublin Core© guidelines.

According to the Dublin Core metadata initiative, these guidelines are respecting the following:

© Image by the Dublin Initiative Core http://dublincore.org/documents/1999/07/02/dces/

  • Name - The label assigned to the data element 
  • Identifier - The unique identifier assigned to the data element 
  • Version - The version of the data element 
  • Registration Authority - The entity authorized to register the data element 
  • Language - The language in which the data element is specified 
  • Definition - A statement that clearly represents the concept and essential nature of the data element 
  • Obligation - Indicates if the data element is required to always or sometimes be present (contains a value) 
  • Datatype - Indicates the type of data that can be represented in the value of the data element 
  • Maximum Occurrence - Indicates any limit to the repeatability of the data element 
  • Comment - A remark concerning the application of the data element 

Certainly, it has never been easier for museum curators to deal with their data.  

On the other side of the project, and this is what makes Wezit  so special, representing the second aspect of the platform: it’s an easy way to thin the best possible visitor’s experience!

Once all the data has been organized, you need to think "user experience" (UX) and how they can also customize their visits more efficiently. Besides, they can also "share"  this experience after their visit. This happens thanks to templates that you can use and re-use to integrate the content you have been creating. 

Wezit moves with the flow of a collection. A CMS with: powerful and adaptable geolocation possibilities, continuum visit experience capabilities, statistical features, and cloud hosted; those are just a few useful main elements 

So we leave it to you... 

Wezit is an "Integrating CMS," connecting not just devices and data but also human experiences...  

Application & (offsite) terminals / Musée lorrain (Lorraine Museum)

Learn more

Interactive table / Nantes Museum Of Fine Arts

Learn more

Kiosks, indoor mobile apps / Cité de l’Architecture

Learn more