Difference between revisions of "Using Issues for Quality Control"
| Line 31: | Line 31: | ||
===Searching for Issues=== | ===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: | ||
| + | |||
| + | [[Image: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: | ||
| + | |||
| + | [[Image:Issues_search_form.png]] | ||
| + | |||
| + | The search results are presented as a list of items, with each item's issues summarised below: | ||
| + | |||
| + | [[Image:Issues_search_results.png]] | ||
| + | |||
| + | ===Reference: Issues identified (EPrints 3.1)== | ||
| + | |||
| + | Repository administrators upgrading to EPrints 3.1 may also want to revisit their data holding | ||
Issues search - some issues may be time dependent | Issues search - some issues may be time dependent | ||
Revision as of 12:14, 23 November 2009
Contents
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.
The Issues Interface
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:
A new "Issues" tab is also available:
Selecting this tab will list the full details of the issues identified with the item:
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:
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:
The search results are presented as a list of items, with each item's issues summarised below:
=Reference: Issues identified (EPrints 3.1)
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
