Switch

Field type switch. Yes or no. Data entry from the cataloguer’s side is described under Switch .

Parameters

Key	Values	If omitted	Effect
`design`	`slider`, `inner`	`slider`	`slider` shows a slider with the label beside it, `inner` writes the label inside the switch
`on`	String	`ja`	Label when switched on
`off`	String	`nein`	Label when switched off
`value_on`	String	`1`	What is stored when the switch is on
`value_off`	String	`0`	What is stored when it is off
`label`	String	empty	Text right at the switch, in addition to the field label
`font_size`	Number	`16`	Font size of the label in pixels
`color`	Colour	`#3057d5`	Colour when switched on
`grey`	Colour	`#E0E0E0`	Colour when switched off

JSON
{
  "design": "slider",
  "on": "erledigt",
  "off": "offen"
}

Label or stored value

on and off change only what is written at the switch. Changing ja/nein to erledigt/offen (done/open) changes nothing in the data, and no template needs adjusting.

value_on and value_off change what is stored, for example Ausgestellt (on display) instead of 1. That has consequences: filters, templates and analyses that check for 1 will then find nothing. Existing values are not rewritten. In templates, fcheck() copes with both forms.

Import

The Excel import translates unambiguous yes and no entries (including the label from on) into value_on and value_off. Everything else is parked, see Resolve references .

Formatting

The field type comes with Label: it outputs the field’s on or off. See Formatting .

When another field type fits

If you need a third state, such as unknown: a select list with three options. Switching from a switch to a select list later is not straightforward, because 1 and 0 are not option texts. The values then have to be rewritten with a bulk edit .