Skip to content
CO2 Help

Reference data

Reference data is the vocabulary everything else speaks: field libraries define reusable typed fields, classifications organise equipment into a taxonomy, standards record the editions you comply with, and data profiles bundle fields into the published versions catalogues bind to.

What you can do here

Section titled “What you can do here”
  • Switch between the four kinds — each has its own workspace list.
  • Open a workspace — view and author its records.
  • Create a workspace — start a new library of any kind.
  • Author records — add fields, classification nodes, standard editions, or profile versions through typed forms.

Authoring a data profile

Section titled “Authoring a data profile”

On the Data profiles tab:

  1. New profile — namespace, code, name, description. The namespace and code are the profile’s stable identity; other workspaces refer to it by them.
  2. Open a draft on the profile row — drafts are the only thing you edit.
  3. Add profile field to the draft — pick the published field definition (field library workspace + version ID), then set Requiredness, Applies to, Control, placeholder, and order.
  4. Publish the draft — it becomes an immutable entry under Published profile versions, ready for catalogues to bind to.

Fields must point at published field definition versions; publish the field in its library first if the picker refuses it.

Good to know

Section titled “Good to know”

Data profiles are versioned and published: catalogues bind to a published version, so editing reference data never silently changes existing listings — they keep the version they were created against. Publishing a newer version records an available path; each listing moves only when someone edits it and chooses the successor, which writes a migration receipt.

Section titled “Related guides”