Configure folder types, completeness, and custom properties

Folder types define information at each level. Completeness determines publication readiness. Custom properties capture organizational fields. Design these before creating spaces.

Define a folder type

Open Data Assets > Folder Type Settings.

Setting	Purpose	Guidance
Name	Tree and form label	Clear singular business noun
Supported asset types	Registrable objects	Only relevant types
Completeness formula	Property completeness	Agree required fields before weights
Custom properties	Organizational information	Type, requirement, validation
Numbering rule	Folder code generation	Stable conventions

Built-in levels commonly include subject domain group, domain, business object, logical entity, and attribute. They can be adapted, but referenced types cannot simply be deleted.

Create or edit a type

1. Select New or Edit.
2. Enter the name and supported asset types.
3. Configure completeness properties and weights totaling no more than 100%.
4. Add custom property names, types, required flags, and descriptions.
5. Configure automatic numbering if needed, save, and test one folder form.

Verify availability in space design. If missing, check saving and space configuration rights.

Design completeness calculations

Completeness measures filled properties, not business quality or publication status. Valid values contribute configured weights; excluded properties do not.

1. List prerequisites such as ownership, steward, keywords, and description.
2. Include them in the formula and check total weights.
3. Test fully completed, required-only, and missing-critical-property examples.
4. Fill missing information instead of manually changing scores.

Folder and asset approvals remain separate from completeness.

Maintain custom properties and numbering

Custom fields extend abbreviation, ownership, approver, keywords, and description. Check existing folders/reports before deletion or renaming; migrate or retire used properties to preserve history.

With automatic numbering disabled, enter codes manually using organizational uniqueness rules, including imports. With it enabled, test prefixes, levels, and sequences before bulk import.

Handle changes

Symptom	Action
Cannot delete	Check space/node references
Existing folders affected by hierarchy changes	Disable relevant space and assess existing nodes first
Completeness unchanged	Check formula inclusion, null values, types
Duplicate imported codes	Check numbering and template codes before overwriting

Next: Space design.