Hi Paul,
Since it works fine for me, I compared our two audit.csv structures:
-
I have the following CSV structure:
instance ID,event,node,start,end,latitude,longitude,accuracy,old-value,new-value
that I generated using the audit parameterstrack-changes-reasons=on-form-edit track-changes=true -
while I see on your side that your structure does not have track changes
instance ID, event, node, start, end,,,,,
I think the analyzer should ultimately be able to work with different audit formats such as the one you provided (even though the available indicators may vary), but this may be the reason why you are not able to upload your audit file in the analyzer.
@hugh_sun
It is a really nice start and very promising, I only looked at an audit file generated using some dummy data, but I must say I am quite excited to look at the data collected by our research assistants to see what the trends are for the different questions.
A few quick suggestions / comments:
- I would have the scale at the top of the screen rather than at the bottom or even better since the list can be really long I would ensure that the scale is always displayed on screen
- it may be handy to have the option to sort results by descending order (so that the questions or submissions that took the longest or have the most number of changes appear first)
- time spent responding per submission: in the studies I am involved in, there will be ~40,000 / 50,000 submissions in total, so in this specific context the list can become really long