Blaise 5.3.0 is coming

Layout Language in the upcoming 5.3.0 release

A layout section has been reintroduced in the datamodel source. The syntax in this section is similar to the layout section in older versions of Blaise, but not exactly the same. For example, FROM .. TO constructions are no longer allowed, but instructions can now contain parameters, and instructions can be assigned to (local) types. It is not required to use the layout section. It is still possible to define all layout in the Layout Designer, but as soon as the datamodel contains any layout section, existing layout will be overwritten by the layout generated based on the layout sections (as soon as the datamodel is prepared). It will be possible to apply changes to the layout using the Layout Designer and generate the layout statements back into the datamodel, but this will not be fully automatic as comments and conditional defines that might be inside the original layout sections can not be generated. The new sections can be manually reviewed and edited using a wizard before updating.

DATAMODEL LayoutSample
PRIMARY
ID
TYPE
TPhoneNumber = STRING[12]

FIELDS
ID "Please enter your identification number": 0..1000
FirstName "What's your first name?": STRING[20]
BirthDate "What's your birthdate?": DATETYPE
YourAge "Your age is": INTEGER[3]
PhoneNumber "What's your phone number": TPhoneNumber
Income "What's your income?": (Below10k "0 to 9,999 dollars",
Below20k "10,000 to 19,999 dollars",
Below30k "20,000 to 29,999 dollars",
Below40k "30,000 to 39,999 dollars",
Below50k "40,000 to 49,999 dollars",
Below60k "50,000 to 59,999 dollars",
Above60k "60,000 or more")
RULES
ID
FirstName
BirthDate
YourAge := Age(BirthDate)
YourAge.SHOW
PhoneNumber
IncomeLAYOUT
BEFORE FirstName NEWPAGE
AT TPhoneNumber RESPONSEVALUE TEMPLATE StringTextBox(EditMask:='(000)-0000000')
LAYOUTSET "CAPI-Large"
BEFORE FirstName ITEMSPERPAGE := 8
AT FirstName FIELDPANE TEMPLATE Vertical(Width:='900')
AT BirthDate CRITICAL
AT BirthDate RESPONSEVALUE TEMPLATE DateControl(Appearance:='TextBox')
AT Income DATAVALUE TEMPLATE AnswerList(Arrangement:='2 Columns')
PRIMARY
AT ID FIELDPANE TEMPLATE Horizontal
LAYOUTSET "Capi-Small"
BEFORE FirstName ITEMSPERPAGE := 1
AT FirstName FIELDPANE TEMPLATE Vertical(Width:='300')
ENDMODEL

CARI in the upcoming 5.3.0 release

The Windows DEP in Blaise 5.3.0 now supports CARI (Computer Assisted Recorded Interviewing). CARI enables audio recording during an interview. Which questions will be recorded is highly customizable using a combination of (consent) fields and other configuration settings.

cari screenshot

Audio data is AAC encoded in order to optimize the relation between audio quality and storage size. The encoded data is saved  in a server side database together with its metadata, including session, fieldname and timing information. Although SQLite is the default database, CARI supports the Blaise General Data Interface allowing you to configure any of the available DBMS.

Video Tutorial - Edit Mask

In order to offer yet another platform for help/self-training and to raise awareness for new functionality, we have made our first video tutorial.

This first video is about edit masks. The edit mask functionality has been available since the release of Blaise 5.2.5 and we wanted to show how it works.
In the video, you get a step-by-step view of how edit masks work and how you can create them.
We would love your feedback, so don't be shy and leave a comment on YouTube if you can.

We hope this video is the first of many, but only time will tell.

First version of Blaise 5 ACASI in the upcoming 5.3.0 release

Blaise 5.3.0 offers a first version of ACASI. This means that it is possible to play audio files in the data entry program(s).

The following functionality has been added to make this possible:

In the resource database editor, it is now possible to store media files outside of the resource database. To accomplish this, all media elements now have a Url property, which can be used instead of the FileName property. When a Url is specified, the media element is not stored in the resource database, but will be loaded at runtime from the specified Url. Specifying a Url will clear the FileName property and vice versa.

Continue Reading

Gaining deeper understanding