New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-write the error codes on the Analyse page to be more understandable to users #232
Comments
great, plan: seb to generate list error codes, lisa to review and write clearer ones for now, then we rethink |
@lmfrench not very user-friendly, but the codes are basically in here - let me know if they are not standing out enough for you! https://github.com/ebmdatalab/openprescribing/blob/master/openprescribing/api/views_spending.py |
yes thanks will go through them later in the week! |
I think the only error code from that list which might appear to users on the analyse page is this one: Possible change: Is it clear that by search box I mean under 'on' they must be the same, and under 'versus' they must be too, but that you could have different lengths in each? I couldn't think of a better way to phrase it |
Will add this to the FAQs, and then need link added to error code |
Error codes on the analyse page are not always clear to users, and don't explain how they might be able to fix the issues e.g:
Use Case:
As the Head of Medicines Optimisation, I want the error codes on the analyse page to be clear on how I can solve the problem so that this doesn't prevent me using this area of the site *
*This particular user tried to use analyse, got an error code, didn't understand it, so didn't use it again
Two things to deal with:
Easy: I can review the error codes we already have (Seb needs to send them across to me)
Hard: We don't have a comprehensive list of all the things that may cause an error to show up on that page. I will make a note of any that come up with demonstrating to users, and will create new github issues as they arise
(this issue can be marked as completed once our current error codes are re-written)
Priority (for rewriting error codes): Low
Ease: Easy
The text was updated successfully, but these errors were encountered: