ListMapping.
How the items of a list field become entities of a kind, each keyed by the first of its key paths that holds a value, with one connection of a registered kind between the object's own entity and each item
Figure 1ListMappingspecified
- kind
- value
- scope
- none
- key
- none
- store
- none
- family
- sources
Fields#
| field | type | required | note |
|---|---|---|---|
field | text | yes | the list field of the source object |
kind | KindOfEntity | yes | |
key_namespace | text | yes | |
key_paths | [text] | yes | the first path that holds a value keys the item |
key_prefix | text | no | put before the key’s value, for a platform-and-handle key |
name_path | text | no | |
connection | KindOfConnection | no | |
own_role | text | no | the object’s entity’s role |
item_role | text | no | each item’s role |
texts | [text] | no | the item fields kept as long texts of the item’s entity, each a claim stated by the source under the field’s name, as the object’s own texts are |
readings | KindOfMeasure | no | the item fields that are counts, each a reading of the measure on the item’s entity at the time the page was read |
parent | ListParent | no | the thing each item belongs to, when the item carries its key |
Routes that use it#
No route takes or returns ListMapping directly. The record holds it, and the objects that point at it reach it.