page237
324
The functional components shown within Figure 9-4 are as follows:
1.
Entitlements provided by an external entitlement component.
2.
A normalized entitlement data model containing
a. Client-specific entitlement
b. Mapping to data product objects
c. Template SQL statements
3.
Various source data feeds
4.
Curated data product objects
5.
Filter engine that
a. Maps entitlement to data product object
b. Applies filters to generate client-specific content
6.
Client-specific share containing entitled data
7.
Imported share manifests as a database in the consumer account
Let’s investigate each component in more detail.
External Entitlement Component
Many organizations experience growth through a merger and acquisition (M&A), which
results in the proliferation of entitlement applications: every acquired product has its
own entitlement system. Plugging the gaps in data product offerings via the M&A activity
involves acquiring a corresponding entitlement application.
Without a single strategic entitlement application, acquired data products cannot be
fully integrated with existing data products for entitlement purposes.
I am assuming entitlements are sourced and then merged into your normalized
entitlement data model.
Entitlement Data Model
The absence of a single strategic entitlement application implies you may require more
than one entitlement data model—one for each source entitlement system. For the
purposes of developing your filter engine, you assume a single entitlement source.
Chapter 9
Client expeCtations