The data collaboration problem
Consider a simple field like gender. Three different data providers might store this information as:| Provider | Column name | Values |
|---|---|---|
| Provider A | gender | "male", "female" |
| Provider B | sex | "M", "F" |
| Provider C | gender_code | 1, 2 |
- Understanding each provider’s schema
- Writing custom ETL logic for each integration
- Maintaining these transformations as schemas evolve
- Repeating this work for every new partnership
What Rosetta Stone is
Rosetta Stone is Narrative’s universal translator for data collaboration. It takes data from providers in their native format and normalizes it to a common schema—enabling you to query, combine, and analyze data from multiple sources without writing custom integrations. The system works through two core primitives:- Attributes: Standardized field definitions that form the common schema (like
hl7_genderwith valuesmale,female,other,unknown) - Mappings: Translations that connect each provider’s columns to the appropriate attributes, including any necessary transformations
Real-world example: Weather data
Imagine you need weather data from multiple providers for a logistics optimization project. Each provider structures their data differently: Provider A (European):- Temperature in Celsius
- Timestamps in
DD/MM/YYYY HH:mmformat - Wind speed in kilometers per hour
- Temperature in Fahrenheit
- Timestamps in
MM-DD-YYYY h:mm AM/PMformat - Wind speed in miles per hour
- Temperature in Kelvin
- Timestamps in ISO 8601 format
- Wind speed in meters per second
- Learn each provider’s schema
- Write conversion logic for each field
- Handle edge cases (what does Provider A do with negative temperatures?)
- Maintain this code as providers update their formats
temperature_celsius, event_timestamp, wind_speed_kph), and the platform handles all translations automatically.
The query planner analogy
Rosetta Stone functions like a sophisticated query planner that operates across organizational boundaries. When you request data:- You specify what you need using standardized attribute names
- Rosetta Stone identifies which providers have the relevant data
- The system translates your query to each provider’s native format
- Results are normalized and returned in a consistent structure
Key benefits
No ETL pipelines per partnership Traditional data collaboration requires building custom integrations for each partner. Rosetta Stone eliminates this by providing a universal translation layer. Schema changes handled transparently When a provider updates their schema, Narrative updates the mappings. Your queries continue working without modification. Query once, access many A single query against Rosetta Stone can retrieve and combine data from dozens of providers, each with their own schemas. Data quality enforcement Mappings include validations that ensure data meets quality standards before it enters the normalized view—catching issues like out-of-range values or malformed dates.Related content
How Rosetta Stone Works
Understand attributes, mappings, and the normalization pipeline
The Normalization Model
Explore the type system and data quality enforcement
Mapping Schemas
Learn how to create mappings for your data
Normalize Your Data
Hands-on tutorial for normalizing your first dataset

