2) There is a server side script which is designed to be run periodically (e.g. nightly) which inspects the contents of your repository. It is recommended that you run this via 'cron'.
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.

00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet

3) In order to bring the database configuration up to date, run epadmin update from the command line.

bin/epadmin update MYREPO

Usage

To use Issues2 once installed, go to the Admin section of your repository.
Under the Editorial Tools you'll see a new button called "Duplicates Search".

Clicking this takes you to a new search interface, where you can search for various types of issues.

The search results page shows you a list a records detailing the detected issues.
From this page you can manage the record in question, see a quick comparison of its metadata against its duplicate, or acknowledge the issue so its removed from the list.

A set of actions are available for detected duplicates.

- The user can 'manage' the record to correct or retire it.

- Or can 'compare' the 2 records to copy the differing field values between them.

- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.