Enum: AttributeCompletenessEnum
Data quality tier for a DonationItem's category-specific attributes. Set by the fragment engine on sorting step completion — not derived from field presence at the schema level.
Design rationale:
lifecycle_state = sorted means the sorting episode completed (process
fact). attribute_completeness records the data quality outcome (data
fact). These are orthogonal:
- A size label may be missing → item sorted with minimal completeness
- A structural assessment may be inconclusive → item sorted but routed
to a hold state, not blocked from progressing in the lifecycle
The match engine reads attribute_completeness to calibrate which demand
signals an item can be matched against.
Each category mixin declares field sets for each tier via annotations:
completeness_minimal: mandatory fields — must be present at sorted state
completeness_standard: standard fields — normal redistribution
completeness_detailed: optional fields — improve match quality
The fragment compiler reads these annotations to configure the sorting UI.
URI: inkind_knowledge_repo:AttributeCompletenessEnum
Permissible Values
| Value | Meaning | Description |
|---|---|---|
| minimal | None | Only mandatory fields recorded |
| standard | None | All standard fields recorded |
| detailed | None | All optional fields also recorded (colour, style, intact labels, etc |
Slots
| Name | Description |
|---|---|
| attribute_completeness | Data quality tier set by the fragment engine on sorting completion |
| attribute_completeness |
Identifier and Mapping Information
Schema Source
- from schema: https://inkind-at.github.io/inkind-knowledge-repo
LinkML Source
name: AttributeCompletenessEnum
description: "Data quality tier for a DonationItem's category-specific attributes.\
\ Set by the fragment engine on sorting step completion — not derived from field\
\ presence at the schema level.\nDesign rationale:\n lifecycle_state = sorted means\
\ the sorting episode completed (process\n fact). attribute_completeness records\
\ the data quality outcome (data\n fact). These are orthogonal:\n - A size label\
\ may be missing → item sorted with minimal completeness\n - A structural assessment\
\ may be inconclusive → item sorted but routed\n to a hold state, not blocked\
\ from progressing in the lifecycle\n The match engine reads attribute_completeness\
\ to calibrate which demand\n signals an item can be matched against.\n\nEach category\
\ mixin declares field sets for each tier via annotations:\n completeness_minimal:\
\ mandatory fields — must be present at sorted state\n completeness_standard:\
\ standard fields — normal redistribution\n completeness_detailed: optional fields\
\ — improve match quality\nThe fragment compiler reads these annotations to configure\
\ the sorting UI."
from_schema: https://inkind-at.github.io/inkind-knowledge-repo
rank: 1000
permissible_values:
minimal:
text: minimal
description: 'Only mandatory fields recorded. Matches broad demand signals only
(e.g. "any adult clothing"). Typical cause: missing labels, inconclusive assessment,
rapid triage under time pressure.'
standard:
text: standard
description: All standard fields recorded. Normal redistribution path. Matches
the majority of demand signals.
detailed:
text: detailed
description: All optional fields also recorded (colour, style, intact labels,
etc.). Maximum match quality. Enables fine-grained demand signal matching.