Concept | Item hierarchy in the Govern node#

Concept | Instance-level governance settings mentions the act of “governing” items, specifically items such as projects, bundles, models, model versions. Before introducing the action of governing an item, it’s important to understand the inherent hierarchy attached to these items.

Dataiku item hierarchy#

Dataiku items follow a specific information hierarchy. They conform to certain parent-child relationships, which, as you’ll see, have important consequences for governance. Use the diagram and table below to review this hierarchy.

Slide of the Dataiku item hierarchy.

Dataiku item

Parent-child relationships

Diagram interpretation

Projects

A project is at the top of the Dataiku information hierarchy. It has no parent item. Possible child items include bundles, models, LLMs, and agents.

Dataiku Project A is the parent of Bundle B, Model C, LLM D, and Agent E.

Bundles

A Dataiku project can have any number of child bundles, but a bundle belongs to exactly one parent project.

Bundle B is a child item of its parent, Dataiku Project A.

Saved models

A Dataiku project can have any number of saved models, but a saved model belongs to exactly one parent project.

Model C is a child item of its parent, Dataiku Project A.

Saved model versions

A saved model can have any number of child model versions, but a model version belongs to exactly one parent model.

Model versions F and G are child items of their parent, Model C.

Fine-tuned LLMs

A Dataiku project can have any number of fine-tuned LLMs, but a fine-tuned LLM belongs to exactly one parent project.

LLM D is a child item of its parent, Dataiku Project A.

Fine-tuned LLM versions

A fine-tuned LLM can have any number of child LLM versions, but an LLM version belongs to exactly one parent LLM.

LLM versions H and J are child items of their parent, LLM D.

Agents

A Dataiku project can have any number of agents, but an agent belongs to exactly one parent project.

Agent E is a child item of its parent, Dataiku Project A.

Agent versions

An agent can have any number of child agent versions, but an agent version belongs to exactly one parent agent.

Agent versions K and L are child items of their parent, Agent E.

Next steps#

Now that you understand the item hierarchy, see Concept | Adding a governance layer to Dataiku items to learn how to actually govern an item.