Difference between revisions of "Using Issues for Quality Control"

From EPrints Documentation
Jump to: navigation, search
Line 7: Line 7:
 
This page describes how issues are shown in the Web UI and how the process of identifying issues works behind the scenes.
 
This page describes how issues are shown in the Web UI and how the process of identifying issues works behind the scenes.
  
==The Issues Interface==
+
==Working with Issues==
  
 
===Issues with individual items===
 
===Issues with individual items===
Line 28: Line 28:
  
 
[[Image:Issues_details.png]]
 
[[Image:Issues_details.png]]
 +
 +
The depositor, editor or administrator can then use the editing options to correct the issue (see Reference below).
  
 
===Searching for Issues===
 
===Searching for Issues===
Line 47: Line 49:
 
[[Image:Issues_search_results.png]]
 
[[Image:Issues_search_results.png]]
  
===Reference: Issues identified (EPrints 3.1)==
+
===Reference: Issues identified (EPrints 3.1)===
 +
 
 +
'''1. In press for too long
 +
 
 +
'''2. Author names backwards
 +
 
 +
'''3. Exact title match
 +
 
 +
'''4. Similar title
  
 
Repository administrators upgrading to EPrints 3.1 may also want to revisit their data holding
 
Repository administrators upgrading to EPrints 3.1 may also want to revisit their data holding

Revision as of 12:19, 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.

Working with Issues

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:

Issues count.png

A new "Issues" tab is also available:

Issues tab.png

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

Issues details.png

The depositor, editor or administrator can then use the editing options to correct the issue (see Reference below).

Searching for Issues

Some issues may be time dependent, so will not be identified up at the point of deposit or during the editorial review process. For example an item that is listed as "in press" (ie. due to be published) in 2007 may need attention if it is still in press 2 years later - by that time the item will probably have been published and there may be extra metadata available (such as page numbers) which can be added to the item record.

Also, Repository administrators upgrading to EPrints 3,1 may want to revisit their existing records and use the new system to identify any potential problems.

EPrints provides an Issues Search function that is available to editors and administrators via the Admin screen:

Issues search button.png

The Issues Search allows the repository to be searched using a number of criteria, including issue type (see Reference below), item publication date, type and subject headings. It is also possible to limit the search to one of the 4 areas of the repository - here the repository administrator searches for all issues related to items in the live area of the repository:

Issues search form.png

The search results are presented as a list of items, with each item's issues summarised below:

Issues search results.png

Reference: Issues identified (EPrints 3.1)

1. In press for too long

2. Author names backwards

3. Exact title match

4. Similar title

Repository administrators upgrading to EPrints 3.1 may also want to revisit their data holding

Issues search - some issues may be time dependent

Behind the scenes

Default Settings (EPrints 3.1)

issues.xml

Example - check for documents with >1 file

Issues plugins

Example - document checksum does not match

issues_audit