Revision as of 11:57, 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.

EPrints reports any potential issues with an individual item on the item control page. This can be useful for:

The number of issues identified appears on the Details tab:

A new "Issues" tab is also available:

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

Issues search - some issues may be time dependent

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==
-When viewing the item control page, the number of issues identified appears on the Details tab:
+===Issues with individual items===
+EPrints reports any potential issues with an individual item on the item control page. This can be useful for:
+* a depositor editing an item before submitting to review
+* an editor reviewing an item before making it live
+* an editor or administrator viewing/editing an item in the live archive
+The number of issues identified appears on the Details tab:
 [[Image:Issues_count.png]]
-A new "Issues" tab also appears on the control page:
+A new "Issues" tab is also available:
 [[Image:Issues_tab.png]]
@@ Line 21: / Line 29: @@
 [[Image:Issues_details.png]]
-Issues tab - eg. in editorial review
+===Searching for Issues===
 Issues search - some issues may be time dependent
-Behind the scenes
+==Behind the scenes==
+===Default Settings (EPrints 3.1)===
 issues.xml