back up to User Stories: Defining features and functionality VIVO needs - September 2011
to be written
Exception reports are very important for identifying and resolving issues related to the usability of the application.
The following should be included in the report:
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.
Errors can be extracted from the log files.
See NIHVIVO-3565 in the "Site management and operational improvements" component