A Business and Technologies journey

With the new year, it's time for a retrospective of the past year and prepare for 2019. First, 2018 was the year of GDPR (The EU G eneral D ata P rotection R egulation). GDPR had been in the agenda of global companies and consulting firms for at least 2 years for being the most important change in data privacy regulation in 20 years. From the MarkLogic perspective GDPR, is a great opportunity to demonstrate the value of an operation DataHub  to store data and metadata together to support robust data governance required by the regulation.Concrete uses cases deal for example with consent management in customer 360 hub or tackling right to be forgotten by managing data lineage from golden record to source dataset records.  A detailed illustration is described is this blog post :  How a Data Hub can help to find back memory to tackle GDPR right to be forgotten . And a more generic illustration is details here :  Metadata in operationa...

The challenge As part of the GDPR, a client can ask for its records to be deleted. In a typical large organization, client records can be spread across multiple different systems from CRM, to eCommerce, to Campaign management solutions. Finding this records can quickly become a nightmare. In this article we will describe how MarkLogic and the datahub pattern can help finding the customer records across these systems. The Operational Data Hub pattern The Operational Data Hub (ODH) pattern, powered by MarkLogic is designed to ease the integration of data from siloes, link and enrich them and create actionable 360 view across all demands. The Data Hub consolidates data from siloes so if we enrich the process with lineage, we can then track all data from the 360 view to their source records.  Data dictionaries meet the triple store Usually organizations maintain data dictionaries for their databases. It's quite easy to get a CSV or an Excel file representing th...