Tomasz.neugebauer@concordia.ca: Created page with '{{dirs}} The `issues_audit` script iterates through eprints and finds issues in the archive. It can be ran like so: `/opt/eprints3/bin/issues_audit …'`


2015-08-21T17:40:32Z
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> …'
New page
{{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>

</code>



The <tt>issues_audit</tt> 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.

Issues audit - Revision history

Tomasz.neugebauer@concordia.ca: Created page with '{{dirs}} The issues_audit script iterates through eprints and finds issues in the archive. It can be ran like so: /opt/eprints3/bin/issues_audit …'

Tomasz.neugebauer@concordia.ca: Created page with '{{dirs}} The `issues_audit` script iterates through eprints and finds issues in the archive. It can be ran like so: `/opt/eprints3/bin/issues_audit …'`