We've listened to our clients and are proud to have incorporated many of their great suggestions into Analyse 5.5. The key new features are described in this article.
The UI and Analyse developers have given Analyse a more modern feel with updated icons throughout the application's user interfaces:
When you load a portfolio, you will now see a progress bar at the bottom of the Analyse window to the left of the file name:
The developer has made a few 'under-the-bonnet' enhancements to the speed and memory consumption required when calculating results (especially in calculated variables):
Until now the conditional formatting menu has allowed basic checks on numeric cells (=, <>, >, < etc.) and a character count of alpha cells. The latter made conditional formatting for column significance tests against totals possible, but not easy. However, we have now removed the need count your columns beforehand and for the set-up of two separate conditional format specifications by adding in new operations on strings (Contains, Does not contain, =, <>):
Now you can have one conditional format specification like below:
(note we set cells with character length = 0 back to the background colour because these are also included in the Does not contain '-' rule which sets cells to be green)
This single conditional formatting specification will work for any number columns.
26 columns or fewer:
More than 26 columns:
More options for opening .qex files directly with Analyse
You can now open a field task and inverted data by directly pointing to a .qex:
Often the default 'Askia file' is the .qex stored in the working directory:
Before we were forced to change this as .qex could not be read:
Now there is no need to change this or create a new .qes:
With the inverted .qes file loaded in Analyse, select the Edit menu > Generate fast metadata files:
Firstly, this creates a .qex file with '-meta' added to the name. Remove the suffix from the .qex name or add '-meta' to the .dat folder name (before the .dat)
Secondly, it creates elements which were formerly stored in the .qes such as Tab templates, Profiles, Calculated variables, Weightings, Sub-populations etc. as .xml and saves them in the .dat directory:
The same Node.js technology that exists in Askia Design is now implemented in Askia Analyse. This allows Analyse to have its own REST API so we can access information about the metadata and get the data from a .qes or .qew file through http communication. This opens up integration possibilities with R, Python and any other modern programming language making use of their extensive libraries.
The blog article in the link above gives full background and detail of how the functionality works. Below are a few key related screenshots:
Previously, the conditional formatting for question totals was tied to the row totals so you couldn't have a separate rule for each. Now we have added and additional option so you can:
We now have a new scripting interface in Analyse 5.5.2 accessible in the 'Automation' menu.
Generic scripts can be run that generate a portfolio for any survey. If the survey has 'Tags' set in Design 5.5.2 or higher (e.g. tags for question types such as Demographics, NPS or tags for response types such as Main brand, Main competitor) then it gives more flexibility to quickly produce the required analysis. Some examples shown below:
i) Generate a portfolio which has each single question (excl. calculated and developed questions) in its own tab definition. Each tab definition has a tab template, 'CountsAndCumulated', from your library set into it:
ii) Generate a portfolio which has a tab definition for every level found in your survey file and display the loop questions as a summary table:
iii) Start with a portfolio that contains a generic NPS set-up on a numeric question:
Call this portfolio in your script to apply the set-up to other numeric questions (those in a brand loop). In each tab definition, show the NPS of the main brand, followed by one of the three competitor brands and add the demographics questions to the columns as a break.
Variable tags (Demographics, NPS):
Response tags (MainBrand, Main Competitor):
The script and portfolio it generates automatically:
The syntax on line 28 allows me to override the tab template that was set in the the original portfolio with one from my tab template library.
The functionality is fairly new and has already some improvements added in 5.5.3. Keep your eyes peeled for knowledge base and blog articles which will showcase more useful applications of the automation scripts and attempt to explain the structure and keywords of the language in some more detail.
You can also run automation scripts from Analyse command line using the /"automate:" parameter e.g: /"automate:C:\Qes\CreateSummaryTabs.txt"
In the View > Data menu you can show raw data for selected variables. These can now be saved in the portfolio by pressing the 'Send to portfolio' button. They can have tab-styles applied to them and even key options from the tab-template (e.g. 'Break according to page layout'). When exported out to Excel, they also work with your table of contents / hyperlinks.
In order to set the tab style or break setting, right-click on a regular tab definition which already has the settings you need > Copy > right-click on your raw data definition > Paste tab-template and/or Paste tab-style.