New Features

Making Web Forms a Web App

You can now install Web Forms as an application on to your iPhone, iPad, Android device or laptop as an application. This allows you to easily use all of the surveys that you have access to whether your are online or offline. If you have an internet connection opening a webform will get the survey from the network. (Although it may still be cached by your browser so its worth pressing the browser refresh button). Else, if you are offline, the last downloaded version of the survey will be downloaded.

Laptop

If you are using a laptop then this should work well with Chrome. Use Chrome to logon to your server and select Web Forms. An option to install the web app should appear in the browser bar as shown below.

Notes

• We are still working on automatically downloading surveys that are present on the webforms page. For the moment you should make sure that you open the survey in the webforms web app or in your browser before going offline.
• Even when auto pre-downloading of surveys is available, this downloading will not include images. Hence if you use these in your survey you definitely have to open the survey itself before going offline.
• Apple devices have to have iOS 13+ and you need to use Safari as your browser.

Personal Organisations

Organisations are one of the tools you can use to structure your surveys. Surveys are collected into projects and then projects are collected into organisations. Administrators can determine the enumerators or analysts that are given access to a project and the surveys it contains. But what if you want to have separate work areas where the administrators in one area cannot access and manage the second area? This is where organisations come in. A user with the “organisational administration” privilege can create organisations and give people access to them. Documentation on this existing feature is available here.

“Personal Organisations” now allow this feature to be used by administrators (that is an administrator who does not also have organisational administration privilege). An administrator who creates an organisation can control who has access to it. No other user can take it upon themselves to give themselves access with the exception of users who have the “organisational administration” privilege.

Creating a personal Organisations

As an administrator select the users menu in the admin module. Then click on the organisations tab. Click the “Add Organisation” button.

You need to give the organisation a name and if you like you can set some options for it. Normally though the default options are fine.

Note as an administrator you will only see your personal organisations on this tab. Someone with org admin privileges will see all organisations.

Giving other users access to your organisation

Click on the users tab and then edit the users you won’t to allow access to your organisation.

You will see a section labelled organisations. This will have a list of your organisations and you can add and remove access for other users as you wish.

Switching to another organisation

Users can change organisations by selecting their profile. (The icon at the top right of every page that looks like a person’s head and shoulders).

Click on the organisation drop down and select the one you want to be. Then press save. The page will refresh and you will find yourself in the new organisation.

Bulk import and Export of users

User roles are now included in an export of users to a spreadsheet. They are also included when importing users from a spreadsheet.

Bug Fixes

• Fixed issue with duplicate surveys being created when uploading a survey in XLSX format. This was caused by clicking multiple times on the upload button.
• Fix colour of menu button in webforms when run on a mobile phone. Previously, if the background colour of the header bar had been changed then the menu button might not be visible.
• Automatically return to the page you were trying to access after performing a logon
• Problem with display of “Rank” widget in web forms when the appearance “minimal” was included
• Add logging of changes to role settings to the application log

Yesterday I encountered a really good example of how using an online lookup of reference data from a survey can dramatically improve performance. The follow image shows the CPU usage on an 8 processor data collection server at the point when a single survey was modified to use online lookups instead of downloading all the reference data to the phones.

The heavy load prior to the switch was negatively impacting all users.

The cause of the problem

A large number of field workers were updating a survey with a hundred thousand records that was the source of reference data for other surveys. These people were working online with data sims in their phones. So as soon as a field worker completed a survey the results were sent to the server updating the reference data. That automatically triggered the downloading of the 100 thousand records, now including updated reference data, to all the other field workers. Each field worker would have the latest reference data each time they completed a survey but the load was high and response times were getting slow.

Choosing a solution for using reference data

The decision about how to access reference data depends on the type of work your field workers are doing and whether or not they have a network connection while they are doing it. Here are three scenarios to help you choose:

Scenario 1 – Working offline without a network connection

In this scenario your workforce might return to a central location that has wi-fi every evening where they will refresh their phones, uploading any data they have collected and downloading changes to surveys and reference data. The next day they head back out into the field and work offline.

The surveys can use the following functions to get reference data from other surveys and from csv files:

• search. To get choices for a select question.
• pulldata. To lookup reference values.

So what happens if the reference data gets really large and is updated continuously by the field worker. Well this is not actually a problem. The server will not be overwhelmed since the workers are only synchronizing their phones once per day. They should actually press the refresh button twice, maybe once in the evening and once in the morning. The first time it will upload all the new data and the second time they will download the updated reference information that includes all of the previous days work from all of the field workers.

Scenario 2 – working online with a permanent network connection

Now the field workers are submitting data as they complete surveys and getting updates to reference data whenever that changes. Because they are online you can use the following functions to get reference data:

• lookup_choices. To get choice for a select question
• lookup. To lookup reference data.

Now when completing a survey, if reference data is required, there will be a small delay while the network call is made and then the required reference data will be made available. It is no longer necessary to download large amounts of reference data, most of which will never be used, and store it on the phone. If the reference data is large you should find this a faster approach on the phone as you no longer need to wait for the reference data to be loaded into the survey when you open it.

If your reference data files are small, only a few thousand records, or they are not updated often then you can use either the online or the offline functions in this scenario.

Scenario 3 – A hybrid approach

In this scenario perhaps the workers are online most of the time and want immediate updates to reference data but occasionally they wander outside of the network and still need to lookup those references.

At the moment you would need to use the offline approach and look out for potential performance problems from large frequently updated sets of reference data. However we do have a change request pending to only synchronise the updates to the reference data and not to download all the data each time a single record changes. This change request will allow the hybrid scenario to scale without causing performance problems. Let us know if you need it and I will increase its priority.

Features

Webforms works offline

Previously you could open a webform and then book mark it in order to be able to access that webform offline. Now, in version 21.01, the entire webforms page works offline. If you visit webforms while connected to the network all of the surveys that you have access to will be automatically downloaded and cached. Then if you go offline you will still be able to open these surveys.

Note there are some restrictions with this feature. If you have media files in your survey then these will not be automatically downloaded. If this is the case make sure that you open the survey while online. Once you have done this the media files will have been downloaded and cached and you will be able to access the survey though the webforms page while offline. In addition files required for language translation are not automatically downloaded. Hence you should open at least one survey before going offline to ensure that you have the language file for your language (English, Spanish etc).

A new look for the server

One of the challenges of maintaining a large server application over time is that the software frameworks that are used to manager the user interface change over time and it can be a lot of work to update old pages to match new ones. So the Smap server has web pages implemented using multiple technologies and with different appearances.

This release introduces a concerted effort to make these pages more consistent, simpler and faster. Of course that means introducing yet another technology version and style! In this case Bootstrap 4.5. However all the pages in the administration module along with the console have already been converted. Our aim is to convert and make consistent at least one other page per future release. Sol please bear with us while we work our way through this transition.

We have also standardised on horizontal menus across the top of the page. For no particular reason! Although they do use less screen space than vertical menus.

One advantage of the new pages is that they work much better in mobile phones.

Converted the user management page into two pages

The user management page now only has tabs for aspects of managing users:

• Users
• Projects
• Organisations
• Enterprises

All the other tabs that were also on that page are now on a Settings page:

Other

• The font colour of the navigation menu can be specified in the appearance tab of the settings page
• Appearance options for an organisation can no longer be set in the organisations tab. This tab is used by administrators to manage multiple organisations. Instead appearance is set in the appearance tab by administrators of an individual organisation.
• Setting of the webform banner image has been moved to the webform options tab on the new settings page.
• Users can be added to a security role in bulk. When creating or editing a role select the “Users” panel to add or remove users.

• Add a menu option to access Web Forms from the home page
• Add an option to select the logo used in a reports for a form. This logo can be specified in the settings dialog in the online editor and is selected from images in shared resources.
• Add support for embedding Quicksight dashboards into the server

This month we have revisited a design decision made 8 years ago to restrict each form to having a single geometry (geopoint, geoshape, geotrace). By form I mean the main form within a survey or a subform that can be created using “begin repeat”.

The rationale for this was that shape files used in GIS analysis, and GeoJSON files, only allow a single geometry. All the other values are attributes of that one geometry. So the geometry might specify the location of a building with attributes such as name, number of stories, construction material. In a similar way in Smap each Form and Sub Form is stored in its own database table and this table was allowed at most one geometry with all the other questions being attributes of that geometry. In addition the location was always renamed to “the_geom” which simplified some of the early coding in Smap.

This restriction has now been lifted. You can specify multiple geopoints, geoshapes and geotraces in a single form. The relationship between these geometries and the other questions in the form is up to you and your from design. You may decide that a single geometry per form still makes sense for your project in which case you can create your forms that way.

Multiple geometries in a form

Uploading Surveys from a spreadsheet

No longer will you get an error if you have more than one location in your form. Also location questions will no longer be automatically renamed to “the_geom”. This has the potential to cause problems if you are updating an existing survey that has already collected location data. The issue can happen if:

• You created a survey in a spreadsheet with a geopoint called say “my_location”
• You uploaded that survey to Smap version 20.09 or less where its name would have been changed to “the_geom”
• You then complete some surveys
• Later you decide to make some change to the survey and you replace the existing survey. In the meantime Smap has been updated to version 20.10.
• Now your location question will not be renamed and future surveys will record the location under “my_location”.

If the above happens you will see a warning in red text when you replace the survey saying that the location question will have a different name. If that is going to be an issue you can go back to your spreadsheet and change the name of the location question to “the_geom” so that it is compatible with the previously collected data. Then replace the survey again.

Analysis Page

When you create a map view for a survey you can now specify the geometry to be used for each form in the survey. A single geometry from each form will then be displayed on the map.

Exporting Shape, KML and VRT files

When exporting these files you first have to select the form / sub form your are exporting. Now you can also select the location question to use.

Data API

If you specify that the data is returned as geoJson you can now optionally specify the question that will be set as the geometry using “geom_question” in the URL, for example:

http://demo.smap.com.au/api/v1/data/s1_34?links=true&geom_question=q3&geo_json=yes

Documentation

Importing Data

Previously when you backed up collect data to a spreadsheet, a geopoint question would be put under two columns “lat” and “lon”. Now each geopoint will still be put in two columns but the name will include the question name so for example “my_location_lat” and “my_location_lon”.

If you have an existing backup with just lat_lon then you can still import that as the system will just grab the first geopoint question that it can find in the form and of course there should only be one in that case.

Start Location

If you set start location in your survey then the location of the start of the survey will be automatically recorded without requiring input from the enumerator.

You can now select this preload to show on a map in the analysis page, export a shapefile based on the location or create follow up tasks at the location.

Note. When creating tasks the location question to be used is found automatically, it is chosen in the following order:

• First. The first geopoint question answered by an enumerator that is found in the top level form
• Second. A geopoint value automatically set using the “Start Location” preload
• Third. The geometric center of the first geoshape or geotrace question that is found in the top level form

Other Changes

• Users with “View Data” permission can now access reports
• Fixed a bug where having server side calculations in a survey caused creation of a backup of the survey results in a spreadsheet to fail
• Add a warning message in webforms if a browser is not supported. Previously some older browsers could just cause webforms to stop

Several customers use Power BI to show a dashboard from Smap data. They extract the data by periodically calling Smap’s data API. This works well, although it can add a significant CPU load to the Smap servers where there is a lot of data and Power BI updates frequently.

I thought I would have a go at using AWS Quicksight to do the same thing. This proved to be straightforward and within a few hours, including the learning curve, I had a working dashboard. which included the donut chart shown below.

Cool things about Quicksight

• It is serverless so It can scale automatically from small implementations to very large. This scaling also applies to cost which should be small for small usage and large for heavy usage.
• Dashboards can be embedded into your website
• You are not restricted to just accessing Smap data you can include text documents, other databases, use artificial intelligence services to gain insights into the data etc.
• Apps are available for iOS and Android to show the data.
• It now supports maps which seems to be a relatively recent addition
• When accessing a Smap server, which is also on AWS, the request does not need to go across the Internet
• A built in data engine called “SPICE” which stands for Super-fast, Parallel, In-memory Calculation Engine offloads the work from the Smap server for your data crunching.
• It is pretty easy to use.

How to get Started

• Create an account on AWS
• Ask Smap to provide a logon to access your data on the server. Specify to Smap the surveys you need to access as well as any table joins you want. We will set up secure read only access for you to just your data.
• Start creating dashboards.
• Embed the dashboards into your own applications

Summary

If you are already a PowerBI, Tableau or other BI user then you can use that tool to add a dashboard to visualise Smap data. Probably using the API but we can also consider a solution with a direct JDBC data connections.

If you are not currently using a BI dashboard then you can consider using AWS Quicksight.

September’s release is now out with a big focus on Webforms and in particular making sure it has the same capabilities as fieldTask.

New Features

lookup and lookup_choices are now supported in webforms

These functions are equivalent to search and pulldata however they only work online as they will make a network request to the server to get data when they need it. “What is this” I hear you say, why would I use them when I can use pulldata() and search() both online and offline. Well if you are going to be using fieldTask in remote areas then you would not use them however if:

• You expect to always have a network connection and
• the data you are looking up is very large 100,000 or a million rows or the data is changing very frequently and you want always to be up to date

then the online versions will be much faster.

documentation

lookup supports multiple values

As per the “pulldata” function you can now use the “lookup” function to get multiple values from the server while online. This means you can use it to get data that will populate “repeats”.

The following video shows how this can be used to create an educational assessment system.

Expressions can be used to filter choices in lookup_choices

Lookup_choices performs an online lookup to get choices from another form or a CSV file. If you are familiar with using the “search” function to get choices from a csv file then you know that there are some pre-defined criteria for filtering the choices. For example ‘matches’, ‘contains’, ‘in’, etc.

Expressions allow you to be much more flexible in how you select choices. For example in the following video the filter is:

#{votes} > ${min_votes}

So the above filter means that only personnel who have more votes than the minimum are returned. ${} means to use the answer to the question in the form that is being filled in. #{} means to use the answer to the question in the form, or csv file, that is being looked up.

Here is another expression taken from the “Book” example survey in the documentation.

'${time_wanted} > #{from} and ${time_wanted} < #{to} and #{available} = 'OK''

More details on how to define filters can be found here: https://smap.com.au/docs/server-expressions.html

Other

• Improvements to performance of dashboard
• Automatic refresh of panels in the dashboard is now limited to maps and charts. If you have a table view you will need to manually press refresh in order to update it.
• Improved tabbing between questions in the online editor. When you tab into a question label it the text will be selected by default so you can just start typing to overwrite it.
• Add an online tool to look up a surveys identifier so it can be used in lookup_choices, pulldata or other functions that refer to other surveys
• Support for Ubuntu 20.04 LTS
• Addition of option to include read only question data in exports. This is now required as people are setting the value of read only questions using calculations. Hence they can contain useful data.
• Added bulk changes to console. You can now select multiple records and then update all of them to the same values.
• Improvements to uploading of media from webforms so that more media files can now be uploaded. 100MB+
• The lookup_labels function also now works in Webforms.

The last release of the winter of 2020.

New Features

1. Support for Matrices in WebForms. These can contain mixtures of question types.
2. The labels of groups are now included in PDF exports
3. Added a Webform view button on the form management so you no longer need to open the editor in order to try out a new survey in webforms
4. When selecting columns to show in the console all columns can be selected or deselected using one click
5. Export of console data in word documents. Data can be formatted as QR codes.
6. PDF titles are now muli line

Matrices

A new question type of “begin matrix” is available in order to create matrix structures like that shown below. Further details are in the documentation.

• Export records and columns shown in console to word. Columns can be selected to be shown as QR codes
• An auto refresh rate can be specified for the analysis dashboard in the organisation settings

It looks like we have just got the May release out in time! Enjoy while I get straight into the June release.

New Features

Transcription of Medical Notes

Transcribe Medical can now be used to convert audio into text with special consideration given to medical terms. To use this you will need to add the following parameters to a text question:

• auto_annotate=yes. This makes the system automatically convert the audio to text otherwise you can use the console to manually do the transcription. You can also use the console to modify an automatic transcription.
• source=question_name. The source identifies the name of the question that has the audio recording
• medical=yes. If not set the standard transcription will be used and probably will make a mess of the medical terms.
• from_lang=en-US. US english is the only language currently supported. Because there is only one valid choice you can omit it.
• med_type=conversation, or med_type=dictation. If you specify conversation then the transcription will expect more than one voice.

After you submit your survey it can take a few minutes for the transcription to happen. Just keep pressing refresh in the console until you see the results.

Online Editor Support

The online editor now supports the setting of translate and transcribe parameters.

In the online editor select “parameters” as the attribute that you want to edit. Then click on the “edit” button of the text question that is going to hold the transcript. The annotation parameters can be set on the “Annotate” tab of the dialog.

Cost

As with the standard transcribe there are fees levied by AWS on the use of transcribe medical. Currently we allow 800 seconds per month free usage. However this free usage has to be enabled for an organisation. Get in touch if you want to try it out or need more than 800 seconds per month.

“In” and “not in” Supported as search functions in WebForms

In the previous release support was added for cascading selects using CSV files in WebForms. These used the ‘matches’ function. For example:

type        name    label     appearance
select_one  country  Country  search(locations)
select_one  city     City     search(locations, 'matches', 'country', ${country})

Now you can also use the ‘in’ function. The list of values is space separated. So the same format as select multiple question. This allows you to do the following:

type            name     label     appearance
select_multiple category  Category  search('list')
select_one      product   Product  search('list', 'in', 'category', ${category})

The products that are in the selected categories will be available for selection in the second question.

“not in” works in a similar way but will only show choices that do not have a match in the list. The other 3 search formats supported by fieldTask are not currently supported in webforms:

1. contains
2. startswith
3. endswith
4. matches (webforms)
5. in (webforms)
6. not in (webforms)

Support for Static Default Images

You can specify the name of an image, from shared resource, as the default value of an image question. For example this could be a diagram on which the user is expected to mark their response.

Other Changes

• The server is now completely translated into Portuguese
• You can now set the background colour of buttons and the colour of button text from the web form settings tab on the users page.
• The server and identity menu options in fieldTask can be disabled on the server
• When conducting an email mailout you can generate the links and export them to an excel file. This allows you to send the links using other channels to the user. For example from your own email server in a fully customised email message.
• The guidance hint in surveys can now be enabled or disabled on fieldTask using a server setting.
• High resolution video capture in fieldTask can now be disabled/enabled from the server
• Links to embedded files are shown in PDFs
• The latest mapbox styles are now supported for custom maps
• Limits have been added to export of survey data for importing into another survey. This overcomes a problem where exporting surveys with tens of thousands of images could cause the server to crash.

Bug Fixes

• Errors in the task creation rule for a single task group should not now cause the application of rules for other task groups in the same project to also fail.
• Leading zeros in task durations that previously caused task group rules to fail are now automatically removed.
• Other miscellaneous crashes reported over the last month

The example application was out of date and did not work. This is because it used the old approach to “oversight” forms. The new approach is that any form can be an oversight form and used to annotate submitted data. My apologies if anyone tried the obsolete example app.

It now works again and I have taken the opportunity to add some artificial intelligence services:

• Automatic identification of objects in photographs
• Automatic conversion of an audio recording into text

Another change is that the documentation on example applications has been moved to https://smap.com.au/docs/example-applications.html from its previous location in the “Products” menu.