Step 1 sets your data product’s location and identity: its Space, domain, name, ID, type, visibility, and descriptions. It is the first of the wizard’s seven steps, and the foundation every later step builds on.
What you set here
This step captures where the product lives, how it is identified, and the descriptions consumers read first. The fields sit in two cards, Location and Identity, followed by the two description editors.
| Field | What you set |
|---|---|
| Space | Where the product lives. Only Spaces with the application appear; if one qualifies, it is selected for you. |
| Domain | The product’s parent domain. Select a Space first, then choose a domain. |
| Name | The product’s display name. |
| ID | A stable identifier. Suggest ID fills it with a kebab-case version of the name once the name is set. |
| Type | The product type, from a controlled list (for example dataset or raw data). |
| Visibility | Who can see it, from a controlled list (for example organisation or public). |
| Description | A Markdown description of the product. |
| Value Proposition | A Markdown statement of the value the product delivers. |
An ⓘ icon beside a field opens its full description, taken from the package definition. Two classifications you might expect here are set elsewhere: PII Level and Confidentiality are not entered on the product — they roll up from the assets it exposes. See PII Level and Confidentiality.
Why it matters
Identity and placement decide how the product is discovered and governed. The domain sets the product’s business area and its governance context, so choosing it correctly matters. Type and visibility drive discovery and control who can access the product. The description and value proposition are the first thing a consumer reads in the Data Market. The Open Data Product Specification requires both.
For the concepts behind these fields, see What are data products and Built on open standards. For the full list of attributes a product carries, see Object types and attributes.
Rules the wizard enforces
The wizard enforces these rules on the Basics step:
- Every field is required. Space, Domain, Name, ID, Type, Visibility, Description, and Value Proposition must all be set before you can publish the product.
- The ID must be stable and unique. The wizard accepts any text, and checks uniqueness across the catalog when you save: a clash comes back as a save error. Once set, do not change it: data contracts, APIs, and lineage tooling may already reference it.
- The application is resolved automatically. The wizard uses the single Data Product Standard application in the selected Space.
- Space and domain lock when you start from a domain. Launching the wizard from a domain in the hierarchy fills both in and prevents changing them, so the product is created where you started.
Recommendations
None of these are enforced, but they decide how easily the product is found and understood:
- Choose an ID naming convention and apply it across your portfolio, for example
dp-sales-daily. - Write the description for someone who has never seen the product.
- Choose visibility deliberately: start narrow, then widen as the product matures and is documented.
A clear, discoverable identity is the foundation of a sellable product. Next, add the meaning and context consumers search by in Step 2 — Business Context.