EPrints Documentation - User contributions [en-gb]

EPrints Cron Jobs

2026-08-11T09:15:25Z

Drn@ecs.soton.ac.uk:

There are various tasks that it is important or useful that EPrints runs on a regular basis. Cron jobs are one of the best and probably simplest ways of achieving this. The best way to add a cron job for EPrints is to open the '''eprints''' user's crontab for editing, as follows:
crontab -e

== Default Cron Jobs ==
There are various different cron jobs you may want to deploy. Below is a template crontab for a vanilla EPrints repositories without extra plugins or ingredients installed.
{{template:EPrints_Crontab_Template}}
The <code>generate_views</code> cron job is to ensure both menu and listing pages for browse views (found under http://HOSTNAME/views/ and its sub-pages) are updated. Browse views menu and listing pages are typically cached for 24 hours. However, by regenerating these by cron job every 24 hours, they will load more quickly, as they won't needed to be regenerated on-the-fly because the cache has expired. If you have a large EPrints repository with lots of different browse views, you may find this cron job takes several hours to complete.

The <code>send_alerts</code> cron jobs send out emails on a daily, weekly or monthly basis. The most common use of these is to send emails to editors reminding them of items they need to review. Updates on results from saved searches also use the script to send out emails. Other plugins or ingredients may add to the types of email that can be sent out by this scripts.

The <code>lift_embargos</code> cron job checks over all embargoed documents in eprint records and removes the access restriction on these documents if the embargo date has been reached. It is useful to retain the out from this script as the embargo date will also be unset and sometimes this information is required retrospectively, so such a logs file is the most straightforward way of retrieving this. (There are certain flags you can set for <code>lift_embargos</code> if you need the embargo date retained.

The <code>generate_sitemap</code> cron job generates a XML sitemap at http://HOSTNAME/sitemap.xml. This sitemap contains links to one or more numbered site maps each of which contain entries for each eprint abstract page in the live archive. As new items are likely to be added continual, it is important to regular update this sitemap to include these new items.

The <code>issues_audit</code> cron job analyses eprints records in the whole, detecting things like those that have the same or similar title.

== Other Cron Jobs ==
Various plugins and ingredients will use cron jobs to support their functionality. The some of the most common examples are:

1. [[IRStats2]], which need to regularly process the access table to update usage statistics.
30 03 * * * EPRINTS_PATH/ingredients/irstats2/bin/stats/process_stats ARCHIVE_ID >> EPRINTS_PATH/archives/ARCHIVE_ID/var/process_stats.log
2. [[Coversheets]], which needs to generate coversheeted versions of PDFs uploaded for certain eprint items.
*/15 6-17 * * 1-5 EPRINTS_PATH/ingredients/coversheets/bin/check_coversheets ARCHIVE_ID 250 2>&1 | grep -v -f EPRINTS_PATH/ingredients/coversheets/bin/ignore_warnings.txt

EPrints Cron Jobs

2026-08-11T09:15:00Z

Drn@ecs.soton.ac.uk: Added issues_audit

There are various tasks that it is important or useful that EPrints runs on a regular basis. Cron jobs are one of the best and probably simplest ways of achieving this. The best way to add a cron job for EPrints is to open the eprints' user's crontab for editing, as follows:
crontab -e

== Default Cron Jobs ==
There are various different cron jobs you may want to deploy. Below is a template crontab for a vanilla EPrints repositories without extra plugins or ingredients installed.
{{template:EPrints_Crontab_Template}}
The <code>generate_views</code> cron job is to ensure both menu and listing pages for browse views (found under http://HOSTNAME/views/ and its sub-pages) are updated. Browse views menu and listing pages are typically cached for 24 hours. However, by regenerating these by cron job every 24 hours, they will load more quickly, as they won't needed to be regenerated on-the-fly because the cache has expired. If you have a large EPrints repository with lots of different browse views, you may find this cron job takes several hours to complete.

The <code>send_alerts</code> cron jobs send out emails on a daily, weekly or monthly basis. The most common use of these is to send emails to editors reminding them of items they need to review. Updates on results from saved searches also use the script to send out emails. Other plugins or ingredients may add to the types of email that can be sent out by this scripts.

The <code>lift_embargos</code> cron job checks over all embargoed documents in eprint records and removes the access restriction on these documents if the embargo date has been reached. It is useful to retain the out from this script as the embargo date will also be unset and sometimes this information is required retrospectively, so such a logs file is the most straightforward way of retrieving this. (There are certain flags you can set for <code>lift_embargos</code> if you need the embargo date retained.

The <code>generate_sitemap</code> cron job generates a XML sitemap at http://HOSTNAME/sitemap.xml. This sitemap contains links to one or more numbered site maps each of which contain entries for each eprint abstract page in the live archive. As new items are likely to be added continual, it is important to regular update this sitemap to include these new items.

The <code>issues_audit</code> cron job analyses eprints records in the whole, detecting things like those that have the same or similar title.

== Other Cron Jobs ==
Various plugins and ingredients will use cron jobs to support their functionality. The some of the most common examples are:

1. [[IRStats2]], which need to regularly process the access table to update usage statistics.
30 03 * * * EPRINTS_PATH/ingredients/irstats2/bin/stats/process_stats ARCHIVE_ID >> EPRINTS_PATH/archives/ARCHIVE_ID/var/process_stats.log
2. [[Coversheets]], which needs to generate coversheeted versions of PDFs uploaded for certain eprint items.
*/15 6-17 * * 1-5 EPRINTS_PATH/ingredients/coversheets/bin/check_coversheets ARCHIVE_ID 250 2>&1 | grep -v -f EPRINTS_PATH/ingredients/coversheets/bin/ignore_warnings.txt

Template:EPrints Crontab Template

2026-08-11T09:12:06Z

Drn@ecs.soton.ac.uk:

# Generate browse views
00 01 * * * EPRINTS_PATH/bin/generate_views ARCHIVE_ID --generate menus

# Send emails alerts (e.g. editorial reviews)
00 02 * * * EPRINTS_PATH/bin/send_alerts ARCHIVE_ID daily
10 02 * * 0 EPRINTS_PATH/bin/send_alerts ARCHIVE_ID weekly
20 02 1 * * EPRINTS_PATH/bin/send_alerts ARCHIVE_ID monthly

# Lift expired embargoes on documents
00 03 * * * EPRINTS_PATH/bin/lift_embargos ARCHIVE_ID >> EPRINTS_PATH/archives/ARCHIVE_ID/var/lift_embargos.log

# Generate Site Map
00 04 * * * EPRINTS_PATH/bin/tools/generate_sitemap ARCHIVE_ID

# Issues Audit
00 05 * * * EPRINTS_PATH/bin/issues_audit ARCHIVE_ID --quiet

Template:EPrints Crontab Template

2026-08-11T09:11:58Z

Drn@ecs.soton.ac.uk: Added Issues Audit

EPrints Cron Jobs

2026-08-11T09:10:27Z

Drn@ecs.soton.ac.uk: Added page about EPrints cron jobs

There are various tasks that it is important or useful that EPrints runs on a regular basis. Cron jobs are one of the best and probably simplest ways of achieving this. The best way to add a cron job for EPrints is to open the eprints' user's crontab for editing, as follows:
crontab -e

== Default Cron Jobs ==
There are various different cron jobs you may want to deploy. Below is a template crontab for a vanilla EPrints repositories without extra plugins or ingredients installed.
{{template:EPrints_Crontab_Template}}
The <code>generate_views</code> cron job is to ensure both menu and listing pages for browse views (found under http://HOSTNAME/views/ and its sub-pages) are updated. Browse views menu and listing pages are typically cached for 24 hours. However, by regenerating these by cron job every 24 hours, they will load more quickly, as they won't needed to be regenerated on-the-fly because the cache has expired. If you have a large EPrints repository with lots of different browse views, you may find this cron job takes several hours to complete.

The <code>send_alerts</code> cron jobs send out emails on a daily, weekly or monthly basis. The most common use of these is to send emails to editors reminding them of items they need to review. Updates on results from saved searches also use the script to send out emails. Other plugins or ingredients may add to the types of email that can be sent out by this scripts.

The <code>lift_embargos</code> cron job checks over all embargoed documents in eprint records and removes the access restriction on these documents if the embargo date has been reached. It is useful to retain the out from this script as the embargo date will also be unset and sometimes this information is required retrospectively, so such a logs file is the most straightforward way of retrieving this. (There are certain flags you can set for <code>lift_embargos</code> if you need the embargo date retained.

The <code>generate_sitemap</code> cron job generates a XML sitemap at http://HOSTNAME/sitemap.xml. This sitemap contains links to one or more numbered site maps each of which contain entries for each eprint abstract page in the live archive. As new items are likely to be added continual, it is important to regular update this sitemap to include these new items.

== Other Cron Jobs ==
Various plugins and ingredients will use cron jobs to support their functionality. The some of the most common examples are:

1. [[IRStats2]], which need to regularly process the access table to update usage statistics.
30 03 * * * EPRINTS_PATH/ingredients/irstats2/bin/stats/process_stats ARCHIVE_ID >> EPRINTS_PATH/archives/ARCHIVE_ID/var/process_stats.log
2. [[Coversheets]], which needs to generate coversheeted versions of PDFs uploaded for certain eprint items.
*/15 6-17 * * 1-5 EPRINTS_PATH/ingredients/coversheets/bin/check_coversheets ARCHIVE_ID 250 2>&1 | grep -v -f EPRINTS_PATH/ingredients/coversheets/bin/ignore_warnings.txt

Getting Started

2026-08-11T08:45:41Z

Drn@ecs.soton.ac.uk: /* Creating a crontab */

{{manual}}
[[Category:Manual]]

==Creating an Archive==

EPrints 3 can run run multiple archives under one install. Multiple archives will require giving additional DNS aliases to the machine running EPrints, EPrints can then create all the parts of the apache configuration file needed to run the virtual hosts.

===Creating MySQL eprints user===
If you are running a modern version of Linux (e.g. Red Hat Enterprise Linux 9+ or Ubuntu 20.04+), the eprints user will not be able to connect to the MySQL database as the root user without a password. Therefore, before running "epadmin create" later in these instructions make sure you switch to the root user, open the MySQL client and run the following commands, (substituting the password (i.e. 'changeme') appropriately):
CREATE USER 'eprints'@'localhost' IDENTIFIED by 'changeme';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
When you are asked for the '''Database Superuser Username''' and '''Database Superuser Password''' be sure to use the username and password set above. If you are running older version of Linux where you have not needed to do the above steps. You can probably use the default options for these to steps.

===Creating the Archive===
Make sure MySQL is actually running.

Change to your "eprints" user.

Change directory to the eprints directory (<tt>/opt/eprints3</tt> by default) and run the '''EXACT''' following command to create a research publications archive. (You will be prompted to answer various questions about the configuration of your archive):
bin/epadmin create pub

If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository. Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory. If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.

===Creating the Database Tables and Website ===
These will have been created when you created the archive.

==Running a Live Archive==
===Creating a crontab===
When you create an archive it will start out as a development system while you learn how to set it up (and your manager keeps changing his mind) but at some point (hopefully) you will declare your archive open for business.

At this point you should schedule certain scripts to run periodically. The best way to do this is to use "cron" which is an integral part of most UNIX systems.

To set up cron, run (as the eprints user):
% crontab -e

Exactly what to add to the cron table is described in the following sections - "Browse Views" and "Subscriptions".

There should be one set of crontab entries per archive.

Here is an example crontab template. <code>EPRINTS_PATH</code> and <code>ARCHIVE_ID</code> should be replaced as appropriate.

{{template:EPrints_Crontab_Template}}

For more information about [[EPrints Cron Jobs|cron jobs for EPrints, click here]].

===Backups===
You should also have made sure that the system is being properly backed up. This is gone into in more detail elsewhere in the documentation.

===OAI===
We would also encourage you to configure the OAI support for your archive and register it. It's quite easy - pretty much fill in the blanks in the ArchiveOAIConfig.pm file in the archive configuration directory.

EPrints 2.1 support OAI versions 1 and 2 at URL paths /perl/oai and /perl/oai2.

Once you register your archive (at http://www.openarchives.org) various search systems will be able to collect the metadata (titles, authors, abstract etc.) and allow more people to find records in your archive.

See http://www.openarchives.org/ for more information on the OAI protocol. For more information setting up the OAI interface archive see the section in this documentation about Configuring an Archive.

==Browse Views==
Once every so often you should run the "generate_views" script on each archive in your system to regenerate the browse views section of the site.

This is a set of static pages. By default one per subject, and one per year (only years with papers in that year not EVERY year ever!). Some users prefer to browse the system than search it. This also gives search engines a way to reach, and index, the abstract pages.

See the ArchiveConfig.pm config notes on how to edit the views it generates.

See the How-To section for some suggestions on how to set up views.

===But I don't want this feature...===
If you don't want to use this feature: don't, it's your archive. Remove the link from the template and front page. Don't run the generate_views script.

===Setting it up===
This is best done by using the UNIX "cron" command (as user "eprints"). Cron will email "eprints" on that machine with the output, so best use the --quiet option so it only bothers you with errors.

How often you want to run this depends on the size of your archive, and how fast the contents changes. This feature is roughly order "n". Which means if you double the number of items in your archive then you double the time it takes to run (ish).

Once an hour would seem a good starting point. If your archive gets real big, say more than 10000 records, then maybe once a day is more realistic - the one thing that you don't want to happen is for a new generate_views to start before the old one finishes as they will mess up each others output.

Run generate_views on the command line to find out how long it takes.

and add the line
23 * * * * /opt/eprints2/bin/generate_views I<archiveid>

This runs at 23 minutes past each hour. If you have more than one archive, don't make them all start rebuilding stuff at the same time, stagger it. Otherwise once an hour everything will slow down as it fights to run several intensive scripts at once.

See the crontab man page <tt>man 5 crontab</tt> for more information on using cron.

==Subscriptions==
Subscriptions provide a way in which users of your system can receive regular updates, via email, when new items are added which match a search they specified.

To automate sending out these subscriptions you must add some entries in the crontab (as for views). You need one set of these per archive.

For example (with dookuprints being the name of the archive):
# 00:15 every morning
15 0 * * * /opt/eprints2/bin/send_subscriptions dookuprints daily

# 00:30 every sunday morning
30 0 * * 0 /opt/eprints2/bin/send_subscriptions dookuprints weekly

# 00:45 every first of the month
45 0 1 * * /opt/eprints2/bin/send_subscriptions dookuprints monthly
Note the spacing out so that all 3 don't start at once and hammer the database. You may wish to change the times, but we recommend early morning as the best time to send them (midnight-6am).

===But I don't want users to be able to do this!===
Then remove the "subscription" power from each type of user in the archives ArchiveConfig.pm file.

==Default Configuration==
EPrints configures a new archive with a set of metadata fields aimed at an archive of research papers.

The initial "types" of eprint (book, poster, conference paper) are configured in metadata-types.xml

The initial subjects are a subset of the library of congress subjects. Feel free to totally replace them with your own subjects, but the more standard your subject tree the more useful your metadata will be to other people.

The authors and editors have the "hasid" option set which allows people to optionally use a unique id for a person in addition to their name (names are NOT unique!) - this can be useful for generating "CV" pages (see the views how-to) and possibly for generating statistics. Without it you will never be sure which "John Smith" wrote that paper. If you don't like this feature remove the "hasid" from the authors and editors - this will require you to recreate the tables, erasing the archive, so decide before you start. If you want to be more clear about what information goes in that field, edit the phrases <tt>eprint_fieldname_authors_id</tt> and <tt>eprint_fieldname_editors_id</tt> in the archive phrase file(s).

In general: Change it! It's not a recommended system setup, just a good starting point.

===Example Configuration===
The "epadmin create" script will run through a number of configuration options, an example of which is listed below. Please change the settings to suit your site configuration.

<pre>
-bash-4.1$ ./bin/epadmin create pub

Create an EPrint Repository

Please select an ID for the repository, which will be used to create a directory
and identify the repository. Lower case letters and numbers, may not start with
a number. examples: "lemurprints" or "test3"

Archive ID? testrepo
We need to create /usr/share/eprints/archives/testrepo, doing it now…

Creating initial files:
Installing: /usr/share/eprints/archives/testrepo/cfg
Installing: /usr/share/eprints/archives/testrepo/cfg/lang
[...]
Installing: /usr/share/eprints/archives/testrepo/cfg/workflows/eprint

Ok. I've created the initial config files and directory structure.
I've also created a "disk0" directory under documents/ if you want
your full texts to be stored on a different partition then remove
the disk0, and create a symbolic link to the directory you wish to
store the full texts in. Additional links may be placed here to be
used when the first is full.

Configure vital settings? [yes] ?
Core configuration for testrepo

Please enter the fully qualified hostname of the repository.

For a production system we recommend against using the real hostname of the
machine.

Example: testrepo.footle.ac.uk

Hostname? testprint

Please enter the port of the webserver. This is probably 80, but you may wish
to run apache on a different port if you are experimenting.

Webserver Port [80] ?

Please enter all the aliases which could reach the repository, and indicate if
you would like EPrints to write a Redirect Rule to redirect requests to this
alias to the correct URL.
Some suggestions:
centos610.local
centos610
centos610

Enter a single hash (#) when you're done.

Alias (enter # when done) [#] ? testprint.local
Redirect testprint.local to testprint [yes] ?

Alias (enter # when done) [#] ?

Please enter the path part of the repository's base URL. This should probably
be '/'.

Path [/] ?

If you will use https for your user pages (including login) enter the https hostname
here, or leave blank when using http only.

HTTPS Hostname [] ?

Administrator Email? someone@example.com

Enter the name of the repository in the default language. If you wish to enter
other titles for other languages or enter non ascii characters then you may
enter something as a placeholder and edit the XML config file which this
script generates.

Archive Name [Test Repository] ?

Write these core settings? [yes] ?
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/adminemail.pl
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/10_core.pl
Wrote /usr/share/eprints/archives/testrepo/cfg/lang/en/phrases/archive_name.xml

Configure database? [yes] ?

Configuring Database for: testrepo
Database Name [testrepo] ?
MySQL Host [localhost] ?

You probably don't need to set socket and port (unless you do!?).
MySQL Port (# for no setting) [#] ?
MySQL Socket (# for no setting) [#] ?
Database User [testrepo] ?
Database Password [nxxxxuAw] ?
Database Engine [MyISAM] ?

Write these database settings? [yes] ?
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/database.pl

EPrints can create the database, and grant the correct permissions.

Create database "testrepo" [yes] ?
Database Superuser Username [root] ?
Database Superuser Password?
Create database tables? [yes] ?
Creating database tables...
Set DB compatibility flag to '3.3.4'.
Done creating database tables.

Create an initial user? [yes] ?
Creating a new user in testrepo

Enter a username [admin] ?
Select a user type (user|editor|admin) [admin] ?
Enter Password?
Email? first.last@example.org

Successfully created new user:
ID: 1
Do you want to build the static web pages? [yes] ?

Starting EPrints Repository.
Connecting to DB ... done.
mkdir /usr/share/eprints/archives/testrepo/html/en/codemirror/mode/velocity
/usr/share/eprints/lib/static/codemirror/mode/velocity/velocity.js -> /usr/share/eprints/archives/testrepo/html/en/codemirror/mode/velocity/velocity.js
mkdir /usr/share/eprints/archives/testrepo/html/en/style/images
/usr/share/eprints/lib/static/style/images/action_edit.png -> /usr/share/eprints/archives/testrepo/html/en/style/images/action_edit.png
[...]
/usr/share/eprints/lib/static/style/images/action_unpack.png -> /usr/share/eprints/archives/testrepo/html/en/style/images/action_unpack.png
/usr/share/eprints/lib/static/codemirror/lib/util/loadmode.js -> /usr/share/eprints/archives/testrepo/html/en/codemirror/lib/util/loadmode.js
Ending EPrints Repository.

Do you want to import the LOC subjects? [yes] ?

Starting EPrints Repository.
Connecting to DB ... done.
Importing from /usr/share/eprints/archives/testrepo/cfg/subjects...
Done importing 280 subjects from /usr/share/eprints/archives/testrepo/cfg/subjects
Reindexing subject dataset to set ancestor data
Reindexing item: subject/A
Reindexing item: subject/AC
Reindexing item: subject/AI
Reindexing item: subject/AM
[...]
Reindexing item: subject/sch_soc
Reindexing item: subject/subjects
Done reindexing
Ending EPrints Repository.

Exiting normally.
Do you want to update the apache config files? (you still need to add the
'Include' line) [yes] ?
Wrote /usr/share/eprints/cfg/apache/testrepo.conf

You must restart apache for any changes to take effect!

--------------------------------------------------------------------------
That seemed to more or less work...
--------------------------------------------------------------------------

Now make any required changes to the cfg files.

Note that changing the metadata configuration may require the database
tables to be regenerated. epadmin erase_data will regenerate the
eprints and documents tables only. erase_data will regenerate everything.
(nb. these also do erase the contents of the tables, and any uploaded
files).

Make sure that your main apache config file contains the line:

Include /usr/share/eprints/cfg/apache.conf

Then stop and start your webserver:
Often:
/etc/rc.d/init.d/httpd stop
/etc/rc.d/init.d/httpd start
(or maybe /usr/local/apache/bin/apachectl stop & start)

And then try connecting to your repository.
--------------------------------------------------------------------------

Don't forget to register your repository at http://roar.eprints.org/

-bash-4.1$

</pre>

==New Configurations==
If you are setting up more than one archive which are related to each other, a "community", you may wish to establish common subjects and metadata.

Removing and adding types is easy. Removing and adding fields is a bit more work. All "screen" names of values are stored in the archives own "phrase file" which comes with phrases for the default config.

If you create a good default configuration for a different purpose or language(s) (and would like to share it), please contact the eprints admin who may want to put it online as an example or even include it as an alternate default in a later version.

Template:EPrints Crontab Template

2026-08-11T08:45:26Z

Drn@ecs.soton.ac.uk: Replaced with EPRINTS_PATH and ARCHIVE_ID as appropriate.

Getting Started

2026-08-11T08:43:53Z

Drn@ecs.soton.ac.uk: /* Running a Live Archive */ Added more info about cron jobs

{{manual}}
[[Category:Manual]]

==Creating an Archive==

EPrints 3 can run run multiple archives under one install. Multiple archives will require giving additional DNS aliases to the machine running EPrints, EPrints can then create all the parts of the apache configuration file needed to run the virtual hosts.

===Creating MySQL eprints user===
If you are running a modern version of Linux (e.g. Red Hat Enterprise Linux 9+ or Ubuntu 20.04+), the eprints user will not be able to connect to the MySQL database as the root user without a password. Therefore, before running "epadmin create" later in these instructions make sure you switch to the root user, open the MySQL client and run the following commands, (substituting the password (i.e. 'changeme') appropriately):
CREATE USER 'eprints'@'localhost' IDENTIFIED by 'changeme';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
When you are asked for the '''Database Superuser Username''' and '''Database Superuser Password''' be sure to use the username and password set above. If you are running older version of Linux where you have not needed to do the above steps. You can probably use the default options for these to steps.

===Creating the Archive===
Make sure MySQL is actually running.

Change to your "eprints" user.

Change directory to the eprints directory (<tt>/opt/eprints3</tt> by default) and run the '''EXACT''' following command to create a research publications archive. (You will be prompted to answer various questions about the configuration of your archive):
bin/epadmin create pub

If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository. Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory. If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.

===Creating the Database Tables and Website ===
These will have been created when you created the archive.

==Running a Live Archive==
===Creating a crontab===
When you create an archive it will start out as a development system while you learn how to set it up (and your manager keeps changing his mind) but at some point (hopefully) you will declare your archive open for business.

At this point you should schedule certain scripts to run periodically. The best way to do this is to use "cron" which is an integral part of most UNIX systems.

To set up cron, run (as the eprints user):
% crontab -e

Exactly what to add to the cron table is described in the following sections - "Browse Views" and "Subscriptions".

There should be one set of crontab entries per archive.

Here is an example crontab template. <code>EPRINTS_PATH</code> and <code>ARCHIVE_ID</code> should be replaced as appropriate.

{{template:EPrints_Crontab_Template}}

For more information about [[EPrints Cron Jobs||cron jobs for EPrints, click here]].

===Backups===
You should also have made sure that the system is being properly backed up. This is gone into in more detail elsewhere in the documentation.

===OAI===
We would also encourage you to configure the OAI support for your archive and register it. It's quite easy - pretty much fill in the blanks in the ArchiveOAIConfig.pm file in the archive configuration directory.

EPrints 2.1 support OAI versions 1 and 2 at URL paths /perl/oai and /perl/oai2.

Once you register your archive (at http://www.openarchives.org) various search systems will be able to collect the metadata (titles, authors, abstract etc.) and allow more people to find records in your archive.

See http://www.openarchives.org/ for more information on the OAI protocol. For more information setting up the OAI interface archive see the section in this documentation about Configuring an Archive.

==Browse Views==
Once every so often you should run the "generate_views" script on each archive in your system to regenerate the browse views section of the site.

This is a set of static pages. By default one per subject, and one per year (only years with papers in that year not EVERY year ever!). Some users prefer to browse the system than search it. This also gives search engines a way to reach, and index, the abstract pages.

See the ArchiveConfig.pm config notes on how to edit the views it generates.

See the How-To section for some suggestions on how to set up views.

===But I don't want this feature...===
If you don't want to use this feature: don't, it's your archive. Remove the link from the template and front page. Don't run the generate_views script.

===Setting it up===
This is best done by using the UNIX "cron" command (as user "eprints"). Cron will email "eprints" on that machine with the output, so best use the --quiet option so it only bothers you with errors.

How often you want to run this depends on the size of your archive, and how fast the contents changes. This feature is roughly order "n". Which means if you double the number of items in your archive then you double the time it takes to run (ish).

Once an hour would seem a good starting point. If your archive gets real big, say more than 10000 records, then maybe once a day is more realistic - the one thing that you don't want to happen is for a new generate_views to start before the old one finishes as they will mess up each others output.

Run generate_views on the command line to find out how long it takes.

and add the line
23 * * * * /opt/eprints2/bin/generate_views I<archiveid>

This runs at 23 minutes past each hour. If you have more than one archive, don't make them all start rebuilding stuff at the same time, stagger it. Otherwise once an hour everything will slow down as it fights to run several intensive scripts at once.

See the crontab man page <tt>man 5 crontab</tt> for more information on using cron.

==Subscriptions==
Subscriptions provide a way in which users of your system can receive regular updates, via email, when new items are added which match a search they specified.

To automate sending out these subscriptions you must add some entries in the crontab (as for views). You need one set of these per archive.

For example (with dookuprints being the name of the archive):
# 00:15 every morning
15 0 * * * /opt/eprints2/bin/send_subscriptions dookuprints daily

# 00:30 every sunday morning
30 0 * * 0 /opt/eprints2/bin/send_subscriptions dookuprints weekly

# 00:45 every first of the month
45 0 1 * * /opt/eprints2/bin/send_subscriptions dookuprints monthly
Note the spacing out so that all 3 don't start at once and hammer the database. You may wish to change the times, but we recommend early morning as the best time to send them (midnight-6am).

===But I don't want users to be able to do this!===
Then remove the "subscription" power from each type of user in the archives ArchiveConfig.pm file.

==Default Configuration==
EPrints configures a new archive with a set of metadata fields aimed at an archive of research papers.

The initial "types" of eprint (book, poster, conference paper) are configured in metadata-types.xml

The initial subjects are a subset of the library of congress subjects. Feel free to totally replace them with your own subjects, but the more standard your subject tree the more useful your metadata will be to other people.

The authors and editors have the "hasid" option set which allows people to optionally use a unique id for a person in addition to their name (names are NOT unique!) - this can be useful for generating "CV" pages (see the views how-to) and possibly for generating statistics. Without it you will never be sure which "John Smith" wrote that paper. If you don't like this feature remove the "hasid" from the authors and editors - this will require you to recreate the tables, erasing the archive, so decide before you start. If you want to be more clear about what information goes in that field, edit the phrases <tt>eprint_fieldname_authors_id</tt> and <tt>eprint_fieldname_editors_id</tt> in the archive phrase file(s).

In general: Change it! It's not a recommended system setup, just a good starting point.

===Example Configuration===
The "epadmin create" script will run through a number of configuration options, an example of which is listed below. Please change the settings to suit your site configuration.

<pre>
-bash-4.1$ ./bin/epadmin create pub

Create an EPrint Repository

Please select an ID for the repository, which will be used to create a directory
and identify the repository. Lower case letters and numbers, may not start with
a number. examples: "lemurprints" or "test3"

Archive ID? testrepo
We need to create /usr/share/eprints/archives/testrepo, doing it now…

Creating initial files:
Installing: /usr/share/eprints/archives/testrepo/cfg
Installing: /usr/share/eprints/archives/testrepo/cfg/lang
[...]
Installing: /usr/share/eprints/archives/testrepo/cfg/workflows/eprint

Ok. I've created the initial config files and directory structure.
I've also created a "disk0" directory under documents/ if you want
your full texts to be stored on a different partition then remove
the disk0, and create a symbolic link to the directory you wish to
store the full texts in. Additional links may be placed here to be
used when the first is full.

Configure vital settings? [yes] ?
Core configuration for testrepo

Please enter the fully qualified hostname of the repository.

For a production system we recommend against using the real hostname of the
machine.

Example: testrepo.footle.ac.uk

Hostname? testprint

Please enter the port of the webserver. This is probably 80, but you may wish
to run apache on a different port if you are experimenting.

Webserver Port [80] ?

Please enter all the aliases which could reach the repository, and indicate if
you would like EPrints to write a Redirect Rule to redirect requests to this
alias to the correct URL.
Some suggestions:
centos610.local
centos610
centos610

Enter a single hash (#) when you're done.

Alias (enter # when done) [#] ? testprint.local
Redirect testprint.local to testprint [yes] ?

Alias (enter # when done) [#] ?

Please enter the path part of the repository's base URL. This should probably
be '/'.

Path [/] ?

If you will use https for your user pages (including login) enter the https hostname
here, or leave blank when using http only.

HTTPS Hostname [] ?

Administrator Email? someone@example.com

Enter the name of the repository in the default language. If you wish to enter
other titles for other languages or enter non ascii characters then you may
enter something as a placeholder and edit the XML config file which this
script generates.

Archive Name [Test Repository] ?

Write these core settings? [yes] ?
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/adminemail.pl
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/10_core.pl
Wrote /usr/share/eprints/archives/testrepo/cfg/lang/en/phrases/archive_name.xml

Configure database? [yes] ?

Configuring Database for: testrepo
Database Name [testrepo] ?
MySQL Host [localhost] ?

You probably don't need to set socket and port (unless you do!?).
MySQL Port (# for no setting) [#] ?
MySQL Socket (# for no setting) [#] ?
Database User [testrepo] ?
Database Password [nxxxxuAw] ?
Database Engine [MyISAM] ?

Write these database settings? [yes] ?
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/database.pl

EPrints can create the database, and grant the correct permissions.

Create database "testrepo" [yes] ?
Database Superuser Username [root] ?
Database Superuser Password?
Create database tables? [yes] ?
Creating database tables...
Set DB compatibility flag to '3.3.4'.
Done creating database tables.

Create an initial user? [yes] ?
Creating a new user in testrepo

Enter a username [admin] ?
Select a user type (user|editor|admin) [admin] ?
Enter Password?
Email? first.last@example.org

Successfully created new user:
ID: 1
Do you want to build the static web pages? [yes] ?

Starting EPrints Repository.
Connecting to DB ... done.
mkdir /usr/share/eprints/archives/testrepo/html/en/codemirror/mode/velocity
/usr/share/eprints/lib/static/codemirror/mode/velocity/velocity.js -> /usr/share/eprints/archives/testrepo/html/en/codemirror/mode/velocity/velocity.js
mkdir /usr/share/eprints/archives/testrepo/html/en/style/images
/usr/share/eprints/lib/static/style/images/action_edit.png -> /usr/share/eprints/archives/testrepo/html/en/style/images/action_edit.png
[...]
/usr/share/eprints/lib/static/style/images/action_unpack.png -> /usr/share/eprints/archives/testrepo/html/en/style/images/action_unpack.png
/usr/share/eprints/lib/static/codemirror/lib/util/loadmode.js -> /usr/share/eprints/archives/testrepo/html/en/codemirror/lib/util/loadmode.js
Ending EPrints Repository.

Do you want to import the LOC subjects? [yes] ?

Starting EPrints Repository.
Connecting to DB ... done.
Importing from /usr/share/eprints/archives/testrepo/cfg/subjects...
Done importing 280 subjects from /usr/share/eprints/archives/testrepo/cfg/subjects
Reindexing subject dataset to set ancestor data
Reindexing item: subject/A
Reindexing item: subject/AC
Reindexing item: subject/AI
Reindexing item: subject/AM
[...]
Reindexing item: subject/sch_soc
Reindexing item: subject/subjects
Done reindexing
Ending EPrints Repository.

Exiting normally.
Do you want to update the apache config files? (you still need to add the
'Include' line) [yes] ?
Wrote /usr/share/eprints/cfg/apache/testrepo.conf

You must restart apache for any changes to take effect!

--------------------------------------------------------------------------
That seemed to more or less work...
--------------------------------------------------------------------------

Now make any required changes to the cfg files.

Note that changing the metadata configuration may require the database
tables to be regenerated. epadmin erase_data will regenerate the
eprints and documents tables only. erase_data will regenerate everything.
(nb. these also do erase the contents of the tables, and any uploaded
files).

Make sure that your main apache config file contains the line:

Include /usr/share/eprints/cfg/apache.conf

Then stop and start your webserver:
Often:
/etc/rc.d/init.d/httpd stop
/etc/rc.d/init.d/httpd start
(or maybe /usr/local/apache/bin/apachectl stop & start)

And then try connecting to your repository.
--------------------------------------------------------------------------

Don't forget to register your repository at http://roar.eprints.org/

-bash-4.1$

</pre>

==New Configurations==
If you are setting up more than one archive which are related to each other, a "community", you may wish to establish common subjects and metadata.

Removing and adding types is easy. Removing and adding fields is a bit more work. All "screen" names of values are stored in the archives own "phrase file" which comes with phrases for the default config.

If you create a good default configuration for a different purpose or language(s) (and would like to share it), please contact the eprints admin who may want to put it online as an example or even include it as an alternate default in a later version.

Template:EPrints Crontab Template

2026-08-11T08:43:35Z

Drn@ecs.soton.ac.uk: Added template crontab for EPrints

# Generate browse views
00 01 * * * /opt/eprints3/bin/generate_views REPO --generate menus

# Send emails alerts (e.g. editorial reviews)
00 02 * * * /opt/eprints3/bin/send_alerts REPO daily
10 02 * * 0 /opt/eprints3/bin/send_alerts REPO weekly
20 02 1 * * /opt/eprints3/bin/send_alerts REPO monthly

# Lift expired embargoes on documents
00 03 * * * /opt/eprints3/bin/lift_embargos REPO >> /opt/eprints3/archives/REPO/var/lift_embargos.log

# Generate Site Map
00 04 * * * /opt/eprints3/ingredients/eps_lib/bin/tools/generate_sitemap REPO

Getting Started

2026-08-06T12:58:22Z

Drn@ecs.soton.ac.uk: /* Creating the Archive */ Tried to make what command better explained.

{{manual}}
[[Category:Manual]]

==Creating an Archive==

EPrints 3 can run run multiple archives under one install. Multiple archives will require giving additional DNS aliases to the machine running EPrints, EPrints can then create all the parts of the apache configuration file needed to run the virtual hosts.

===Creating MySQL eprints user===
If you are running a modern version of Linux (e.g. Red Hat Enterprise Linux 9+ or Ubuntu 20.04+), the eprints user will not be able to connect to the MySQL database as the root user without a password. Therefore, before running "epadmin create" later in these instructions make sure you switch to the root user, open the MySQL client and run the following commands, (substituting the password (i.e. 'changeme') appropriately):
CREATE USER 'eprints'@'localhost' IDENTIFIED by 'changeme';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
When you are asked for the '''Database Superuser Username''' and '''Database Superuser Password''' be sure to use the username and password set above. If you are running older version of Linux where you have not needed to do the above steps. You can probably use the default options for these to steps.

===Creating the Archive===
Make sure MySQL is actually running.

Change to your "eprints" user.

Change directory to the eprints directory (<tt>/opt/eprints3</tt> by default) and run the '''EXACT''' following command to create a research publications archive. (You will be prompted to answer various questions about the configuration of your archive):
bin/epadmin create pub

If you don't want a research publications archive, in the above command use <code>zero</code> instead of <code>pub</code>. This will create a very basic repository, which can either store very generic items or can be more greatly customised as it does not have some of the intentional restrictions that come with a Research Publications repository. Other flavours of repository may be available but these will have to have be added their <tt>FLAVOUR_lib</tt> to the <tt>EPRINTS_PATH/flavours/</tt> directory. If you run just <code>bin/epadmin create</code> without a further parameter or one that is not recognised, the command should suggest what types (flavours) of repository archive are available.

===Creating the Database Tables and Website ===
These will have been created when you created the archive.

==Running a Live Archive==
===Creating a crontab===
When you create an archive it will start out as a development system while you learn how to set it up (and your manager keeps changing his mind) but at some point (hopefully) you will declare your archive open for business.

At this point you should schedule certain scripts to run periodically. The best way to do this is to use "cron" which is an integral part of most UNIX systems.

To set up cron, run (as the eprints user):
% crontab -e

Exactly what to add to the cron table is described in the following sections - "Browse Views" and "Subscriptions".

There should be one set of crontab entries per archive.

===Backups===
You should also have made sure that the system is being properly backed up. This is gone into in more detail elsewhere in the documentation.

===OAI===
We would also encourage you to configure the OAI support for your archive and register it. It's quite easy - pretty much fill in the blanks in the ArchiveOAIConfig.pm file in the archive configuration directory.

EPrints 2.1 support OAI versions 1 and 2 at URL paths /perl/oai and /perl/oai2.

Once you register your archive (at http://www.openarchives.org) various search systems will be able to collect the metadata (titles, authors, abstract etc.) and allow more people to find records in your archive.

See http://www.openarchives.org/ for more information on the OAI protocol. For more information setting up the OAI interface archive see the section in this documentation about Configuring an Archive.

==Browse Views==
Once every so often you should run the "generate_views" script on each archive in your system to regenerate the browse views section of the site.

This is a set of static pages. By default one per subject, and one per year (only years with papers in that year not EVERY year ever!). Some users prefer to browse the system than search it. This also gives search engines a way to reach, and index, the abstract pages.

See the ArchiveConfig.pm config notes on how to edit the views it generates.

See the How-To section for some suggestions on how to set up views.

===But I don't want this feature...===
If you don't want to use this feature: don't, it's your archive. Remove the link from the template and front page. Don't run the generate_views script.

===Setting it up===
This is best done by using the UNIX "cron" command (as user "eprints"). Cron will email "eprints" on that machine with the output, so best use the --quiet option so it only bothers you with errors.

How often you want to run this depends on the size of your archive, and how fast the contents changes. This feature is roughly order "n". Which means if you double the number of items in your archive then you double the time it takes to run (ish).

Once an hour would seem a good starting point. If your archive gets real big, say more than 10000 records, then maybe once a day is more realistic - the one thing that you don't want to happen is for a new generate_views to start before the old one finishes as they will mess up each others output.

Run generate_views on the command line to find out how long it takes.

and add the line
23 * * * * /opt/eprints2/bin/generate_views I<archiveid>

This runs at 23 minutes past each hour. If you have more than one archive, don't make them all start rebuilding stuff at the same time, stagger it. Otherwise once an hour everything will slow down as it fights to run several intensive scripts at once.

See the crontab man page <tt>man 5 crontab</tt> for more information on using cron.

==Subscriptions==
Subscriptions provide a way in which users of your system can receive regular updates, via email, when new items are added which match a search they specified.

To automate sending out these subscriptions you must add some entries in the crontab (as for views). You need one set of these per archive.

For example (with dookuprints being the name of the archive):
# 00:15 every morning
15 0 * * * /opt/eprints2/bin/send_subscriptions dookuprints daily

# 00:30 every sunday morning
30 0 * * 0 /opt/eprints2/bin/send_subscriptions dookuprints weekly

# 00:45 every first of the month
45 0 1 * * /opt/eprints2/bin/send_subscriptions dookuprints monthly
Note the spacing out so that all 3 don't start at once and hammer the database. You may wish to change the times, but we recommend early morning as the best time to send them (midnight-6am).

===But I don't want users to be able to do this!===
Then remove the "subscription" power from each type of user in the archives ArchiveConfig.pm file.

==Default Configuration==
EPrints configures a new archive with a set of metadata fields aimed at an archive of research papers.

The initial "types" of eprint (book, poster, conference paper) are configured in metadata-types.xml

The initial subjects are a subset of the library of congress subjects. Feel free to totally replace them with your own subjects, but the more standard your subject tree the more useful your metadata will be to other people.

The authors and editors have the "hasid" option set which allows people to optionally use a unique id for a person in addition to their name (names are NOT unique!) - this can be useful for generating "CV" pages (see the views how-to) and possibly for generating statistics. Without it you will never be sure which "John Smith" wrote that paper. If you don't like this feature remove the "hasid" from the authors and editors - this will require you to recreate the tables, erasing the archive, so decide before you start. If you want to be more clear about what information goes in that field, edit the phrases <tt>eprint_fieldname_authors_id</tt> and <tt>eprint_fieldname_editors_id</tt> in the archive phrase file(s).

In general: Change it! It's not a recommended system setup, just a good starting point.

===Example Configuration===
The "epadmin create" script will run through a number of configuration options, an example of which is listed below. Please change the settings to suit your site configuration.

<pre>
-bash-4.1$ ./bin/epadmin create pub

Create an EPrint Repository

Please select an ID for the repository, which will be used to create a directory
and identify the repository. Lower case letters and numbers, may not start with
a number. examples: "lemurprints" or "test3"

Archive ID? testrepo
We need to create /usr/share/eprints/archives/testrepo, doing it now…

Creating initial files:
Installing: /usr/share/eprints/archives/testrepo/cfg
Installing: /usr/share/eprints/archives/testrepo/cfg/lang
[...]
Installing: /usr/share/eprints/archives/testrepo/cfg/workflows/eprint

Ok. I've created the initial config files and directory structure.
I've also created a "disk0" directory under documents/ if you want
your full texts to be stored on a different partition then remove
the disk0, and create a symbolic link to the directory you wish to
store the full texts in. Additional links may be placed here to be
used when the first is full.

Configure vital settings? [yes] ?
Core configuration for testrepo

Please enter the fully qualified hostname of the repository.

For a production system we recommend against using the real hostname of the
machine.

Example: testrepo.footle.ac.uk

Hostname? testprint

Please enter the port of the webserver. This is probably 80, but you may wish
to run apache on a different port if you are experimenting.

Webserver Port [80] ?

Please enter all the aliases which could reach the repository, and indicate if
you would like EPrints to write a Redirect Rule to redirect requests to this
alias to the correct URL.
Some suggestions:
centos610.local
centos610
centos610

Enter a single hash (#) when you're done.

Alias (enter # when done) [#] ? testprint.local
Redirect testprint.local to testprint [yes] ?

Alias (enter # when done) [#] ?

Please enter the path part of the repository's base URL. This should probably
be '/'.

Path [/] ?

If you will use https for your user pages (including login) enter the https hostname
here, or leave blank when using http only.

HTTPS Hostname [] ?

Administrator Email? someone@example.com

Enter the name of the repository in the default language. If you wish to enter
other titles for other languages or enter non ascii characters then you may
enter something as a placeholder and edit the XML config file which this
script generates.

Archive Name [Test Repository] ?

Write these core settings? [yes] ?
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/adminemail.pl
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/10_core.pl
Wrote /usr/share/eprints/archives/testrepo/cfg/lang/en/phrases/archive_name.xml

Configure database? [yes] ?

Configuring Database for: testrepo
Database Name [testrepo] ?
MySQL Host [localhost] ?

You probably don't need to set socket and port (unless you do!?).
MySQL Port (# for no setting) [#] ?
MySQL Socket (# for no setting) [#] ?
Database User [testrepo] ?
Database Password [nxxxxuAw] ?
Database Engine [MyISAM] ?

Write these database settings? [yes] ?
Wrote /usr/share/eprints/archives/testrepo/cfg/cfg.d/database.pl

EPrints can create the database, and grant the correct permissions.

Create database "testrepo" [yes] ?
Database Superuser Username [root] ?
Database Superuser Password?
Create database tables? [yes] ?
Creating database tables...
Set DB compatibility flag to '3.3.4'.
Done creating database tables.

Create an initial user? [yes] ?
Creating a new user in testrepo

Enter a username [admin] ?
Select a user type (user|editor|admin) [admin] ?
Enter Password?
Email? first.last@example.org

Successfully created new user:
ID: 1
Do you want to build the static web pages? [yes] ?

Starting EPrints Repository.
Connecting to DB ... done.
mkdir /usr/share/eprints/archives/testrepo/html/en/codemirror/mode/velocity
/usr/share/eprints/lib/static/codemirror/mode/velocity/velocity.js -> /usr/share/eprints/archives/testrepo/html/en/codemirror/mode/velocity/velocity.js
mkdir /usr/share/eprints/archives/testrepo/html/en/style/images
/usr/share/eprints/lib/static/style/images/action_edit.png -> /usr/share/eprints/archives/testrepo/html/en/style/images/action_edit.png
[...]
/usr/share/eprints/lib/static/style/images/action_unpack.png -> /usr/share/eprints/archives/testrepo/html/en/style/images/action_unpack.png
/usr/share/eprints/lib/static/codemirror/lib/util/loadmode.js -> /usr/share/eprints/archives/testrepo/html/en/codemirror/lib/util/loadmode.js
Ending EPrints Repository.

Do you want to import the LOC subjects? [yes] ?

Starting EPrints Repository.
Connecting to DB ... done.
Importing from /usr/share/eprints/archives/testrepo/cfg/subjects...
Done importing 280 subjects from /usr/share/eprints/archives/testrepo/cfg/subjects
Reindexing subject dataset to set ancestor data
Reindexing item: subject/A
Reindexing item: subject/AC
Reindexing item: subject/AI
Reindexing item: subject/AM
[...]
Reindexing item: subject/sch_soc
Reindexing item: subject/subjects
Done reindexing
Ending EPrints Repository.

Exiting normally.
Do you want to update the apache config files? (you still need to add the
'Include' line) [yes] ?
Wrote /usr/share/eprints/cfg/apache/testrepo.conf

You must restart apache for any changes to take effect!

--------------------------------------------------------------------------
That seemed to more or less work...
--------------------------------------------------------------------------

Now make any required changes to the cfg files.

Note that changing the metadata configuration may require the database
tables to be regenerated. epadmin erase_data will regenerate the
eprints and documents tables only. erase_data will regenerate everything.
(nb. these also do erase the contents of the tables, and any uploaded
files).

Make sure that your main apache config file contains the line:

Include /usr/share/eprints/cfg/apache.conf

Then stop and start your webserver:
Often:
/etc/rc.d/init.d/httpd stop
/etc/rc.d/init.d/httpd start
(or maybe /usr/local/apache/bin/apachectl stop & start)

And then try connecting to your repository.
--------------------------------------------------------------------------

Don't forget to register your repository at http://roar.eprints.org/

-bash-4.1$

</pre>

==New Configurations==
If you are setting up more than one archive which are related to each other, a "community", you may wish to establish common subjects and metadata.

Removing and adding types is easy. Removing and adding fields is a bit more work. All "screen" names of values are stored in the archives own "phrase file" which comes with phrases for the default config.

If you create a good default configuration for a different purpose or language(s) (and would like to share it), please contact the eprints admin who may want to put it online as an example or even include it as an alternate default in a later version.

User:Polyrobin

2026-07-15T10:10:49Z

Drn@ecs.soton.ac.uk: Creating user page for new user.

Administrateur de PolyPublie pour Polytechnique Montréal
Repository admin for Polytechnique Montréal's PolyPublie

« Rien n’est plus permanent qu’un hack temporaire dans EPrints. »

User talk:Polyrobin

2026-07-15T10:10:49Z

Drn@ecs.soton.ac.uk: Welcome!

'''Welcome to ''EPrints Documentation''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Drn@ecs.soton.ac.uk|Drn@ecs.soton.ac.uk]] ([[User talk:Drn@ecs.soton.ac.uk|talk]]) 10:10, 15 July 2026 (UTC)

User:EDumbill

2026-07-15T10:00:23Z

Drn@ecs.soton.ac.uk: Creating user page for new user.

I work at CoSector and have been developing EPrints since 2020. My github account with the same username includes some of my contributions :)

User talk:EDumbill

2026-07-15T10:00:23Z

Drn@ecs.soton.ac.uk: Welcome!

DataCite DOI

2026-07-15T09:29:46Z

Drn@ecs.soton.ac.uk: Added info about Test API

'''This documentation relates to release candidate version of the DataCite DOI plugin, available at [https://github.com/eprintsug/DataCiteDoi/tree/datacite-documents]'''

==DataCite DOI Manager Screen==
The process for registering and minting DOIs is now managed via the '''DataCite DOI Manager''' screen, available via an eprint item’s '''Actions''' tab.

[[File:Actions tab highlighted.png|600px|thumb|center|Actions tab with the DataCite DOI Manager option.]]

The '''DataCite DOI Manager''' is only available for items in the review queue or the live archive, and only to those users with editor or administrator permissions.

Each eprint record has its own DOI that can be registered with DataCite, derived from the repository’s DataCite prefix (e.g. 10.xxx), the repository’s name, and the eprint’s ID.

[[File:Available doi.jpg|600px|thumb|center|An eprint in the live archive with an available DOI. Options are available to either reserve or mint the DOI.]]

If this DOI has not yet been registered on DataCite, it will be listed as an '''Available DOI''', and is available either to reserve or mint:

* '''Reserve:''' The DOI is created in DataCite as a Draft DOI. The DOI is not listed in the global handle system and is not publicly findable.
* '''Mint:''' The DOI is registered with the global handle system and listed as Findable in DataCite.

==Reserving DOIS==
Items in the repository’s review queue may only have DOIs reserved. Not all of the mandatory metadata is required when reserving a DOI.

[[File:Reserve doi.jpg|600px|thumb|center|An item in the review queue. A DOI may be reserved adding it as a draft DOI in DataCite.]]

Clicking the '''Reserve DOI''' button will create a draft DOI in DataCite. This process happens instantly and the '''DataCite DOI Manager''' screen will update to show when the DOI was reserved as well as adding the DOI to the item’s DOI metadata field. Draft DOIs are not registered against the global handle system, i.e. they won’t redirect to the eprint. Once a reserved DOI has been created it can be updated with the item’s current metadata.

[[File:Update reserve.jpg|600px|thumb|center|A reserved DOI, with the option to update the metadata associated with this DOI.]]

==Minting DOIs==
Minting a DOI adds it as a findable DOI in DataCite. There are two main approaches to minting a DOI:

# Using the '''Mint DOI''' button for an item in the live archive, which has all of the required metadata.
# Transferring an item with a reserved DOI and all of the required metadata, to the live archive, from the review queue.

The '''Mint DOI''' button will register the DOI with the global handle system, and the DOI will be registered as “Findable” in DataCite. This process may take a few minutes and is handled by the repository’s indexer. Upon successful completion the new DOI will be added to the eprint’s DOI metadata field.

[[File:Mint doi.jpg|600px|thumb|center|An item in the live archive with a DOI available to mint. The option to update the previously reserved DOI is still available too.]]

Once a DOI has successfully been minted for an eprint, the option to '''Update Metadata''' becomes available, which will resend the eprint metadata for this DOI.

'''This should only be used for minor updates, e.g. correcting errors or adding additional files.'''

==Tombstone Pages==
If an item which has previously had a DOI minted for it is either retired or removed from the repository, the DataCite record is updated to point to a tombstone page for the record. This consists of the basic citation metadata that was last registered with DataCite, i.e. the data available when either of the '''Mint DOI''' or '''Update Metadata''' buttons was last used.

[[File:Eprint tombstone.jpg|600px|thumb|center|A tombstone page for a retired eprint, which the DOI will now redirect to, providing basic citation information.]]

==Versioning==
When creating a new version of an eprint via the '''New version''' button in the '''Actions''' tab, any existing DOI value will be copied across to the new version of the eprint.

The '''DataCite DOI Manager''' will highlight when a Current DOI redirects to an earlier version of an eprint, and will present two options when the later version is in the live archive (i.e. has a page a DOI can successfully redirect to).

# '''Update Metadata & URL''' – this will update the current DataCite record to redirect to the new version of this eprint
# '''Reserve DOI''' and '''Mint DOI''' – the regular options available when the Available DOI for a record has not yet been reserved or registered on DataCite.

[[File:Update metadata and url.jpg|600px|thumb|center|This eprint is a later version of an existing eprint and has inherited a DOI. The metadata and URL associated with this DOI can be updated to redirect to the newer record.]]

DOIs registered for eprints which are earlier or later versions of other eprints, will use DataCite’s “HasVersion” and “IsVersionOf” properties to link forwards and backwards as appropriate.

==External DOIs==
If an eprint already has a DOI associated with it, e.g. one that has previously been provided by a journal publication, then this will be listed as the '''Current DOI'''. The DataCite DOI Manager screen will indicate where this DOI redirects to, and will still present options for an '''Available DOI''' if the DOI for this record can still be minted on DataCite.

[[File:External doi.jpg|600px|thumb|center|An eprint with an external DOI set. This can be replaced with an available DOI via DataCite.]]

The '''DataCite DOI Manager''' will also run a search of the eprint’s title against DataCites findable records, to see if a DOI has been coined previously. If one of the records matches the eprint, the '''Claim DOI''' button will set the eprint’s DOI metadata field to the DOI already on DataCite.

[[File:Claim doi.jpg|600px|thumb|center|Items with similar titles are already present on DataCite. If one matches the eprint, click "Claim DOI" to use the existing DOI rather than coining a new one.]]

==Document DOIs==
All of the above features are also available for documents uploaded to a repository. DOIs must resolve to a landing page about the record they identify, and as such these features are only available for repositories with document landing pages enabled.

In order to enable this functionality your repository must meet the following requirements:
# Support document landing pages (see for further details)
# Define a document field for storing newly minted DOIs and specify the name of this field in the DataCite DOI configuration
# Have the document_dois configuration flag enabled.

The '''document_dois''' flag and field name can be configured in '''z_datacitedoi.pl'''.
<pre>
# flag to indicate if this repository is able to coin dois for documents (off by default)
$c->{datacitedoi}{document_dois} = 1;

# which fields to use for the doi
$c->{datacitedoi}{eprintdoifield} = "id_number";
$c->{datacitedoi}{documentdoifield} = "id_number";
</pre>

Similarly an '''id_number''' field can be defined in '''document_fields.pl''' or elsewhere in the repository configuration:
<pre>
$c->{fields}->{document} = [
{
name => "id_number",
type => "text",
render_value => 'EPrints::Extras::render_possible_doi',
},
];
</pre>

[[File:Document actions.jpg|600px|thumb|center| The document "test.pdf" attached to this eprint can also have a DOI reserved or coined.]]

=Document Landing Pages=
The DataCite DOI plugin supports minting DOIs for documents uploaded to eprint records, however all DOIs must resolve to a landing page however and so in order to enable this your repository needs to support document landing pages. The following code snippets illustrate how to implement document landing pages in EPrints.

First we need a URL rewrite trigger to catch the URLs which should resolve to the landing page. The following needs to be added to the eprints or archives' configuration files, e.g. '''lib/cfg.d/doc_landing_pages.pl'''. We can also define a flag here for plugins to check to see if document landing pages are enabled on this repository.

<pre>
# configuration flag used to check if document landing pages are enabled on this repository
$c->{doc_landing_pages_enabled} = 1;

$c->add_trigger( EP_TRIGGER_URL_REWRITE, sub
{
my( %args ) = @_;

my( $uri, $rc, $request ) = @args{ qw( uri return_code request ) };

# matches https://myrepo.ac.uk/document/<doc_id>
if( defined $uri && ($uri =~ m#^/document/(.*)$# ) )
{
$request->handler('perl-script');
$request->set_handlers(PerlResponseHandler => [ 'EPrints::Apache::Document' ] );
${$rc} = EPrints::Const::OK;
}

return EP_TRIGGER_OK;

}, priority => 100 );
</pre>

This trigger uses a Document handler we need to implement, e.g. '''perl_lib/EPrints/Apache/Document.pm'''

<pre>
######################################################################
#
# EPrints::Apache::Document
#
######################################################################

package EPrints::Apache::Document;

use strict;

use EPrints;
use EPrints::Apache::AnApache;

sub handler
{
my( $r ) = @_;

my $uri = $r->uri;

if( $uri =~ m#^/document/(.*)$# )
{
my $repository = $EPrints::HANDLE->current_repository;
return DECLINED if( !defined $repository );

# Document landing pages enabled for this repository?
return DECLINED unless( $repository->config( "doc_landing_pages_enabled" ) );

my $doc_id = $1;

my $doc_ds = $repository->dataset( "document" );
my $doc = $doc_ds->dataobj( $doc_id );

if( defined $doc )
{
EPrints::ScreenProcessor->process(
session => $repository,
screenid => "Document",
document => $doc,
);
return OK;
}
}

return DECLINED;
}

1;
</pre>

The handler calls on an EPrints screen to generate the content for the landing page, e.g. '''perl_lib/EPrints/Plugin/Screen/Document.pm'''

<pre>
=head1 NAME

EPrints::Plugin::Screen::Document

=cut#

package EPrints::Plugin::Screen::Document;

use EPrints::Plugin::Screen;

@ISA = ( 'EPrints::Plugin::Screen' );

use strict;

sub new
{
my( $class, %params ) = @_;

my $self = $class->SUPER::new(%params);

return $self;
}

sub properties_from
{
my( $self ) = @_;

$self->{processor}->{eprint} = $self->{processor}->{document}->get_eprint;

$self->SUPER::properties_from;
}

sub render_title
{
my( $self ) = @_;

my $session = $self->{session};

my $f = $self->{session}->make_doc_fragment;

my $eprint = $self->{processor}->{eprint};
my $doc = $self->{processor}->{document};

$f->appendChild( $self->{processor}->{eprint}->render_citation( "screen" ) );

$f->appendChild( $self->{session}->html_phrase( "document_join" ) );

$f->appendChild( $self->{processor}->{document}->render_citation( "screen" ) );

return $f;
}

sub render
{
my( $self ) = @_;

my $repo = $self->{repository};
my $doc = $self->{processor}->{document};

my $page = $repo->make_doc_fragment;

my $div = $repo->make_element( "div", class => "doc_citation" );

$div->appendChild( $doc->render_citation( "landing_page", eprint => $self->{processor}->{eprint} ) );

return( $div );
}

1;
</pre>

And finally, the screen uses a citation file to display the document landing page content in an easily customisable fashion, e.g. '''lib/defaultcfg/citations/document/landing_page.xml'''

<pre>

<?xml version="1.0" ?>



<cite:citation xmlns="http://www.w3.org/1999/xhtml" xmlns:epc="http://eprints.org/ep3/control" xmlns:cite="http://eprints.org/ep3/citation" >


<epc:print expr="$eprint.citation_link('default')" />


<table>
<tr>
<td valign="top" align="right"><epc:print expr="$item.icon( 'HoverPreview', 'noNewWindow' )" /></td>
<td valign="top">
<epc:print expr="$item.citation('default')" /><br />
<a href="{$item.url()}" class="ep_document_link"><epc:phrase ref="summary_page:download"/> (<epc:print expr="$item.doc_size().human_filesize()" />)</a>
</td>
</tr>
</table>

</cite:citation>
</pre>

=Test and Production APIs=
After initially installing the DataCiteDoi plugin it will be configured to use the test API and MDS URLs, using the following configuration in ''cfg.d/z_datacitedoi.pl'' (either in your archive's cfg/ directory if installed from the Bazaar or as an EPM but under ingredients/DataCiteDoi/ if installed as an ingredient):

$c->{datacitedoi}{mdsurl} = "https://mds.test.datacite.org/";
$c->{datacitedoi}{apiurl} = "https://api.test.datacite.org/";

If you want to use the real API and MDS, you will need to take out the ".test" to become:

$c->{datacitedoi}{mdsurl} = "https://mds.datacite.org/";
$c->{datacitedoi}{apiurl} = "https://api.datacite.org/";

However, whilst you are using the test API, be aware that although the DataCiteDoi plugin will generate DOI links of the form:
https://doi.org/10.1234/5678
these will resolve to a page saying the DOI is not found. To check the the DOI has successfully been minted you should replace '''doi.org''' with '''handle.test.datacite.org'''. E.g.
https://handle.test.datacite.org/10.1234/5678
If the minting has been successful, like the production DOIs, this should redirect to the EPrints abstract/summary page for the relevant item.

EPrints 3.5.0 Release Candidate 1

2026-07-03T17:17:42Z

Drn@ecs.soton.ac.uk: /* Things to try next */

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1.

We invite the EPrints Community to test RC1, please report any issues you may find on GitHub, see below on how to do this.

There may be further release candidates before the official release, but we do not anticipate any large scale changes.

== Installation Instructions ==
=== Red Hat Enterprise Linux / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel
yum install ffmpeg-free # if you need to process videos
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-rc1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .

# if you wish to use changes since RC1, skip this line
git checkout v3.5.0-rc1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd
15. Start EPrints indexer. This can be done either via the '''System Tools''' tab on the Admin page in the web interface or with the following command:
/opt/eprints3/bin/indexer start

==== Things to try next ====
Set up HTTPS using LetsEncrypt certificates
As the eprints user
/opt/eprints3/bin/generate_le_cert <REPO> --verbose
As the root user
Add "Include /opt/eprints3/archives/REPO/ssl/securevhost.conf" to /etc/httpd/conf.d/eprints.conf
mv /etc/httpd/conf.d/ssl.conf.disabled /etc/httpd/conf.d/ssl.conf
apachectl restart

Use the new rich text easy pages instead of the standard xpage ones.
As the eprints user
/opt/eprints3/ingredients/easy_pages/bin/create_standard_pages <REPO>
These can be edited via "Manage records" -> "Page".
Or a new page can be create via "Admin" -> "Config Tools" -> "Create a Page".

=== Ubuntu 24.04 / Debian 13 (Trixie) ===
'''N.B.''' Ubuntu 26.04 LTS is not yet supported due to issue with libxml2.

'''To be written'''

== Potential Gotchas ==
1. If you are looking to import some EPrints 3.4 data into your new 3v5:

EPrints 3.5 new '''Contributions''' field supersedes fields like ''Creators'', ''Editors'', ''Corporate Creators'', ''Contributors''. It will write value back to these legacy fields but if you try to import EP3XML exported from an EPrints 3.4 repository it will not map these legacy fields into the Contributions field. If you want to import a load of EPrints 3.4 records for testing, then be sure to disable the Contributions field in your archive's the eprint workflow before doing this import. (You may need to copy the workflow file from '''/opt/eprints3/flavours/pub_lib/workflows/eprint/default/core.xml''' to your archive's '''cfg/workflows/eprint/''' directory before editing this file to disable the Contributions field.

== Reporting Issues ==
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

To switch from testing RC1 to testing out master, as the eprints user
cd /opt/eprints3
git checkout master
git pull --recurse-submodules

[[Category:EPrints3.5]]

EPrints 3.5.0 Release Candidate 1

2026-07-03T17:16:48Z

Drn@ecs.soton.ac.uk: /* Red Hat Enterprise Linux / Rocky Linux 9 */

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1.

We invite the EPrints Community to test RC1, please report any issues you may find on GitHub, see below on how to do this.

There may be further release candidates before the official release, but we do not anticipate any large scale changes.

== Installation Instructions ==
=== Red Hat Enterprise Linux / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel
yum install ffmpeg-free # if you need to process videos
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-rc1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .

# if you wish to use changes since RC1, skip this line
git checkout v3.5.0-rc1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd
15. Start EPrints indexer. This can be done either via the '''System Tools''' tab on the Admin page in the web interface or with the following command:
/opt/eprints3/bin/indexer start

=== Things to try next ===
Set up HTTPS using LetsEncrypt certificates
As the eprints user
/opt/eprints3/bin/generate_le_cert <REPO> --verbose
As the root user
Add "Include /opt/eprints3/archives/REPO/ssl/securevhost.conf" to /etc/httpd/conf.d/eprints.conf
mv /etc/httpd/conf.d/ssl.conf.disabled /etc/httpd/conf.d/ssl.conf
apachectl restart

Use the new rich text easy pages instead of the standard xpage ones.
As the eprints user
/opt/eprints3/ingredients/easy_pages/bin/create_standard_pages <REPO>
These can be edited via "Manage records" -> "Page".
Or a new page can be create via "Admin" -> "Config Tools" -> "Create a Page".

=== Ubuntu 24.04 / Debian 13 (Trixie) ===
'''N.B.''' Ubuntu 26.04 LTS is not yet supported due to issue with libxml2.

'''To be written'''

== Potential Gotchas ==
1. If you are looking to import some EPrints 3.4 data into your new 3v5:

EPrints 3.5 new '''Contributions''' field supersedes fields like ''Creators'', ''Editors'', ''Corporate Creators'', ''Contributors''. It will write value back to these legacy fields but if you try to import EP3XML exported from an EPrints 3.4 repository it will not map these legacy fields into the Contributions field. If you want to import a load of EPrints 3.4 records for testing, then be sure to disable the Contributions field in your archive's the eprint workflow before doing this import. (You may need to copy the workflow file from '''/opt/eprints3/flavours/pub_lib/workflows/eprint/default/core.xml''' to your archive's '''cfg/workflows/eprint/''' directory before editing this file to disable the Contributions field.

== Reporting Issues ==
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

To switch from testing RC1 to testing out master, as the eprints user
cd /opt/eprints3
git checkout master
git pull --recurse-submodules

[[Category:EPrints3.5]]

EPrints 3.5.0 Testing

2026-07-03T17:15:43Z

Drn@ecs.soton.ac.uk: /* Things for beta testers to test? */

This page discusses the various testing carried out and to be carried out as part of the EPrints 3.5.0 release

== Continuous Integration Testing ==
A build of [https://github.com/eprints/eprints3.5/ EPrints 3.5 GitHub head] is carried out every day with the following tested:
1. Unit tests as found under https://github.com/eprints/eprints3.5/tree/master/tests
2. User acceptance tests (written using the [https://www.selenium.dev/selenium-ide/ Selenium IDE]) described at https://github.com/eprints/eprints_ci/blob/main/sides/templates/eprints35_pub.side.tmpl

Also, we are currently in the process of integrating CI with GitHub pull requests to test a build of the pull request to informed reviewers of whether it is OK to merge. These tests are written in [https://playwright.dev/ Playwright] and can be found under https://github.com/eprints/eprints3.5/tree/master/ci/pytest/eprints/ but there are only a few tests at the moment and it is a work in progress to build up a suite of tests that will ultimately be more comprehensive than the current Selenium IDE acceptance tests

== Accessibility Testing ==
A full survey of pages in a vanilla EPrints research publication repository has been carried out using the WAVE Accessibility plugin for Firefox. The current results for this survey can be found at https://raw.githubusercontent.com/eprints/eprints3.5/refs/heads/master/lib/lang/en/static/accessibility/report.xpage or if you have deployed an EPrints instance at http://YOUR.REPOSITORY.HOSTNAME/accessibility/report.html

== Spell Checking ==
[https://github.com/codespell-project/codespell Codespell] has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary.txt standard] and [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary_rare.txt rare] Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator).

== Things for beta testers to test? ==
Obviously when developing a new EPrints repository a lot of the testing falls into two categories:
# Testing the new features being implemented.
# Doing stock testing of generic functionality.
What is often gets missed is more niche features or just using an EPrints repository in non-standard ways. Therefore testing ingredients, plugins, etc. that don't come as part of the initial install would be really useful to get feedback. As EPrints 3.5 has quite a few changes to 3.4, then trying to deploying the whole configuration, ingredients, plugins for an archive is unrealistic. However, testing individual ingredients/plugins you will want to use on 3.5 or interesting bespoke changes to your EPrints repository, are just the sort of things we are looking for as beta test feedback.

However, to start with you probably just want to follow the current [[EPrints_3.5.0_Release_Candidate_1#Installation_Instructions|EPrints 3.5.0 RC1 installation instructions]] and make sure you can get an EPrints repository up and running.

== Suggestions for features/aspects to test ==
If you have an EPrints wiki account and want to suggest things that should be tested (which don't look to have been covered above) then please add these below.

EPrints 3.5.0 Testing

2026-07-03T17:12:48Z

Drn@ecs.soton.ac.uk: /* Continuous Integration Testing */

This page discusses the various testing carried out and to be carried out as part of the EPrints 3.5.0 release

== Continuous Integration Testing ==
A build of [https://github.com/eprints/eprints3.5/ EPrints 3.5 GitHub head] is carried out every day with the following tested:
1. Unit tests as found under https://github.com/eprints/eprints3.5/tree/master/tests
2. User acceptance tests (written using the [https://www.selenium.dev/selenium-ide/ Selenium IDE]) described at https://github.com/eprints/eprints_ci/blob/main/sides/templates/eprints35_pub.side.tmpl

Also, we are currently in the process of integrating CI with GitHub pull requests to test a build of the pull request to informed reviewers of whether it is OK to merge. These tests are written in [https://playwright.dev/ Playwright] and can be found under https://github.com/eprints/eprints3.5/tree/master/ci/pytest/eprints/ but there are only a few tests at the moment and it is a work in progress to build up a suite of tests that will ultimately be more comprehensive than the current Selenium IDE acceptance tests

== Accessibility Testing ==
A full survey of pages in a vanilla EPrints research publication repository has been carried out using the WAVE Accessibility plugin for Firefox. The current results for this survey can be found at https://raw.githubusercontent.com/eprints/eprints3.5/refs/heads/master/lib/lang/en/static/accessibility/report.xpage or if you have deployed an EPrints instance at http://YOUR.REPOSITORY.HOSTNAME/accessibility/report.html

== Spell Checking ==
[https://github.com/codespell-project/codespell Codespell] has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary.txt standard] and [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary_rare.txt rare] Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator).

== Things for beta testers to test? ==
Obviously when developing a new EPrints repository a lot of the testing falls into two categories:
1. Testing the new features being implemented.
2. Doing stock testing of generic functionality.
What is often gets missed is more niche features or just using an EPrints repository in non-standard ways. Therefore testing ingredients, plugins, etc. that don't come as part of the initial install would be really useful to get feedback. As EPrints 3.5 has quite a few changes to 3.4, then trying to deploying the whole configuration, ingredients, plugins for an archive is unrealistic. However, testing individual ingredients/plugins you will want to use on 3.5 or interesting bespoke changes to your EPrints repository, are just the sort of things we are looking for as beta test feedback.

However, to start with you probably just want to follow the current [[EPrints_3.5.0_Release_Candidate_1#Installation_Instructions|EPrints 3.5.0 RC1 installation instructions]] and make sure you can get an EPrints repository up and running.

== Suggestions for features/aspects to test ==
If you have an EPrints wiki account and want to suggest things that should be tested (which don't look to have been covered above) then please add these below.

EPrints 3.5.0 Testing

2026-07-03T17:10:40Z

Drn@ecs.soton.ac.uk: /* Spell Checking */

This page discusses the various testing carried out and to be carried out as part of the EPrints 3.5.0 release

== Continuous Integration Testing ==
A build of [https://github.com/eprints/eprints3.5/ EPrints 3.5 GitHub head] is carried out every day with the following tested:
1. Unit tests as found under https://github.com/eprints/eprints3.5/tree/master/tests
2. User acceptance tests (written using the [https://www.selenium.dev/selenium-ide/ Selenium IDE]) described at https://github.com/eprints/eprints_ci/blob/main/sides/templates/eprints35_pub.side.tmpl

Also, we are currently in the process of integrating CI with pull requests to test a build of the pull request to informed reviewers of whether it is OK to merge. These tests are written in [https://playwright.dev/ Playwright] and can be found under https://github.com/eprints/eprints3.5/tree/master/ci/pytest/eprints/ but there are only a few tests at the moment and it is a work in progress to build up a suite of tests that will ultimately be more comprehensive than the current Selenium IDE acceptance tests

== Accessibility Testing ==
A full survey of pages in a vanilla EPrints research publication repository has been carried out using the WAVE Accessibility plugin for Firefox. The current results for this survey can be found at https://raw.githubusercontent.com/eprints/eprints3.5/refs/heads/master/lib/lang/en/static/accessibility/report.xpage or if you have deployed an EPrints instance at http://YOUR.REPOSITORY.HOSTNAME/accessibility/report.html

== Spell Checking ==
[https://github.com/codespell-project/codespell Codespell] has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary.txt standard] and [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary_rare.txt rare] Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator).

== Things for beta testers to test? ==
Obviously when developing a new EPrints repository a lot of the testing falls into two categories:
1. Testing the new features being implemented.
2. Doing stock testing of generic functionality.
What is often gets missed is more niche features or just using an EPrints repository in non-standard ways. Therefore testing ingredients, plugins, etc. that don't come as part of the initial install would be really useful to get feedback. As EPrints 3.5 has quite a few changes to 3.4, then trying to deploying the whole configuration, ingredients, plugins for an archive is unrealistic. However, testing individual ingredients/plugins you will want to use on 3.5 or interesting bespoke changes to your EPrints repository, are just the sort of things we are looking for as beta test feedback.

However, to start with you probably just want to follow the current [[EPrints_3.5.0_Release_Candidate_1#Installation_Instructions|EPrints 3.5.0 RC1 installation instructions]] and make sure you can get an EPrints repository up and running.

== Suggestions for features/aspects to test ==
If you have an EPrints wiki account and want to suggest things that should be tested (which don't look to have been covered above) then please add these below.

EPrints 3.5.0 Testing

2026-07-03T17:10:13Z

Drn@ecs.soton.ac.uk: Added testing 3.5.0 page

This page discusses the various testing carried out and to be carried out as part of the EPrints 3.5.0 release

== Continuous Integration Testing ==
A build of [https://github.com/eprints/eprints3.5/ EPrints 3.5 GitHub head] is carried out every day with the following tested:
1. Unit tests as found under https://github.com/eprints/eprints3.5/tree/master/tests
2. User acceptance tests (written using the [https://www.selenium.dev/selenium-ide/ Selenium IDE]) described at https://github.com/eprints/eprints_ci/blob/main/sides/templates/eprints35_pub.side.tmpl

Also, we are currently in the process of integrating CI with pull requests to test a build of the pull request to informed reviewers of whether it is OK to merge. These tests are written in [https://playwright.dev/ Playwright] and can be found under https://github.com/eprints/eprints3.5/tree/master/ci/pytest/eprints/ but there are only a few tests at the moment and it is a work in progress to build up a suite of tests that will ultimately be more comprehensive than the current Selenium IDE acceptance tests

== Accessibility Testing ==
A full survey of pages in a vanilla EPrints research publication repository has been carried out using the WAVE Accessibility plugin for Firefox. The current results for this survey can be found at https://raw.githubusercontent.com/eprints/eprints3.5/refs/heads/master/lib/lang/en/static/accessibility/report.xpage or if you have deployed an EPrints instance at http://YOUR.REPOSITORY.HOSTNAME/accessibility/report.html

== Spell Checking ==
[https://github.com/codespell-project/codespell Codespell] has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary.txt standard] and [ https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary_rare.txt rare] Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator).

== Things for beta testers to test? ==
Obviously when developing a new EPrints repository a lot of the testing falls into two categories:
1. Testing the new features being implemented.
2. Doing stock testing of generic functionality.
What is often gets missed is more niche features or just using an EPrints repository in non-standard ways. Therefore testing ingredients, plugins, etc. that don't come as part of the initial install would be really useful to get feedback. As EPrints 3.5 has quite a few changes to 3.4, then trying to deploying the whole configuration, ingredients, plugins for an archive is unrealistic. However, testing individual ingredients/plugins you will want to use on 3.5 or interesting bespoke changes to your EPrints repository, are just the sort of things we are looking for as beta test feedback.

However, to start with you probably just want to follow the current [[EPrints_3.5.0_Release_Candidate_1#Installation_Instructions|EPrints 3.5.0 RC1 installation instructions]] and make sure you can get an EPrints repository up and running.

== Suggestions for features/aspects to test ==
If you have an EPrints wiki account and want to suggest things that should be tested (which don't look to have been covered above) then please add these below.

Denial-of-Service Symptoms

2026-07-02T16:38:44Z

Drn@ecs.soton.ac.uk: /* Common Apache Error messages */

This page is intended to details some of the symptoms experienced if your EPrints repository is suffering from a (Distributed) Denial-of-Service attack or at least does not have enough resources to service the scale of requests it is getting

== Common Apache Error messages ==
Line numbers may not be the same in the current HEAD of this git repository:
# (Broken pipe / The timeout specified has expired / Connection reset by peer) at <code>/opt/eprints3/perl_lib/EPrints/Page.pm line 78</code>
# (Broken pipe / Connection reset by peer) at <code>/opt/eprints3/perl_lib/EPrints/Plugin/Export.pm line 283</code>
# (Broken pipe / Connection reset by peer) at <code>opt/eprints3/cgi/exportview line 126</code>
# Broken pipe at <code>/opt/eprints3/perl_lib/EPrints/Apache/CRUD.pm line 1670</code>

Denial-of-Service Symptoms

2026-07-02T16:37:21Z

Drn@ecs.soton.ac.uk: Added page about DoS

This page is intended to details some of the symptoms experienced if your EPrints repository is suffering from a (Distributed) Denial-of-Service attack or at least does not have enough resources to service the scale of requests it is getting

== Common Apache Error messages ==
Line numbers may not be the same in the current HEAD of this git repository:
# (Broken pipe / The timeout specified has expired / Connection reset by peer) at **/opt/eprints3/perl_lib/EPrints/Page.pm line 78**
# (Broken pipe / Connection reset by peer) at **/opt/eprints3/perl_lib/EPrints/Plugin/Export.pm line 283**
# (Broken pipe / Connection reset by peer) at **opt/eprints3/cgi/exportview line 126**
# Broken pipe at **/opt/eprints3/perl_lib/EPrints/Apache/CRUD.pm line 1670**

Issues with Installing EPrints on Ubuntu 26.04

2026-07-02T11:37:05Z

Drn@ecs.soton.ac.uk:

As of 2nd July 2026, Ubuntu 26.04 is still under testing to determine if EPrints can be successfully installed and if so if there are any issues with doing this, which require a different approach from the general approach for installing EPrints on Debian/Ubuntu Linux.

==== Current Issues ====
; XML library compatibility problems : This will first occur at the point where you complete the credentials you want to use for your archive's database whilst you are running <code>bin/epadmin create pub</code>. It will exhibit itself as either a segmentation fault or an error with the memory allocation (malloc) or free commands. This is due to EPrints use of the <code>XML:LibXML</code> Perl library that ultimately uses the C library <tt>libxml2</tt>. [https://github.com/eprints/eprints3.4/issues/509 This GitHub issue] first raised for what appears to be the same issue with FreeBSD 14.3 provides some more detail about this problem. It is likely this relates to [https://github.com/cpan-authors/XML-LibXML/issues/81 this XML::LibXML GitHub issue], which says it has been resolved upstream, which we believe to mean in the libxml2 C library (although it does not seem to gave made it into version 2.15.3). Ubuntu 26.04 as of 2nd July 2026 is still providing libxml2 version 2.15.2, so there will hopefully be an update soon.

EPrints 3.5.0 Release Candidate 1

2026-06-19T14:55:02Z

Drn@ecs.soton.ac.uk: Added Potential Gotchas section

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1. There may be further release candidatesbefore the first official release of EPrints 3.5.0.

== Installation Instructions ==
=== Red Hat Enterprise Linux / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel xapian-core xapian-core-devel
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-beta-1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .
git checkout v3.5.0-beta-1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd
15. Start EPrints indexer. This can be done either via the '''System Tools''' tab on the Admin page in the web interface or with the following command:
/opt/eprints3/bin/indexer start

=== Ubuntu 24.04 / Debian 13 (Trixie) ===
'''N.B.''' Ubuntu 26.04 LTS is not yet supported due to issue with libxml2.

'''To be written'''

== Potential Gotchas ==
# EPrints 3.5 new '''Contributions''' field supersedes fields like ''Creators'', ''Editors'', ''Corporate Creators'', ''Contributors''. It will write value back to these legacy fields but if you try to import EP3XML exported from an EPrints 3.4 repository it will not map these legacy fields intp the Contributions field. If you want to import a load of EPrints 3.4 records for testing, then be sure to disable the Contributions field in your archive's the eprint workflow before doing this import. (You may need to copy the workflow file from '''/opt/eprints3/flavours/pub_lib/workflows/eprint/default.xml''' to your archive's '''cfg/workflows/eprint/''' directory before editing this file to disable the Contributions field.

== Reporting Issues ==
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

[[Category:EPrints3.5]]

EPrints 3.5.0 Release Candidate 1

2026-06-19T14:45:43Z

Drn@ecs.soton.ac.uk: /* Red Hat Enterprise Linux / Rocky Linux 9 */ Added line about starting the Indexer.

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1. There may be further release candidatesbefore the first official release of EPrints 3.5.0.

== Installation Instructions ==
=== Red Hat Enterprise Linux / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel xapian-core xapian-core-devel
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-beta-1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .
git checkout v3.5.0-beta-1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd
15. Start EPrints indexer. This can be done either via the '''System Tools''' tab on the Admin page in the web interface or with the following command:
/opt/eprints3/bin/indexer start

=== Ubuntu 24.04 / Debian 13 (Trixie) ===
'''N.B.''' Ubuntu 26.04 LTS is not yet supported due to issue with libxml2.

'''To be written'''

== Reporting Issues ==
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

[[Category:EPrints3.5]]

EPrints 3.5.0 Release Candidate 1

2026-06-19T14:42:35Z

Drn@ecs.soton.ac.uk: /* Installation Instructions */ Added placeholder section for Debian / Ubuntu installation instructions

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1. There may be further release candidatesbefore the first official release of EPrints 3.5.0.

== Installation Instructions ==
=== Red Hat Enterprise Linux / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel xapian-core xapian-core-devel
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-beta-1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .
git checkout v3.5.0-beta-1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd

=== Ubuntu 24.04 / Debian 13 (Trixie) ===
'''N.B.''' Ubuntu 26.04 LTS is not yet supported due to issue with libxml2.

'''To be written'''

== Reporting Issues ==
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

[[Category:EPrints3.5]]

EPrints 3.5.0 Release Candidate 1

2026-06-19T14:39:48Z

Drn@ecs.soton.ac.uk: /* Reporting Issues */

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1. There may be further release candidatesbefore the first official release of EPrints 3.5.0.

== Installation Instructions ==
=== RHEL / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel xapian-core xapian-core-devel
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-beta-1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .
git checkout v3.5.0-beta-1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd

== Reporting Issues ==
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

[[Category:EPrints3.5]]

EPrints 3.5.0 Release Candidate 1

2026-06-19T14:39:32Z

Drn@ecs.soton.ac.uk: Added 3.5.0 release candidate 1 specific page,

This page provides information about the first release candidate for EPrints 3.5.0 on Friday 19th June 2026, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-rc1. There may be further release candidatesbefore the first official release of EPrints 3.5.0.

== Installation Instructions ==
=== RHEL / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl mod_ssl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel xapian-core xapian-core-devel
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-beta-1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .
git checkout v3.5.0-beta-1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd

=== Reporting Issues ===
We have create a [https://github.com/eprints/eprints3.5/issues/416 parent issue on GitHub] to list all issues with this release candidate. We will then create sub-issues as appropriate to tackle item individual in this list. If you add an issue on GitHub specific to this release candidate we will look to reference this from this parent issue.

[[Category:EPrints3.5]]

EPrints 3.5.0 Beta 1

2026-06-18T13:20:24Z

Drn@ecs.soton.ac.uk: /* Installation Instructions */ Added openssl-devel as needed to install Crypt::LE modules required by bin/generate_le_cert

This page provides information about the first beta release for EPrints 3.5.0 on Wednesday 18th June 2025, as can be found at https://github.com/eprints/eprints3.5/releases/tag/v3.5.0-beta-1. There will be further beta releases and one or more release candidates before the first official release of EPrints 3.5.0.

== Installation Instructions ==
=== RHEL / Rocky Linux 9 ===
1. Install and enable MariaDB (you may choose to install MySQL instead).
yum install mariadb-server mariadb
systemctl enable --now mariadb
2. Install The EPEL package repository and the subscription-manager and then enable the Code Ready Builder package repository
yum install epel-release
yum config-manager --enable crb
3. Install prerequite packages and tools. (Some extra packages may be required to build CPAN packages later on).
yum install git libxml2 libxslt httpd mod_perl openssl-devel perl-DBD-MySQL tetex-latex wget gzip tar ImageMagick elinks poppler-utils chkconfig unzip cpan python3-html2text expat-devel libxslt-devel xapian-core xapian-core-devel
4. Add the eprints user
adduser eprints
5. Add the eprints user to the apache group and vice-versa
usermod -a -G eprints apache
usermod -a -G apache eprints
6. For now disable SELinux. (If you want to make this permanent you will need to configure /etc/selinux/config and change SELINUX=permissive). An SELinux policy for EPrints will be provided with the full release of EPrints 3.5.0.
setenforce 0
7. Make a directory to checkout EPrints and set appropriate permissions:
mkdir /opt/eprints3
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
8. Become the eprints user and clone EPrints 3.5 recursively and checkout v3.5.0-beta-1
su eprints
cd /opt/eprints3
git clone https://github.com/eprints/eprints3.5.git --recurse-submodules .
git checkout v3.5.0-beta-1
9. Become the root user again and install CPAN modules. (Answer 'y' if prompted whilst running cpan_modules.pl). This could take 10 minutes or more to complete but ensures you get modules tested against this version of EPrints. It is worth running cpan_modules.pl a second time after it completes, to get a better idea if all CPAN modules have been installed successfully.
su root
/opt/eprints3/cpan_modules.pl
10. Be sure to either set a password for the MariaDB root user or create another user (e.g. eprints) that can create new databases and add new MariaDB users
mysql
CREATE USER 'eprints'@'localhost' IDENTIFIED by '<CHANGE_ME>';
GRANT ALL PRIVILEGES ON *.* TO 'eprints'@'localhost' WITH GRANT OPTION;
11. Become the eprints user again and create your new EPrints archive using the 'pub' flavour and then follow the interactive instructions.
su eprints
/opt/eprints3/bin/epadmin create
12. Become the root user and create an Apache configuration file at /etc/httpd/conf.d/eprints.conf with the following line:
Include /opt/eprints3/cfg/apache.conf
13. For now, disable /etc/httpd/conf.d/ssl.conf
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled
14. Test and start Apache..
apachectl configtest
systemctl enable --now httpd

=== Troubleshooting ===

==== Error when creating context field for citationcache table ====
Some versions of MySQL/MariaDB will not allow a longtext field to have an index assigned to it. This can be fixed by modifying the code for /opt/eprints3/perl_lib/EPrints/DataObj/CitationCache.pm and editing the line to remove the SQL index for the context field, so that:
{ name=>"context", type=>"longtext", sql_index=>1 },
becomes:
{ name=>"context", type=>"longtext" },
You will then need to run the follow command on your archive to make sure all fields for the CitationCache have been added to the database before you start Apache for the first time.
/opt/eprints3/bin/epadmin update <ARCHIVE_ID>
We considered making the above code change to Beta 1 but were unsure whether it might affect the way citation caching works. As this issue only affects some versions of MySQL/MariaDB we felt it better to leave the SQL index in for now and test whether it is required before a future beta release.

==== Indexer not starting ====
Make sure /opt/eprints3/var/ is group writeable.
chmod g+w /opt/eprints3/var

==== Contributions autocompleter gives 500 error ====
This may be due to certain versions of MySQL / MariaDB enforcing sql_mode=only_full_group_by. You will need to add configuration to a file in /etc/my.cnf.d/zz_disable_ofgb.cnf or /etc/mysql/my.cnf.d/zz_disable_ofgb.cnf on some operating system and add the following two lines. Then restart MySQL / MariaDB.

[mysqld]
sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION

[https://github.com/eprints/eprints3.5/issues/161 We are looking into whether the code can be modified] so that you do not need to disable this restriction in MySQL / MariaDB.

==== Errors when generating thumbnails for PDFs ====
If you are running Debian / Ubuntu the ImageMagick policy file may block you from parsing PDF to generate thumbnails. [[Debian_Known_Issues#ImageMagick_policy_settings_prevent_PDF_preview.2Fthumbnail_generation|Follow this advice on how to amend the policy]].

=== Deploying HTTPS using Let's Encrypt ===
'''TO BE WRITTEN'''

== Reporting Issues ==
We are already aware of a number of issues with this beta, which we are currently working on and are logged at https://github.com/eprints/eprints3.5. Please check over these before reporting any issues you may discover.

[[Category:EPrints3.5]]
[[Category:Releases]]

EPrints 3.5.0

2026-06-12T15:19:48Z

Drn@ecs.soton.ac.uk: /* New Features */

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== PDF led deposit ====
* Upload a set of PDFs all at once.
* Each PDF generates a new eprint records
* Each PDF is parsed to exact as much useful metadata as possible to prefill the eprint workflow.

==== Creation of first-order objects for people and organisation ====
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ====
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ====
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
* Simple, advanced and eprint admin search is enabled with facets by default.
* Infinite scroll replaces pagination.

==== Potential AI Integation ====
* Allow document/metadata to be used produce AI summaries on abstract pages.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
* WSIWYG (TinyMCE) editor to write your own static (HTML) pages
* Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
* Suite of tools to assist upgrade from EPrints 3.4.x.
* Better representation of "concepts" currently captures by subject trees (subject classification and divisions) or just free text (projects, keywords, etc.)

See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:58:07Z

Drn@ecs.soton.ac.uk: Added some more points

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== PDF led deposit ====
* Upload a set of PDFs all at once.
* Each PDF generates a new eprint records
* Each PDF is parsed to exact as much useful metadata as possible to prefill the eprint workflow.

==== Creation of first-order objects for people and organisation ====
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ====
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ====
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Potential AI Integation ====
* Allow document/metadata to be used produce AI summaries on abstract pages.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
* Suite of tools to assist upgrade from EPrints 3.4.x.
* Better representation of "concepts" currently captures by subject trees (subject classification and divisions) or just free text (projects, keywords, etc.)

See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:51:20Z

Drn@ecs.soton.ac.uk: /* Further Planned Features and Improvements */ Added some important future planned features

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== Creation of first-order objects for people and organisation ====
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ====
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ====
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
* Suite of tools to assist upgrade from EPrints 3.4.x.
* Better representation of "concepts" currently captures by subject trees (subject classification and divisions) or just free text (projects, keywords, etc.)

See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:47:16Z

Drn@ecs.soton.ac.uk: /* = New modern layout for abstract/summary pages */

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== Creation of first-order objects for people and organisation ====
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ====
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ====
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:46:59Z

Drn@ecs.soton.ac.uk: /* = Use Bootstrap CSS library by default */

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== Creation of first-order objects for people and organisation ====
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ====
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ===
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:46:53Z

Drn@ecs.soton.ac.uk: /* = Creation of first-order objects for people and organisation */

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== Creation of first-order objects for people and organisation ====
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ===
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ===
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:46:40Z

Drn@ecs.soton.ac.uk: /* = Enhanced developer mode */

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== Creation of first-order objects for people and organisation ===
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ===
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ===
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ====
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-12T12:46:30Z

Drn@ecs.soton.ac.uk: /* New Features */ Added new features

{{releasenotes}}

This page contains information about the planned EPrints v3.5.0 tag and release on GitHub.

== Release Notes ==
EPrints 3.5.0 will become available on [https://github.com/eprints/eprints3.5 EPrints 3.5 GitHub] as a release.
* '''Codename:''' ''Highfield Hippogriff''

=== New Dependencies ===
''To be determined''. Please refer to the [[Installation for EPrints 3.5]].

=== Upgrade Considerations ===
EPrints 3.5.0 is only intended are a release for those deploying an new EPrints installation. EPrints 3.5.0 is not intended as a version for which you can upgrade from EPrints 3.4.x. EPrints 3.5.1 will be built with upgrading from 3.4 in mind and will offer suite of tools to assist in this process.

=== New Features ===

==== Creation of first-order objects for people and organisation ===
* Replaces reliance on partial loose association with user objects or lack of unique identification at for organisations at all.
* People and organisation objects can either be imported or are generated on-the-fly when added to an epruns

==== Introduction of new Contributions field ====
* Added to the (eprint) workflow to replace various fields that often have different formats (e.g. creators, editors, contributors, corporate creators, funders, publisher. etc.)
* Field brings together two parts an "entity" (person or organisation) and a "type of contribution" as specified by the [https://id.loc.gov/vocabulary/relators.html Library of Congress "relators" vocabulary].

==== Use Bootstrap CSS library by default ===
* Improves accessibility.
* Provides a cleaner more modern look.
* Better support for mobile and unusual resolutions.

==== New modern layout for abstract/summary pages ===
* Embedded PDF viewer
* Tabs or panels for display metadata.
* Enhanced representation of people and organisations related to a publication.

==== Faceted, infinite search by default ====
** Simple, advanced and staff eprint search is enabled with facets by default.
** Infinite scroll replaces pagination.

==== Design your only static pages by default ====
* Such as your homepage, information, contact and policies pages.
** WSIWYG (TinyMCE) editor to write your own static (HTML) pages
** Macros available to allow pages to be automatically updated on institutional name changes

==== Dynamic page templating ====
* Use phrases rather than code to specify layout dynamic pages, such as search, browse views, etc.
* Easier to customise and later maintain.

==== Removal of Prototype JavaScript ====
* By default now only uses standard JavaScript not a specific library
* Compatible version of JQuery can be installed through an ingredient ([https://github.com/eprints/jquery4eprints jquery4eprints])

==== Increased isolation between archives ====
* Each archive now has a "package" YAML file to indicate flavour and ingredients used rather than an "inc" file under each flavour.
* Each flavour, ingredient, etc. has a "component" YAML file that described it and its dependencies.

==== Enhanced developer mode ===
* Enabled with <code>epadmin set_developer_mode ARCHIVE_ID on</code>
* Configurable with 11 different settings for configuration loading, various cache disabling, SQL debugging, indexing, logging, robots.txt to displaying a banner to indicate you are in developer mode.

== Further Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.5/milestone/6 3.5.1 milestone on GitHub] for more details. Longer term planned features and improvements are listed under the [https://github.com/eprints/eprints3.5/milestone/2 3.5.x milestone]

[[Category:Eprints3.5]]
[[Category:Planned Releases]]

EPrints 3.5.0

2026-06-11T17:54:37Z

Drn@ecs.soton.ac.uk: /* New Features */ Added initial new features

EPrints 3.5.0

2026-06-11T14:20:37Z

Drn@ecs.soton.ac.uk:

Category:Eprints3.5

2026-06-11T13:47:59Z

Drn@ecs.soton.ac.uk: Added category page

EPrints 3.5's first official will be in June 2026.
[[Category:Releases]]

EPrints 3.5.0

2026-06-11T13:46:47Z

Drn@ecs.soton.ac.uk: Added planned release page for EPrints 3.5.0

Installation for EPrints 3.5

2026-05-29T10:16:37Z

Drn@ecs.soton.ac.uk: Added initial placeholder text

There are number of changes for how to install EPrints 3.5 compared to earlier versions. For now, please use these instructions rather than the generic instructions on the main [[Installation]] page for installing EPrints 3.5. At some later stage, those instructions will changed to be for EPrints 3.5 and the current instructions move to a "Installation for EPrints 3.4" instructions page.

EPrints 3.4.8

2026-05-18T13:04:44Z

Drn@ecs.soton.ac.uk: /* Bug Fixes */

This page contains information about the provisional EPrints v3.4.8 tag and release on GitHub. A date for this release is yet to be scheduled.

== Release Notes (Provisional) ==
EPrints 3.4.8 is planned to be released in the Summer of 2026.
* '''Zero codename:''' ''TO BE DETERMINED''
* '''Publications flavour codename:''' ''TO BE DETERMINED''

=== New Dependencies ===
Check earlier dependencies for [[EPrints 3.4.7]] and before.

If you wish to set a timezone of the dates and times displayed on your repository, you will need to make sure the <code>DateTime</code> Perl module is installed. For RHEL-based Linux this can be installed with the <code>perl-DateTime</code> RPM. For Debian-based Linux this requires <code>libdatetime-perl</code>.

=== Changes Since 3.4.7 ===

==== New Functionality ====
* [https://github.com/eprints/eprints3.4/commit/be86f99b3662083a4f35034f14776d86bcc9e087 Adds <code>export_file_as_attachment</code> option to force exports to be downloaded]
* [https://github.com/eprints/eprints3.4/pull/513 Adds an export plugin for document URLs]
* [https://github.com/eprints/eprints3.4/pull/512 Adds clear buttons to multiple <code>Compound</code> fields]
* [https://github.com/eprints/eprints3.4/pull/525 Adds support for rendering time with a given timezone]
* [https://github.com/eprints/eprints3.4/issues/567 Provides EPC script for getting <code>icon_url</code> for a document]
* [https://github.com/eprints/eprints3.4/issues/568 Provides EPC script for getting the raw value of a property for a data object]
* [https://github.com/eprints/eprints3.4/issues/576 Adds delete option to epadmin]
* [https://github.com/eprints/eprints3.4/issues/579 Add "Clear abortive tasks" and "Retry abortive tasks" buttons for indexer]
* [https://github.com/eprints/eprints3.4/issues/584 Adds <code>ignore_edit_lock</code> field to <code>event_queue</code> data objects so certain tasks need not be delayed by the edit lock on a record]

==== Security and Privacy Improvements ====
* [https://github.com/eprints/eprints3.4/pull/511 Prevents 'javascript:' URLs from being saved in URL fields]
* [https://github.com/eprints/eprints3.4/commit/c5884562ed72b31681d3f0308b5987b2564052ad Modifies fix for SetLang referrer misuse]
* [https://github.com/eprints/eprints3.4/issues/575 Adds <code>XSLT::Identity</code> export to those restricted to staff by default]

==== General Improvements ====
* Updates metatags functionality to equivalent to [https://github.com/eprints/metatags/releases/tag/v1.4 v1.4] plus further improvements to ensure its export plugins are compliant with unit tests
* [https://github.com/eprints/eprints3.4/pull/515 Removes the progress bar even if the upload fails]
* [https://github.com/eprints/eprints3.4/commit/5fe2b24938ed19c38b0ffa6a5bc5d67253cfb514 Remove no longer required <code>progressid</code> from file uploads]
* [https://github.com/eprints/eprints3.4/pull/519 Adds support for number format months to BibTex import]
* [https://github.com/eprints/eprints3.4/pull/518 Makes the default encoding of imports 'UTF-8']
* [https://github.com/eprints/eprints3.4/pull/520 Adds labels connecting to radio buttons for <code>Boolean</code> and <code>Set</code>]
* [https://github.com/eprints/eprints3.4/commit/21687bd917244717674e613ce0d0e372fffcf619 Improves <code>Longtext_counter</code> <code>MetaField</code>]
* [https://github.com/eprints/eprints3.4/issues/530 Removes MPM event warning message]
* [https://github.com/eprints/eprints3.4/issues/527 Improves CRUD API fault tolerance]
* [https://github.com/eprints/eprints3.4/issues/536 Better specifies MetaField property defaults]
* [https://github.com/eprints/eprints3.4/issues/464 Removes <code>rename_subject_id</code> that will not work in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/537 Reviews and Removes legacy scripts that are no longer useful in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/540 Removes <code>cgi/cal</code> (as it should be in an ingredient and not in core) and moves <code>cgi/history_search</code> to not be publicly accessible]
* [https://github.com/eprints/eprints3.4/pull/542 Improves <code>cache_table</code> method to be compatible with UUIDs]
* [https://github.com/eprints/eprints3.4/pull/538 Use public link in "Request Copy" email when using pin security]
* [https://github.com/eprints/eprints3.4/issues/549 More reliable caching of auto.{js,css}]
* [https://github.com/eprints/eprints3.4/issues/563 Programmatically allows search export for restricted formats]
* [https://github.com/eprints/eprints3.4/issues/551 Support for indexing RTF files]
* [https://github.com/eprints/eprints3.4/issues/552 Improves determination of appropriate application for conversion of document to plaintext (for indexing?)]
* [https://github.com/eprints/eprints3.4/issues/566 Removes hard-coded defaults in bin/indexer]
* [https://github.com/eprints/eprints3.4/pull/569 Updates <code>cgi/opensearchdescription</code> to use <code>cgi/opensearch</code> rather than <code>cgi/search/simple</code>]
* [https://github.com/eprints/eprints3.4/commit/8cea29fb31e67dc92e1e1448c7935279977eb348 Allows opensearchdescription to list staff restricted export formats if Authorization header used]
* [https://github.com/eprints/eprints3.4/pull/573 Provides support for startIndex and size params in opensearch]
* [https://github.com/eprints/eprints3.4/pull/574 Allow export formats available to opensearch to be customised]

==== Bug Fixes ====
* [https://github.com/eprints/eprints3.4/pull/503 Fixes sample <code>EP_TRIGGER_BEGIN</code> and <code>EP_TRIGGER_END</code> subroutines]
* [https://github.com/eprints/eprints3.4/pull/521 Checks that <code>$id->{id_type}</code> is set before comparing it]
* [https://github.com/eprints/eprints3.4/issues/531 Fixes issues with <code>Convert::PlainText</code> handling large DOCX]
* [https://github.com/eprints/eprints3.4/commit/d1777a5a3170afed02f727b989cb8ebc009c3549 Makes unsupported packaging format a bad request (400) not server error (500)]
* [https://github.com/eprints/eprints3.4/pull/534 Don't add export link elements to deleted item page head]
* [https://github.com/eprints/eprints3.4/issues/535 Specifies more appropriate <code>empty_value</code>s for <code>Int</code> and <code>Float</code> MetaFields]
* [https://github.com/eprints/eprints3.4/issues/508 Fixes <code>eval</code> blocks calling user-defined <code>toform</code> or <code>fromform</code> functions to work as effective try/catch blocks]
* [https://github.com/eprints/eprints3.4/issues/467 Fixes <code>show_children</code> not working if subject tree based browse has multiple menu levels]
* [https://github.com/eprints/eprints3.4/issues/545 Fixes issues with broken field validation warning links]
* [https://github.com/eprints/eprints3.4/pull/543 Test that a cachemap is defined before trying to retrieve its uuid]
* [https://github.com/eprints/eprints3.4/pull/544 Check modified time of citation style file when using cached citations]
* [https://github.com/eprints/eprints3.4/issues/526 Fixes OAI 2.0 will sometimes misreporting the 'Earliest Datestamp']
* [https://github.com/eprints/eprints3.4/issues/546 Moves timezone adjustment inside an <code>eval</code> to avoid it dying if datetime is invalid]
* [https://github.com/eprints/eprints3.4/issues/547 Checks if config option get_custom_view_header_location is set before comparing]
* [https://github.com/eprints/eprints3.4/issues/539 Adds missing phrases for <code>AjaxSubject</code> field]
* [https://github.com/eprints/eprints3.4/issues/555 Fixes not be able to use <code>Workflow::Edit</code> to upload a file to an eprint]
* [https://github.com/eprints/eprints3.4/issues/565 Fixes lots of calls to <code>EPrints::Index::Daemon->is_running</code> when user is not logged in]
* [https://github.com/eprints/eprints3.4/issues/561 Fixes check for whether a user is "staff" (for export plugins) to <code>is_staff</code> function rather than something hard-coded]
* [https://github.com/eprints/eprints3.4/issues/506 Fixes CRUD requests creating empty records if values are invalid for the corresponding fields in the database (e.g. text for an integer field)]
* [https://github.com/eprints/eprints3.4/issues/571 Fixes error when running render_value directly on a Compound field]
* [https://github.com/eprints/eprints3.4/issues/572 Stops <code>EPrints::DataObj->new_from_data</code> tries to delete multiple compound sub-field values that don't exist]
* [https://github.com/eprints/eprints3.4/issues/583 Makes output of redo_thumbnails more helpful]
* [https://github.com/eprints/eprints3.4/issues/580 Fixes mistyping of <code>event_queue</code> (not <code>eventqueue</code>) in the configuration for data objects excluded from citation caching]
* [https://github.com/eprints/eprints3.4/issues/586 Fixes subject fields showing undepositable options when used as a subfield]
* [https://github.com/eprints/eprints3.4/issues/585 Fixes <code>EPrints::Script::Compiled->run_contains</code> not returning proper boolean results]

== Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.4/milestone/9 3.4.8 milestone on GitHub] for more details.

[[Category:Eprints3.4]]
[[Category:Planned Releases]]

EPrints 3.4.8

2026-05-18T12:53:56Z

Drn@ecs.soton.ac.uk: /* General Improvements */

This page contains information about the provisional EPrints v3.4.8 tag and release on GitHub. A date for this release is yet to be scheduled.

== Release Notes (Provisional) ==
EPrints 3.4.8 is planned to be released in the Summer of 2026.
* '''Zero codename:''' ''TO BE DETERMINED''
* '''Publications flavour codename:''' ''TO BE DETERMINED''

=== New Dependencies ===
Check earlier dependencies for [[EPrints 3.4.7]] and before.

If you wish to set a timezone of the dates and times displayed on your repository, you will need to make sure the <code>DateTime</code> Perl module is installed. For RHEL-based Linux this can be installed with the <code>perl-DateTime</code> RPM. For Debian-based Linux this requires <code>libdatetime-perl</code>.

=== Changes Since 3.4.7 ===

==== New Functionality ====
* [https://github.com/eprints/eprints3.4/commit/be86f99b3662083a4f35034f14776d86bcc9e087 Adds <code>export_file_as_attachment</code> option to force exports to be downloaded]
* [https://github.com/eprints/eprints3.4/pull/513 Adds an export plugin for document URLs]
* [https://github.com/eprints/eprints3.4/pull/512 Adds clear buttons to multiple <code>Compound</code> fields]
* [https://github.com/eprints/eprints3.4/pull/525 Adds support for rendering time with a given timezone]
* [https://github.com/eprints/eprints3.4/issues/567 Provides EPC script for getting <code>icon_url</code> for a document]
* [https://github.com/eprints/eprints3.4/issues/568 Provides EPC script for getting the raw value of a property for a data object]
* [https://github.com/eprints/eprints3.4/issues/576 Adds delete option to epadmin]
* [https://github.com/eprints/eprints3.4/issues/579 Add "Clear abortive tasks" and "Retry abortive tasks" buttons for indexer]
* [https://github.com/eprints/eprints3.4/issues/584 Adds <code>ignore_edit_lock</code> field to <code>event_queue</code> data objects so certain tasks need not be delayed by the edit lock on a record]

==== Security and Privacy Improvements ====
* [https://github.com/eprints/eprints3.4/pull/511 Prevents 'javascript:' URLs from being saved in URL fields]
* [https://github.com/eprints/eprints3.4/commit/c5884562ed72b31681d3f0308b5987b2564052ad Modifies fix for SetLang referrer misuse]
* [https://github.com/eprints/eprints3.4/issues/575 Adds <code>XSLT::Identity</code> export to those restricted to staff by default]

==== General Improvements ====
* Updates metatags functionality to equivalent to [https://github.com/eprints/metatags/releases/tag/v1.4 v1.4] plus further improvements to ensure its export plugins are compliant with unit tests
* [https://github.com/eprints/eprints3.4/pull/515 Removes the progress bar even if the upload fails]
* [https://github.com/eprints/eprints3.4/commit/5fe2b24938ed19c38b0ffa6a5bc5d67253cfb514 Remove no longer required <code>progressid</code> from file uploads]
* [https://github.com/eprints/eprints3.4/pull/519 Adds support for number format months to BibTex import]
* [https://github.com/eprints/eprints3.4/pull/518 Makes the default encoding of imports 'UTF-8']
* [https://github.com/eprints/eprints3.4/pull/520 Adds labels connecting to radio buttons for <code>Boolean</code> and <code>Set</code>]
* [https://github.com/eprints/eprints3.4/commit/21687bd917244717674e613ce0d0e372fffcf619 Improves <code>Longtext_counter</code> <code>MetaField</code>]
* [https://github.com/eprints/eprints3.4/issues/530 Removes MPM event warning message]
* [https://github.com/eprints/eprints3.4/issues/527 Improves CRUD API fault tolerance]
* [https://github.com/eprints/eprints3.4/issues/536 Better specifies MetaField property defaults]
* [https://github.com/eprints/eprints3.4/issues/464 Removes <code>rename_subject_id</code> that will not work in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/537 Reviews and Removes legacy scripts that are no longer useful in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/540 Removes <code>cgi/cal</code> (as it should be in an ingredient and not in core) and moves <code>cgi/history_search</code> to not be publicly accessible]
* [https://github.com/eprints/eprints3.4/pull/542 Improves <code>cache_table</code> method to be compatible with UUIDs]
* [https://github.com/eprints/eprints3.4/pull/538 Use public link in "Request Copy" email when using pin security]
* [https://github.com/eprints/eprints3.4/issues/549 More reliable caching of auto.{js,css}]
* [https://github.com/eprints/eprints3.4/issues/563 Programmatically allows search export for restricted formats]
* [https://github.com/eprints/eprints3.4/issues/551 Support for indexing RTF files]
* [https://github.com/eprints/eprints3.4/issues/552 Improves determination of appropriate application for conversion of document to plaintext (for indexing?)]
* [https://github.com/eprints/eprints3.4/issues/566 Removes hard-coded defaults in bin/indexer]
* [https://github.com/eprints/eprints3.4/pull/569 Updates <code>cgi/opensearchdescription</code> to use <code>cgi/opensearch</code> rather than <code>cgi/search/simple</code>]
* [https://github.com/eprints/eprints3.4/commit/8cea29fb31e67dc92e1e1448c7935279977eb348 Allows opensearchdescription to list staff restricted export formats if Authorization header used]
* [https://github.com/eprints/eprints3.4/pull/573 Provides support for startIndex and size params in opensearch]
* [https://github.com/eprints/eprints3.4/pull/574 Allow export formats available to opensearch to be customised]

==== Bug Fixes ====
* [https://github.com/eprints/eprints3.4/pull/503 Fixes sample <code>EP_TRIGGER_BEGIN</code> and <code>EP_TRIGGER_END</code> subroutines]
* [https://github.com/eprints/eprints3.4/pull/521 Checks that <code>$id->{id_type}</code> is set before comparing it]
* [https://github.com/eprints/eprints3.4/issues/531 Fixes issues with <code>Convert::PlainText</code> handling large DOCX]
* [https://github.com/eprints/eprints3.4/commit/d1777a5a3170afed02f727b989cb8ebc009c3549 Makes unsupported packaging format a bad request (400) not server error (500)]
* [https://github.com/eprints/eprints3.4/pull/534 Don't add export link elements to deleted item page head]
* [https://github.com/eprints/eprints3.4/issues/535 Specifies more appropriate <code>empty_value</code>s for <code>Int</code> and <code>Float</code> MetaFields]
* [https://github.com/eprints/eprints3.4/issues/508 Fixes <code>eval</code> blocks calling user-defined <code>toform</code> or <code>fromform</code> functions to work as effective try/catch blocks]
* [https://github.com/eprints/eprints3.4/issues/467 Fixes <code>show_children</code> not working if subject tree based browse has multiple menu levels]
* [https://github.com/eprints/eprints3.4/issues/545 Fixes issues with broken field validation warning links]
* [https://github.com/eprints/eprints3.4/pull/543 Test that a cachemap is defined before trying to retrieve its uuid]
* [https://github.com/eprints/eprints3.4/pull/544 Check modified time of citation style file when using cached citations]
* [https://github.com/eprints/eprints3.4/issues/526 Fixes OAI 2.0 will sometimes misreporting the 'Earliest Datestamp']
* [https://github.com/eprints/eprints3.4/issues/546 Moves timezone adjustment inside an <code>eval</code> to avoid it dying if datetime is invalid]
* [https://github.com/eprints/eprints3.4/issues/547 Checks if config option get_custom_view_header_location is set before comparing]
* [https://github.com/eprints/eprints3.4/issues/539 Adds missing phrases for <code>AjaxSubject</code> field]
* [https://github.com/eprints/eprints3.4/issues/555 Fixes not be able to use <code>Workflow::Edit</code> to upload a file to an eprint]
* [https://github.com/eprints/eprints3.4/issues/565 Fixes lots of calls to <code>EPrints::Index::Daemon->is_running</code> when user is not logged in]
* [https://github.com/eprints/eprints3.4/issues/561 Fixes check for whether a user is "staff" (for export plugins) to <code>is_staff</code> function rather than something hard-coded]
* [https://github.com/eprints/eprints3.4/issues/506 Fixes CRUD requests creating empty records if values are invalid for the corresponding fields in the database (e.g. text for an integer field)]
* [https://github.com/eprints/eprints3.4/issues/571 Fixes error when running render_value directly on a Compound field]
* [https://github.com/eprints/eprints3.4/issues/572 Stops <code>EPrints::DataObj->new_from_data</code> tries to delete multiple compound sub-field values that don't exist]
* [https://github.com/eprints/eprints3.4/issues/583 Makes output of redo_thumbnails more helpful]
* [https://github.com/eprints/eprints3.4/issues/580 Fixes mistyping of <code>event_queue</code> (not <code>eventqueue</code> in the configuration for data objects excluded from citation caching]
* [https://github.com/eprints/eprints3.4/issues/586 Fixes subject fields showing undepositable options when used as a subfield]
* [https://github.com/eprints/eprints3.4/issues/585 Fixes <code>EPrints::Script::Compiled->run_contains</code> not returning proper boolean results]

== Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.4/milestone/9 3.4.8 milestone on GitHub] for more details.

[[Category:Eprints3.4]]
[[Category:Planned Releases]]

EPrints 3.4.8

2026-05-18T11:24:56Z

Drn@ecs.soton.ac.uk: /* Bug Fixes */

This page contains information about the provisional EPrints v3.4.8 tag and release on GitHub. A date for this release is yet to be scheduled.

== Release Notes (Provisional) ==
EPrints 3.4.8 is planned to be released in the Summer of 2026.
* '''Zero codename:''' ''TO BE DETERMINED''
* '''Publications flavour codename:''' ''TO BE DETERMINED''

=== New Dependencies ===
Check earlier dependencies for [[EPrints 3.4.7]] and before.

If you wish to set a timezone of the dates and times displayed on your repository, you will need to make sure the <code>DateTime</code> Perl module is installed. For RHEL-based Linux this can be installed with the <code>perl-DateTime</code> RPM. For Debian-based Linux this requires <code>libdatetime-perl</code>.

=== Changes Since 3.4.7 ===

==== New Functionality ====
* [https://github.com/eprints/eprints3.4/commit/be86f99b3662083a4f35034f14776d86bcc9e087 Adds <code>export_file_as_attachment</code> option to force exports to be downloaded]
* [https://github.com/eprints/eprints3.4/pull/513 Adds an export plugin for document URLs]
* [https://github.com/eprints/eprints3.4/pull/512 Adds clear buttons to multiple <code>Compound</code> fields]
* [https://github.com/eprints/eprints3.4/pull/525 Adds support for rendering time with a given timezone]
* [https://github.com/eprints/eprints3.4/issues/567 Provides EPC script for getting <code>icon_url</code> for a document]
* [https://github.com/eprints/eprints3.4/issues/568 Provides EPC script for getting the raw value of a property for a data object]
* [https://github.com/eprints/eprints3.4/issues/576 Adds delete option to epadmin]
* [https://github.com/eprints/eprints3.4/issues/579 Add "Clear abortive tasks" and "Retry abortive tasks" buttons for indexer]
* [https://github.com/eprints/eprints3.4/issues/584 Adds <code>ignore_edit_lock</code> field to <code>event_queue</code> data objects so certain tasks need not be delayed by the edit lock on a record]

==== Security and Privacy Improvements ====
* [https://github.com/eprints/eprints3.4/pull/511 Prevents 'javascript:' URLs from being saved in URL fields]
* [https://github.com/eprints/eprints3.4/commit/c5884562ed72b31681d3f0308b5987b2564052ad Modifies fix for SetLang referrer misuse]
* [https://github.com/eprints/eprints3.4/issues/575 Adds <code>XSLT::Identity</code> export to those restricted to staff by default]

==== General Improvements ====
* Updates metatags functionality to equivalent to [https://github.com/eprints/metatags/releases/tag/v1.4 v1.4] plus further improvements to ensure its export plugins are compliant with unit tests
* [https://github.com/eprints/eprints3.4/pull/515 Removes the progress bar even if the upload fails]
* [https://github.com/eprints/eprints3.4/commit/5fe2b24938ed19c38b0ffa6a5bc5d67253cfb514 Remove no longer required <code>progressid</code> from file uploads]
* [https://github.com/eprints/eprints3.4/pull/519 Adds support for number format months to BibTex import]
* [https://github.com/eprints/eprints3.4/pull/518 Makes the default encoding of imports 'UTF-8']
* [https://github.com/eprints/eprints3.4/pull/520 Adds labels connecting to radio buttons for <code>Boolean</code> and <code>Set</code>]
* [https://github.com/eprints/eprints3.4/commit/21687bd917244717674e613ce0d0e372fffcf619 Improves <code>Longtext_counter</code> <code>MetaField</code>]
* [https://github.com/eprints/eprints3.4/issues/530 Removes MPM event warning message]
* [https://github.com/eprints/eprints3.4/issues/527 Improves CRUD API fault tolerance]
* [https://github.com/eprints/eprints3.4/issues/536 Better specifies MetaField property defaults]
* [https://github.com/eprints/eprints3.4/issues/464 Removes <code>rename_subject_id</code> that will not work in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/537 Reviews and Removes legacy scripts that are no longer useful in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/540 Removes <code>cgi/cal</code> (as it should be in an ingredient and not in core) and moves <code>cgi/history_search</code> to not be publicly accessible]
* [https://github.com/eprints/eprints3.4/pull/542 Improves <code>cache_table</code> method to be compatible with UUIDs]
* [https://github.com/eprints/eprints3.4/pull/538 Use public link in "Request Copy" email when using pin security]
* [https://github.com/eprints/eprints3.4/issues/549 More reliable caching of auto.{js,css}]
* [https://github.com/eprints/eprints3.4/issues/563 Programmatically allows search export for restricted formats]
* [https://github.com/eprints/eprints3.4/issues/551 Support for indexing RTF files]
* [https://github.com/eprints/eprints3.4/issues/552 Improves determination of appropriate application for conversion of document to plaintext (for indexing?)]
* [https://github.com/eprints/eprints3.4/issues/566 Removes hard-coded defaults in bin/indexer]
* [https://github.com/eprints/eprints3.4/pull/569 Updates <code>cgi/opensearchdescription</code> to use <code>cgi/opensearch</code> rather than <code>cgi/search/simple</code>
* [https://github.com/eprints/eprints3.4/commit/8cea29fb31e67dc92e1e1448c7935279977eb348 Allows opensearchdescription to list staff restricted export formats if Authorization header used]
* [https://github.com/eprints/eprints3.4/pull/573 Provides support for startIndex and size params in opensearch]
* [https://github.com/eprints/eprints3.4/pull/574 Allow export formats available to opensearch to be customised]

==== Bug Fixes ====
* [https://github.com/eprints/eprints3.4/pull/503 Fixes sample <code>EP_TRIGGER_BEGIN</code> and <code>EP_TRIGGER_END</code> subroutines]
* [https://github.com/eprints/eprints3.4/pull/521 Checks that <code>$id->{id_type}</code> is set before comparing it]
* [https://github.com/eprints/eprints3.4/issues/531 Fixes issues with <code>Convert::PlainText</code> handling large DOCX]
* [https://github.com/eprints/eprints3.4/commit/d1777a5a3170afed02f727b989cb8ebc009c3549 Makes unsupported packaging format a bad request (400) not server error (500)]
* [https://github.com/eprints/eprints3.4/pull/534 Don't add export link elements to deleted item page head]
* [https://github.com/eprints/eprints3.4/issues/535 Specifies more appropriate <code>empty_value</code>s for <code>Int</code> and <code>Float</code> MetaFields]
* [https://github.com/eprints/eprints3.4/issues/508 Fixes <code>eval</code> blocks calling user-defined <code>toform</code> or <code>fromform</code> functions to work as effective try/catch blocks]
* [https://github.com/eprints/eprints3.4/issues/467 Fixes <code>show_children</code> not working if subject tree based browse has multiple menu levels]
* [https://github.com/eprints/eprints3.4/issues/545 Fixes issues with broken field validation warning links]
* [https://github.com/eprints/eprints3.4/pull/543 Test that a cachemap is defined before trying to retrieve its uuid]
* [https://github.com/eprints/eprints3.4/pull/544 Check modified time of citation style file when using cached citations]
* [https://github.com/eprints/eprints3.4/issues/526 Fixes OAI 2.0 will sometimes misreporting the 'Earliest Datestamp']
* [https://github.com/eprints/eprints3.4/issues/546 Moves timezone adjustment inside an <code>eval</code> to avoid it dying if datetime is invalid]
* [https://github.com/eprints/eprints3.4/issues/547 Checks if config option get_custom_view_header_location is set before comparing]
* [https://github.com/eprints/eprints3.4/issues/539 Adds missing phrases for <code>AjaxSubject</code> field]
* [https://github.com/eprints/eprints3.4/issues/555 Fixes not be able to use <code>Workflow::Edit</code> to upload a file to an eprint]
* [https://github.com/eprints/eprints3.4/issues/565 Fixes lots of calls to <code>EPrints::Index::Daemon->is_running</code> when user is not logged in]
* [https://github.com/eprints/eprints3.4/issues/561 Fixes check for whether a user is "staff" (for export plugins) to <code>is_staff</code> function rather than something hard-coded]
* [https://github.com/eprints/eprints3.4/issues/506 Fixes CRUD requests creating empty records if values are invalid for the corresponding fields in the database (e.g. text for an integer field)]
* [https://github.com/eprints/eprints3.4/issues/571 Fixes error when running render_value directly on a Compound field]
* [https://github.com/eprints/eprints3.4/issues/572 Stops <code>EPrints::DataObj->new_from_data</code> tries to delete multiple compound sub-field values that don't exist]
* [https://github.com/eprints/eprints3.4/issues/583 Makes output of redo_thumbnails more helpful]
* [https://github.com/eprints/eprints3.4/issues/580 Fixes mistyping of <code>event_queue</code> (not <code>eventqueue</code> in the configuration for data objects excluded from citation caching]
* [https://github.com/eprints/eprints3.4/issues/586 Fixes subject fields showing undepositable options when used as a subfield]
* [https://github.com/eprints/eprints3.4/issues/585 Fixes <code>EPrints::Script::Compiled->run_contains</code> not returning proper boolean results]

== Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.4/milestone/9 3.4.8 milestone on GitHub] for more details.

[[Category:Eprints3.4]]
[[Category:Planned Releases]]

EPrints 3.4.8

2026-05-18T11:24:38Z

Drn@ecs.soton.ac.uk: Added changes up to 14th May 2026

This page contains information about the provisional EPrints v3.4.8 tag and release on GitHub. A date for this release is yet to be scheduled.

== Release Notes (Provisional) ==
EPrints 3.4.8 is planned to be released in the Summer of 2026.
* '''Zero codename:''' ''TO BE DETERMINED''
* '''Publications flavour codename:''' ''TO BE DETERMINED''

=== New Dependencies ===
Check earlier dependencies for [[EPrints 3.4.7]] and before.

If you wish to set a timezone of the dates and times displayed on your repository, you will need to make sure the <code>DateTime</code> Perl module is installed. For RHEL-based Linux this can be installed with the <code>perl-DateTime</code> RPM. For Debian-based Linux this requires <code>libdatetime-perl</code>.

=== Changes Since 3.4.7 ===

==== New Functionality ====
* [https://github.com/eprints/eprints3.4/commit/be86f99b3662083a4f35034f14776d86bcc9e087 Adds <code>export_file_as_attachment</code> option to force exports to be downloaded]
* [https://github.com/eprints/eprints3.4/pull/513 Adds an export plugin for document URLs]
* [https://github.com/eprints/eprints3.4/pull/512 Adds clear buttons to multiple <code>Compound</code> fields]
* [https://github.com/eprints/eprints3.4/pull/525 Adds support for rendering time with a given timezone]
* [https://github.com/eprints/eprints3.4/issues/567 Provides EPC script for getting <code>icon_url</code> for a document]
* [https://github.com/eprints/eprints3.4/issues/568 Provides EPC script for getting the raw value of a property for a data object]
* [https://github.com/eprints/eprints3.4/issues/576 Adds delete option to epadmin]
* [https://github.com/eprints/eprints3.4/issues/579 Add "Clear abortive tasks" and "Retry abortive tasks" buttons for indexer]
* [https://github.com/eprints/eprints3.4/issues/584 Adds <code>ignore_edit_lock</code> field to <code>event_queue</code> data objects so certain tasks need not be delayed by the edit lock on a record]

==== Security and Privacy Improvements ====
* [https://github.com/eprints/eprints3.4/pull/511 Prevents 'javascript:' URLs from being saved in URL fields]
* [https://github.com/eprints/eprints3.4/commit/c5884562ed72b31681d3f0308b5987b2564052ad Modifies fix for SetLang referrer misuse]
* [https://github.com/eprints/eprints3.4/issues/575 Adds <code>XSLT::Identity</code> export to those restricted to staff by default]

==== General Improvements ====
* Updates metatags functionality to equivalent to [https://github.com/eprints/metatags/releases/tag/v1.4 v1.4] plus further improvements to ensure its export plugins are compliant with unit tests
* [https://github.com/eprints/eprints3.4/pull/515 Removes the progress bar even if the upload fails]
* [https://github.com/eprints/eprints3.4/commit/5fe2b24938ed19c38b0ffa6a5bc5d67253cfb514 Remove no longer required <code>progressid</code> from file uploads]
* [https://github.com/eprints/eprints3.4/pull/519 Adds support for number format months to BibTex import]
* [https://github.com/eprints/eprints3.4/pull/518 Makes the default encoding of imports 'UTF-8']
* [https://github.com/eprints/eprints3.4/pull/520 Adds labels connecting to radio buttons for <code>Boolean</code> and <code>Set</code>]
* [https://github.com/eprints/eprints3.4/commit/21687bd917244717674e613ce0d0e372fffcf619 Improves <code>Longtext_counter</code> <code>MetaField</code>]
* [https://github.com/eprints/eprints3.4/issues/530 Removes MPM event warning message]
* [https://github.com/eprints/eprints3.4/issues/527 Improves CRUD API fault tolerance]
* [https://github.com/eprints/eprints3.4/issues/536 Better specifies MetaField property defaults]
* [https://github.com/eprints/eprints3.4/issues/464 Removes <code>rename_subject_id</code> that will not work in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/537 Reviews and Removes legacy scripts that are no longer useful in EPrints 3.4+]
* [https://github.com/eprints/eprints3.4/issues/540 Removes <code>cgi/cal</code> (as it should be in an ingredient and not in core) and moves <code>cgi/history_search</code> to not be publicly accessible]
* [https://github.com/eprints/eprints3.4/pull/542 Improves <code>cache_table</code> method to be compatible with UUIDs]
* [https://github.com/eprints/eprints3.4/pull/538 Use public link in "Request Copy" email when using pin security]
* [https://github.com/eprints/eprints3.4/issues/549 More reliable caching of auto.{js,css}]
* [https://github.com/eprints/eprints3.4/issues/563 Programmatically allows search export for restricted formats]
* [https://github.com/eprints/eprints3.4/issues/551 Support for indexing RTF files]
* [https://github.com/eprints/eprints3.4/issues/552 Improves determination of appropriate application for conversion of document to plaintext (for indexing?)]
* [https://github.com/eprints/eprints3.4/issues/566 Removes hard-coded defaults in bin/indexer]
* [https://github.com/eprints/eprints3.4/pull/569 Updates <code>cgi/opensearchdescription</code> to use <code>cgi/opensearch</code> rather than <code>cgi/search/simple</code>
* [https://github.com/eprints/eprints3.4/commit/8cea29fb31e67dc92e1e1448c7935279977eb348 Allows opensearchdescription to list staff restricted export formats if Authorization header used]
* [https://github.com/eprints/eprints3.4/pull/573 Provides support for startIndex and size params in opensearch]
* [https://github.com/eprints/eprints3.4/pull/574 Allow export formats available to opensearch to be customised]

==== Bug Fixes ====
* [https://github.com/eprints/eprints3.4/pull/503 Fixes sample <code>EP_TRIGGER_BEGIN</code> and <code>EP_TRIGGER_END</code> subroutines]
* [https://github.com/eprints/eprints3.4/pull/521 Checks that <code>$id->{id_type}</code> is set before comparing it]
* [https://github.com/eprints/eprints3.4/issues/531 Fixes issues with <code>Convert::PlainText</code> handling large DOCX]
* [https://github.com/eprints/eprints3.4/commit/d1777a5a3170afed02f727b989cb8ebc009c3549 Makes unsupported packaging format a bad request (400) not server error (500)]
* [https://github.com/eprints/eprints3.4/pull/534 Don't add export link elements to deleted item page head]
* [https://github.com/eprints/eprints3.4/issues/535 Specifies more appropriate <code>empty_value</code>s for <code>Int</code> and <code>Float</code> MetaFields]
* [https://github.com/eprints/eprints3.4/issues/508 Fixes <code>eval</code> blocks calling user-defined <code>toform</code> or <code>fromform</code> functions to work as effective try/catch blocks]
* [https://github.com/eprints/eprints3.4/issues/467 Fixes <code>show_children</code> not working if subject tree based browse has multiple menu levels]
* [https://github.com/eprints/eprints3.4/issues/545 Fixes issues with broken field validation warning links]
* [https://github.com/eprints/eprints3.4/pull/543 Test that a cachemap is defined before trying to retrieve its uuid]
* [https://github.com/eprints/eprints3.4/pull/544 Check modified time of citation style file when using cached citations]
* [https://github.com/eprints/eprints3.4/issues/526 Fixes OAI 2.0 will sometimes misreporting the 'Earliest Datestamp']
* [https://github.com/eprints/eprints3.4/issues/546 Moves timezone adjustment inside an <code>eval</code> to avoid it dying if datetime is invalid]
* [https://github.com/eprints/eprints3.4/issues/547 Checks if config option get_custom_view_header_location is set before comparing]
* [https://github.com/eprints/eprints3.4/issues/539 Adds missing phrases for <code>AjaxSubject</code> field]
* [https://github.com/eprints/eprints3.4/issues/555 Fixes not be able to use <code>Workflow::Edit</code> to upload a file to an eprint]
* [https://github.com/eprints/eprints3.4/issues/565 Fixes lots of calls to <code>EPrints::Index::Daemon->is_running</code> when user is not logged in]
* [https://github.com/eprints/eprints3.4/issues/561 Fixes check for whether a user is "staff" (for export plugins) to <code>is_staff</code> function rather than something hard-coded]
* [https://github.com/eprints/eprints3.4/issues/506 Fixes CRUD requests creating empty records if values are invalid for the corresponding fields in the database (e.g. text for an integer field)]
* [https://github.com/eprints/eprints3.4/issues/571 Fixes error when running render_value directly on a Compound field]
* [https://github.com/eprints/eprints3.4/issues/572 Stops <code>EPrints::DataObj->new_from_data</code> tries to delete multiple compound sub-field values that don't exist]
* [https://github.com/eprints/eprints3.4/issues/583 Makes output of redo_thumbnails more helpful]
* [https://github.com/eprints/eprints3.4/issues/580 Fixes mistyping of <code>event_queue</code) (not <code>eventqueue</code> in the configuration for data objects excluded from citation caching]
* [https://github.com/eprints/eprints3.4/issues/586 Fixes subject fields showing undepositable options when used as a subfield]
* [https://github.com/eprints/eprints3.4/issues/585 Fixes <code>EPrints::Script::Compiled->run_contains</code> not returning proper boolean results]

== Planned Features and Improvements ==
See [https://github.com/eprints/eprints3.4/milestone/9 3.4.8 milestone on GitHub] for more details.

[[Category:Eprints3.4]]
[[Category:Planned Releases]]

EPrints 3.4.8

2026-05-18T10:27:21Z

Drn@ecs.soton.ac.uk: /* Bug Fixes */

Issues with Installing EPrints on Ubuntu 26.04

2026-05-13T11:06:35Z

Drn@ecs.soton.ac.uk: Updated info as of 13th May 2026

As of 13th May 2026, Ubuntu 26.04 is still under testing to determine if EPrints can be successfully installed and if so if there are any issues with doing this, which require a different approach from the general approach for installing EPrints on Debian/Ubuntu Linux.

==== Current Issues ====
; XML library compatability problems : This will first occur at the point where you complete the credentials you want to use for your archive's database whilst you are running <code>bin/epadmin create pub</code>. It will exhibit itself as either a segmentation fault or an error with the memory allocation (malloc) or free commands. This is due to EPrints use of the <code>XML:LibXML</code> Perl library that ultimately uses the C library <tt>libxml2</tt>. [https://github.com/eprints/eprints3.4/issues/509 This GitHub issue] first raised for what appears to be the same issue with FreeBSD 14.3 provides some more detail about this problem. It is likely this relates to [https://github.com/cpan-authors/XML-LibXML/issues/81 this XML::LibXML GitHub issue], which says it has been resolved upstream, which we believe to mean in the libxml2 C library (possibly version 2.15.3). Ubuntu 26.04 as of 13th May 2026 is still providing libxml2 version 2.15.2, so there will hopefully be an update soon.

EPScript/Examples

2026-05-12T16:05:23Z

Drn@ecs.soton.ac.uk: /* Testing a boolean field */ Added advice for unset boolean fields

{{formats}}

{{EPScript}}

= Examples =

== Pluralising the editors of a book ==
<source lang="xml">
<if test="type = 'book' and is_set(editors)">
<print expr="editors" />, (ed<if test="length(editors) gt 1">s</if>
</if>
</source>

== Rendering the URL of an EPrint ==
<source lang="xml">
<print expr="$config{base_url}" />/<print expr="eprintid" />/
</source>

== Testing a boolean field ==
Boolean fields can be <tt>TRUE</tt>, <tt>FALSE</tt> or an empty string, the last of which means neither the true or false option has been selected. Just doing a <code>test="boolean_field"</code> isn't enough. Use this:
<source lang="xml">
<if test="boolean_field = 'TRUE'">
...
</if>
</source>
If you want to test if neither a true or false option has been selected, you will need to use:
<source lang="xml">
<if test="boolean_field = ''">
...
</if>
</source>