Significance and Count Threshold

Why does significance change when I switch level or add waves of data in Askia Analyse?

This post explains which count is considered for the ‘Count threshold’ setting in Col sig advanced options. There is detail on how to calculate ‘Counts when independent’ and why this can change sig testing when the total base grows.


From time to time clients will raise a query regarding sig testing (Column significativity on closed) for a particular cell changing when the total base of their table grows, even though the count and % for cells in the table remains the same. E.g. this can happen when new waves of data are added or the level has been changed to show the response counts rather than respondent counts.

The reason for this is almost certainly the Count threshold setting in the col sig advanced options; it has been left as the default value, 5.

Column significativity advanced options in askiaanalyse

The Count threshold does not use the counts you would normally see in your tables but, instead, it uses the counts from the calculation Counts when independent.

You need to use the count when independent rather than the actual count because the usual count in the cell (crossed count) can still carry importance at low or zero counts.

Below is an example of when the the sig testing changes even though the count and % have remained the same (see column G)

Example of sig test change in askiaanalyse

5 is the default because this doesn’t bring to your attention differences which are not statistically important. The side effect is that you can have changes as the total base grows over time (and hence changes the count when independent). If this behaviour is not in line with requirements, the Count threshold can be changed to 0.

This applies to Column significativity on closed but you cannot perform the same calculation for Column significativity on numeric. The Count threshold setting exists in its advanced settings but it is not applicable and has no effect.

Link to this knowledge base article in our help centre

 

New AskiaVista AJAX API 2.2.0

The new AskiaVista AJAX API (2.2.0) is now released with the latest 6.0.3.x version of AskiaVista.

The documentation is now up-to-date

List of new features/fixes:

  • Add `footnote` parameter in cross-tab query (settings.results.footnote)
  • Add `language` parameter in queries to specify the survey language. It could also be add on the config, or specify via url
  • Add a new `languageUrlParam` in the configuration to read the survey language via the URL
  • Add methods:
    • getPortfolioLinks
    • getPortfolioLink
    • savePortfolioLink
    • deletePortfolioLink
    • getPortfolioLinkLayouts
    • getPortfolioLinkThemes
    • savePortfolioLinkTheme
    • deletePortfolioLinkTheme
    • getResources
    • saveResource
    • deleteResource
    • htmlEncode
  • Take in account the new calculations and their advanced options
  • Add the `baseUrl` key in the config. Strongly recommended to use it instead of `url`
  • Manage the new `rawdata` and `sectionpage` portfolio item type
  • Add a dedicated exception severity flag when the authenticity token in cookie is bad or obsolete, it then ask again the login form
  • Manage severity on server-side error to throw the `securityError` when it’s needed
  • Error messages are now htmlEncoded in the client side.
  • Security error don’t block the query stack, it now fire the security error and the regular error event

This askiavista is massive!

We have finally released version 6.0.3.0 of askiavista! First, of all, don’t judge a book by looking at the cover: this is more a 6.1 version than a minor version. Indeed, it packs:

  • 22 new features
  • 22 bug fixes
  • 7 miscellaneous tasks

Below, some of the key new features:

Portfolio section pages

Askiavista portfolio section pages

Users can now create Section pages within their Portfolios; these pages allow to add formatted text and media (image & video).
Such pages are a great solution for report introductions, notes, metadata, …

New portfolio link management

Askiavista new portfolio by link management

Portfolio links have been completely overhauled in order to allow many nifty features such as Expiry dates, Filter management, dynamic tabbing, custom URLs, default page, …
Portfolio links can also be duplicated in order to batch create multiple links.

Reorder portfolio items

Reorder portfolio items in askiavista

This was a recurrent client request: having the possibility to reorder elements (table definitions & now section pages) from within a portfolio.

Raw data / open-ended management

Askiavista raw data and open-ended management

Askiavista is now able to render data at interview level and can also render open-ended data! These flat tables are accessible in a dedicated view and can of course be embedded within a Portfolio.

Fixed headers

Fixed headers for large tables in askiavista

In order to improve our user experience when browsing large cross-tabs, we have added fixed headers (for Rows, Columns & Edges) to the Default table style.

Select all / unselect all in Dimensions

Select all - unselect all in askiavista's dimensions

This client request allows users to select all questions or response items in a given Dimension (R/C/E). This is especially useful when dealing with many questions or for very long lists of response items to which you may want to apply a given action (group, hide, …).

View source

View crosstab source in askiavista

This option (hidden by default), allows advanced users and API developers to embed table & chart data directly in their web page; could it be an askiavista-driven dashboard, portal or web page.

Compressed inverted data

We have decided to improve the inverted format:

  • We decided to rename the old files and not use the number of responses as an extension – this was causing unnecessary problems when a question was recalculated or if the max number of responses was manually changed in Design. The extension is always .dat.
  • The developed questions in a loop are no longer stored individually – the greyed questions always contained the information so we thought the cost of reading the whole greyed data for that question was a small price to pay compared to store all the data twice
  • We store system data -or peri-data – such as start time, end-time, IP-address, completion, …
  • The data is now compressed
  • We have backwards compatibility: inverted data produced with a version prior to 5.3.4 is read properly but the new inverted files are not readable by Vista (yet) or an old Analyse / Tools

We have seen up to 90% decrease of the inverted database size and almost no noticeable deterioration of the reading speed

For the full list of new features & bug fixes, check the changelog.

New Knowledge Base articles incoming!

We have been regularly updating Askia’s Help centre with various KB articles that cover our software offering. Here are some of these latest articles:

Askiadesign: about:blank error message

Microsoft recently updated Internet Explorer. This update may cause the below error message to be displayed in askiadesign:

about:blank error message in askiadesign

See the full article to fix this issue.

Askiafield: Data exports: Methods, Pros & Cons

This in-depth article covers all you need to know about the different data export methods along with the pros & cons for each method. From Supervisor’s Export to QES file to Analyse’s Data Inversion; this article also details SQL Synchronisation from AskiaTools as well as the powerful Fast Export method.

Read the full article for the detailed explanations.

 Askiaanalyse: Mean Summary Tables

This article goes through step by step examples and explanations of how to set up calculations in Analyse which will create a mean or sum summary table. There is also an introduction to script formatting and advanced sorting for such calculations.
This detailed article also provides downloadable example .QES files.

Access the KB article for more details.

Askiafield: Survey XML file is corrupt

Askiaface for iOS & Android make use of the XML version of the .QEX file; it sometimes occurs that certain characters (trailing spaces, &, >, <, …) will cause the survey’s XML definition to be invalid.

This article guides you through the necessary steps to fix a corrupt XML file: by identifying the cuplrit(s) and getting rid of them!

Check out the article for more details.

Askiafield: wildcards

This article describes how to use the Wildcard feature in Supervisor to find and update sample contacts based on regular expressions. Wildcards are a set of extremely useful tools that can power your workflow when searching / targeting specific contacts with large sample files.

Read the detailed article for more information.

Props to Seyf, Stephen & Jérome D for their contribution!