Tour a fully assembled collection via a scenario zip

In Lessons 2–4, you built a collection · a dataset · a chart one at a time. This lesson goes the other direction — receive a fully assembled collection in a single shot and tour it. Touching both ends — what you built in 5 steps and what a complete scenario loaded at once looks like — is this Path's central insight.

Get the IoT Smart Factory scenario

This lesson starts with the IoT Smart Factory scenario — a small 44 KB zip that downloads instantly.

The zip carries 2 collections · 3 datasets · 4 codes · 3 pipelines · an ontology (3 entities, 2 relations) · 1 dashboard.

Open portal's Import dialog

Go to Collections in the left sidebar. In the Explorer top header's more (⋯) menu, you see an Import (가져오기) item. Click it to open the Import dialog.

Pick the iot.zip you just downloaded and upload. Progress shows inside the dialog; on a zip this small, it usually finishes in a few seconds.

Tour the loaded collection

When the upload finishes, the left tree shows raw and processed side by side — the raw landing zone and processed / derived data split.

Click through five items, one at a time.

1. The machine_sensors dataset in raw — in the Preview tab, you see 30-second-cadence sensor rows.
2. The anomaly_detections dataset in processed — 0 rows right after load. The next-step pipeline fills it.
3. The anomaly_detection pipeline in processed — in the Workflow editor, two nodes show up.
4. The left sidebar Ontology area — three entities (IOT_Machine · IOT_Sensor · IOT_MaintenanceEvent) appear.
5. The equipment_health dashboard in processed — four widgets fill one screen.

Notice that the five are interconnected. The same resource appears as a dataset, as a pipeline node input/output, as an ontology's backing dataset, and as a dashboard widget's source. One resource alive across multiple surfaces simultaneously is the core value of D.Hub.

Self-check

• Both raw and processed collections appear in the left tree.
• You confirmed one resource (e.g. machine_sensors) appears in two places — as a dataset and as a pipeline node input.

What you should be able to do after this lesson

• The entry path to portal's Import dialog
• The shape of a fully assembled collection — datasets, pipelines, ontology, dashboard, all together
• D.Hub's integration model where one resource lives across multiple surfaces

Next lesson

The final lesson — pick the role Path that matches your work.