Design Pattern "Ways to add new combobox/tokens values"

From SMW CindyKate by dataspects
Component 975982
Jump to navigation Jump to search
[edit]
Keywords/Contexts

MECE · Consistency

Annotations
{{#compound_query:Component 975982Property "-Has subobject" has a restricted application area and cannot be used as annotation property by a user.UseCaseMotivation;?HasDirection;?IsMotivating;?IsMotivatedBy;?HasReasoning
Property "-Has subobject" has a restricted application area and cannot be used as annotation property by a user.Design Pattern "Ways to add new combobox/tokens values";?HasDirection;?IsMotivating;?IsMotivatedBy;?HasReasoning Property "-Has subobject" has a restricted application area and cannot be used as annotation property by a user.Design Pattern "Ways to add new combobox/tokens values";?HasDirection;?IsMotivating;?IsMotivatedBy;?HasReasoning
name=MotivationsDeclaredOnThisPageResultItem|link=none}}
Motivations
Lua error in Module:Motivations at line 23: attempt to concatenate field 'hasReasoning' (a nil value).
[edit]

Content

In many cases, combobox and tokens values serve as "facet hooks". So MECE and consistency is crucial. So there are 2 ways to handle adding new values:

Centralized administrator-controlled authorization of new values

{{{field
  |General Tags
  |property=Has general tag
  |input type=tokens
  |values from category=General Tag
  |existing values only
  |delimiter=;}}}

Distributed user-tolerated spontaneous introduction of new values

{{{field
  |General Tags
  |property=Has general tag
  |input type=tokens
  |values from property=Has general tag
  |delimiter=;}}}