Exception reports
back up to User Stories: Defining features and functionality VIVO needs - September 2011
User types involved
Narrative User Story (for sharing/review/voting)
to be written
Background
Exception reports are very important for identifying and resolving issues related to the usability of the application.
Wish list for improvement
The following should be included in the report:
- System related errors
- Errors triggered by user actions
The report can be displayed on the VIVO interface.
e.g.
2011-10-21 10:18:58,995 [PSet_TripleStore_RDB] Exception executing delete com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
2011-10-21 10:27:26,614 [RDFDefaultErrorHandler] (line 1 column 1): Content is not allowed in prolog.
Technical considerations
Errors can be extracted from the log files.
Priority or staging considerations
See NIHVIVO-3565 in the "Site management and operational improvements" component
