Let's just understand the importance of a single source of truth first before we look at how this is done for us in practice:
Improved accuracy: When all data is stored in one place, it's easier to ensure that it's accurate. There's no need to reconcile conflicting information or worry about discrepancies between different data sets. Instead, everyone can trust that the data is up-to-date and accurate.
Increased efficiency: There's no need to waste time reconciling data from different sources. This means that data analysis can be completed more quickly and efficiently, allowing organizations to make better decisions in a timely manner.
Better decision-making: When everyone is working from the same data, it's easier to make informed decisions. Decision-makers can trust that the data is accurate and complete, which allows them to make better decisions based on facts rather than assumptions.
Improved collaboration: It also promotes collaboration among stakeholders. With everyone working from the same data, it's easier to share information and insights, which can lead to better teamwork and more effective problem-solving.
Reduced risk: Having a single source of truth can also reduce the risk of errors and mistakes. With consistent data, there's less chance of making decisions based on incorrect or incomplete information, which can help mitigate potential risks and avoid costly mistakes.
Bottomline is that we all agree having a single source of truth is fairly critical...
1. Direct from the CMS
Manage data end to end using the map content management solution so that any updates or edits will feed seamlessly through to wherever the live map is published. On paper this is the easiest way to ensure up to date information.
2. Linking to your existing Content Portal
In many cases, there is an existing CMS in place and the pain of uprooting this may not make sense and the data may be used for different uses not just for the maps. In this case you will typically extract information that is relevant via an API or other data sharing method and then upload and publish to the map. The challenge is that CMS functionality of a map CMS is different to what is already in place so how do we bridge that gap?
The reality is there is no ideal solution so we have to look at ways to streamline processes and share only the information needed to visualise a point of interest and minimise the effort needed from the venue side to manage data for the map.
In many cases, you will need sync data from multiple sources as for example retail data related to the map may come from one bucket while Gate information (in the case of airports) will come from another bucket. What we do is combine with unique Ids to create our own dictionary to ensure when the information hits the map - it is consistent in format and style.
If you want to understand more, reach out for an informal chat.