kobotoolbox / enketo-literacy-test-widget Goto Github PK

https://docs.google.com/spreadsheets/d/1xpPW7QoNpILt-rR2q6BobZ1KrivHls18pd4EDM1s5V0/edit?usp=sharing

LTR: http://localhost:8005/::YY8M

Both: http://localhost:8005/preview/?form=https://gist.githubusercontent.com/MartijnR/47b8fda8059b904b773be883985c6980/raw/83ef708ec422c6befe367c6b598a965d3e0441fa/literacy-dev.xml

Either exactly at the flash point the finish button is clicked, or during the flash state the finish button is clicked (without selecting a flash word)

first 10 items are custom or null. The remainder are the incorrectly-read word (values)

12 23 23 343 null null null null null null 1 3 4 5 6 7 8 10

Message to show: ?

Show 3 values in human-readable format

However, if any word has been marked as in correct (stricken through), all the check boxes appear as expected.

Full details: https://community.kobotoolbox.org/t/literacy-widget-word-at-flash/14362/9?u=jnm

I assumed that 'word at flash' should be null in that case.

• to verify with SCF

A word can have these different states:

• unread
• read, correct
• read, incorrect

Is that right?

Hi @MartijnR,

In light of this change, do you have any advice on how to handle the following?

Right now, it's throwing a

TypeError: Cannot set property readonly of #<Object> which has only a getter
    at LiteracyWidget.get props [as props] (enketo-webform-bundle.min.js:1)
    at LiteracyWidget._getCurrentModelValue (enketo-webform-bundle.min.js:1)
    at LiteracyWidget._init (enketo-webform-bundle.min.js:1)
    at new Widget (enketo-webform-bundle.min.js:1)
    at new LiteracyWidget (enketo-webform-bundle.min.js:1)
    at Collection._instantiateSingleWidget (enketo-webform-bundle.min.js:1)
    at enketo-webform-bundle.min.js:1
    at Array.forEach (<anonymous>)
    at Collection.instantiate (enketo-webform-bundle.min.js:1)
    at enketo-webform-bundle.min.js:1

P.S.: The <Object> part of the exception message isn't getting escaped when presented to the user:

when installing in EE with Grid Theme

(or not inside group perhaps)

• test fix with form that has widget inside a repeat

• check

Though this seems very unlikely to happen, we need to program a behavior in case it does happen. I am assuming:

• the second ticked word indicates where the user was stuck at 600 seconds
• if second ticked word exists, we can make the calculations for the 3 (or 4) values
• if second ticked word does not exist submit something like "null null 5"

• When is the exercise completely finished and 'frozen'. When last word is clicked?

Here are three scenarios in order of our preference:

1.  After selecting “Finish”, the “correct/incorrect” and “word at n seconds” are frozen, but the “final word attempted” is not frozen and can be changed if the assessor marks the incorrect word.
   

2.  After selecting “Finish”, the enumerator is prompted with a message that says “Are you sure? If so, click ‘yes’ and then select the final word attempted“. Enumerator selects the final word and the assessment is frozen
   

3.  After selecting “Finish”, the enumerator is prompted with a message that says “Select the final word attempted“. Enumerator selects the final word and the assessment is frozen.
   

4.  After selecting “Finish”, there is no message, the enumerator selects the final word and the assessment is frozen.
   

1. click start to show words
2. click checkbox to mark as read at flash timer (e.g. 30 seconds)
3. click word to mark as incorrectly read
4. record (name of) last-read-word at 30 seconds (name is likely an index in practice, see this doc)
5. stop the exercise, without a possibility to re-do or resume
6. or auto-stop at 500 seconds?

At the end calculate:

a. words per minute (both correct and incorrect words? - excluding skipped words?)
b. number of incorrectly read words

The value stored in Enketo has 3 space-separated components:
e.g.

<lit1>5 45 4</lit1>

• number of words read incorrectly (5 in example) - value required
• words per minute, (45 in example) - value required
• word at 30 seconds (4 in example)s - value optional?

e.g. a required or constraint error

E.g. not when appearance=minimal, and not for any non 'select_multiple' type

Is that a required feature?

Is there a rule for how many words should be shown on a line or is can this be dynamic based on screen and word size?

once Enketo Core 5.0 is released

Probably leave disabled until start button is clicked

to comply with general Enketo widget requirement

Also check: Are the relevant, constraint expressions copied correctly?

This has not been implemented yet. Normally any Enketo widget should be able to load an earlier submitted/saved value. In this particular case, this would always be a completed test and show the end screen.

Assumed that this includes both correct and incorrect words.

• verify