search

ldbase / ldbase_issues

A repository for managing issues with LDbase
0 stars 0 forks source link

The Data Entry Gamification #13

Open trreynolds opened 4 years ago

trreynolds commented 4 years ago

While the user is entering their data, we need an easier system of showing them what is happening. (For example: somewhere on the screen is some sort of visual showing them what they will be entering: project details, datasets, codebooks, presentations, DOIs...) and the visual shows them both what they have entered, and what they still need to enter. At one point you had suggested a thermometer for this.) Also, as they enter each portion of their project, we would like it to pop up screens that say something along the lines of: Great! You have created a project. The next step is to add a dataset... And then after the dataset it would be "Great! Do you have a codebook that goes with this data? (option to click yes, no).... "Have you done any presentations on this?" .. That kind of thing we had talked about in the beginning of project design. Remember too, that during this testing process, we are feeling "lost" in this process (If I take a minute to go do something else and come back to my computer, I can't tell if I am in the middle of entering a dataset or what).

bryjbrown commented 4 years ago

Cross-referencing with https://github.com/ldbase/ldbase_issues/issues/4 as they seem related. Having the walkthrough existing somewhere would go a long way towards the goal this issue is trying to accomplish.

Favenzio commented 4 years ago

Similar to Issue #4, it makes sense for us to add signs and guideposts when we have a better understanding of the problems users may be encountering. Once Mason starts testing and we have more data regarding usability issues, we can use the techniques described in the original issue to enhance the user experience.