DatriseAI-first ETL

New York Times Holistics

AI-first ETL from New York Times into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads New York Times into Holistics

Datrise syncs New York Times's records, events, and configuration objects into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

New York Times: SaaS or API data source for analytics and warehouse sync.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How New York Times entities map to Holistics

New York Times entityHolistics objectNotes
recordsnew_york_times_recordsid PK · custom fields → flattened columns for the modeling layer
eventsnew_york_times_eventsdate/time dimensions events
configuration objectsnew_york_times_configuration_objectsid PK · linked to new_york_times_records

FAQ

How does Datrise handle New York Times's custom fields in Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the New York Times to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect New York Times to Holistics the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.