Tamr Cloud is a fully managed SaaS solution for creating and managing high-quality data products. The platform provides auto scaling, performance and security monitoring, and automatic updates.
Tamr Cloud offers data product templates that solve specific use cases. Each template includes the following features to help you quickly master, clean, and enrich your data:
- Industry-specific schemas.
- A fully trained model to identify and group similar and matching records.
- Data quality services, enrichment, record consolidation rules, and other capabilities.
Tamr's data product templates master large volumes of data, allowing you to publish clean, enriched, unified datasets. You can use this data to power analytics, data visualizations, business intelligence, and other tools used by your organization.
Tamr Cloud's data product approach offers many advantages over traditional rules-based data mastering, including the following:
|Tamr Cloud Approaches
|Developer-created rules that require constant updates as data changes.
|Pre-built, purpose-trained machine learning models.
|Closed systems aimed at selling a broader suite of products.
|Interoperability with existing applications across the data value chain.
|High cost for adding new sources requires significant preprocessing and modification.
|Easily onboard new sources by leveraging purpose-trained machine learning models and pre-defined data mastering flows.
In Tamr Cloud, you master source records by data product.
A data product represents a type of mastered data. For example, you may have a "Customer Sites" data product with mastered entity records for customer locations or branches.
During the mastering flow for a data product, Tamr Cloud identifies source records that refer to the same entity. Each entity is a mastered entity record that represents a group of related source records across your company’s datasets.
During the mastering process, each entity is given a Tamr ID, which is a unique, persistent primary key. Tamr Cloud automatically manages the Tamr ID throughout the mastering process to ensure that it remains a unique string.
Use this ID to identify this entity in and across your downstream applications.
See Requirements for Source Datasets for more information about the importance of maintaining stable primary keys to retain persistent Tamr IDs.
Updated about 1 month ago