ami-day
commented
4 years ago @clairerye I changed the description again, is it more accurate this time?! After discussing I thought I better move the previous description to a different ticket since the wrangler view is less of a priority.
aaclan-ebi
Description
User story: "As a Contributor I want it to be easy to read and understand error messages so that I can easily correct my mistakes."
Background: When contributors contact us about a new project, they will be directed to the contributor UI to register their project. Currently, if/when errors are encountered, the error messages may be difficult for a contributor to interpret. The goal of this ticket is to identify and list possible errors that contributors may encounter when registering their project using the ingest UI and to then implement solutions to address these errors. Once the errors are established/confirmed they will be added to separate tickets for the development team this sprint.
Acceptance Criteria
[x] Test example user errors in staging ingest UI acting as a contributor might do. Add a description of the user error to a document along with the associated error message (if any) and a link to the specific test (ingest project url).
[x] Share document to confirm the errors are expected and general feedback
[x] Group/Summarise the error types
[ ] Create a set of tickets reflecting each of the agreed error types
[ ] Implement technical solution for each ticket if possible this sprint (We may need to wait until we meet with Melanie and the JSON validator team to discuss direct changes to the validator output?)
Shared google doc.: https://docs.google.com/document/d/1EKenGaXzDKYYgaE316Jf4W6HMTvwy3GvFLuIXX-j9fg/edit