Revision as of 11:48, 23 November 2009

Using Issues for Quality Control

EPrints 3.1 introduces a new feature to assist with the quality control process.

EPrints can automatically identify potential issues with an item and bring them to the attention of the repository editor or administrator.

This page describes how issues are shown in the Web UI and how the process of identifying issues works behind the scenes.

When viewing the item control page, the number of issues identified appears on the Details tab:

A new "Issues" tab also appears on the control page:

Selecting this tab will list the full details of any issues identified with the item:

[[Image::Issues_details.png]]

Issues tab - eg. in editorial review

Issues search - some issues may be time dependent

Behind the scenes

issues.xml

Example - check for documents with >1 file

Issues plugins

Example - document checksum does not match

issues_audit

@@ Line 9: / Line 9: @@
 ==The Issues Interface==
-An issues count appears on the Details tab of the item control page.
+When viewing the item control page, the number of issues identified appears on the Details tab:
-A new Issues tab appears on the item control page.
+[[Image:Issues_count.png]]
+A new "Issues" tab also appears on the control page:
 [[Image:Issues_tab.png]]
-Selecting this tab will list any issues identified with the item.
+Selecting this tab will list the full details of any issues identified with the item:
+[[Image::Issues_details.png]]
 Issues tab - eg. in editorial review