Issues audit
Revision as of 17:40, 21 August 2015 by Tomasz.neugebauer@concordia.ca (talk | contribs) (Created page with '{{dirs}} The <tt>issues_audit</tt> script iterates through eprints and finds issues in the archive. It can be ran like so: <code> /opt/eprints3/bin/issues_audit <archiveid> …')
EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects
The issues_audit script iterates through eprints and finds issues in the archive. It can be ran like so:
/opt/eprints3/bin/issues_audit <archiveid>
The issues_audit script should be ran on a regular basis to identify potential quality control problems. You may find it useful to setup a cron job to automate running this script. See Using Issues for Quality Control for more information.
