Maybe if we defined file formats and said X was Version 1.0 then we could tag every 1.0 document with a formatVersion attribute.

While administering a subtest with validation, a timer gets set that console.log's "ERROR!" if some input doesn't validate.

This behavior continues even though the page has changed, say to Collect or Manage.

Give guidance to enumerator as to what format to enter (number versus letters) e.g. "For how many years have you been a teacher".

From Liberia: Concerning the freezing of the Kindle and the time elapses; what I understood from the assessors was that for example while conducting a test , in particular, oral reading fluency,the timer goes well until it get to 8 seconds and it freezes at that point and just jump to 3 seconds.

I have seen some of these "jumps" myself. I don't think they impact data or the actual seconds that passed, but it does seems as if the timer 'hangs" a little sometimes from what is outwardly visible, but in the background continues to run down appropriately. Something to do with the page refresh?

If child does not consent, and non consent button is clicked, sends into endless loop. Needs to register that there was a non consenting child then move to start a new assessment.

If you click "Next" while a timer is running during a test, it prompts you to click on the last attempted grid option, but does not change the input mode to "Last Attempted". As a result the user is left marking their last attempted option as wrong.

Currently we are downloading almost 1MB worth of subtests everytime.

We need to make sure people have enough information to construct assessments that will generate data that's useful.

It would be very useful to enable the countdown timer in the timed subtests to float on the screen so that it is always in view. I feel a bit lost not being able to see the timer (except at bottom and top) during these sections and it would give the assessor a bit more warning before the timer ends and screen flashes.

Another reason for making the time always visible to the assessor is the need for them to apply the 3 second rule-- if a student stops/hesistates for three seconds they are suppposed to provide the letter/word, mark it wrong and tell the student to go on. Adept assessor will count three seconds in their head, but others may need the timer to remind them.

Example "Don't Know" gets trunkated to "Don".

When going to http://tangerine.iriscouch.com/tangerine/_design/tangerine/index.html#login
entering credentials, hitting "Login" does not work. Hitting "Enter" on keyboard works

https://play.google.com/store/apps/details?id=com.gears42.surelock&hl=en

returns correct, incorrect, missing, total regardless of prototype. Should give useful information instead.

During each student assessment a statement of informed consent is read aloud to the student and they are asked if they want to participate. Those (very few) who do not wish to participate are permitted to return to their classrooms and a replacement student is randomly sampled.

Currently, if "No" is clicked during the student consent section, Tangerine sends the user into an endless loop. Instead, it should send the user to a screen to collect the child's gender, grade and a note on the reason for declining to participate, if available (e.g. student cried). This output should be associated with the "No" responses for student consent so that we are able to calculate how many students declined from each school/grade/gender.

Use quick fix to handle this (external script)

When going to http://tangerine.iriscouch.com/tangerine/_design/tangerine/index.html#login
entering credentials, hitting "Login" does not work. Hitting "Enter" on keyboard works

From the "using the back button" issue that Sarah mentioned, perhaps we can have the button on the save results screen send the user back to the main assessment selection screen rather than to the beginning of the same assessment. This would be particularly useful in situations where there are different egra/egma first instruments.

1. Start the timer on a timed math subtest, such as number id or addition or subtraction.
2. Stop the test.
3. Mark the last item as the last attempted.
   I want to mark them all as incorrect, but if I mark the first 5 wrong the autostop will kick in. Instead I will start marking them from the end and work my way back to the beginning.
4. Mark last, second to last, third to last. Continue . . .
5. And then you see it, suddenly items 4-9 cannot be edited. And only those four items.

Weird.

Currently there is no autostop feature on the untimed sections (such as Kenya Missing Number).

Start the time, then switch to "last attempted mode" and you can mark the last attempted while the timer just sits there counting away the time. . . .

Add option for drop down list to question answer type - e.g. numbers, etc; Especially if more than 5 answers [even if only for single option question answer types]

The Kimba Yassah Error: Data verification to ensure the entire subtest was downloaded.

Repeated issues with out of order questions, specifically on the Liberia orientation to print subtests.

Need to remove cleaning code.

In the grid responses there exist buttons all along the right-most column that allow the user to toggle an entire row off and on. Unfortunately, this feature exists even after the test has stopped and the last grid attempted has been marked. This enables the student to get a grid wrong even if they never got that far.

Liberia: It was noticed by few of the assessors that in some cases, the passage ( Musu story) and the questions appeared on the same page [I have never seen this at all], while sometimes it would need to tip the next button to get to the answer. [we have already seen this before the data collection. Mostly, enumerator would score the passage, then hit next, and the questions subtest screen would appear, but without questions, only with the instructions and 'NEXT' button - one needs to hit 'NEXT' to have the questions appear.

Does not seem to impact data, just weird for enumerator.

The result should include the following

• Revision number of the assessment
• Unique Kindle identifier
• Tangerine Version

it should

Once in a while a survey will say that something needs to be filled out. Yet it has been filled out. Reclicking will let you proceed.

This causes events to register multiple times.

Recommend dividing views into "durable views" and "disposable views."

Maybe one subtest view to rule them all.

Auto stop feature triggers if the first line is all wrong, but with one click, the user can then mark first row correct afterwards and move on. In fact, all answers and last-marks are adjustable after the autostop feature.

Getting combined with irrelevant other subtest information

After starting and stopping the timer on a grid the value often goes negative.

There is a function in Utils that will sanitize html entities and a few characters for safe rendering.