Ontologies

Duplicate an ontology

Duplicating gives you an independent copy of an ontology. Use it to branch a variant, try changes without touching the original, or start a new ontology from one you’ve already built.

In the app: Data Context › Ontologies › your ontology › More › Duplicate

[screenshot]
The Duplicate Ontology dialog with the Copy bindings switch and the Name, Namespace, Description, and Owner fields.

Before you start

You need write access to the organization.

Make the copy

  1. Open the ontology and choose More › Duplicate.
  2. In the Duplicate Ontology dialog, decide whether to turn on Copy bindings (see below).
  3. Enter a Name. It starts empty and must be unique in your organization. If the name is taken, the dialog says “An ontology with this name already exists in your organization.” and stays open.
  4. Adjust Namespace, Description, and Owner if you want. They are prefilled from the original.
  5. Click Duplicate.

Kenseme copies the classes, relationships, attributes, instances, and prefixes into the new ontology and opens it. The copy has the same Base IRI as the original.

Note: The copy is a snapshot. Editing the copy doesn’t change the original, and editing the original doesn’t change the copy.

Copy the bindings too

If the original is bound to a Fabric lakehouse or to a database, turn on Copy bindings to bring the bindings along. The copy gets its own twin of each binding environment, with the same table and column mappings.

The twin environments are not connected to the original’s Fabric items. The first time you push or sync one, Kenseme creates a new Fabric item for the copy instead of overwriting the original’s. The original ontology and its bindings are not touched.

If the original has no bindings, the switch is off and reads “This ontology has no bindings to copy.” Without Copy bindings, the copy starts unbound. You can bind it to a lakehouse or to a database later.