https://wiki.eprints.org/w/api.php?action=feedcontributions&feedformat=atom&user=Jb4%40ecs.soton.ac.ukEPrints Documentation - User contributions [en-gb]2026-06-13T02:23:39ZUser contributionsMediaWiki 1.31.8https://wiki.eprints.org/w/index.php?title=User:Wr1r25&diff=17067User:Wr1r252026-05-15T14:43:47Z<p>Jb4@ecs.soton.ac.uk: Creating user page for new user.</p>
<hr />
<div>A new member of the eprints services team, starting to learn the eprints ecosystem and how it works. Started September, 2025</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=User_talk:Wr1r25&diff=17068User talk:Wr1r252026-05-15T14:43:47Z<p>Jb4@ecs.soton.ac.uk: Welcome!</p>
<hr />
<div>'''Welcome to ''EPrints Documentation''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:Jb4@ecs.soton.ac.uk|Jb4@ecs.soton.ac.uk]] ([[User talk:Jb4@ecs.soton.ac.uk|talk]]) 14:43, 15 May 2026 (UTC)</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_using_Docker&diff=13231Installing EPrints using Docker2019-07-31T13:52:36Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Simple EPrints 3.4 docker setup.<br />
<br />
- Justin Bradley, July 2019<br />
<br />
<br />
Sets up two containers, one for the database, the second for httpd and eprints.<br />
<br />
Needs Docker and Docker Compose, if you install Docker Desktop you get both of these.<br />
<br />
<br />
Edit docker-compose.yml and set EPRINTS_HOSTNAME to the name of your host machine, localhost is the default and fine if running locally.<br />
<br />
Disable any services binding to port 80, ie apache httpd.<br />
<br />
EPrints publications installation will be available via http://yourhost once set up.<br />
<br />
User: admin<br />
<br />
Password: admin123<br />
<br />
<br />
build and start<br />
<br />
$ docker-compose up --build -d<br />
<br />
normal start <br />
<br />
$ docker-compose up -d<br />
<br />
shut down<br />
<br />
$ docker-compose down<br />
<br />
<br />
There are a few issues.<br />
<br />
- The indexer often fails to start automatically.<br />
<br />
- Some additional perl modules may be required for some import/export libraries.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_using_Docker&diff=13230Installing EPrints using Docker2019-07-31T13:52:19Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Simple EPrints 3.4 docker setup.<br />
<br />
- Justin Bradley, July 2019<br />
<br />
<br />
Sets up two containers, one for the database, the second for httpd and eprints.<br />
<br />
Needs Docker and Docker Compose, if you install Docker Desktop you get both of these.<br />
<br />
<br />
Edit docker-compose.yml and set EPRINTS_HOSTNAME to the name of your host machine, localhost is the default and fine if running locally.<br />
<br />
Disable any services binding to port 80, ie apache httpd.<br />
<br />
EPrints publications installation will be available via http://yourhost once set up.<br />
<br />
User: admin<br />
<br />
Password: admin123<br />
<br />
<br />
build and start<br />
$ docker-compose up --build -d<br />
<br />
normal start <br />
$ docker-compose up -d<br />
<br />
shut down<br />
$ docker-compose down<br />
<br />
<br />
There are a few issues.<br />
<br />
- The indexer often fails to start automatically.<br />
<br />
- Some additional perl modules may be required for some import/export libraries.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_using_Docker&diff=13229Installing EPrints using Docker2019-07-31T13:52:07Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Simple EPrints 3.4 docker setup.<br />
<br />
- Justin Bradley, July 2019<br />
<br />
<br />
Sets up two containers, one for the database, the second for httpd and eprints.<br />
<br />
Needs Docker and Docker Compose, if you install Docker Desktop you get both of these.<br />
<br />
<br />
Edit docker-compose.yml and set EPRINTS_HOSTNAME to the name of your host machine, localhost is the default and fine if running locally.<br />
<br />
Disable any services binding to port 80, ie apache httpd.<br />
<br />
EPrints publications installation will be available via http://yourhost once set up.<br />
<br />
User: admin<br />
<br />
Password: admin123<br />
<br />
<br />
build and start<br />
$ docker-compose up --build -d<br />
<br />
# normal start <br />
$ docker-compose up -d<br />
<br />
shut down<br />
$ docker-compose down<br />
<br />
<br />
There are a few issues.<br />
<br />
- The indexer often fails to start automatically.<br />
<br />
- Some additional perl modules may be required for some import/export libraries.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_using_Docker&diff=13228Installing EPrints using Docker2019-07-31T13:51:25Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Simple EPrints 3.4 docker setup.<br />
<br />
- Justin Bradley, July 2019<br />
<br />
<br />
Sets up two containers, one for the database, the second for httpd and eprints.<br />
<br />
Needs Docker and Docker Compose, if you install Docker Desktop you get both of these.<br />
<br />
<br />
Edit docker-compose.yml and set EPRINTS_HOSTNAME to the name of your host machine, localhost is the default and fine if running locally.<br />
<br />
Disable any services binding to port 80, ie apache httpd.<br />
<br />
EPrints publications installation will be available via http://yourhost once set up.<br />
<br />
User: admin<br />
<br />
Password: admin123<br />
<br />
<br />
# build and start<br />
docker-compose up --build -d<br />
<br />
# normal start <br />
docker-compose up -d<br />
<br />
# shut down<br />
docker-compose down<br />
<br />
<br />
There are a few issues.<br />
<br />
- The indexer often fails to start automatically.<br />
<br />
- Some additional perl modules may be required for some import/export libraries.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Installing_EPrints_using_Docker&diff=13227Installing EPrints using Docker2019-07-31T13:50:43Z<p>Jb4@ecs.soton.ac.uk: Created page with "Simple EPrints 3.4 docker setup. - Justin Bradley, July 2019 Sets up two containers, one for the database, the second for httpd and eprints. Needs Docker and Docker Compose,..."</p>
<hr />
<div>Simple EPrints 3.4 docker setup.<br />
- Justin Bradley, July 2019<br />
<br />
Sets up two containers, one for the database, the second for httpd and eprints.<br />
Needs Docker and Docker Compose, if you install Docker Desktop you get both of these.<br />
<br />
Edit docker-compose.yml and set EPRINTS_HOSTNAME to the name of your host machine, localhost is the default and fine if running locally.<br />
Disable any services binding to port 80, ie apache httpd.<br />
EPrints publications installation will be available via http://yourhost once set up.<br />
User: admin<br />
Password: admin123<br />
<br />
# build and start<br />
docker-compose up --build -d<br />
<br />
# normal start <br />
docker-compose up -d<br />
<br />
# shut down<br />
docker-compose down<br />
<br />
There are a few issues.<br />
- The indexer often fails to start automatically.<br />
- Some additional perl modules may be required for some import/export libraries.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=GDPR&diff=12801GDPR2018-06-14T08:46:55Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>This page has been created to gather information and share code snippets to help EPrints repositories handle GDPR responsibilities. Some of the issues around GDPR will be specific to a repository contents, but others are quite generic. nb. We're not lawyers!<br />
<br />
As a general rule of thumb, this is about people's rights and privacy. Imagine a worst case scenario where the entire filesystem and database is made entirely public -- it's not a great situation, but consider what steps you could take to reduce the damage if that did happen - don't store any information about people that you don't actually need.<br />
<br />
=== Areas of GDPR that may be relevant to EPrints repositories ===<br />
* Giving people a clear privacy policy about how you will use data you gather about them<br />
* Gaining consent for storing and processing data you gather about them<br />
* Defining and enforcing a retention policy to remove information about people that is no longer required <br />
* "Subject Access Requests" where someone wants to know everything you know about them<br />
* "Right to Erasure" where people may request you remove information about them, but there are exceptions to this.<br />
<br />
=== Information about people ===<br />
EPrints potentially stores information about people in a number of places.<br />
* Users Dataset<br />
* EPrints Metadata <br />
** In the revision XML files storing old versions of metadata.<br />
* In actual documents<br />
* In the "request a copy" Dataset<br />
* Web access logs<br />
** In the History Dataset<br />
** The Access Dataset, IP Addresses can sometimes be used to identify an individual.<br />
** In the Apache logs in the operating system (this will not be dealt with on this page, but should not be forgotten)<br />
<br />
== Users Dataset ==<br />
This dataset is either populated with a web based sign up form, or in many cases, it is automatically built from an institutional accounts system. These cases need to be addressed in different ways.<br />
<br />
=== Imported users Dataset ===<br />
<br />
First of all, stop importing any fields you don't actually need and remove those fields from EPrints. nb. Removing the field in the config may not remove it from the database (citation required.. how the hell does that work?)<br />
<br />
Next stop importing any users you just don't need -- if they can't do anything while logged in they should never exist in the Users dataset.<br />
<br />
Next implement a data retention policy. This will be a script that removes or blanks the data of users that match a criteria. eg. have not appeared in the import script for more than 90 days and never made a deposit.<br />
<br />
=== Web signup users Dataset ===<br />
<br />
You should ensure that the privacy policy is up to date and in line with GDPR best practice.<br />
<br />
Stop collecting any information you don't actually need, and remove those fields from the database.<br />
<br />
Next implement a data retention policy. This will be a script that removes or blanks the data of users that match a criteria. eg. accounts more than a year old that have never made a deposit.<br />
<br />
=== Removing vs Blanking ===<br />
<br />
In some cases it may be more desirable to remove all the personal metadata from a record in the Users dataset rather than delete it completely. This has pros and cons.<br />
<br />
If you remove a user entirely who has deposited EPrints you may wish to reassign those deposits to an admin user, or a fake user called "left".<br />
<br />
=== Last Login Time===<br />
Storing the last login time of a user can be useful to identify which users are active and which are not to help ensure data is not being stored longer than is necessary.<br />
<br />
See [[GDPR/Last Login Time]]<br />
<br />
===Non-Active Users Report ===<br />
TODO<br />
worth having a count of items linked with the user on the report, along with their statuses?<br />
<br />
===Delete User Action===<br />
*Suggestion* Cron job to select all user accounts which have been inactive over a certain time threshold, check those users for affiliation to a publication (creator, editor, depositor etc.) which is either archive or buffer status and, where no connection exists, remove those user accounts.<br />
<br />
Admin will be able to select user accounts from the report to delete (within the report or individually?)<br />
<br />
Could be similar to: <tt>EPrints::DataObj::LoginTicket::expire_all</tt> - but with an <tt>$c->{'account_retention_time'}</tt> param taken away from the <tt>time()</tt> call?<br />
<br />
Need to check logintickets too?<br />
Someone may not have actually logged in for ages, but maintained a browser session/cookies for a long time?<br />
(currently our longest 'active' login is ~20 days).<br />
<br />
==Add 'Agree to privacy and data statement' checkbox on registration or request forms==<br />
TODO - should be 'versioned' - so if the statement changes, the version that was agreed to can be shown.<br />
Possibly a set/namedset, with the available options limited to only one when rendered to a user?<br />
<br />
Chris Gutteridge has written a blog post on GDPR with a few comments about the EPrints Request a Copy feature: http://blog.soton.ac.uk/webteam/2018/05/10/gdpr-preperations/#post-content-1793;char=5429-7155<br />
<br />
==EPrints Metadata==<br />
TODO<br />
==In actual documents==<br />
TODO<br />
==Request a copy Dataset==<br />
This collects an email address and a reason for requesting the document. Without intervention this can be stored indefinitely.<br />
<br />
You should add a privacy statement to the form to say what you'll do with the information, add a reminder to the email sent to the authors that they shouldn't misuse the contact info, define a retention policy, automate the enforcement of the retention policy.<br />
<br />
===Adding a Privacy Statement===<br />
TODO<br />
===Altering the email to authors===<br />
TODO<br />
===Automating the removal of old requests===<br />
TODO<br />
<br />
==History dataset (used for access stats)==<br />
TODO</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12635Issues22017-10-13T14:17:45Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div><br />
== Duplicate Checker (Issues2) ==<br />
<br />
<br />
'''Version 1.0.2 - minor update'''<br />
<br />
Following feedback from initial review, the Compare and Merge popup window has been updated to include an extra set of buttons, and some additional labels to aid its use.<br />
<br />
Thank you to Alison Sutton from the University of Reading for all the valuable testing and feedback.<br />
<br />
'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 the user can now copy fields between two compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|600px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|600px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12634Issues22017-10-13T14:16:53Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div><br />
== Duplicate Checker (Issues2) ==<br />
<br />
<br />
'''Version 1.0.2 - minor update'''<br />
<br />
Following feedback from initial review, the Compare and Merge popup window has been updated to include an extra set of buttons, and some additional labels to aid its use.<br />
<br />
Thank you to Alison Sutton from Reading to all the valuable testing and feedback.<br />
<br />
'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 the user can now copy fields between two compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|600px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|600px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12633Issues22017-10-13T14:16:38Z<p>Jb4@ecs.soton.ac.uk: /* Duplicate Checker (Issues2) */</p>
<hr />
<div><br />
== Duplicate Checker (Issues2) ==<br />
<br />
<br />
'''Version 1.0.2 - minor update'''<br />
<br />
Following feedback from initial review, the Compare and Merge popup window has been updated to include an extra set of buttons, and some additional labels to aid its use.<br />
Thank you to Alison Sutton from Reading to all the valuable testing and feedback.<br />
<br />
'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 the user can now copy fields between two compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|600px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|600px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12559Issues22017-09-25T14:50:23Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div><br />
== Duplicate Checker (Issues2) ==<br />
<br />
<br />
'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 the user can now copy fields between two compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|600px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|600px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12558Issues22017-09-22T14:54:30Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div><br />
== Duplicate Checker (Issues2) ==<br />
<br />
<br />
'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 user can now copy fields between to compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|600px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|600px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12557Issues22017-09-22T14:53:26Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div><br />
== Duplicate Checker (Issues2) ==<br />
<br />
<br />
'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 user can now copy fields between to compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|500px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|500px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12556Issues22017-09-22T14:47:25Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 user can now copy fields between to compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px|Admin Tools]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px|Search Form]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results2.png|500px|Search Results]]<br />
<br />
A set of actions are available for detected duplicates.<br />
<br />
- The user can 'manage' the record to correct or retire it.<br />
<br />
- Or can 'compare' the 2 records to copy the differing field values between them.<br />
<br />
- Or if the reported problem is not something that requires action, it can be 'acknowledged' and it will not be included in future reports.<br />
<br />
[[File:issues2-manage-popup.png|400px|Manage]]<br />
<br />
[[File:issues2-compare-popup.png|500px|Compare & Merge]]<br />
<br />
[[File:issues2-ack-dlg.png|300px|Acknowledge]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-compare-popup.png&diff=12555File:Issues2-compare-popup.png2017-09-22T14:37:24Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-ack-dlg.png&diff=12554File:Issues2-ack-dlg.png2017-09-22T14:37:07Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-manage-popup.png&diff=12553File:Issues2-manage-popup.png2017-09-22T14:36:48Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-results2.png&diff=12552File:Issues2-results2.png2017-09-22T14:36:16Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12551Issues22017-09-22T13:48:41Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 user can now copy fields between to compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
<br />
----<br />
<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12550Issues22017-09-22T13:48:16Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0.1 - update'''<br />
<br />
In 1.0.1 user can now copy fields between to compared records.<br />
<br />
The new comparison popup shows the differences between 2 records and lets the user select which fields should be copied into the definitive record.<br />
<br />
The presentation and filtering of search results has also been improved.<br />
<br />
'''Version 1.0.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12526Issues22017-09-12T14:30:46Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12525Issues22017-09-12T14:30:29Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
3) In order to bring the database configuration up to date, run epadmin update from the command line.<br />
bin/epadmin update MYREPO<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12460Issues22017-09-06T10:06:15Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
[[File:issues2-admin.png|400px]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
<br />
[[File:issues2-search.png|400px]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12459Issues22017-09-06T10:05:59Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
[[File:issues2-admin.png|400px]]<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
[[File:issues2-search.png|400px]]<br />
<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12458Issues22017-09-06T10:04:44Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-admin.png|400px]]<br />
[[File:issues2-search.png|400px]]<br />
[[File:issues2-results.png|400px]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12457Issues22017-09-06T10:03:02Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-admin.png|width=300px]]<br />
[[File:issues2-search.png]]<br />
[[File:issues2-results.png]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12456Issues22017-09-06T10:00:03Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-admin.png]]<br />
[[File:issues2-search.png]]<br />
[[File:issues2-results.png]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12455Issues22017-09-06T09:59:39Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.<br />
<br />
[[File:issues2-admin]]<br />
[[File:issues2-search]]<br />
[[File:issues2-results]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-results.png&diff=12454File:Issues2-results.png2017-09-06T09:58:27Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-search.png&diff=12453File:Issues2-search.png2017-09-06T09:58:06Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Issues2-admin.png&diff=12452File:Issues2-admin.png2017-09-06T09:57:47Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12451Issues22017-09-06T09:57:05Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12450Issues22017-09-06T09:56:43Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
The package is called "Issues2", rather the "Duplicates" as the aim is that it will grow to cover issues beyond duplicates, and can then be used to replace the original Issues features.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet<br />
<br />
'''Usage'''<br />
<br />
To use Issues2 once installed, go to the Admin section of your repository.<br />
Under the Editorial Tools you'll see a new button called "Duplicates Search".<br />
Clicking this takes you to a new search interface, where you can search for various types of issues.<br />
The search results page shows you a list a records detailing the detected issues.<br />
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.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12438Issues22017-09-05T10:55:31Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>'''Version 1.0 - initial release'''<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.<br />
<br />
'''Installation'''<br />
<br />
1) Install the Bazaar package via the normal Admin -> System Tools -> EPrints Bazaar route.<br />
<br />
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'.<br />
e.g. add the following to your crontab (run "crontab -e") to run at 5am each night.<br />
<br />
00 05 * * * /opt/eprints3/lib/bin/issues_audit2 MYREPO --quiet</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Issues2&diff=12430Issues22017-09-05T10:37:13Z<p>Jb4@ecs.soton.ac.uk: Created page with "Version 1.0 - initial release This package helps repository administrators find records with duplicate metadata. It is an alternative to the existing Issues tool, with a simp..."</p>
<hr />
<div>Version 1.0 - initial release<br />
<br />
This package helps repository administrators find records with duplicate metadata.<br />
It is an alternative to the existing Issues tool, with a simplified interface.<br />
<br />
This is our initial version, we are already planning on further work to this plugin.<br />
<br />
This work has been funded by Jisc and carried out by EPrints Services.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Files/EPrints_3.4_Preview_2&diff=12172Files/EPrints 3.4 Preview 22016-09-13T10:40:58Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Please see [http://www.eprints.org/eprints-3.4 http://www.eprints.org/eprints-3.4]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Files/EPrints_3.4_Preview_2&diff=12171Files/EPrints 3.4 Preview 22016-09-13T10:39:32Z<p>Jb4@ecs.soton.ac.uk: Created page with "Please see http://www.eprints.org/eprints-3.4"</p>
<hr />
<div>Please see [[http://www.eprints.org/eprints-3.4]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Robots&diff=12167Robots2016-08-11T08:52:01Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content.<br />
<br />
However there are also an increasing number of robots which are causing repository owners problems.<br />
<br />
These robots cause unnecessary load on the repository servers, as well as skewing the download statistics for the published data.<br />
<br />
We at EPrints Services and IRUS have observed a number of harmful robots which can be identified either by their IP address or their user agent.<br />
<br />
Are we working to produce and maintain a simple list of these, so they can be more easily filtered or blocked by repository systems administrators.<br />
<br />
The first version of this list can be found below.<br />
<br />
[[Media:bad_robots.txt]]<br />
<br />
IRUS are currently using entries in this file to improve their reports.<br />
<br />
EPrints Services are rolling out a version of IRStats2 which will filter out accesses from this list, and for hosted services blocking accesses at the firewall level.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Robots&diff=12166Robots2016-08-09T15:49:01Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content.<br />
<br />
However there are also an increasing number of robots which are causing repository owners problems.<br />
<br />
These robots cause unnecessary load on the repository servers, as well as skewing the download statistics for the published data.<br />
<br />
We at EPrints Services and IRUS have observed a number of harmful robots which can be identified either by their IP address or their user agent.<br />
<br />
Are we working to produce and maintain a simple list of these, so they can be more easily filtered or blocked by repository systems administrators.<br />
<br />
The first version of this list can be found below.<br />
<br />
[[Media:bad_robots.txt]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Robots&diff=12165Robots2016-08-09T15:47:20Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content.<br />
<br />
However there are also an increasing number of robots which are causing repository owners problems.<br />
<br />
These robots cause unnecessary load on the repository servers, as well as skewing the download statistics for the published data.<br />
<br />
We at EPrints Services and IRUS have observed a number of harmful robots either by their IP address or their user agent.<br />
<br />
Are we working to produce and maintain a simple list of these, so they can be more easily filtered or blocked by repository systems administrators.<br />
<br />
[[Media:bad_robots.txt]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Robots&diff=12164Robots2016-08-09T15:45:37Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content.<br />
<br />
However there are also an increasing number of robots which are causing repository owners problems.<br />
<br />
These robots cause unnecessary load on the repository servers, as well as skewing the download statistics for the published data.<br />
<br />
We at EPrints Services and IRUS have observed a number of harmful robots either by their IP address or their user agent.<br />
<br />
Are we working to produce and maintain a simple list of these, so they can be more easily filtered or blocked by repository systems administrators.<br />
<br />
[[bad_robots.txt]]</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:Bad_robots.txt&diff=12163File:Bad robots.txt2016-08-09T15:43:53Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div></div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Robots&diff=12162Robots2016-08-09T14:16:45Z<p>Jb4@ecs.soton.ac.uk: </p>
<hr />
<div>Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content.<br />
<br />
However there are also an increasing number of robots which are causing repository owners problems.<br />
<br />
These robots cause unnecessary load on the repository servers, as well as skewing the download statistics for the published data.<br />
<br />
We at EPrints Services and IRUS have observed a number of harmful robots either by their IP address or their user agent.<br />
<br />
Are we working to produce and maintain a simple list of these, so they can be more easily filtered or blocked by repository systems administrators.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=Robots&diff=12161Robots2016-08-09T14:16:20Z<p>Jb4@ecs.soton.ac.uk: Created page with "Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content. However there are also an increasing number of r..."</p>
<hr />
<div>Web crawling robots are a fact of life. There are many "out there" on the web, many doing a good job at indexing our content.<br />
However there are also an increasing number of robots which are causing repository owners problems.<br />
These robots cause unnecessary load on the repository servers, as well as skewing the download statistics for the published data.<br />
We at EPrints Services and IRUS have observed a number of harmful robots either by their IP address or their user agent.<br />
Are we working to produce and maintain a simple list of these, so they can be more easily filtered or blocked by repository systems administrators.</div>Jb4@ecs.soton.ac.ukhttps://wiki.eprints.org/w/index.php?title=File:EprintsServices2015icon-265.jpg&diff=12103File:EprintsServices2015icon-265.jpg2016-06-17T16:21:13Z<p>Jb4@ecs.soton.ac.uk: EPrints Services Icon</p>
<hr />
<div>EPrints Services Icon</div>Jb4@ecs.soton.ac.uk