Cumulative updates & future milestones

Over the past month, we have slightly shifted our development & release process with askiavista: instead of longer development cycles with many fixes & improvements, we have began to release smaller versions that mainly include fixes where new features are added at a slower pace.
This helps us maximise our response rate when fixing urgent issues. So, we are doing our best to release early, release often.

Below, a breakdown of the two latest minor updates for askiavista:

Version 6.0.3.1

released 21/11/2014

  • Add footnotes property to tables (new)
  • Export all in one page to Excel (fix)
  • Czech characters not rednered in MS Excel export (fix)
  • Infinite loader on Results when removing a raw data variable (fix)
  • Raw data response sorting not maintained when saved to Portfolio (fix)
  • User level survey offline status not taken into account (fix)

Version 6.0.3.1

released 24/11/2014

  • View switcher breaks when deleting Profiles and/or Portfolios (fix)
  • AskiaVista6 unable to open survey with numeric name (fix)
  • Vista6 – does not remove selected question when the question appears more than once in R/C/E (fix)
  • Calculated responses don’t compute the correct amount of responses (fix)
  • Portfolio linkID cannot be customised (fix)
  • Superpose response is applied when it shouldn’t be (fix)
  • Sub-population by GUI from V5 is not well interpreted in V6 (fix)
  • HTML encoding issues (fix)
  • Adding / removing a Profile or Variables empties the list of Profiles or Variables (fix)
  • Online – offline survey status causing issues (fix)

Future milestones

6.0.3.3
  • Export to PDF (new)
  • Highcharts not displaying Mean & combination charts (fix)
  • The chart is not saved into the template (fix)
  • Issue with fixed header in Firefox (fix)
  • Assigned factors not saved in Portfolio (fix)
  • Empty table when deactivating all calculations for tables (fix)
  • Erratic results in Search questionnaire (fix)
6.0.4.0

The integration of askiavista into askiaadmin that is planned for version 6.0.4.0.

Later

The improvement of AskiaVistaServer farming. This major overhaul has not yet been assigned to a version (and it may actually be introduced before the askiaadmin integration.

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

 

Myforce opens a new office in Prague!

I have a bit of important MyForce news to share with you: we opened a new office in Prague, Czech Republic!
Kateřina Marková (whom we have worked with for many years already) becomes managing director of MyForce CZ.

As Myforce keeps on growing both in turnover and in number of countries where our solutions are installed, opening MyForce CZ was a logical next step for us. Choosing Prague as our new office location is no coincidence, as we had good reasons to opt for this particular city: First of all, this will help us to support a number of important local MyForce customers. Secondly, MyForce has always had close relationships with Kateřina Marková, as we have been working with her on local projects for many years now. And finally, we are certain that having a Czech office will aid us in sustaining our relationship with Brno’s University of Technology.

Kateřina Marková, managing director MyForce CZ, added: “Becoming part of the larger MyForce group ensures stability and business continuity for our local clients. With the resources of the whole MyForce team at our disposal, we can provide an even better service.

As a result, Myforce has updated the website as well: www.myforce.cz is available for those of you who know Czech 😉

MyForce CZ
Počernická 272/96
108 00 Praha 10, Czech republic
+420 272 731 711
info@myforce.cz