8. [Builder] Ontology Data Pipelines4. The Backing Dataset

4 - The Backing Dataset

This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.

📖 Task Introduction

How does the transition between dataset and Ontology object type happen?

This object type is "backed by" or "mapped to" the aircraft dataset, which happens to be an output of a scheduled build.

🔨 Task Instructions

  1. While still looking at the Object View you just opened, click the More ▾ button in the upper-right area of the screen and then on … Advanced and click the words View backing dataset (i.e., not on the ).
  2. You're now in the Dataset application. Click on the header for the tail_number column. This will open the stats window at the bottom of the screen.
  3. Once the stats load, locate the Filter field in the bottom right area of the screen. Enter N101NN and then click on it in the Value list below.
  4. Two buttons appear just above; click the blue Keep N101NN button.
    • We’re now looking at the row in the backing dataset that informs the N101NN object in the Ontology. In the Ontology Management Application (OMA)—the subject of an upcoming exercise in this tutorial—columns from the backing dataset are mapped to properties of the Object type. OMA allows for some minor presentation-level changes to the data (e.g., the column name tail_number becomes Tail Number), but substantive changes to data quality and schema should be performed in the data transformation stage of project development rather than in OMA.