Design work

[davidblader]

• One checkpoint when visit created/started;
• second when media uploaded and data entry done;
• third is when double data entry has been done;
• fourth checkpoint is when conflict resolved, and when sent to DCC; add an extra flag when data monitored.

[davidblader]

Some more of Victor's comments:

[Victor] Highlight the background of the cell of the visit yellow if it is being monitored; or [Rida] add “M” next to the circle of the visit to say it is being monitored [Victor] All data entered means site can be reimbursed, while Double data entry, conflict resolution and send to DCC is when the visit gets locked [Victor] Set to green if sent to DCC;

[davidblader]

Personally I think setting the inner circle to green might be better suited for when initial data entry is done, then setting to blue when DDE is done, and then adding a white checkmark :white_check_mark: for when it gets sent to DCC. For data monitoring I would definitely prefer having an M within the circle rather than having a yellow background highlight as that would probably not look good and further complicate the current logic of row and column highlighting

[taracampbell]

What do you think about something like this? Once data entry has happened it turns blue, but not dark blue. We can add symbols to the circle to differentiate between the status. When everything is complete, it turns dark blue like the border and has a white checkmark.

I think we should add more info to the mouse over so that all of these small items are covered (data entry, media uploaded, double data entry, conflicts resolved, monitoring, etc.)

I'm still trying to think about how to do monitoring...

[taracampbell]

I think we should avoid a legend and rely on the mouseover to explicate. I think the users will learn quickly what the colours mean, and will be able to look at the mouseover whenever they need a hint. I haven't looked at your legend pull request yet though.

[davidblader]

this looks great! i agree with you on the legend, but i think some users would still like to have an explicit explanation of everything. typically i think users would prefer having a legend rather than having to do the color-semantic mental mapping themselves, especially with the additional symbols we'll need for the new stuff. i think we can omit it in the next demo and see what people say.

for data monitoring, maybe we could use this eyeball symbol and place it next to the circle (with better spacing obviously):

that being said i'm not 100% sure what data monitoring is tbh so i'm not sure if an eyeball is the most logical symbol for it, but we have all these glyphicons in bootstrap.min.css we can use

[taracampbell]

@davidblader What do you think about a legend in the help section then? One click of the '?' and it will show up.

Data monitoring is when one of the head neuropsych people reviews how new staff at the sites are administering the neurospych tests, and how they score them I believe. It's kind of a separate concept from the "data entry completion" that we are trying to track, so I want to do something that doesn't confuse that status info we are trying to convey. Glyphicons are cool - I used one to get the checkmark for completion. I'm gonna keep thinking about it.

[davidblader]

putting it in the help section is a good idea but i'm not sure how complicated it would be. i think the help section is typically generalized for the entire module / corresponding PHP page, right? so having the legend in there could make things kind of cluttered for the other things you have planned for the dashboard, unless we came up with a way to only have it displayed in there when the study tracker is in focus? i'm also not sure that the help sections are able to support anything other than UTF-8

[taracampbell]

You can put html into the help tables I'm 99% sure. Let's aim for that add see if we can get to work how we would like.

[taracampbell]

@davidblader We can hold off of the monitoring stuff until we merge the monitoring flag into LORIS. (We can still work on it, but it can't be included until then.)