1. Home
  2. Docs
  3. Managing an Elevator Instance
  4. Working with Templates
  5. Types of Fields

Types of Fields


A text field is a simple one-line text entry box.

Text Area

A text area is a larger text entry field which supports line returns and formatting.


A date field can contain either a single date (4/1/2014) or a range of dates.  Date fields also support dates in the form of “10000 BCE”.  


A location will be a latitude and longitude, along with a label.  You can look up a location by address, or by entering the coordinates.  If you don’t enter a label, the latitude and longitude will be displayed to your viewers.


A select dropdrop.  The items in the drop down are defined in the template, using the JSON format.  A basic drop down is:

  "multiSelect": false,
    "Option 1":"more text about option 1",
    "Option 2":"more text about option 2",
    "Option 3":"more text about option 3"

The “more text” is the text that will be displayed to the viewer of an asset.  The “option” entry is what will be displayed to the person adding the asset.

The “more text” section can be omitted.    Sample JSON is displayed when adding this field to a template.


 A multiselect is a cascading select.  For example, you may first select a country, then a state, then a city.

These are complicated structures and it’s recommended that you define the JSON for them using a JSON editor.  Sample JSON is displayed when selecting this field in the template.

Tag List

A tag list is a comma separated set of tags. Each tag will automatically be linked to a search for that term.


A simple on/off checkbox

Related Assets

This field allows you to link or embed other assets within one asset.  For example, you may create a “person” template for defining content creators, and then nest those records within records describing their content.  This type of field can be customized using some additional JSON, as follows.

{ "nestData":true, "showLabel":true, "collapseNestedChildren":false, "thumbnailView":false, "defaultTemplate": 0, "matchAgainst": 0, "displayInline": false}


Should the nested asset be displayed inline, or should the user click a link and open the asset in a new field.


In addition to creating the relationship to the asset, should a label be attached describing the relationship?


If the related asset points to other related assets, should those all be flattened into a single record when displaying?


Instead of displaying the nested assets as a list, should be they displayed as thumbnails?


Should the related assets default to a specific template?


Controls whether this template draws directly inside another template, or is opened in its own screen.


An array listing the other templates that this field should be matched against when doing autocomplete.


A file-attachment field.  This allows users to upload a file their computer.  JSON controls whether dates and locations should automatically be extracted from uploaded files.

Sidecar Data

Some file formats (movies, 3d objects) will present an additional field when being uploaded.  In this case of movies, this is where you can add SRT subtitles.  For 3d Objects, a custom JSON attachment can describe points of interest.  This format will be documented in a separate application.

Was this article helpful to you? Yes No

How can we help?