Skip to content
Datablau DAMData governance documentation

Data catalog quick start ​

Design, catalog, authorize, publish, and verify one business folder and a few harvested tables.

Before you begin ​

RequirementCheck
Clear business scopeInclusions, exclusions, maintainer
Harvested tablesSearchable with verified source/meaning
Stewards/reviewersPermissions and separate approval responsibilities
Ordinary business userConsumer visibility testing

Reuse a suitable space. Create one only if its structure is insufficient.

1. Design types and a space ​

Follow Space design for levels, assets, properties, completeness, and separate approvals; create and enable the space.

Folder asset types, properties, completeness, numbering

Use actual organizational thresholds/rules. Verify enabled state, table support, properties, and approvals. Enablement does not create folders or assets.

2. Create folders and node permissions ​

  1. Follow Folder maintenance to create a node.
  2. Complete name, scope, description, ownership, and required properties.
  3. Grant user/group/organization management, edit, and access rights.
  4. Verify child inheritance does not broaden scope unexpectedly.

Test steward editing and consumer access. Locked public display is not an access grant.

3. Register tables ​

Use Register Table, verify system/source and business ownership, then inspect assets/numbers. For missing tables, check type support, metadata, and module rights. Avoid same-name objects in other environments.

4. Publish folders and assets separately ​

Use More Actions > Publish Asset Folder, reason, and inclusion options. For individual assets, select and Publish. Verify all folder/child/asset states and each approval or direct-publication result.

5. Verify as a business user ​

  1. Open Marketplace with expected ordinary-user rights.
  2. Find the asset by keyword or folder.
  3. Verify path, description, source, and request action.
  4. If hidden, check enablement, parent/asset publication, then access.

Completion means authorized consumers can find and understand assets. Actual data use still requires Requests and offline delivery.

Expand coverage ​

After the pilot, use Inventory or templates. Acceptance/import does not replace publication or consumer testing.