The indicator set component is used to create the data model and view models for any forms needed on your community. While some systems use the same data model for all forms (hiding and changing the labels for fields), BetterData allows you to create a unique data model for each form that you need. This gives you more flexibility when it comes to using that data to generate reports.
The data model is determined by the fields that you need on a form. However, it can also include fields that are calculated, populated by an external application or auto-populated from data elsewhere in the community. Once configured an indicator set can be used in one or more Apps on your community. Indicator sets are accessible both via a web browser and on the Android app.
The labels, help text and validations for each field can be defined in multiple languages. BetterData will detect the language settings of your browser and only display the form in the matching language (if available). This enables you to translate forms (at once or over time) to be in multiple languages simultaneously.
Each indicator set can have one or more form views. The form view is used to enter or edit data. Each form view can include the following elements:
Widgets define the functionality for each field on the form. Some of the widgets available include:
- Date or time
- Repeat structure
- Calculated fields
- Radio buttons
Each widget can also have validations defined. These determine which data can be entered. Fields can initially be defined as required or optional, with a validation error message specified to guide users as to the response needed. If defined as required then the following additional validations can also be set:
- Equal to
- Greater than equal to
- Less than equal to
- Minimum number of characters
- Maximum number of characters
- Must be an email address
- Must be a number
- Must be a date
Permissions define which which user roles are able to view, edit or delete the form and it's data. Roles are defined in the application component and will appear in each form as they are modified.
Form views may also reference the following other components:
- Linkages - This allows users to link two forms and specify the relationship between them
- Comments - This allows users to add comments
- Taxonomies - This allows users to select tags from a pre-defined taxonomy and add them to the form
- Duplicate - This component introduces a duplicate check that prompts users to search and check for duplicate forms based on a pre-specified key (like the title field, ID field, email address or similar)
- Mailbox - This component links to the mailing engine, enabling users to contribute new form data via email and receive updates the same way. Similar integrations are possible (for simple forms) via SMS
Rules determine what happens once a form is created or updated. Some examples of the options here are:
- Initiate a workflow - This triggers a workflow that the form is linked to
- Create an app profile - This takes the data from the form and uses it to create an app profile
- Network linkage - If the form is used to create a new profile, this rule can also then assign one or more users specified on the form to be the owner or member of that profile
Each indicator set can also have one or more views. This typically include an object view that shows the data saved on the form in a read only view. The object view uses the same elements as the form view, but they made be arranged in a different way.
The object view is also configureable to define which options are visible and to which user role. For example:
- Who can edit the form object?
- Who can delete it?
- Who can create a linkage?
Users also have the option to save a link to the object to their personal library. This helps people to create their own collections of relevant content.
Following are some screenshots of the indicator set component.