Lists are predefined key-label pairs to restrict the choices a user can select from. Use it to get normalized values and reduce the margin for misentry. Lists are often useful for type assignments or categorizations.
Prerequisites
- A Pathbuilder with a group ... is a fundamental structure element of the pathbuilder and can be used as a disambiguation point. Enabled groups resulting in bundles, if you click Save and generate bundles and fields. Administrative names are i. e. Collection or Person and machine names should be start with "g_", like g_person. and a field, which values are distinct and repetitive, like school degree.
Usage
Go to Manage Configure and Pathbuilders (WissKI section). Edit the desired pathbuilder ... is the place where you define the WissKI structure, configure groups and fields and tell WissKI to which adapter it should send the queries. You can export/import your pathbuilder setup. The administrative name of a pathbuilder could something like Collection and Collection Items or Named Entities. . In the row of the future list field, unfold the Operations menu by clicking the caret ˇ and click Configure Field. Change the Type of the field that should be generated to List (text). Keep the options of Type of form display for field and Click Save. Back in the pathbuilder ... is the place where you define the WissKI structure, configure groups and fields and tell WissKI to which adapter it should send the queries. You can export/import your pathbuilder setup. The administrative name of a pathbuilder could something like Collection and Collection Items or Named Entities. view, click Save and generate bundles and fields.
As long as no keys are defined, there are no selection lists. These settings must be made in the field options in the structure panel. Continue the configuration as discribed in chapter Lists inside the WissKI Entities section.