Manual review of data
Manual Review and Corrections
The results from the automated correction can be manually reviewed and edited via the web interface. It is especially importanat to review the errors and warnings. More minor changes are flagged as 'info' messages. Since some of the problems could be caused by technical issues whereas other could be caused by problems with the content of the documents, it is advised to have both, the Contributing Scientist and the Content Administrator go through the review together.
There is an online XML editor included in the eXist release. The editor is called eXide[1] and is a modification of the online source code editor ACE[2]. With eXide it is possible to directly edit documents stored in the database, including features like syntax highlighting or code folding.
The eXide editor that comes packaged with eXist has been modified to create the reBiND editor. A screenshot showing a data file loaded in the reBiND editor after running the default automated correction is shown below.
It should be possible to modify eXist in a way that it takes the documentation of the changes and generates a list out of it. When the reviewer clicks on any of the items in the list, the editor will directly jump to the element that was changed within the document. A modified GUI could also allow to only view changes of a certain type (class) or done by a certain module. It could also allow to flag changes as reviewed and hide reviewed changes from the list.
Though this might be a good way for the Content Administrator and the Technical Administrator to review the changes, there is still the problem that the Contributing Scientist is confronted with the XML document and required to work with it. So at some point in the future a better interface for the Contributing Scientist to work with the data might be desirable (e.g. the use of automatically generated web forms to edit the data), but for the general infrastructure described in this text, the online XML editor is sufficient enough.
It is not necessary to review all the changes at once. The document can be stored at any time and the review process can be resumed at a later point. So it is possible that after the correction one of the administrators reviews the changes which are caused by technical issues or the XML format used, leaving only changes which are related to the data. Then the Contributing Scientist gets an introduction on how to review the file and the different change types that are still open for review. After the introduction the scientist can get back to his/her office or home and reviews the remaining changes whenever some time is at hand.- ↑ an Online Demo is already available at the eXist homepage.
- ↑ Ajax.org Could9 Editor
