<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://wiki.eprints.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jy2e08%40ecs.soton.ac.uk</id>
	<title>EPrints Documentation - User contributions [en-gb]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.eprints.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jy2e08%40ecs.soton.ac.uk"/>
	<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/Special:Contributions/Jy2e08@ecs.soton.ac.uk"/>
	<updated>2026-09-22T17:49:50Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.8</generator>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12777</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12777"/>
		<updated>2018-05-08T12:23:23Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 (and newer version of EPrints 3.3) to EPrints 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assume Centos 7 OS and run as the eprints user, unless it stated to run as the root user.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12776</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12776"/>
		<updated>2018-05-04T10:59:16Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Process */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 (and newer version of EPrints 3.3) to EPrints 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS and run as the eprints user, unless it stated to run as the root user.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12775</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12775"/>
		<updated>2018-05-04T10:58:18Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 (and newer version of EPrints 3.3) to EPrints 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS and run as the eprints user, unless it stated to run as the root user.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12774</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12774"/>
		<updated>2018-05-03T13:03:16Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Process */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS and run as the eprints user, unless it stated to run as root user.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12773</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12773"/>
		<updated>2018-05-03T13:01:52Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Upgrade from Tarball */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS and run as the eprints user, unless it stated to run as root user.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
as root:&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12772</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12772"/>
		<updated>2018-05-03T13:00:41Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS and run as the eprints user, unless it stated to run as root user.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12771</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12771"/>
		<updated>2018-05-03T12:59:57Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Process */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/ Files.eprints.org]&lt;br /&gt;
as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
as root:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12770</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12770"/>
		<updated>2018-05-03T12:58:44Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Pre-upgrade */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 as root:&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs.&lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12769</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12769"/>
		<updated>2018-05-03T12:58:20Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) file and installed in /opt/eprints3. The commands in these instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12768</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12768"/>
		<updated>2018-05-03T12:57:35Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12+ to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12+ was installed using a tarball (tar.gz) in /opt/eprints3. These instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12+ installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12766</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12766"/>
		<updated>2018-05-03T12:53:54Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Jy2e08@ecs.soton.ac.uk moved page Upgrading 3.3.12 to 3.4 to Upgrading 3.3.12+ to 3.4&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12 was installed using a tarball (tar.gz) in /opt/eprints3. These instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12 installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12_to_3.4&amp;diff=12767</id>
		<title>Upgrading 3.3.12 to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12_to_3.4&amp;diff=12767"/>
		<updated>2018-05-03T12:53:54Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Jy2e08@ecs.soton.ac.uk moved page Upgrading 3.3.12 to 3.4 to Upgrading 3.3.12+ to 3.4&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Upgrading 3.3.12+ to 3.4]]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12765</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12765"/>
		<updated>2018-05-03T12:52:22Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12 was installed using a tarball (tar.gz) in /opt/eprints3. These instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
=Upgrade from Tarball=&lt;br /&gt;
&lt;br /&gt;
==Pre-upgrade==&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
==Process==&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12 installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12764</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12764"/>
		<updated>2018-05-03T12:51:42Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12 was installed using a tarball (tar.gz) in /opt/eprints3. These instructions assumes Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
====Upgrade from Tarball====&lt;br /&gt;
&lt;br /&gt;
=====Pre-upgrade=====&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
=====Process=====&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12 installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12763</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12763"/>
		<updated>2018-05-03T12:51:16Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions help you upgrade EPrints 3.3.12 to 3.4 while keeping all your eprints, documents and local configuration changes.&lt;br /&gt;
&lt;br /&gt;
It assumes your EPrints 3.3.12 was installed using a tarball (tar.gz) in /opt/eprints3. These instructions assumes running on the Centos 7 OS.&lt;br /&gt;
&lt;br /&gt;
====Upgrade from Tarball====&lt;br /&gt;
&lt;br /&gt;
=====Pre-upgrade=====&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
=====Process=====&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12 installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12762</id>
		<title>Upgrading 3.3.12+ to 3.4</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_3.3.12%2B_to_3.4&amp;diff=12762"/>
		<updated>2018-05-03T12:46:17Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Created page with &amp;quot;These instructions assume your EPrints 3.3.12 was installed in /opt/eprints3 and it was previously installed using a tarball.  EPrints 3.4 tarball is used in these instruction...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These instructions assume your EPrints 3.3.12 was installed in /opt/eprints3 and it was previously installed using a tarball. &lt;br /&gt;
EPrints 3.4 tarball is used in these instructions, A RPM or Deb package should also work. These instructions assumes Centos 7 OS. &lt;br /&gt;
Ubuntu 16 and plus removed some packages and left EPrints with unmet dependencies. More info here: [https://wiki.eprints.org/w/Installing_EPrints_on_Debian/Ubuntu#For_Ubuntu_16.04_and_Debian_8 Ubuntu_16.04 and Debian 8]&lt;br /&gt;
&lt;br /&gt;
====Upgrade from Tarball====&lt;br /&gt;
&lt;br /&gt;
=====Pre-upgrade=====&lt;br /&gt;
* If you have local modifications to the core files (in /opt/eprints3/perl_lib), you may need to manually migrate your changes.&lt;br /&gt;
* If you use Twitter integration, as root use CPAN to install LWP::Authen::OAuth as this is no longer in perl_lib.&lt;br /&gt;
 cpan LWP::Authen::OAuth&lt;br /&gt;
* Note down the enabled bazaar package on your repository.&lt;br /&gt;
* Make a backup of your local configs. &lt;br /&gt;
&lt;br /&gt;
=====Process=====&lt;br /&gt;
&lt;br /&gt;
We will move your existing eprints 3.3.12 installation from /opt/eprints3/ to /opt/eprints3.3, install eprints 3.4, then migrate your configurations into EPrints 3.4. &lt;br /&gt;
 as root:&lt;br /&gt;
 apachectl stop&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3 eprints3.3&lt;br /&gt;
&lt;br /&gt;
* Download EPrints 3.4 core and publication flavour tarball and install them [http://files.eprints.org/]&lt;br /&gt;
 as root:&lt;br /&gt;
 cd /root&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1.tar.gz&lt;br /&gt;
 tar xvzf eprints-3.4.0-rc1-flavours.tar.gz&lt;br /&gt;
 cd eprints-3.4.0&lt;br /&gt;
 ./configure&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
* Move your current repository from 3.3 to 3.4&lt;br /&gt;
 as root user:&lt;br /&gt;
 cd /opt&lt;br /&gt;
 mv eprints3.3/archives/ARCHIVENAME eprints3/archives/&lt;br /&gt;
 After moving, make sure all files inside /opt/eprints3 are still owned by eprints user and belongs to eprints group.&lt;br /&gt;
&lt;br /&gt;
* In /opt/eprints3/archives/ARCHIVENAME/, create cfg/cfg.d/00_flavour.pl and set the appropriate flavour, typically 'pub':&lt;br /&gt;
 $c-&amp;gt;{flavour} = 'pub';&lt;br /&gt;
&lt;br /&gt;
* create a symbolic link to default.xml &lt;br /&gt;
 cd /opt/eprints3/archives/ARCHIVENAME/cfg/templates/ (or /opt/eprints3/archives/ARCHIVENAME/cfg/lang/en/templates/&lt;br /&gt;
 ln -s default.xml default_internal.xml&lt;br /&gt;
&lt;br /&gt;
* Audit each of their local config files against the pub_lib flavours config files.  The first Diff below will identify all the files that are the same.  If so delete the ones in archives/ARCHIVENAME/cfg/cfg.d/.  There is a good chance you will not find any.  The second diff will find where files exists in both directory are different.  Here they should be compared to see if the local differences are superficial (e.g. slightly different comments or spacing) and therefore can be removed.  Also the pub_lib flavour version may fix an outstanding bug or perform the required functionality more succinctly.  If this is the only change then the local archive version can be deleted otherwise the change should be incorporated in the local version.&lt;br /&gt;
 cd /opt/eprints3/&lt;br /&gt;
 diff -rs archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ are identical$'&lt;br /&gt;
 diff -rq archives/ARCHIVENAME/cfg/cfg.d flavours/pub_lib/cfg.d | egrep '^Files .+ and .+ differ$'&lt;br /&gt;
&lt;br /&gt;
* Compare archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl with flavours/pub_lib/cfg/cfg.d/eprint_fields_pub.pl, &lt;br /&gt;
** If these are different and fields are present in eprint_fields_pub.pl and not eprint_fields.pl or the definitions (e.g. type, options, etc.)  for the same field are different then:&lt;br /&gt;
**# Copy flavours/pub_lib/cfg.d/eprint_fields_pub.pl to their archive's cfg/cfg.d/&lt;br /&gt;
**# Modify the fields in their archive's cfg/cfg.d/eprint_fields_pub.pl where they have different definitions (e.g. type, options, etc.) to those in eprint_fields.pl&lt;br /&gt;
**# Remove all fields in their archive's cfg/cfg.d/eprint_fields.pl where they also occur in their archive's cfg/cfg.d/eprint_fields_pub.pl&lt;br /&gt;
** If there are only additional fields in archives/ARCHIVENAME/cfg/cfg.d/eprint_fields.pl then just do the last step.&lt;br /&gt;
** If the two files are identical then you need to nothing.  However, this is extremly unlikely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As the eprints user, run epadmin update to add any new fields that were not previously present (typically this is embargo_reason for documents and requester_email for request)&lt;br /&gt;
 /opt/eprints3/bin/epadmin update ARCHIVENAME&lt;br /&gt;
&lt;br /&gt;
* Generate Apache configuration and as root test (fixing any issues) and restart Apache.&lt;br /&gt;
 /opt/eprints3/bin/generate_apacheconf --system --replace&lt;br /&gt;
 apachectl configtest&lt;br /&gt;
 apachectl restart&lt;br /&gt;
&lt;br /&gt;
* Once confirming that EPrints is generally working.  Go to Admin-&amp;gt; Bazaar then install the required bazaar packages. Ensure the following bazaar files are disabled by renaming to FILENAME.pl.disabled.  Once they have been reinstalled via the Bazaar then they can be moved back into place:&lt;br /&gt;
 mv z_orcid_support.pl z_orcid_support.pl.disabled&lt;br /&gt;
 mv zz_hefce_oa_fields.pl zz_hefce_oa_fields.pl.disabled&lt;br /&gt;
 mv zz_rioxx2.pl zz_rioxx2.pl.disabled&lt;br /&gt;
 mv z_meprints.pl z_meprints.pl.disabled &lt;br /&gt;
&lt;br /&gt;
* Finally, run generate statics to make sure all pages are regenerates with any changes to configuration.&lt;br /&gt;
  /opt/eprints3/bin/generate_static ARCHIVE_NAME&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* 3.4 does not automatically update an archive's html/en/ files. If there are any bugs with broken Javascript or unexpected CSS, try deleting the archives html/en/javascript/auto.js or html/en/style/auto.css.  Similarly if a static page cannot be changed try deleting it under the archive's html/en/ or running generate_static.&lt;br /&gt;
* If some perl modules are giving out error message like: &lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Event::PIRUS&amp;quot; at /opt/eprints3/bin/../perl_lib/EPrints/PluginFactory.pm line 276.&lt;br /&gt;
  Can't locate object method &amp;quot;new&amp;quot; via package &amp;quot;EPrints::Plugin::Screen::EPrint::Box::Tools::SUPER&amp;quot; at /opt/eprints3/site_lib/plugins/EPrints/Plugin/Screen/EPrint/Box/Tools.pm line 12.&lt;br /&gt;
It is because their parent module has not been initialised. This happens when the parent module lives in perl_lib, and the problem module live in elsewhere  e.g. parent module of PIRUS(Event.pm) is in perl_lib, while the PIRUS.pm is in pub_lib. &lt;br /&gt;
Just need to &amp;quot;use&amp;quot; the parent module before the ISA line:&lt;br /&gt;
 use EPrints::Plugin::Event;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Files/EPrints_3.4_Release_Candidate_1&amp;diff=12732</id>
		<title>Files/EPrints 3.4 Release Candidate 1</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Files/EPrints_3.4_Release_Candidate_1&amp;diff=12732"/>
		<updated>2018-03-29T16:06:11Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Created page with &amp;quot;Please see http://www.eprints.org/eprints-3.4&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please see http://www.eprints.org/eprints-3.4&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Shibboleth&amp;diff=12704</id>
		<title>Shibboleth</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Shibboleth&amp;diff=12704"/>
		<updated>2018-02-08T12:32:53Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This page details how to install and integrate Shibboleth with EPrints 3.3 on a CentOS 7 operating system.'''  The process should be fairly similar for other modern RedHat-based Linux distributions such as RHEL 7 and Fedora 21/22.  However, it will somewhat different for Debian-based Linux, such as Ubuntu and Debian itself and other Linux distributions.  Typically, this will just be different package names and different commands to manage applications.&lt;br /&gt;
&lt;br /&gt;
Generally, it is a good idea to run EPrints with '''HTTPS''' when using Shibboleth authentication for increased security on the attributes being sent back by the Shibboleth Identity Provider (IdP).  Therefore, it is assumed that EPrints has already been set up to use HTTPS and there already exists an '''ssl/securevhost.conf''' under the archive directory structure.&lt;br /&gt;
&lt;br /&gt;
== Installing Shibboleth ==&lt;br /&gt;
* First, add the Shibboleth repository to your list of Yum repositories:&lt;br /&gt;
  root&amp;gt; cd /etc/yum.repos.d/&lt;br /&gt;
  root&amp;gt; wget http://download.opensuse.org/repositories/security:shibboleth/CentOS_7/security:shibboleth.repo&lt;br /&gt;
&lt;br /&gt;
* Now you can use Yum to install all package dependencies:&lt;br /&gt;
  root&amp;gt; yum install log4shib opensaml shibboleth unixODBC xerces-c xml-security-c xmltooling &lt;br /&gt;
&lt;br /&gt;
* You may be prompted to accept the importing of the key for the Shibboleth repository, for which you should type '''y''' and press enter.&lt;br /&gt;
&lt;br /&gt;
* Once you have done that, test that '''shibd''' has no issues:&lt;br /&gt;
  root&amp;gt; LD_LIBRARY_PATH=/opt/shibboleth/lib64 shibd -t&lt;br /&gt;
&lt;br /&gt;
* ''shibd -t'' should return a couple of warning, like those listed below.  These are due to it not yet being configured.&lt;br /&gt;
  2015-05-11 10:39:01 WARN Shibboleth.Application : insecure cookieProps setting, set to &amp;quot;https&amp;quot; for SSL/TLS-only usage&lt;br /&gt;
  2015-05-11 10:39:01 WARN Shibboleth.Application : handlerSSL should be enabled for SSL/TLS-enabled web sites&lt;br /&gt;
  2015-05-11 10:39:01 WARN Shibboleth.Application : no MetadataProvider available, configure at least one for standard SSO usage&lt;br /&gt;
  overall configuration is loadable, check console for non-fatal problems&lt;br /&gt;
&lt;br /&gt;
* If there are no other warning or error messages from ''shibd -t'', you can start it properly and check to make sure it is running. You may also want ensure Shibboleth starts at boot using '''systemctl  enable'''&lt;br /&gt;
  root&amp;gt; systemctl start shibd.service&lt;br /&gt;
  root&amp;gt; ps aux | grep shib&lt;br /&gt;
  shibd    29338  0.4  0.7 419784 15024 ?        Ssl  11:16   0:00 /usr/sbin/shibd -p /var/run/shibboleth/shibd.pid -f -w 30&lt;br /&gt;
  root     29345  0.0  0.0 112640   940 pts/2    S+   11:17   0:00 grep --color=auto -i shib&lt;br /&gt;
  root&amp;gt; systemctl enable shibd.service&lt;br /&gt;
&lt;br /&gt;
== Configuring Shibboleth ==&lt;br /&gt;
* Replace '''/etc/shibboleth/shibboleth2.xml''' with the following.  Substitute '''foo.eprints.org''' for the hostname of your EPrints repository, '''https://shib.foo.example.org/idp/shibboleth''' with the entity ID for you Shibboleth IdP and '''foo''' in the pathname of files with the name or your repository (e.g. ''foo/attribute-map.xml'' becomes ''myrepo/attribute-map.xml'').&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;SPConfig xmlns=&amp;quot;urn:mace:shibboleth:2.0:native:sp:config&amp;quot;&lt;br /&gt;
    xmlns:conf=&amp;quot;urn:mace:shibboleth:2.0:native:sp:config&amp;quot;&lt;br /&gt;
    xmlns:saml=&amp;quot;urn:oasis:names:tc:SAML:2.0:assertion&amp;quot;&lt;br /&gt;
    xmlns:samlp=&amp;quot;urn:oasis:names:tc:SAML:2.0:protocol&amp;quot;    &lt;br /&gt;
    xmlns:md=&amp;quot;urn:oasis:names:tc:SAML:2.0:metadata&amp;quot;&lt;br /&gt;
    clockSkew=&amp;quot;180&amp;quot;&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
    &amp;lt;ApplicationDefaults entityID=&amp;quot;https://foo.eprints.org/shibboleth&amp;quot;&lt;br /&gt;
                         REMOTE_USER=&amp;quot;eppn persistent-id targeted-id&amp;quot;&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
      &amp;lt;Sessions lifetime=&amp;quot;28800&amp;quot; timeout=&amp;quot;3600&amp;quot; relayState=&amp;quot;ss:mem&amp;quot;&lt;br /&gt;
                  checkAddress=&amp;quot;false&amp;quot; handlerSSL=&amp;quot;true&amp;quot; cookieProps=&amp;quot;https&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;lt;SSO entityID=&amp;quot;https://shib.foo.example.org/idp/shibboleth&amp;quot;&amp;gt;&lt;br /&gt;
              SAML2 SAML1&lt;br /&gt;
        &amp;lt;/SSO&amp;gt;&lt;br /&gt;
        &amp;lt;Logout&amp;gt;SAML2 Local&amp;lt;/Logout&amp;gt;&lt;br /&gt;
        &amp;lt;Handler type=&amp;quot;MetadataGenerator&amp;quot; Location=&amp;quot;/Metadata&amp;quot; signing=&amp;quot;false&amp;quot;/&amp;gt;&lt;br /&gt;
        &amp;lt;Handler type=&amp;quot;Status&amp;quot; Location=&amp;quot;/Status&amp;quot; acl=&amp;quot;127.0.0.1 ::1&amp;quot;/&amp;gt;&lt;br /&gt;
        &amp;lt;Handler type=&amp;quot;Session&amp;quot; Location=&amp;quot;/Session&amp;quot; showAttributeValues=&amp;quot;false&amp;quot;/&amp;gt;&lt;br /&gt;
        &amp;lt;Handler type=&amp;quot;DiscoveryFeed&amp;quot; Location=&amp;quot;/DiscoFeed&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;/Sessions&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
      &amp;lt;Errors supportContact=&amp;quot;root@localhost&amp;quot; helpLocation=&amp;quot;/about.html&amp;quot; styleSheet=&amp;quot;/shibboleth/main.css&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;MetadataProvider type=&amp;quot;XML&amp;quot; file=&amp;quot;foo/idp-metadata.xml&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;AttributeExtractor type=&amp;quot;XML&amp;quot; validate=&amp;quot;true&amp;quot; reloadChanges=&amp;quot;false&amp;quot; path=&amp;quot;foo/attribute-map.xml&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;AttributeResolver type=&amp;quot;Query&amp;quot; subjectMatch=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;AttributeFilter type=&amp;quot;XML&amp;quot; validate=&amp;quot;true&amp;quot; path=&amp;quot;attribute-policy.xml&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;CredentialResolver type=&amp;quot;File&amp;quot; key=&amp;quot;foo/sp-key.pem&amp;quot; certificate=&amp;quot;foo/sp-cert.pem&amp;quot;/&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
    &amp;lt;/ApplicationDefaults&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
    &amp;lt;SecurityPolicyProvider type=&amp;quot;XML&amp;quot; validate=&amp;quot;true&amp;quot; path=&amp;quot;security-policy.xml&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;ProtocolProvider type=&amp;quot;XML&amp;quot; validate=&amp;quot;true&amp;quot; reloadChanges=&amp;quot;false&amp;quot; path=&amp;quot;protocols.xml&amp;quot;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
  &amp;lt;/SPConfig&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Create the directory '''/etc/shibboleth/foo''', substituting ''foo'' for your repository name.&lt;br /&gt;
  root&amp;gt; mkdir /etc/shibboleth/foo&lt;br /&gt;
&lt;br /&gt;
* Copy '''attribute-map.xml''' into this new directory.&lt;br /&gt;
  cp /etc/shibboleth/attribute-map.xml /etc/shibboleth/foo/&lt;br /&gt;
&lt;br /&gt;
* Temporarily rename '''sp-cert.pem''' and '''sp-key.pem''' in '''/etc/shibboleth/''' to '''sp-cert.pem.old''' and '''sp-key.pem.old'''.&lt;br /&gt;
  root&amp;gt; cd /etc/shibboleth&lt;br /&gt;
  root&amp;gt; mv sp-cert.pem sp-cert.pem.old&lt;br /&gt;
  root&amp;gt; mv sp-key.pem sp-key.pem.old&lt;br /&gt;
&lt;br /&gt;
* Run '''keygen.sh''' from the '''/etc/shibboleth/''' directory, as follows replacing '''foo.eprints.org''' with your EPrints repository hostname.&lt;br /&gt;
  root&amp;gt; cd /etc/shibboleth&lt;br /&gt;
  root&amp;gt; ./keygen.sh -f -h foo.eprints.org -e https://foo.eprints.org/shibboleth&lt;br /&gt;
&lt;br /&gt;
* Move the new '''sp-cert.pem''' and '''sp-key.pem''' to '''/etc/shibboleth/foo/''' amd move the ''.old'' files back in place:&lt;br /&gt;
  root&amp;gt; cd /etc/shibboleth&lt;br /&gt;
  root&amp;gt; mv sp-cert.pem sp-key.pem foo/&lt;br /&gt;
  root&amp;gt; mv sp-cert.pem.old sp-cert.pem&lt;br /&gt;
  root&amp;gt; mv sp-key.pem.old sp-key.pem&lt;br /&gt;
&lt;br /&gt;
* Check that '''sp-cert.pem''' and '''sp-key.pem''' in '''/etc/shibboleth/foo/''' still have the owner and group '''shibd'''.&lt;br /&gt;
  root&amp;gt; ls -l /etc/shibboleth/foo/sp-*&lt;br /&gt;
  -rw-r--r-- 1 shibd shibd 1192 May  6 19:04 /etc/shibboleth/foo/sp-cert.pem&lt;br /&gt;
  -rw------- 1 shibd shibd 1708 May  6 19:04 /etc/shibboleth/foo/sp-key.pem&lt;br /&gt;
&lt;br /&gt;
* Use ''wget'' to download the metadata from your Shibboleth IdP (e.g. shib.foo.example.org) to the '''/etc/shibboleth/foo/''' directory.&lt;br /&gt;
  root&amp;gt; wget -O /etc/shibboleth/foo/idp-metadata.xml https://shib.foo.example.org/idp/shibboleth&lt;br /&gt;
&lt;br /&gt;
== Configuring Apache and EPrints ==&lt;br /&gt;
'''N.B. All these actions should be carried out by the ''eprints'' user, except when prepended with ''root&amp;gt;'' which means the command should be run as the ''root'' user.'''&lt;br /&gt;
* Add the following configuration to your archive's '''ssl/securevhost.conf''', after the '''Include /opt/eprints3/cfg/apache_ssl/foo.conf''', substituting '''foo''' for your archive's name where appropriate.  (This assumes you are running Apache 2.4 or greater).  See [[#Apache 2.2 (and lower) Configuration for EPrints Shibboleth Integration |Troubleshooting]] for instructions on the configuration to use for Apache 2.2. or lower.&lt;br /&gt;
&lt;br /&gt;
 Alias /shibboleth /opt/eprints3/archives/foo/shibboleth&lt;br /&gt;
 &amp;lt;Location &amp;quot;/shibboleth&amp;quot;&amp;gt;&lt;br /&gt;
   SetHandler perl-script&lt;br /&gt;
   PerlHandler ModPerl::Registry&lt;br /&gt;
   PerlSendHeader Off&lt;br /&gt;
   Options ExecCGI FollowSymLinks&lt;br /&gt;
 &lt;br /&gt;
   AuthType shibboleth&lt;br /&gt;
   ShibRequestSetting requireSession 1&lt;br /&gt;
   require shib-session&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;Location /cgi/shibboleth&amp;gt;&lt;br /&gt;
   AuthType shibboleth&lt;br /&gt;
   ShibRequestSetting requireSession 1&lt;br /&gt;
   require shib-session&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Copy the following code into your archive (e.g. /opt/eprints3/archives/foo/) as '''cgi/shibboleth'''.&lt;br /&gt;
 use EPrints;&lt;br /&gt;
 use strict;&lt;br /&gt;
 my $session = new EPrints::Session;&lt;br /&gt;
 exit( 0 ) unless( defined $session );&lt;br /&gt;
 &lt;br /&gt;
 $session-&amp;gt;send_http_header( content_type=&amp;gt;&amp;quot;text/html&amp;quot; );&lt;br /&gt;
 &lt;br /&gt;
 print &amp;quot;&amp;amp;lt;html&amp;amp;gt;&amp;amp;lt;head/&amp;amp;gt;&amp;amp;lt;body&amp;amp;gt;&amp;amp;lt;code&amp;amp;gt;\n&amp;quot;;&lt;br /&gt;
 &lt;br /&gt;
 foreach my $key (sort keys(%ENV)) {&lt;br /&gt;
   print &amp;quot;&amp;amp;lt;p&amp;amp;gt;$key = $ENV{$key}&amp;amp;lt;/p&amp;amp;gt;&amp;quot;;&lt;br /&gt;
 }&lt;br /&gt;
  &lt;br /&gt;
 print &amp;quot;&amp;amp;lt;/code&amp;amp;gt;&amp;amp;lt;/body&amp;amp;gt;&amp;amp;lt;/html&amp;amp;gt;&amp;quot;;&lt;br /&gt;
 $session-&amp;gt;terminate;&lt;br /&gt;
 exit;&lt;br /&gt;
&lt;br /&gt;
* Now restart Shibboleth and Apache:&lt;br /&gt;
  root&amp;gt; systemctl restart shibd.service&lt;br /&gt;
  root&amp;gt; apachectl restart&lt;br /&gt;
&lt;br /&gt;
* In a web browser go the '''/cgi/shibboleth''' page for your repository, (e.g. ''https://foo.eprints.org/cgi/shibboleth'').  You should be redirected to an error page for your your Shibboleth IdP (e.g. ''https://shib.foo.example.org/idp/profile/SAML2/Redirect/SSO?...'').  &lt;br /&gt;
&lt;br /&gt;
* If instead you are displayed with a list of key values or are forbidden to access the page, you have not configured Apache properly, if so, see [[#Apache_Configuration_Issues|Apache_Configuration_Issues]] under [[#Troubleshooting|Troubleshooting]].  If you see an error message like the one below, you have not set up Shibboleth properly, if so, see [[#Shibboleth_Configuration_Issues|Shibboleth_Configuration_Issues]] under [[#Troubleshooting|Troubleshooting]].&lt;br /&gt;
 opensaml::saml2md::MetadataException&lt;br /&gt;
 The system encountered an error at Wed May 6 15:19:27 2015&lt;br /&gt;
 To report this problem, please contact the site administrator at root@localhost.&lt;br /&gt;
 Please include the following message in any email:&lt;br /&gt;
 opensaml::saml2md::MetadataException at (http://foo.eprints.org/cgi/shibboleth)&lt;br /&gt;
 Unable to locate metadata for identity provider (https://shib.foo.example.org/idp/shibboleth)&lt;br /&gt;
&lt;br /&gt;
* Next, copy the following code into your archive (e.g. ''/opt/eprints3/archives/foo/'') as '''cfg/cfg.d/zz_shibboleth.pl'''.  This is needed to redirect login and logout to use Shibboleth rather than local login.&lt;br /&gt;
 $c-&amp;gt;{get_login_url} = sub {&lt;br /&gt;
   my( $session, $target ) = @_;&lt;br /&gt;
 &lt;br /&gt;
   # preserve CGI params&lt;br /&gt;
   $session-&amp;gt;read_params;&lt;br /&gt;
   $target = $session-&amp;gt;get_url(&lt;br /&gt;
     host =&amp;gt; 1,&lt;br /&gt;
     path =&amp;gt; &amp;quot;auto&amp;quot;,&lt;br /&gt;
     query =&amp;gt; 1,&lt;br /&gt;
   );&lt;br /&gt;
 &lt;br /&gt;
   my $url = URI-&amp;gt;new( $session-&amp;gt;config( &amp;quot;https_url&amp;quot; )  . &amp;quot;/shibboleth/login&amp;quot; );&lt;br /&gt;
   $url-&amp;gt;query_form( target =&amp;gt; &amp;quot;$target&amp;quot; );&lt;br /&gt;
   return &amp;quot;$url&amp;quot;;&lt;br /&gt;
 };&lt;br /&gt;
 &lt;br /&gt;
 $c-&amp;gt;{on_logout} = sub {&lt;br /&gt;
   my( $session ) = @_;&lt;br /&gt;
   my $query = $session-&amp;gt;query;&lt;br /&gt;
   return unless defined $query;&lt;br /&gt;
 &lt;br /&gt;
   # remove _shibsession_ cookie&lt;br /&gt;
   my( $shibname, $shibvalue );&lt;br /&gt;
   for( $query-&amp;gt;cookie() ) {&lt;br /&gt;
     if( $_ =~ /^_shibsession/ ) {&lt;br /&gt;
       $shibname = $_;&lt;br /&gt;
       $shibvalue = $query-&amp;gt;cookie( $shibname );&lt;br /&gt;
     }&lt;br /&gt;
   }&lt;br /&gt;
 &lt;br /&gt;
   my $cookie = $query-&amp;gt;cookie(&lt;br /&gt;
     -name    =&amp;gt; $shibname,&lt;br /&gt;
     -path    =&amp;gt; &amp;quot;/&amp;quot;,&lt;br /&gt;
     -value   =&amp;gt; &amp;quot;&amp;quot;,&lt;br /&gt;
     -host  =&amp;gt; $session-&amp;gt;config(&amp;quot;cookie_domain&amp;quot;),&lt;br /&gt;
     -expires =&amp;gt; &amp;quot;-1d&amp;quot;,&lt;br /&gt;
   );&lt;br /&gt;
   EPrints::Apache::AnApache::header_out(&lt;br /&gt;
     $session-&amp;gt;{request},&lt;br /&gt;
     &amp;quot;Set-Cookie&amp;quot; =&amp;gt; $cookie &lt;br /&gt;
   );&lt;br /&gt;
 };&lt;br /&gt;
 &lt;br /&gt;
 push @{$c-&amp;gt;{rewrite_exceptions}}, &amp;quot;/shibboleth/&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
* Create a folder at the top level of your archive (e.g. ''/opt/eprints3/archives/foo/'') called '''shibboleth''' and copy the main CSS file for Shibboleth into this folder:&lt;br /&gt;
 eprints&amp;gt; mkdir /opt/eprints3/archives/foo/shibboleth/&lt;br /&gt;
 eprints&amp;gt; cp /usr/share/shibboleth/main.css /opt/eprints3/archives/foo/shibboleth/&lt;br /&gt;
&lt;br /&gt;
* Now, copy the following code into your archive (e.g. ''/opt/eprints3/archives/foo/'') as '''shibboleth/login'''.  This is the most basic login script that should work with the minimal attributes any Shibboleth IdP returns and '''only logging in users with existing accounts'''. Look under the [[#Customisation|Customisation]] section for advice on how to modify this script to meet your requirements, such as creation user accounts on-the-fly.&lt;br /&gt;
 use EPrints;&lt;br /&gt;
 use strict;&lt;br /&gt;
 &lt;br /&gt;
 my $session = EPrints::Session-&amp;gt;new();&lt;br /&gt;
 my $url = $session-&amp;gt;param( &amp;quot;target&amp;quot; );&lt;br /&gt;
 $url = $session-&amp;gt;get_repository-&amp;gt;get_conf( &amp;quot;userhome&amp;quot; ) unless EPrints::Utils::is_set( $url );&lt;br /&gt;
 &lt;br /&gt;
 my $user = &amp;amp;get_user;&lt;br /&gt;
 &lt;br /&gt;
 if( defined $user ) {&lt;br /&gt;
   $user-&amp;gt;set_value( &amp;quot;last_login&amp;quot;, EPrints::Time::get_iso_timestamp() );&lt;br /&gt;
   $user-&amp;gt;commit;&lt;br /&gt;
 &lt;br /&gt;
   EPrints::DataObj::LoginTicket-&amp;gt;expire_all( $session );&lt;br /&gt;
   $session-&amp;gt;dataset( &amp;quot;loginticket&amp;quot; )-&amp;gt;create_dataobj({&lt;br /&gt;
     userid =&amp;gt; $user-&amp;gt;id,&lt;br /&gt;
   })-&amp;gt;set_cookies();&lt;br /&gt;
 &lt;br /&gt;
   $session-&amp;gt;redirect( $url );&lt;br /&gt;
 }&lt;br /&gt;
 else {&lt;br /&gt;
   $session-&amp;gt;redirect( $session-&amp;gt;get_repository-&amp;gt;get_conf( &amp;quot;base_dir&amp;quot; ) . &amp;quot;/account_required.html&amp;quot;);&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 $session-&amp;gt;terminate;&lt;br /&gt;
   &lt;br /&gt;
 sub get_user {&lt;br /&gt;
   my ( $username, $email ) = ( undef, &amp;quot;&amp;quot; );&lt;br /&gt;
   if( $ENV{eppn} ) {&lt;br /&gt;
    ( $username ) = split( /@/, $ENV{eppn}, 2);&lt;br /&gt;
    $username = lc( $username );&lt;br /&gt;
    $email = $ENV{eppn};&lt;br /&gt;
   }&lt;br /&gt;
   return unless EPrints::Utils::is_set( $username );&lt;br /&gt;
   my $user = $session-&amp;gt;user_by_username( $username );&lt;br /&gt;
   if( defined $user &amp;amp;&amp;amp; defined $email )&lt;br /&gt;
   {&lt;br /&gt;
     $user-&amp;gt;set_value( &amp;quot;email&amp;quot;, $email );&lt;br /&gt;
     $user-&amp;gt;commit;&lt;br /&gt;
   }&lt;br /&gt;
   return $user;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
* Next, add the following markup to '''cfg/lang/en/static/account_required.xpage''' under your archive (e.g. ''/opt/eprints3/archives/foo/'').  Substituting ''staff and students of the University of Foo'' to describe to which particular group of people logged in access is restricted.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;?xml version=&amp;quot;1.0&amp;quot; standalone=&amp;quot;no&amp;quot; ?&amp;gt;&lt;br /&gt;
 &amp;lt;!DOCTYPE page SYSTEM &amp;quot;entities.dtd&amp;quot; &amp;gt;&lt;br /&gt;
 &amp;lt;xpage:page xmlns=&amp;quot;http://www.w3.org/1999/xhtml&amp;quot; xmlns:xpage=&amp;quot;http://eprints.org/ep3/xpage&amp;quot; xmlns:epc=&amp;quot;http://eprints.org/ep3/control&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;xpage:title&amp;gt;Login Failed&amp;lt;/xpage:title&amp;gt;&lt;br /&gt;
 &amp;lt;xpage:body&amp;gt;&lt;br /&gt;
    &amp;amp;lt;p style='text-align: center;'&amp;amp;gt;Please note that only staff and students of the University of Foo may log in to &amp;lt;epc:phrase ref=&amp;quot;archive_name&amp;quot; /&amp;gt;&amp;amp;lt;/p&amp;amp;gt;&lt;br /&gt;
 &amp;lt;/xpage:body&amp;gt;&lt;br /&gt;
 &amp;lt;/xpage:page&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Now, reload Apache.&lt;br /&gt;
  root&amp;gt; apachectl reload&lt;br /&gt;
&lt;br /&gt;
* In a web browser go to the '''/shibboleth/login''' page for your repository, (e.g. ''https://foo.eprints.org/shibboleth/login'').  Like before with ''/cgi/shibboleth'' you should be taken to your Shibboleth IdP's site albeit displaying an error message.&lt;br /&gt;
&lt;br /&gt;
* The Shibboleth IdP shows an error message because EPrints as a Shibboleth Service Provider is not yet registered with it.  To do this you need to send the administrator of the Shibboleth IdP the metadata for your Service Provider.  This may not be externally accessible, you can test this by requesting the following URL in a web browser (replacing '''foo.eprints.org''' with you repository's hostname):&lt;br /&gt;
&lt;br /&gt;
  https://foo.eprints.org/Shibboleth.sso/Metadata &lt;br /&gt;
&lt;br /&gt;
* If it is you can just tell the administrator of the Shibboleth Identity Provider to download it from the above URL and then wait for them to get back to you to tell you it has been registered.  If not you will need to download it locally externally, using ''wget'' from the command line:&lt;br /&gt;
  wget --no-check-certificate -O - -o /dev/null https://localhost/Shibboleth.sso/Metadata | xmllint --format - &amp;gt; ~/sp-metadata.xml&lt;br /&gt;
&lt;br /&gt;
* If you get no error messages, this command will have saved you Shibboleth Service Provider metadata in a file in your home directory called '''sp-metadata.xml'''.  You will need to replace all occurrences of '''localhost''' with the full hostname of your EPrints repository (e.g. ''foo.eprints.org'').  Then you can email this file to the administrator of the Shibboleth Identity Provider instead.&lt;br /&gt;
&lt;br /&gt;
* Once registered, use a web browser to go to '''/shibboleth/login''' page for your repository, (e.g. ''https://foo.eprints.org/shibboleth/login'') again.  This time you should be prompted for a username and password on the Shibboleth IdP site. Once you have typed this in and clicked to login, you should be returned to EPrints on the '''/cgi/users/home''' page for your repository.  If not, see [[#Login_Issues|Login Issues]] under [[#Troubleshooting|Troubleshooting]] below.&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
=== Apache Configuration Issues ===&lt;br /&gt;
==== Apache 2.2 (and lower) Configuration for EPrints Shibboleth Integration ====&lt;br /&gt;
* Similarly to the instructions for Apache 2.4 and above, place the slightly different following configuration after the '''Include''' line for ''apache_ssl/foo.conf'', (substituting '''foo''' for your archive's name):&lt;br /&gt;
&lt;br /&gt;
  Alias /shibboleth /opt/eprints3/archives/foo/shibboleth&lt;br /&gt;
  &amp;lt;Directory &amp;quot;/opt/eprints3/archives/foo/shibboleth&amp;quot;&amp;gt;&lt;br /&gt;
    SetHandler perl-script&lt;br /&gt;
    PerlHandler ModPerl::Registry&lt;br /&gt;
    PerlSendHeader Off&lt;br /&gt;
    Options ExecCGI FollowSymLinks&lt;br /&gt;
  &lt;br /&gt;
    AuthType shibboleth&lt;br /&gt;
    ShibRequireSession On&lt;br /&gt;
    require valid-user&lt;br /&gt;
  &amp;lt;/Directory&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
  &amp;lt;Location /cgi/shibboleth&amp;gt;&lt;br /&gt;
    AuthType shibboleth&lt;br /&gt;
    ShibRequireSession On&lt;br /&gt;
    require valid-user&lt;br /&gt;
  &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Shibboleth Configuration Issues ===&lt;br /&gt;
==== With attribute-map.xml ====&lt;br /&gt;
When authenticating using Shibboleth to login to EPrints you may see the following line in '''/var/log/shibboleth.shibd.log'''&lt;br /&gt;
&lt;br /&gt;
  2015-09-09 09:26:43 INFO Shibboleth.AttributeExtractor.XML [2]: skipping unmapped SAML 2.0 Attribute with Name:  urn:mace:dir:attribute-def:department&lt;br /&gt;
&lt;br /&gt;
In some cases this might not be an issue, as EPrints does not necessarily to make use of all the attributes returned by the IdP but without a mapping in attribute-map.xml.  In this case '''urn:mace:dir:attribute-def:department''' is not by default needed by EPrints to create/update a user account.  However, values like '''sn''', '''givenName''' and '''mail''' are but if you have used the attribute-map.xml provided later on the page you should not see a line like above in '''shibd.log'''.  In some cases you may still see an line like this in the log even if you think you have defined the attribute.  The line below demonstrate two known issues:&lt;br /&gt;
&lt;br /&gt;
  2015-09-09 09:26:43 INFO Shibboleth.AttributeExtractor.XML [2]: skipping unmapped SAML 2.0 Attribute with Name:  givenName, Format:urn:oasis:names:tc:SAML:2.0:attrname-format:basic&lt;br /&gt;
&lt;br /&gt;
# The attribute itself has no namespace it is just ''''givenName''' rather than '''urn:mace:dir:attribute-def:givenName'''&lt;br /&gt;
# The attribute has a format that most also be defined in the attribute-map.xml attribute.&lt;br /&gt;
&lt;br /&gt;
Below shows how to both include the format, which is required for the attribute to be successful mapped.  As well as define the name of the attribute without a namespace:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;Attribute name=&amp;quot;givenName&amp;quot; nameFormat=&amp;quot;urn:oasis:names:tc:SAML:2.0:attrname-format:basic&amp;quot; id=&amp;quot;givenName&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A typical Shibboleth IdP would have both a namespaced attribute name and would not apply a format to an attribute that is a simple text string.  Therefore it is worth enquiring with the IdP provider if either of these two happen to be the case.&lt;br /&gt;
&lt;br /&gt;
==== With idp-metadata.xml ====&lt;br /&gt;
If you want to be able extract scoped attributes (e.g. '''eduPersonPrincipalName''' otherwise described as '''eppn''').  Then you will need to ensure that the expected scope of this attribute, (effectively the domain part in eduPersonPrincipalName is the scope or one of the scopes in the idp-metadata.xml you downloaded from the Shibboleth IdP.  For example if the '''eduPersonPrincipalName''' is '''bar@foo.ac.uk'''.  Then the following should be defined in idp-metadata.xml ('''N.B. the namespace abbreviations (md: and shibmd:) may be different for the IdP you are working with'''):&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;md:Extensions&amp;gt;&lt;br /&gt;
    &amp;lt;shibmd:Scope regexp=&amp;quot;false&amp;quot;&amp;gt;foo.ac.uk&amp;lt;/shibmd:Scope&amp;gt;&lt;br /&gt;
  &amp;lt;/md:Extensions&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Login Issues ===&lt;br /&gt;
To be added.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Customisation ==&lt;br /&gt;
&lt;br /&gt;
=== Shibboleth /etc/shibboleth/foo/attribute-map.xml config ===&lt;br /&gt;
This is adapted from the default '''attribute-map.xml''' provided when the Shibboleth SP package is installed to only include the attribute subsequently used by EPrints Shibboleth Perl script that can be found below.  You may wish to refer to the default '''attribute-map.xml''' is you want to use other attributes.&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;Attributes xmlns=&amp;quot;urn:mace:shibboleth:2.0:attribute-map&amp;quot; xmlns:xsi=&amp;quot;http://www.w3.org/2001/XMLSchema-instance&amp;quot;&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:mace:dir:attribute-def:eduPersonPrincipalName&amp;quot; id=&amp;quot;eppn&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;AttributeDecoder xsi:type=&amp;quot;ScopedAttributeDecoder&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;/Attribute&amp;gt;&lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:oid:1.3.6.1.4.1.5923.1.1.1.6&amp;quot; id=&amp;quot;eppn&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;AttributeDecoder xsi:type=&amp;quot;ScopedAttributeDecoder&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;/Attribute&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:mace:dir:attribute-def:sn&amp;quot; id=&amp;quot;sn&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:mace:dir:attribute-def:givenName&amp;quot; id=&amp;quot;givenName&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:mace:dir:attribute-def:mail&amp;quot; id=&amp;quot;mail&amp;quot;/&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:oid:2.5.4.4&amp;quot; nameFormat=&amp;quot;urn:oasis:names:tc:SAML:2.0:attrname-format:basic&amp;quot; id=&amp;quot;sn&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:oid:2.5.4.42&amp;quot; nameFormat=&amp;quot;urn:oasis:names:tc:SAML:2.0:attrname-format:basic&amp;quot; id=&amp;quot;givenName&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;Attribute name=&amp;quot;urn:oid:0.9.2342.19200300.100.1.3&amp;quot; nameFormat=&amp;quot;urn:oasis:names:tc:SAML:2.0:attrname-format:basic&amp;quot; id=&amp;quot;mail&amp;quot;/&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
  &amp;lt;/Attributes&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== EPrints /shibboleth/login script with user account creation ===&lt;br /&gt;
This is the standard EPrints Shibboleth login script.  It makes a number of assumptions:&lt;br /&gt;
# That accounts should be created if they do not already exist for a particular user.&lt;br /&gt;
# That you wish to create a standard user account (not an editor administrator) account.&lt;br /&gt;
# That the Shibboleth IdP provides all the attributes (eduPersonPrinicpalName (seen as eppn), sn, givenName and mail) required.&lt;br /&gt;
&lt;br /&gt;
  use EPrints;&lt;br /&gt;
  use strict;&lt;br /&gt;
  &lt;br /&gt;
  my $session = EPrints::Session-&amp;gt;new();&lt;br /&gt;
  my $url = $session-&amp;gt;param( &amp;quot;target&amp;quot; );&lt;br /&gt;
  $url = $session-&amp;gt;get_repository-&amp;gt;get_conf( &amp;quot;userhome&amp;quot; ) unless EPrints::Utils::is_set( $url );&lt;br /&gt;
  &lt;br /&gt;
  my $user = &amp;amp;get_user;&lt;br /&gt;
  &lt;br /&gt;
  if( defined $user )&lt;br /&gt;
  {&lt;br /&gt;
    $user-&amp;gt;set_value( &amp;quot;last_login&amp;quot;, EPrints::Time::get_iso_timestamp() );&lt;br /&gt;
    $user-&amp;gt;commit;&lt;br /&gt;
  &lt;br /&gt;
    EPrints::DataObj::LoginTicket-&amp;gt;expire_all( $session );&lt;br /&gt;
    $session-&amp;gt;dataset( &amp;quot;loginticket&amp;quot; )-&amp;gt;create_dataobj({&lt;br /&gt;
      userid =&amp;gt; $user-&amp;gt;id,&lt;br /&gt;
    })-&amp;gt;set_cookies();&lt;br /&gt;
  &lt;br /&gt;
    $session-&amp;gt;redirect( $url );&lt;br /&gt;
  }&lt;br /&gt;
  else&lt;br /&gt;
  {&lt;br /&gt;
    $session-&amp;gt;redirect( $session-&amp;gt;get_repository-&amp;gt;get_conf( &amp;quot;base_dir&amp;quot; ) . &amp;quot;/account_required.html&amp;quot;);&lt;br /&gt;
  }&lt;br /&gt;
  &lt;br /&gt;
  $session-&amp;gt;terminate;&lt;br /&gt;
  &lt;br /&gt;
  sub get_user&lt;br /&gt;
  {&lt;br /&gt;
    my ($username, $given, $family, $email) = (undef, &amp;quot;&amp;quot;, &amp;quot;&amp;quot;, &amp;quot;&amp;quot;);&lt;br /&gt;
  &lt;br /&gt;
    if( $ENV{eppn} ) {&lt;br /&gt;
      ( $username ) = split( /@/, $ENV{eppn}, 2);&lt;br /&gt;
      $username = lc( $username );&lt;br /&gt;
    }&lt;br /&gt;
    $email = $ENV{mail} if $ENV{mail};&lt;br /&gt;
    if( $ENV{givenName} )&lt;br /&gt;
    {&lt;br /&gt;
      $given = lc( $ENV{givenName} );&lt;br /&gt;
      $given =~ s/^(.)/uc($1)/e;&lt;br /&gt;
      $given =~ s/([- ].)/uc($1)/e;&lt;br /&gt;
    }&lt;br /&gt;
    if( $ENV{sn} )&lt;br /&gt;
    {&lt;br /&gt;
      $family = lc( $ENV{sn} );&lt;br /&gt;
      $family =~ s/^(.)/uc($1)/e;&lt;br /&gt;
      $family =~ s/([- ].)/uc($1)/e;&lt;br /&gt;
    }&lt;br /&gt;
  &lt;br /&gt;
    return unless EPrints::Utils::is_set( $username );&lt;br /&gt;
  &lt;br /&gt;
    my $user = $session-&amp;gt;user_by_username( $username ); # relying on this to be case insensitive&lt;br /&gt;
  &lt;br /&gt;
    if( !defined $user )&lt;br /&gt;
    {&lt;br /&gt;
      my $usertype = 'user';&lt;br /&gt;
      $user = EPrints::DataObj::User::create( $session, $usertype );&lt;br /&gt;
      $user-&amp;gt;set_value( &amp;quot;username&amp;quot;, $username );&lt;br /&gt;
    }&lt;br /&gt;
    my $name = {&lt;br /&gt;
      given =&amp;gt; $given,&lt;br /&gt;
      family =&amp;gt; $family,&lt;br /&gt;
    };&lt;br /&gt;
    $user-&amp;gt;set_value( &amp;quot;name&amp;quot;, $name );&lt;br /&gt;
    $user-&amp;gt;set_value( &amp;quot;email&amp;quot;, $email );&lt;br /&gt;
    $user-&amp;gt;commit;&lt;br /&gt;
    return $user;&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
== Further Information ==&lt;br /&gt;
* Older instructions of how to set up EPrints for Shibboleth using UK Access management Federation discovery service is available [[Shibboleth authentication|here]].&lt;br /&gt;
&lt;br /&gt;
* For general information about installing and configuring Shibboleth [http://shibboleth.internet2.edu/ click here].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Authentication]]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=API:bin/epadmin&amp;diff=12302</id>
		<title>API:bin/epadmin</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=API:bin/epadmin&amp;diff=12302"/>
		<updated>2017-06-06T09:49:55Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* reindex */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Pod2Wiki=_preamble_ &lt;br /&gt;
This page has been automatically generated from the EPrints 3.2 source. Any wiki changes made between the 'Pod2Wiki=*' and 'Edit below this comment' comments will be lost.&lt;br /&gt;
 --&amp;gt;{{API}}{{Pod2Wiki}}{{API:Source|file=bin/epadmin|package_name=bin/epadmin}}[[Category:API|BIN/EPADMIN]][[Category:API:bin/epadmin|BIN/EPADMIN]][[Category:API:bin/epadmin|BIN/EPADMIN]]&amp;lt;div&amp;gt;&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=_private_ --&amp;gt;&amp;lt;!-- Pod2Wiki=head_name --&amp;gt;&lt;br /&gt;
==NAME==&lt;br /&gt;
epadmin - EPrints repository admin tool&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_synopsis --&amp;gt;&lt;br /&gt;
==SYNOPSIS==&lt;br /&gt;
epadmin '''options''' &amp;lt;em&amp;gt;command&amp;lt;/em&amp;gt; [repository_id]&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;em&amp;gt;command&amp;lt;/em&amp;gt; is one of:&lt;br /&gt;
&lt;br /&gt;
* cleanup_cachemaps&lt;br /&gt;
* config_core&lt;br /&gt;
* config_db&lt;br /&gt;
* create&lt;br /&gt;
* create_db&lt;br /&gt;
* create_tables&lt;br /&gt;
* create_user&lt;br /&gt;
* erase_data&lt;br /&gt;
* erase_eprints&lt;br /&gt;
* erase_fulltext_index&lt;br /&gt;
* help&lt;br /&gt;
* profile&lt;br /&gt;
* rebuild_triples&lt;br /&gt;
* recommit&lt;br /&gt;
* reorder&lt;br /&gt;
* redo_files_modified&lt;br /&gt;
* redo_mime_type&lt;br /&gt;
* redo_thumbnails&lt;br /&gt;
* refresh_abstracts&lt;br /&gt;
* refresh_views&lt;br /&gt;
* reindex&lt;br /&gt;
* reload&lt;br /&gt;
* set_developer_mode&lt;br /&gt;
* show_config&lt;br /&gt;
* show_plugins&lt;br /&gt;
* test&lt;br /&gt;
* unit_tests&lt;br /&gt;
* update&lt;br /&gt;
* upgrade&lt;br /&gt;
Type &amp;lt;code&amp;gt;epadmin help command&amp;lt;/code&amp;gt; for further help.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_commands --&amp;gt;&lt;br /&gt;
==COMMANDS==&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_create --&amp;gt;&lt;br /&gt;
===create===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin create&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create a new repository instance based on question-and-answer.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_create_test --&amp;gt;&lt;br /&gt;
===create_test===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin create_test&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create a test repository instance called &amp;quot;test&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_cleanup_cachemaps --&amp;gt;&lt;br /&gt;
===cleanup_cachemaps===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin cleanup_cachemaps repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Drop any orphaned cache tables.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_config_core --&amp;gt;&lt;br /&gt;
===config_core===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin config_core repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set hostname, contact email and repository name. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_config_db --&amp;gt;&lt;br /&gt;
===config_db===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin config_db repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set database connection properties and, optionally, to create database and database user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_create_db --&amp;gt;&lt;br /&gt;
===create_db===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin create_db repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create a database and database user with the current settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_create_user --&amp;gt;&lt;br /&gt;
===create_user===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin create_user repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create a new user. You need to do this to create your first admin account.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_delete --&amp;gt;&lt;br /&gt;
===delete===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin delete repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Destroy repository_id and all of its content. Only use if you are absolutely sure you know what you're doing.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_help --&amp;gt;&lt;br /&gt;
===help===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin help [command]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Show help for &amp;lt;code&amp;gt;epadmin&amp;lt;/code&amp;gt;. Specify a &amp;lt;code&amp;gt;command&amp;lt;/code&amp;gt; to get detailed help on a particular command&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_redo_files_modified --&amp;gt;&lt;br /&gt;
===redo_files_modified===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin redo_files_modified repository_id [ dataset objectid, ... ]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Call [[API:EPrints/DataObj/Document#files_modified|EPrints::DataObj::Document/files_modified]] for every document.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_redo_mime_type --&amp;gt;&lt;br /&gt;
===redo_mime_type===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin redo_mime_type repository_id dataset [ objectid, ... ]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Redo file format identification. Dataset may be &amp;lt;code&amp;gt;eprint&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;document&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;file&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_redo_thumbnails --&amp;gt;&lt;br /&gt;
===redo_thumbnails===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin redo_thumbnails repository_id [ eprintid, ... ]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Regenerate all the thumbnail and image-preview files and any other things which are triggered if the document file changed. Optionally supply a list of eprint ids to re-generate thumbnails for.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_refresh_views --&amp;gt;&lt;br /&gt;
===refresh_views===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin refresh_views repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Tell the webserver that all views pages must be regenerated. The webserver will update them next time they are requested. Also causes config to be reloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_refresh_abstracts --&amp;gt;&lt;br /&gt;
===refresh_abstracts===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin refresh_abstracts repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Tell the webserver that all abstract summary pages must be regenerated. The webserver will update them next , but won't update them again unless something on the EPrint changes or you re-run refresh abstracts. Also causes config to be reloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_reload --&amp;gt;&lt;br /&gt;
===reload===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin reload repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cause the web server to reload the repository configuration.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_create_tables --&amp;gt;&lt;br /&gt;
===create_tables===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin create_tables repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Create the database tables.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_erase_data --&amp;gt;&lt;br /&gt;
===erase_data===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin erase_data repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Erases and recreates the database. Removes all documents and files. Does not touch the configuration files.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_erase_eprints --&amp;gt;&lt;br /&gt;
===erase_eprints===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin erase_eprints repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Erases all the documents and eprints (including their files). Recreates the eprint and document tables. Leaves configuration files and the users and subjects tables alone.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_erase_fulltext_index --&amp;gt;&lt;br /&gt;
===erase_fulltext_index===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin erase_fulltext_index repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This erases all the .words and .indexcodes cache files from your repository, forcing the indexer to rerun the tools used to extract full text from your documents.&lt;br /&gt;
&lt;br /&gt;
This is useful if you only setup the fulltext indexing after your repository is already live, or if you discover there has been a problem.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_show_config --&amp;gt;&lt;br /&gt;
===show_config===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin show_config repository_id key1 [key2 ...]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dump the given configuration section identified by key1. Use extra keys to get a lower-level configuration setting.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_show_plugins --&amp;gt;&lt;br /&gt;
===show_plugins===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin show_plugins repository_id [filters]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dump a list of all enabled plugins. You can constrain this list by providing filters e.g.:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  type=Import&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_test --&amp;gt;&lt;br /&gt;
===test===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin test repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A null operation which just checks your configuration files are OK and that you can connect to the database. If no repository_id is specified loads each repository in turn. Use --verbose to generate more information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_profile --&amp;gt;&lt;br /&gt;
===profile===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin profile test&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Run a performance profile of test using {{API:PodLink|file=Devel/NYTProf|package_name=Devel::NYTProf|section=|text=Devel::NYTProf}}.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_unit_tests --&amp;gt;&lt;br /&gt;
===unit_tests===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin unit_tests&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Run unit tests, printing the results to STDOUT. If everything passed will exit with a return code of 0.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_rehash --&amp;gt;&lt;br /&gt;
===rehash===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin rehash repository_id [document_id]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Recalculate the hashes of the files in this document and write it to a probity log file. If a document id is given then just generate the hash for that document.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_update --&amp;gt;&lt;br /&gt;
===update===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin update repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will add tables and columns to your SQL database to bring it in-line with your current configuration. It will not remove data. Use with caution on a live database. Database backup is recommended before use on live systems.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_recommit --&amp;gt;&lt;br /&gt;
===recommit===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin recommit repository_id dataset_id [eprint_id eprint_id ...]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Recommit all the records in the given dataset. What this does is cause the automatic values to be re-calculated. If a list of eprint_ids is given then just recommit those.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_reorder --&amp;gt;&lt;br /&gt;
===reorder===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin reorder repository_id dataset_id [eprint_id eprint_id ...]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Regenerate the order values for the dataset. If a list of eprint_ids is given then just recalculate ordervalues for those.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_rebuild_triples --&amp;gt;&lt;br /&gt;
===rebuild_triples===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin rebuild_triples repository_id [dataset_id item_id item_id ...]]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Queue all the records to have their RDF triple cache rebuilt. This may tie-up the indexer for some time on a large repository. Do this if you have made changes to the way RDF triples are produced from an EPrint. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_reindex --&amp;gt;&lt;br /&gt;
===reindex===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin reindex repository_id dataset_id [eprint_id eprint_id ...]&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Schedule the dataset for reindexing. The indexer will do the actual indexing and it may take some time. This only schedules the reindexing. If a list of eprint_ids is given then just reindex those.&lt;br /&gt;
Please note it only works on the indexable dataset, e.g. eprint, document, but not the '''file''' dataset.&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_remove_field --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===remove_field===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin remove_field repository_id dataset field_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Remove the database entries for the given field, can not be undone!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_set_developer_mode --&amp;gt;&lt;br /&gt;
===set_developer_mode===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin set_developer_mode repository_id &amp;amp;lt;on|off&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
While set to on developer mode causes the web server to reload the repository configuration on every page request. This makes development much quicker but must not be left switched on in a production environment since it increases server load dramatically.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_upgrade --&amp;gt;&lt;br /&gt;
===upgrade===&lt;br /&gt;
&amp;lt;pre&amp;gt;  epadmin upgrade repository_id&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After upgrading EPrints, use this to update the database tables. It will advise any other tasks that are required.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_options --&amp;gt;&lt;br /&gt;
==OPTIONS==&lt;br /&gt;
* '''--help'''&lt;br /&gt;
: Print a brief help message and exit.&lt;br /&gt;
&lt;br /&gt;
* '''--man'''&lt;br /&gt;
: Print the full manual page and then exit.&lt;br /&gt;
&lt;br /&gt;
* '''--quiet'''&lt;br /&gt;
: This option does not do anything.&lt;br /&gt;
&lt;br /&gt;
* '''--verbose'''&lt;br /&gt;
: Explain in detail what is going on. May be repeated for greater effect.&lt;br /&gt;
&lt;br /&gt;
* '''--force'''&lt;br /&gt;
: Be more forceful (don't ask for confirmation).&lt;br /&gt;
&lt;br /&gt;
* '''--version'''&lt;br /&gt;
: Output version information and exit.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_copyright --&amp;gt;&lt;br /&gt;
==COPYRIGHT==&lt;br /&gt;
Copyright 2000-2011 University of Southampton.&lt;br /&gt;
&lt;br /&gt;
This file is part of EPrints http://www.eprints.org/.&lt;br /&gt;
&lt;br /&gt;
EPrints is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.&lt;br /&gt;
&lt;br /&gt;
EPrints is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.&lt;br /&gt;
&lt;br /&gt;
You should have received a copy of the GNU General Public License along with EPrints.  If not, see http://www.gnu.org/licenses/.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=_postamble_ --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Core_API&amp;diff=12295</id>
		<title>Core API</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Core_API&amp;diff=12295"/>
		<updated>2017-03-27T14:22:28Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{API}}&lt;br /&gt;
[[Category:API]]&lt;br /&gt;
&lt;br /&gt;
The core API was introduced in EPrints 3.2.0 and is intended to provide a clean and consistent programming interface to the EPrints system. &lt;br /&gt;
&lt;br /&gt;
Not all essential functionality is yet available in the new API, as we've only included functions which we are confident we can keep stable for a number of versions. &lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 use EPrints;&lt;br /&gt;
 my $ep = EPrints-&amp;gt;new();&lt;br /&gt;
 my $repo = $ep-&amp;gt;repository( &amp;quot;myrepo&amp;quot; );&lt;br /&gt;
 my $an_eprint = $repo-&amp;gt;eprint( 23 );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== EPrints ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $ep = EPrints-&amp;gt;new();&lt;br /&gt;
 @ids = $ep-&amp;gt;repository_ids; # list active repository ids&lt;br /&gt;
 $repo = $ep-&amp;gt;repository( &amp;quot;devel&amp;quot;, noise=&amp;gt;1 );&lt;br /&gt;
 $repo = $ep-&amp;gt;current_repository(); # from Apache::Request URI&lt;br /&gt;
 EPrints-&amp;gt;abort( $message );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== Repository ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
$xml = $repo-&amp;gt;xml;&lt;br /&gt;
$dataset = $repo-&amp;gt;dataset( &amp;quot;user&amp;quot; );&lt;br /&gt;
$user = $repo-&amp;gt;current_user;&lt;br /&gt;
$query = $repo-&amp;gt;query;&lt;br /&gt;
$current_page_url = $repo-&amp;gt;current_url( host =&amp;gt; 1, path =&amp;gt; 1, query =&amp;gt; 1, etc. );&lt;br /&gt;
$config_element = $repo-&amp;gt;config( $key, [@subkeys] );&lt;br /&gt;
$repository-&amp;gt;log( $message ); &lt;br /&gt;
$string = $repo-&amp;gt;query-&amp;gt;param( &amp;quot;X&amp;quot; );&lt;br /&gt;
$repo-&amp;gt;redirect( $url );&lt;br /&gt;
$eprint = $repo-&amp;gt;eprint( 23 );&lt;br /&gt;
$user = $repo-&amp;gt;user( 23 );&lt;br /&gt;
$user = $repo-&amp;gt;user_by_username( &amp;quot;cjg&amp;quot; );&lt;br /&gt;
$user = $repo-&amp;gt;user_by_email( 'cjg@ecs.soton.ac.uk' );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Dataset ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $dataset = $repo-&amp;gt;dataset( &amp;quot;eprint&amp;quot; )&lt;br /&gt;
 $string = $dataset-&amp;gt;base_id; # eprint&lt;br /&gt;
 $string = $dataset-&amp;gt;id; # inbox&lt;br /&gt;
 &lt;br /&gt;
 $repo = $dataobj-&amp;gt;repository;&lt;br /&gt;
 &lt;br /&gt;
 $dataobj = $dataset-&amp;gt;create_dataobj( $data );&lt;br /&gt;
 $eprint = $dataset-&amp;gt;dataobj( 23 );&lt;br /&gt;
 &lt;br /&gt;
 %options = (filters =&amp;gt; [ { meta_fields =&amp;gt; [ 'contributors_id' ], value =&amp;gt; &amp;quot;13249&amp;quot;, match=&amp;gt;&amp;quot;EX&amp;quot; } ]);&lt;br /&gt;
 $search = $dataset-&amp;gt;prepare_search( %options );&lt;br /&gt;
 $list = $dataset-&amp;gt;search( %options ); # prepare_search( %options )-&amp;gt;execute&lt;br /&gt;
 $list = $dataset-&amp;gt;search; # match ALL&lt;br /&gt;
 &lt;br /&gt;
 $metafield = $dataset-&amp;gt;field( $fieldname );&lt;br /&gt;
 $metafield = $dataset-&amp;gt;key_field;&lt;br /&gt;
 @metafields = $dataset-&amp;gt;fields; &lt;br /&gt;
 &lt;br /&gt;
 $dataset-&amp;gt;search-&amp;gt;map( sub {}, $ctx );&lt;br /&gt;
 $n = $dataset-&amp;gt;search-&amp;gt;count; &lt;br /&gt;
 $ids = $dataset-&amp;gt;search-&amp;gt;ids;&lt;br /&gt;
 $list = $dataset-&amp;gt;list( \@ids );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== list ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $n = $list-&amp;gt;count;&lt;br /&gt;
 $list-&amp;gt;map( sub {&lt;br /&gt;
     my ( $repository, $dataset, $dataobj, $ctx ) = @_;&lt;br /&gt;
     # do something to the dataobj here&lt;br /&gt;
 }, $ctx );&lt;br /&gt;
 $dataobj = $list-&amp;gt;item( $offset );&lt;br /&gt;
 @all_dataobjs = $list-&amp;gt;slice &lt;br /&gt;
 @dataobjs = $list-&amp;gt;slice( $offset, $length ); &lt;br /&gt;
 \@ids = $list-&amp;gt;ids;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== XML ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $doc = $xml-&amp;gt;parse_string( $string );&lt;br /&gt;
 $doc = $xml-&amp;gt;parse_file( $filename );&lt;br /&gt;
 $doc = $xml-&amp;gt;parse_url( $url );&lt;br /&gt;
 &lt;br /&gt;
 $utf8_string = $xml-&amp;gt;to_string( $dom_node, %opts );&lt;br /&gt;
 &lt;br /&gt;
 $dom_node = $xml-&amp;gt;clone( $dom_node ); # deep&lt;br /&gt;
 $dom_node = $xml-&amp;gt;clone_node( $dom_node ); # shallow&lt;br /&gt;
 &lt;br /&gt;
 $dom_node = $xml-&amp;gt;contents_of( $dom_node ); # clone and return child nodes&lt;br /&gt;
 $utf8_string = $xml-&amp;gt;text_contents_of( $dom_node ); # Return text child nodes as a string&lt;br /&gt;
 &lt;br /&gt;
 $dom_node = $xml-&amp;gt;create_element( $name, %attr );&lt;br /&gt;
 $dom_node = $xml-&amp;gt;create_text_node( $value );&lt;br /&gt;
 $dom_node = $xml-&amp;gt;create_comment( $value );&lt;br /&gt;
 $dom_node = $xml-&amp;gt;create_document_fragment;&lt;br /&gt;
 &lt;br /&gt;
 $bool = $xml-&amp;gt;is( $dom_node, &amp;quot;Text&amp;quot; );&lt;br /&gt;
 &lt;br /&gt;
 $xml-&amp;gt;dispose( $dom_node ); &lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== XHTML ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $xhtml = $repo-&amp;gt;xhtml;&lt;br /&gt;
 &lt;br /&gt;
 $utf8_string = $xhtml-&amp;gt;to_xhtml( $dom_node, %opts ); # remove NS prefixes, fix &amp;lt;script&amp;gt; etc.&lt;br /&gt;
 &lt;br /&gt;
 $xhtml_dom_node = $xhtml-&amp;gt;input_field( $name, $value, %opts ); # nb. type &amp;amp; noenter are now options. noenter prevents the enter being pressed in the input field using javascript&lt;br /&gt;
 $xhtml_dom_node = $xhtml-&amp;gt;hidden_field( $name, $value, %opts ); # tdb: this is used *a lot* and is well defined&lt;br /&gt;
 $xhtml_dom_node = $xhtml-&amp;gt;text_area_field( $name, $value, %opts ); # tdb: value becomes a child text node &lt;br /&gt;
 $xhtml_dom_node = $xhtml-&amp;gt;form( $method, $url );&lt;br /&gt;
 &lt;br /&gt;
 $xhtml_dom_node = $xhtml-&amp;gt;data_element( $name, $value, %opts ); # tdb: render_data_element&lt;br /&gt;
 &lt;br /&gt;
 $page = $xhtml-&amp;gt;page( $map, %opts );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== Page ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $page-&amp;gt;send( %options ); &lt;br /&gt;
 $page-&amp;gt;write_to_file( $filename );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== DataObj ===&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 $dataobj = $dataset-&amp;gt;dataobj( $id );&lt;br /&gt;
 $dataobj-&amp;gt;delete;&lt;br /&gt;
 $dataobj-&amp;gt;commit( $force );&lt;br /&gt;
 &lt;br /&gt;
 $dataset = $dataobj-&amp;gt;dataset;&lt;br /&gt;
 $repo = $dataobj-&amp;gt;repository;&lt;br /&gt;
 &lt;br /&gt;
 $id = $dataobj-&amp;gt;id;&lt;br /&gt;
 $dataobj-&amp;gt;set_value( $fieldname, $value );&lt;br /&gt;
 $value = $dataobj-&amp;gt;value( $fieldname );&lt;br /&gt;
 \@value = $dataobj-&amp;gt;value( $fieldname ); # multiple&lt;br /&gt;
 $boolean = $dataobj-&amp;gt;is_set( $fieldname );&lt;br /&gt;
 &lt;br /&gt;
 $xhtml = $dataobj-&amp;gt;render_value( $fieldname );&lt;br /&gt;
 $xhtml = $dataobj-&amp;gt;render_citation( $style, %opts );&lt;br /&gt;
 &lt;br /&gt;
 $uri = $dataobj-&amp;gt;uri;&lt;br /&gt;
 $url = $dataobj-&amp;gt;url;&lt;br /&gt;
 &lt;br /&gt;
 $string = $dataobj-&amp;gt;export( $plugin_id, %opts );&lt;br /&gt;
 $dataobj = $dataobj-&amp;gt;create_subobject( $fieldname, $epdata );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
=== MetaField ===&lt;br /&gt;
Now has a handle on both it's repository/session AND dataset.&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&lt;br /&gt;
 my $field = $dataset-&amp;gt;field( $fieldname );&lt;br /&gt;
 &lt;br /&gt;
 $dataset = $field-&amp;gt;dataset;&lt;br /&gt;
 $repo = $field-&amp;gt;repository;&lt;br /&gt;
 &lt;br /&gt;
 $field-&amp;gt;set_property( $property, $value );&lt;br /&gt;
 $value = $field-&amp;gt;property( $property );&lt;br /&gt;
 &lt;br /&gt;
 $name = $field-&amp;gt;name;&lt;br /&gt;
 $type = $field-&amp;gt;type;&lt;br /&gt;
 &lt;br /&gt;
 $xhtml = $field-&amp;gt;render_name;&lt;br /&gt;
 $xhtml = $field-&amp;gt;render_help;&lt;br /&gt;
 $xhtml = $field-&amp;gt;render_value_label( $value );&lt;br /&gt;
 &lt;br /&gt;
 $values = $field-&amp;gt;all_values( %opts );&lt;br /&gt;
 $sorted_list = $field-&amp;gt;sort_values( $unsorted_list );&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=API:EPrints/Plugin/Export/XSLT&amp;diff=12173</id>
		<title>API:EPrints/Plugin/Export/XSLT</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=API:EPrints/Plugin/Export/XSLT&amp;diff=12173"/>
		<updated>2016-09-16T15:12:43Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* SYNOPSIS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Pod2Wiki=_preamble_ &lt;br /&gt;
This page has been automatically generated from the EPrints 3.2 source. Any wiki changes made between the 'Pod2Wiki=*' and 'Edit below this comment' comments will be lost.&lt;br /&gt;
 --&amp;gt;{{API}}{{Pod2Wiki}}{{API:Source|file=perl_lib/EPrints/Plugin/Export/XSLT.pm|package_name=EPrints::Plugin::Export::XSLT}}[[Category:API|XSLT]][[Category:API:EPrints/Plugin/Export|XSLT]][[Category:API:EPrints/Plugin/Export/XSLT|XSLT]]&amp;lt;div&amp;gt;&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=_private_ --&amp;gt;&amp;lt;!-- Pod2Wiki=head_name --&amp;gt;&lt;br /&gt;
==NAME==&lt;br /&gt;
EPrints::Plugin::Export::XSLT - XSLT-based exports&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_synopsis --&amp;gt;&lt;br /&gt;
==SYNOPSIS==&lt;br /&gt;
Create a file in &amp;lt;code&amp;gt;Plugins/Export/XSLT/&amp;lt;/code&amp;gt; called 'Title.xsl' containing:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;perl&amp;quot;&amp;gt;&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;xsl:stylesheet&lt;br /&gt;
	version=&amp;quot;1.0&amp;quot;&lt;br /&gt;
	xmlns:xsl=&amp;quot;http://www.w3.org/1999/XSL/Transform&amp;quot;&lt;br /&gt;
	ept:name=&amp;quot;Titles&amp;quot;&lt;br /&gt;
	ept:visible=&amp;quot;all&amp;quot;&lt;br /&gt;
	ept:advertise=&amp;quot;1&amp;quot;&lt;br /&gt;
	ept:accept=&amp;quot;list/eprint dataobj/eprint&amp;quot;&lt;br /&gt;
	ept:mimetype=&amp;quot;application/xml; charset=utf-8&amp;quot;&lt;br /&gt;
	ept:qs=&amp;quot;0.1&amp;quot;&lt;br /&gt;
	xmlns:ept=&amp;quot;http://eprints.org/ep2/xslt/1.0&amp;quot;&lt;br /&gt;
	xmlns:ep=&amp;quot;http://eprints.org/ep2/data/2.0&amp;quot;&lt;br /&gt;
	exclude-result-prefixes=&amp;quot;ept ep&amp;quot;&lt;br /&gt;
&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;xsl:param name=&amp;quot;results&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;xsl:template match=&amp;quot;text()&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;xsl:template match=&amp;quot;ept:template&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;titles&amp;gt;&amp;lt;xsl:value-of select=&amp;quot;$results&amp;quot;/&amp;gt;&amp;lt;/titles&amp;gt;&lt;br /&gt;
&amp;lt;/xsl:template&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;xsl:template match=&amp;quot;/ep:eprints/ep:eprint&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;title&amp;gt;&amp;lt;xsl:value-of select=&amp;quot;ep:title&amp;quot;/&amp;gt;&amp;lt;/title&amp;gt;&lt;br /&gt;
&amp;lt;/xsl:template&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/xsl:stylesheet&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_description --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==DESCRIPTION==&lt;br /&gt;
This export plugin allows you to use XSL Transforms to export data from EPrints. The plugin is fed EPrints XML and can output any resulting data supported by XSLT.&lt;br /&gt;
&lt;br /&gt;
This is the inverse process of [[API:EPrints/Plugin/Import/XSLT|EPrints::Plugin::Import::XSLT]].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_headers_and_footers --&amp;gt;&lt;br /&gt;
===Headers and Footers===&lt;br /&gt;
You can specify a template to use for your output:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  &amp;amp;lt;xsl:template match=&amp;quot;ept:template&amp;quot;&amp;amp;gt;&lt;br /&gt;
    &amp;amp;lt;html&amp;amp;gt;&lt;br /&gt;
      &amp;amp;lt;body&amp;amp;gt;&lt;br /&gt;
        &amp;amp;lt;xsl:value-of select=&amp;quot;$results&amp;quot;/&amp;amp;gt;&lt;br /&gt;
      &amp;amp;lt;/body&amp;amp;gt;&lt;br /&gt;
    &amp;amp;lt;/html&amp;amp;gt;&lt;br /&gt;
  &amp;amp;lt;/xsl:template&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: you can output unbalanced XML by using disable-output-escaping:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  &amp;amp;lt;xsl:template match=&amp;quot;ept:template&amp;quot;&amp;amp;gt;&lt;br /&gt;
    &amp;amp;lt;xsl:text disable-output-escaping=&amp;quot;yes&amp;quot;&amp;amp;gt;&lt;br /&gt;
      &amp;amp;amp;lt;html&amp;amp;amp;gt;&lt;br /&gt;
        &amp;amp;amp;lt;body&amp;amp;amp;gt;&lt;br /&gt;
    &amp;amp;lt;/xsl:text&amp;amp;gt;&lt;br /&gt;
    &amp;amp;lt;xsl:value-of select=&amp;quot;$results&amp;quot;/&amp;amp;gt;&lt;br /&gt;
  &amp;amp;lt;/xsl:template&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_controlling_xml_declarations --&amp;gt;&lt;br /&gt;
===Controlling XML Declarations===&lt;br /&gt;
If your stylesheet outputs XML (the default):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  &amp;amp;lt;xsl:output method=&amp;quot;xml&amp;quot;/&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The XML declaration will only be outputted once at the start of the export, regardless of how many records there are.&lt;br /&gt;
&lt;br /&gt;
To output as XML and suppress the XML declaration entirely define an empty prefix:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  &amp;amp;lt;xsl:stylesheet&lt;br /&gt;
    xmlns:ept=&amp;quot;http://eprints.org/ep2/xslt/1.0&amp;quot;&lt;br /&gt;
    ept:prefix=&amp;quot;&amp;quot;&lt;br /&gt;
  &amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_plugin_options --&amp;gt;&lt;br /&gt;
==PLUGIN OPTIONS==&lt;br /&gt;
All attributes on &amp;amp;lt;xsl:stylesheet&amp;amp;gt; that are in the EPT namespace are treated as plugin parameters. In addition to those parameters used by all [[API:EPrints/Plugin/Export|EPrints::Plugin::Export]] plugins XSLT uses:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  prefix&lt;br /&gt;
    Value is printed before any content (defaults to XML decl.)&lt;br /&gt;
  postfix&lt;br /&gt;
    Value is printed after any content.&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_stylesheet_parameters --&amp;gt;&lt;br /&gt;
==STYLESHEET PARAMETERS==&lt;br /&gt;
The following parameters are passed to the transform for each item:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;  total&lt;br /&gt;
    Total items in result set.&lt;br /&gt;
  position&lt;br /&gt;
    1-indexed position in result set.&lt;br /&gt;
  dataset&lt;br /&gt;
    Base id of the item's dataset (e.g. &amp;quot;eprint&amp;quot;).&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_extended_functions --&amp;gt;&lt;br /&gt;
==EXTENDED FUNCTIONS==&lt;br /&gt;
The standard EPrints global extended XPath functions are supported, see [[API:EPrints/XSLT|EPrints::XSLT]].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_see_also --&amp;gt;&lt;br /&gt;
==SEE ALSO==&lt;br /&gt;
[[API:EPrints/Plugin/Export|EPrints::Plugin::Export]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=head_copyright --&amp;gt;&lt;br /&gt;
==COPYRIGHT==&lt;br /&gt;
Copyright 2000-2011 University of Southampton.&lt;br /&gt;
&lt;br /&gt;
This file is part of EPrints http://www.eprints.org/.&lt;br /&gt;
&lt;br /&gt;
EPrints is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.&lt;br /&gt;
&lt;br /&gt;
EPrints is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public License for more details.&lt;br /&gt;
&lt;br /&gt;
You should have received a copy of the GNU Lesser General Public License along with EPrints.  If not, see http://www.gnu.org/licenses/.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Pod2Wiki= --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Pod2Wiki=_postamble_ --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Edit below this comment --&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_Debian/Ubuntu&amp;diff=12134</id>
		<title>Installing EPrints on Debian/Ubuntu</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_Debian/Ubuntu&amp;diff=12134"/>
		<updated>2016-08-01T08:49:18Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: video no longer plays&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Debian and Ubuntu]]&lt;br /&gt;
[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=APT Mirrors=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Add one of the following mirrors (2 lines) to your /etc/apt/sources.list file as the root user. Please ensure that there is only one set in the file or you may not experience the correct behaviour.&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==EPrints Latest==&lt;br /&gt;
&lt;br /&gt;
To install the testing build add the following to /etc/apt/sources.list:&lt;br /&gt;
&lt;br /&gt;
===Stable Builds===&lt;br /&gt;
&lt;br /&gt;
 deb http://deb.eprints.org/ stable/&lt;br /&gt;
&lt;br /&gt;
=Installing Eprints via apt-get&lt;br /&gt;
&lt;br /&gt;
To install Eprints and all its dependencies execute the following (as root):&lt;br /&gt;
&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install eprints&lt;br /&gt;
&lt;br /&gt;
=Setting up a Repository=&lt;br /&gt;
You should now have a working installation of eprints in /usr/share/eprints3/. Please follow the on-screen instructions to set up an eprints repository. You probably want to start with (as root):&lt;br /&gt;
&lt;br /&gt;
'''For more information about setting up an EPrints repository take a look at [[Getting Started with EPrints 3]]'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Read First: Known issues with the Debian/Ubuntu package can be found at [[Debian Known Issues]].&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 su eprints&lt;br /&gt;
 cd&lt;br /&gt;
 ./bin/epadmin create&lt;br /&gt;
 logout&lt;br /&gt;
 a2ensite eprints3&lt;br /&gt;
 apache2ctl restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have any problems getting set up you can get free help and support from the EP-Tech mailing list. {{EPrintsTech}}&lt;br /&gt;
&lt;br /&gt;
== Setting up your crontab ==&lt;br /&gt;
&lt;br /&gt;
See [[Automating your maintenance]]&lt;br /&gt;
&lt;br /&gt;
=Getting and Compiling from Source (not required)=&lt;br /&gt;
&lt;br /&gt;
To install dependencies and retrieve the Eprints source execute the following:&lt;br /&gt;
&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get build-dep eprints&lt;br /&gt;
 apt-get source eprints&lt;br /&gt;
&lt;br /&gt;
The source will be saved to a tarball in the current directory.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Issues with Ubuntu 13/14 (Apache 2.3/2.4)=&lt;br /&gt;
&lt;br /&gt;
Apache 2.3+ and PERL v5.16+ introduce a few changes which break EPrints.&lt;br /&gt;
&lt;br /&gt;
A complete HOW-TO guide to install EPrints3 on Ubuntu 14.04 is available [http://wiki.unimas.my/unimaswiki//bin/view/HOW-TO,+Tutorial+&amp;amp;+User+Manual/HOW-TO+:+Install+Eprints+v3.3.12++on+Ubuntu+14.04+With+LDAP+Authentication here]&lt;br /&gt;
&lt;br /&gt;
Current patches on github are:&lt;br /&gt;
&lt;br /&gt;
* See last comment on https://github.com/eprints/eprints/issues/214  [ use of remote_ip ]&lt;br /&gt;
* https://github.com/eprints/eprints/issues/237 [ NameVirtualHost deprecated ]&lt;br /&gt;
* https://github.com/eprints/eprints/issues/236 [ Order allow,deny deprecated ]&lt;br /&gt;
* https://github.com/eprints/eprints/commit/157db0d27d423d38f9c0fc31ce47e519cd861d45 [ utf8::decode and URI parameters ]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ensure that mpm_prefork module is enabled in /etc/apache2/mods-enabled (among others).&lt;br /&gt;
&lt;br /&gt;
Complete list of modules for a working repository include the following (although some may be surplus to requirements e.g. php5 is not strictly necessary)&lt;br /&gt;
&lt;br /&gt;
*access_compat.load                    &lt;br /&gt;
*alias.conf                                     &lt;br /&gt;
*alias.load                               &lt;br /&gt;
*auth_basic.load                             &lt;br /&gt;
*authn_core.load&lt;br /&gt;
*authn_file.load&lt;br /&gt;
*authz_core.load&lt;br /&gt;
*authz_host.load&lt;br /&gt;
*authz_user.load&lt;br /&gt;
*autoindex.conf&lt;br /&gt;
*autoindex.load&lt;br /&gt;
*deflate.conf&lt;br /&gt;
*deflate.load&lt;br /&gt;
*dir.conf&lt;br /&gt;
*dir.load &lt;br /&gt;
*env.load&lt;br /&gt;
*filter.load&lt;br /&gt;
*mime.conf&lt;br /&gt;
*mime.load&lt;br /&gt;
*mpm_prefork.conf&lt;br /&gt;
*mpm_prefork.load&lt;br /&gt;
*negotiation.conf&lt;br /&gt;
*negotiation.load&lt;br /&gt;
*perl.load&lt;br /&gt;
*php5.conf&lt;br /&gt;
*php5.load&lt;br /&gt;
*setenvif.conf&lt;br /&gt;
*setenvif.load&lt;br /&gt;
*status.conf&lt;br /&gt;
*status.load&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading_EPrints_3_versions&amp;diff=11964</id>
		<title>Upgrading EPrints 3 versions</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading_EPrints_3_versions&amp;diff=11964"/>
		<updated>2016-02-08T11:19:54Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Upgrading]]&lt;br /&gt;
&lt;br /&gt;
EPrints developer Christopher Gutteridge gives the following instructions:&lt;br /&gt;
&lt;br /&gt;
== Upgrading 3.0.x to 3.0.y ==&lt;br /&gt;
&lt;br /&gt;
This is very easy - just run &amp;lt;tt&amp;gt;configure&amp;lt;/tt&amp;gt; with the &lt;br /&gt;
&amp;lt;tt&amp;gt;--prefix&amp;lt;/tt&amp;gt; set to the location of the current repo (you may also need to set the --with-user and --with-group options). Then run install.pl to upgrade the software.  Then run&lt;br /&gt;
&lt;br /&gt;
 epadmin upgrade REPOID&lt;br /&gt;
&lt;br /&gt;
For each repository to update the database. Normally minor updates would not update the db at all. In this case all it does is add an SQL index to make things go faster. Restart the webserver in indexer after an upgrade. (or better, shut them off before you start to upgrade)&lt;br /&gt;
&lt;br /&gt;
(lightly edited from [http://www.eprints.org/tech.php/6598.html], 2007-04-13 to eprints-tech)&lt;br /&gt;
&lt;br /&gt;
== Upgrading 3.0.x to 3.1.x ==&lt;br /&gt;
&lt;br /&gt;
This is not yet widely tested, so at your own risk. Initial notes on 3.1.0-beta-2.&lt;br /&gt;
* large repositories can take a significant chunk of time to run epadmin upgrade (many minutes)&lt;br /&gt;
* &amp;quot;Views&amp;quot; get a little screwed up as the new configuration options are slightly altered.&lt;br /&gt;
* [[New Features in EPrints 3.1]] has a list of suggested configuration changes. The &amp;quot;variations&amp;quot; option replaces &amp;quot;subheadings&amp;quot; option.&lt;br /&gt;
&lt;br /&gt;
Known issues:&lt;br /&gt;
* epadmin upgrade reports lots of SQL errors, but these don't cause any problems &lt;br /&gt;
* VLit plugin is broken &lt;br /&gt;
* beta-2 has a bug which means &amp;quot;Smith, J&amp;quot; searches don't work on names but searching &amp;quot;Smith&amp;quot; does.&lt;br /&gt;
* &amp;quot;include&amp;quot; option in view.pl is being ignored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrading 3.1.x to 3.1.y ==&lt;br /&gt;
* unpack tar file to /[path]&lt;br /&gt;
* (as root) cd /[path]/eprints-3.1.y&lt;br /&gt;
* ./configure&lt;br /&gt;
* ./install.pl&lt;br /&gt;
* (as eprints) cd /opt/eprints3&lt;br /&gt;
* epadmin upgrade [repoid]&lt;br /&gt;
* epadmin update [repoid]&lt;br /&gt;
* restart Apache ( /etc/init.d/apache2 force-reload )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrading using rpm (based on upgrading from 3.3.11 to 3.3.13) ==&lt;br /&gt;
* download the package for the version of EPrints you want to use to a folder of your choice (this is the rpm file)&lt;br /&gt;
* (as root) rpm -Uvh [rpm file] (e.g. eprints-3.3.13-1.el6.noarch.rpm)&lt;br /&gt;
* (as eprints) cd /usr/share/eprints&lt;br /&gt;
* bin/epadmin upgrade [repoid]&lt;br /&gt;
* bin/epadmin update [repoid]&lt;br /&gt;
* restart Apache and indexer&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Coversheets&amp;diff=11963</id>
		<title>Coversheets</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Coversheets&amp;diff=11963"/>
		<updated>2016-01-26T14:24:28Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Known issue with Centos 7 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Bazaar Package]]&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The purpose of the Coversheets is to add a front and/or back covering page to a PDF document uploaded to an EPrints repository.&lt;br /&gt;
&lt;br /&gt;
Coversheets work by using a user-defined [https://www.openoffice.org/ Apache OpenOffice] coversheet template uploaded to your EPrints repository.  This template is then populated with the predefined attributes for the particular EPrint, before being attached to the front (or if specified, back) of any PDF documents uploaded for that EPrint.  To do this a number of dependencies need to be installed:&lt;br /&gt;
* '''Ghostscript''' or '''PDFtk''':  Either of these can be used to attach the coversheet to the rest of the PDF document.&lt;br /&gt;
* '''Apache OpenOffice''': This is used to open up the coversheet template, so that a coversheet for a particular EPrint can be created.&lt;br /&gt;
* '''Oracle (Sun) Java''': This is required to run the script to interact with OpenOffice and replace the templates tags with the appropriate EPrint attributes (title, authors, etc.).&lt;br /&gt;
* '''Perl Modules''': Needed for EPrints to interact with OpenOffice.&lt;br /&gt;
&lt;br /&gt;
The instructions below provide guidance on testing and using the Coversheets Bazaar package on an EPrints 3.3 repository running on either Debian or RedHat based Linux distributions.  These instructions are intended to be sufficiently generic to be interpreted for use when installing on other Linux distributions.&lt;br /&gt;
&lt;br /&gt;
==Installing Dependencies==&lt;br /&gt;
&lt;br /&gt;
===GhostScript or PDFtk===&lt;br /&gt;
The Coversheets Bazaar package requires either '''PDFtk''' or '''Ghostscript''' to attach the generated coversheet to the rest of the PDF document.  For the more recent Linux distributions (e.g. Ubuntu 14.04, Debian 7 and RedHat/CentOS 7) Ghostscript is recommended as this is easier to install and more reliable, (e.g. it can reliably attach the coversheet without breaking the character encoding of the rest of the document, so you can still copy and paste out sections of the document).  However, it may be less straightforward to get Ghostscript working for Coversheets on earlier distributions of Linux (e.g. pre Ubuntu 12.04 and RedHat/CentOS 6)&lt;br /&gt;
&lt;br /&gt;
====Ghostscript====&lt;br /&gt;
Installing Ghostscript just requires a number of Linux packages.  As root or with sudo run the appropriate following command:&lt;br /&gt;
* Debian/Ubuntu:&lt;br /&gt;
  apt-get install ghostscript gsfonts gsfonts-other libgs9 libgs9-common&lt;br /&gt;
* RedHat/Fedora/CentOS:&lt;br /&gt;
  yum install ghostscript ghostscript-devel ghostscript-fonts ghostscript-gtk&lt;br /&gt;
&lt;br /&gt;
If you installed EPrints using the DEB or RPM package, it is likely many if not all of these packages will already be installed.&lt;br /&gt;
&lt;br /&gt;
====PDFtk====&lt;br /&gt;
'''N.B. If you have already installed Ghostscript you do not need to install PDFtk as well.'''&lt;br /&gt;
&lt;br /&gt;
As root or using sudo install '''gcj''', '''g++''' and '''make''' so you can compile '''pdftk'''.&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install gcj-jdk g++ make&lt;br /&gt;
* '''RedHat/Fedora/CentOS'''&lt;br /&gt;
  yum install gcc-java gcc-c++ make&lt;br /&gt;
&lt;br /&gt;
Next, download and compile '''pdftk''' and deploy it in '''/usr/bin/'''.&lt;br /&gt;
* Substitute '''LinuxDist''' for '''Debian''' on Debian/Ubuntu distributions and '''Redhat''' for RedHat/Fedora/CentOS distributions.&lt;br /&gt;
* If you are using '''MakeFile.Debian''' check your version of gcj (gcj --version).  You will then need to change '''VERSUFF''' in '''MakeFile.Debian''' to your version number but only the first two points of the version (e.g. 4.8.2 = 4.8).&lt;br /&gt;
  wget https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk-2.02-src.zip&lt;br /&gt;
  unzip pdftk-2.02-src.zip&lt;br /&gt;
  cd pdftk-2.02-dist/pdftk&lt;br /&gt;
  make -f Makefile.LinuxDist&lt;br /&gt;
  mv pdftk /usr/bin/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Oracle (Sun) Java===&lt;br /&gt;
Oracle (Sun) Java is required to make use of the Coversheets package.  By default this is not available in the standard package repositories of most Linux distributions.  Follow the instructions below (as the root user or with sudo) to install Oracle (Sun) Java on your Linux distribution:&lt;br /&gt;
&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install python-software-properties&lt;br /&gt;
  add-apt-repository ppa:webupd8team/java&lt;br /&gt;
  apt-get update&lt;br /&gt;
  apt-get install oracle-java8-installer&lt;br /&gt;
* When prompted agree to the license agreement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''RedHat/Fedora/CentOS'''&lt;br /&gt;
** Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html and agree to the licence conditions.&lt;br /&gt;
** Download the appropriate .rpm package (i.e. i586 or x64) for you system architecture.&lt;br /&gt;
** Install the RPM from the command line, (substitute for '''&amp;lt;version&amp;gt;''' and '''&amp;lt;arch&amp;gt;''' based on the filename of the RPM you actually downloaded):&lt;br /&gt;
  rpm -Uvh jdk-8u&amp;lt;version&amp;gt;-linux-&amp;lt;arch&amp;gt;.rpm&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Perl Modules===&lt;br /&gt;
Before installing the Perl modules make sure that '''make''' and '''gcc''' are installed as these are needed to build the OpenOffice Perl module.  Run the appropriate command below as root or using sudo.&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install make gcc&lt;br /&gt;
* '''RedHat/Fedora/Centos'''&lt;br /&gt;
  yum install make gcc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As the root user install the following Perl modules using CPAN.  Choose the default option for any prompted questions.&lt;br /&gt;
  cpan ExtUtils::MakeMaker OpenOffice::OODoc PDF::API2 ADAMK/Archive-Zip-1.30.tar.gz&lt;br /&gt;
&lt;br /&gt;
'''N.B.'''&lt;br /&gt;
# If you have not had to install any CPAN modules up to now ,you may be prompted to configure CPAN before installing these modules, if so always choose the default option provided.&lt;br /&gt;
# For Archive::Zip it is recommended to use the specific version 1.30 tarball (as specified above).  CPAN will download this specific tarball as part of the installation, like it would for non-version specific modules.  The reason for using this specific version is, that as of at least 28th April 2015 the latest CPAN module has a bug, which means it does not work as required for EPrints Coversheet purposes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apache OpenOffice===&lt;br /&gt;
Download the tarballed package of OpenOffice 3.4.1 for your Linux distribution. Later and some earlier versions of OpenOffice should work just as well but 3.4.1 is tried and tested.  Then extract your DEB or RPM packages and install as root (or with sudo) using  '''dpkg''' or '''rpm''' as appropriate.&lt;br /&gt;
 &lt;br /&gt;
* Debian/Ubuntu (64-bit):&lt;br /&gt;
  wget http://downloads.sourceforge.net/project/openofficeorg.mirror/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US.tar.gz&lt;br /&gt;
  tar -xzvf Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US.tar.gz&lt;br /&gt;
  mv en-US Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US&lt;br /&gt;
  dpkg -i Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US/DEBS/*.deb&lt;br /&gt;
  &lt;br /&gt;
* RedHat/Fedora/CentOS (64-bit):&lt;br /&gt;
  wget http://downloads.sourceforge.net/project/openofficeorg.mirror/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz&lt;br /&gt;
  tar -xzvf Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz&lt;br /&gt;
  mv en-US Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US&lt;br /&gt;
  rpm -Uvh Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US/RPMS/*.rpm&lt;br /&gt;
&lt;br /&gt;
* ''N.B. For 32-bit versions remove '-64' from each of the lines above.''  You can check this by running the following command.  If it returns something with '64' in it, it is 64-bit, if it does not, it is almost certainly 32-bit.&lt;br /&gt;
  uname -i&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Enabling Coversheets ==&lt;br /&gt;
* Login to the EPrints Archive as an administrator and go to the '''Admin''' page and under the '''System Tools''' tab, click on '''EPrints Bazaar''' button.&lt;br /&gt;
* On the EPrints Bazaar page scroll and click on '''Enable''' next to the '''OpenOffice Toolkit''' package.&lt;br /&gt;
* If the OpenOffice Toolkit package installs successfully, click on '''Enable''' next the '''Coversheets''' package.&lt;br /&gt;
* If the Coversheets package successfully installed.  Click on the '''Admin''' link in the top menu bar and under the '''System Tools''' tab click on '''Start OpenOffice'''.&lt;br /&gt;
* When the page reloads next click on '''Start Indexer''', if t is not already started.&lt;br /&gt;
* Coversheets should now be installed and ready to go.  You can test this by following the instructions under '''[[#Deploying Coversheets|Deploying Coversheets]]'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Deploying Coversheets ==&lt;br /&gt;
* Logged in as an adminstrator, click on '''Manage records''' then '''Coversheets'''.  If you cannot find the the '''Manage records''' link you can go straight to the list of coversheet records at (substituting '''example.eprints.org''' for the hostname of you Eprints repository):&lt;br /&gt;
  http://example.eprints.org/cgi/users/home?screen=Listing&amp;amp;dataset=coversheet&lt;br /&gt;
* Under the Coversheets page, click on '''Create New Coversheet'''.  Fill in the '''Name''' and Description fields under '''Apply to''' checked  the types you want to use a coversheet for.and set '''Priority''' to '''1'''.  If you wish to apply the coversheet to other types make sure they are checked as well.&lt;br /&gt;
* Then, under '''Documents''' -&amp;gt; '''Front Page(s)''' upload the template coversheet front page, which you can adapt from the template at the URL below, before clicking '''Update''' button at the button of the page:&lt;br /&gt;
  http://files.eprints.org/1047/2/frontfile-example.odt&lt;br /&gt;
* When the page reloads, click on the '''Exit'' button to go back to the Coversheet index page.&lt;br /&gt;
* On the Coversheet index page, click on the icon with a green tick next to the coversheet you just added and then click on the '''Activate''' button on the page that loads.&lt;br /&gt;
* Now follow the '''[[#Testing Coversheets|Testing Coversheets]]''' instructions to check that everything is configured and working as expected.&lt;br /&gt;
&lt;br /&gt;
== Testing Coversheets ==&lt;br /&gt;
* Now add an EPrint as usually, ensuring it is of one of the types you selected under '''Apply to''' earlier.&lt;br /&gt;
* Once you have deposited the EPrint and moved it to the repository.  Click on the link to download the PDF.  The PDF will load initially without a coversheet.&lt;br /&gt;
* Click back to go back to the EPrints web interface and click on the '''Admin''' link.&lt;br /&gt;
* On the Admin page click on the '''System Tools''' tab and then click on the '''Status''' button.&lt;br /&gt;
* On the Status page click on the link on the '''Background Task Queue'' row.  On the page that loads you should be able to see a ''''Document:AddCoversheet''' task pending.&lt;br /&gt;
* Once this task disappears from the list, go back to the PDF you loaded previously and do a hard refresh (e.g. '''Ctrl+F5''') of the page.&lt;br /&gt;
* If all has gone to plan your PDF document should now have a coversheet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing your own Coversheet Template ==&lt;br /&gt;
* If you have downloaded the example coversheet template from http://files.eprints.org/1047/1/frontfile.odt you can adapt it for your own EPrints repository by editing it in [https://www.openoffice.org/download/index.html OpenOffice] or [https://www.libreoffice.org/download/libreoffice-fresh/ LibreOffice].  &lt;br /&gt;
** Unfortunately, you cannot edit this in Microsoft Office as the document needs to be saved in .odt format.&lt;br /&gt;
* Once you have opened the example coversheet template in OpenOffice or LibreOffice you can change the logos (images) used and the layout of the page as you choose fit.  &lt;br /&gt;
* Where a word is enclosed with '''##''' either side (e.g. ''##title##'').  Then this will be substituted with the appropriate EPrint attribute.  By default the following tags can be put into a template coversheet to be replaced by the value for that EPrint attribute:&lt;br /&gt;
** ##title## &lt;br /&gt;
** ##type## (e.g. article, conference item, book section, etc.)&lt;br /&gt;
** ##url## (to the EPrint on your EPrints repository)&lt;br /&gt;
** ##date## (of when the EPrint was published)&lt;br /&gt;
** ##citation## (of the EPrint as it would appear in an EPrints search result)&lt;br /&gt;
** ##creators## (list of authors/editors of the EPrint)&lt;br /&gt;
** ##doi_url##&lt;br /&gt;
* Once you have finished your design, before saving make you do not have any white space at the end of the document, as this may cause a blank page to be added between your coversheet and main document.&lt;br /&gt;
* After saving the file, you can upload to your EPrints repository as described in '''[[#Deploying Coversheets|Deploying Coversheets]]'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Adding Extra Coversheet Tags ===&lt;br /&gt;
Extra coversheet tags can be added by editing '''z_coversheet_tags.pl''' under the archives '''cfg/cfg.d/''' directory.&lt;br /&gt;
&lt;br /&gt;
=== Configuring 'Apply to' Options ===&lt;br /&gt;
Additional options (e.g. eprint_status, userid, series, publication, etc.) can be added to the '''$c-&amp;gt;{license_application_fields}''' in '''z_coversheet.pl''' under the archives '''cfg/cfg.d/''' directory.  This will cause these options to appear in the form for editing a particular coversheet.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
=== Troubleshooting whilst Designing your own Coversheet Template ===&lt;br /&gt;
==== Adding and formatting tags on your Coversheet Template ====&lt;br /&gt;
Make sure when you add tags (e.g. ##title##) to your coversheet template you type the whole string in one go.  Try to avoid copying and pasting tags about, especially avoid copy parts of tags.  Also be careful when changing the formatting (e.g. font size, colour, etc.) of a tag, making sure you change the format for the whole tag.  &lt;br /&gt;
&lt;br /&gt;
Not doing these things could lead to the underlying representing of the whole tag being broken up by styling elements, meaning that the coversheet package will no be able to find these tags to substitute them with the appropriate attribute from the EPrint.  So when you come to look at the coversheet for your document, you will see the tag rather than the substituted attribute.&lt;br /&gt;
&lt;br /&gt;
===Known issue with Centos 7===&lt;br /&gt;
/tmp folder on Centos 7 has unexpected behaviours, causing the generated coversheet to disappear. &lt;br /&gt;
&lt;br /&gt;
A solution is to change the tmp directory location to /opt/eprints3/tmp:&lt;br /&gt;
&lt;br /&gt;
in cfg.d/session.pl, add the following to line ~22:&lt;br /&gt;
 $ENV{'TMPDIR'} = &amp;quot;/opt/eprints3/tmp&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
create the directory:&lt;br /&gt;
 mkdir /opt/eprints3/tmp&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Coversheets&amp;diff=11962</id>
		<title>Coversheets</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Coversheets&amp;diff=11962"/>
		<updated>2016-01-26T14:23:44Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Troubleshooting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Bazaar Package]]&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The purpose of the Coversheets is to add a front and/or back covering page to a PDF document uploaded to an EPrints repository.&lt;br /&gt;
&lt;br /&gt;
Coversheets work by using a user-defined [https://www.openoffice.org/ Apache OpenOffice] coversheet template uploaded to your EPrints repository.  This template is then populated with the predefined attributes for the particular EPrint, before being attached to the front (or if specified, back) of any PDF documents uploaded for that EPrint.  To do this a number of dependencies need to be installed:&lt;br /&gt;
* '''Ghostscript''' or '''PDFtk''':  Either of these can be used to attach the coversheet to the rest of the PDF document.&lt;br /&gt;
* '''Apache OpenOffice''': This is used to open up the coversheet template, so that a coversheet for a particular EPrint can be created.&lt;br /&gt;
* '''Oracle (Sun) Java''': This is required to run the script to interact with OpenOffice and replace the templates tags with the appropriate EPrint attributes (title, authors, etc.).&lt;br /&gt;
* '''Perl Modules''': Needed for EPrints to interact with OpenOffice.&lt;br /&gt;
&lt;br /&gt;
The instructions below provide guidance on testing and using the Coversheets Bazaar package on an EPrints 3.3 repository running on either Debian or RedHat based Linux distributions.  These instructions are intended to be sufficiently generic to be interpreted for use when installing on other Linux distributions.&lt;br /&gt;
&lt;br /&gt;
==Installing Dependencies==&lt;br /&gt;
&lt;br /&gt;
===GhostScript or PDFtk===&lt;br /&gt;
The Coversheets Bazaar package requires either '''PDFtk''' or '''Ghostscript''' to attach the generated coversheet to the rest of the PDF document.  For the more recent Linux distributions (e.g. Ubuntu 14.04, Debian 7 and RedHat/CentOS 7) Ghostscript is recommended as this is easier to install and more reliable, (e.g. it can reliably attach the coversheet without breaking the character encoding of the rest of the document, so you can still copy and paste out sections of the document).  However, it may be less straightforward to get Ghostscript working for Coversheets on earlier distributions of Linux (e.g. pre Ubuntu 12.04 and RedHat/CentOS 6)&lt;br /&gt;
&lt;br /&gt;
====Ghostscript====&lt;br /&gt;
Installing Ghostscript just requires a number of Linux packages.  As root or with sudo run the appropriate following command:&lt;br /&gt;
* Debian/Ubuntu:&lt;br /&gt;
  apt-get install ghostscript gsfonts gsfonts-other libgs9 libgs9-common&lt;br /&gt;
* RedHat/Fedora/CentOS:&lt;br /&gt;
  yum install ghostscript ghostscript-devel ghostscript-fonts ghostscript-gtk&lt;br /&gt;
&lt;br /&gt;
If you installed EPrints using the DEB or RPM package, it is likely many if not all of these packages will already be installed.&lt;br /&gt;
&lt;br /&gt;
====PDFtk====&lt;br /&gt;
'''N.B. If you have already installed Ghostscript you do not need to install PDFtk as well.'''&lt;br /&gt;
&lt;br /&gt;
As root or using sudo install '''gcj''', '''g++''' and '''make''' so you can compile '''pdftk'''.&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install gcj-jdk g++ make&lt;br /&gt;
* '''RedHat/Fedora/CentOS'''&lt;br /&gt;
  yum install gcc-java gcc-c++ make&lt;br /&gt;
&lt;br /&gt;
Next, download and compile '''pdftk''' and deploy it in '''/usr/bin/'''.&lt;br /&gt;
* Substitute '''LinuxDist''' for '''Debian''' on Debian/Ubuntu distributions and '''Redhat''' for RedHat/Fedora/CentOS distributions.&lt;br /&gt;
* If you are using '''MakeFile.Debian''' check your version of gcj (gcj --version).  You will then need to change '''VERSUFF''' in '''MakeFile.Debian''' to your version number but only the first two points of the version (e.g. 4.8.2 = 4.8).&lt;br /&gt;
  wget https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk-2.02-src.zip&lt;br /&gt;
  unzip pdftk-2.02-src.zip&lt;br /&gt;
  cd pdftk-2.02-dist/pdftk&lt;br /&gt;
  make -f Makefile.LinuxDist&lt;br /&gt;
  mv pdftk /usr/bin/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Oracle (Sun) Java===&lt;br /&gt;
Oracle (Sun) Java is required to make use of the Coversheets package.  By default this is not available in the standard package repositories of most Linux distributions.  Follow the instructions below (as the root user or with sudo) to install Oracle (Sun) Java on your Linux distribution:&lt;br /&gt;
&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install python-software-properties&lt;br /&gt;
  add-apt-repository ppa:webupd8team/java&lt;br /&gt;
  apt-get update&lt;br /&gt;
  apt-get install oracle-java8-installer&lt;br /&gt;
* When prompted agree to the license agreement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''RedHat/Fedora/CentOS'''&lt;br /&gt;
** Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html and agree to the licence conditions.&lt;br /&gt;
** Download the appropriate .rpm package (i.e. i586 or x64) for you system architecture.&lt;br /&gt;
** Install the RPM from the command line, (substitute for '''&amp;lt;version&amp;gt;''' and '''&amp;lt;arch&amp;gt;''' based on the filename of the RPM you actually downloaded):&lt;br /&gt;
  rpm -Uvh jdk-8u&amp;lt;version&amp;gt;-linux-&amp;lt;arch&amp;gt;.rpm&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Perl Modules===&lt;br /&gt;
Before installing the Perl modules make sure that '''make''' and '''gcc''' are installed as these are needed to build the OpenOffice Perl module.  Run the appropriate command below as root or using sudo.&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install make gcc&lt;br /&gt;
* '''RedHat/Fedora/Centos'''&lt;br /&gt;
  yum install make gcc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As the root user install the following Perl modules using CPAN.  Choose the default option for any prompted questions.&lt;br /&gt;
  cpan ExtUtils::MakeMaker OpenOffice::OODoc PDF::API2 ADAMK/Archive-Zip-1.30.tar.gz&lt;br /&gt;
&lt;br /&gt;
'''N.B.'''&lt;br /&gt;
# If you have not had to install any CPAN modules up to now ,you may be prompted to configure CPAN before installing these modules, if so always choose the default option provided.&lt;br /&gt;
# For Archive::Zip it is recommended to use the specific version 1.30 tarball (as specified above).  CPAN will download this specific tarball as part of the installation, like it would for non-version specific modules.  The reason for using this specific version is, that as of at least 28th April 2015 the latest CPAN module has a bug, which means it does not work as required for EPrints Coversheet purposes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apache OpenOffice===&lt;br /&gt;
Download the tarballed package of OpenOffice 3.4.1 for your Linux distribution. Later and some earlier versions of OpenOffice should work just as well but 3.4.1 is tried and tested.  Then extract your DEB or RPM packages and install as root (or with sudo) using  '''dpkg''' or '''rpm''' as appropriate.&lt;br /&gt;
 &lt;br /&gt;
* Debian/Ubuntu (64-bit):&lt;br /&gt;
  wget http://downloads.sourceforge.net/project/openofficeorg.mirror/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US.tar.gz&lt;br /&gt;
  tar -xzvf Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US.tar.gz&lt;br /&gt;
  mv en-US Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US&lt;br /&gt;
  dpkg -i Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US/DEBS/*.deb&lt;br /&gt;
  &lt;br /&gt;
* RedHat/Fedora/CentOS (64-bit):&lt;br /&gt;
  wget http://downloads.sourceforge.net/project/openofficeorg.mirror/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz&lt;br /&gt;
  tar -xzvf Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz&lt;br /&gt;
  mv en-US Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US&lt;br /&gt;
  rpm -Uvh Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US/RPMS/*.rpm&lt;br /&gt;
&lt;br /&gt;
* ''N.B. For 32-bit versions remove '-64' from each of the lines above.''  You can check this by running the following command.  If it returns something with '64' in it, it is 64-bit, if it does not, it is almost certainly 32-bit.&lt;br /&gt;
  uname -i&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Enabling Coversheets ==&lt;br /&gt;
* Login to the EPrints Archive as an administrator and go to the '''Admin''' page and under the '''System Tools''' tab, click on '''EPrints Bazaar''' button.&lt;br /&gt;
* On the EPrints Bazaar page scroll and click on '''Enable''' next to the '''OpenOffice Toolkit''' package.&lt;br /&gt;
* If the OpenOffice Toolkit package installs successfully, click on '''Enable''' next the '''Coversheets''' package.&lt;br /&gt;
* If the Coversheets package successfully installed.  Click on the '''Admin''' link in the top menu bar and under the '''System Tools''' tab click on '''Start OpenOffice'''.&lt;br /&gt;
* When the page reloads next click on '''Start Indexer''', if t is not already started.&lt;br /&gt;
* Coversheets should now be installed and ready to go.  You can test this by following the instructions under '''[[#Deploying Coversheets|Deploying Coversheets]]'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Deploying Coversheets ==&lt;br /&gt;
* Logged in as an adminstrator, click on '''Manage records''' then '''Coversheets'''.  If you cannot find the the '''Manage records''' link you can go straight to the list of coversheet records at (substituting '''example.eprints.org''' for the hostname of you Eprints repository):&lt;br /&gt;
  http://example.eprints.org/cgi/users/home?screen=Listing&amp;amp;dataset=coversheet&lt;br /&gt;
* Under the Coversheets page, click on '''Create New Coversheet'''.  Fill in the '''Name''' and Description fields under '''Apply to''' checked  the types you want to use a coversheet for.and set '''Priority''' to '''1'''.  If you wish to apply the coversheet to other types make sure they are checked as well.&lt;br /&gt;
* Then, under '''Documents''' -&amp;gt; '''Front Page(s)''' upload the template coversheet front page, which you can adapt from the template at the URL below, before clicking '''Update''' button at the button of the page:&lt;br /&gt;
  http://files.eprints.org/1047/2/frontfile-example.odt&lt;br /&gt;
* When the page reloads, click on the '''Exit'' button to go back to the Coversheet index page.&lt;br /&gt;
* On the Coversheet index page, click on the icon with a green tick next to the coversheet you just added and then click on the '''Activate''' button on the page that loads.&lt;br /&gt;
* Now follow the '''[[#Testing Coversheets|Testing Coversheets]]''' instructions to check that everything is configured and working as expected.&lt;br /&gt;
&lt;br /&gt;
== Testing Coversheets ==&lt;br /&gt;
* Now add an EPrint as usually, ensuring it is of one of the types you selected under '''Apply to''' earlier.&lt;br /&gt;
* Once you have deposited the EPrint and moved it to the repository.  Click on the link to download the PDF.  The PDF will load initially without a coversheet.&lt;br /&gt;
* Click back to go back to the EPrints web interface and click on the '''Admin''' link.&lt;br /&gt;
* On the Admin page click on the '''System Tools''' tab and then click on the '''Status''' button.&lt;br /&gt;
* On the Status page click on the link on the '''Background Task Queue'' row.  On the page that loads you should be able to see a ''''Document:AddCoversheet''' task pending.&lt;br /&gt;
* Once this task disappears from the list, go back to the PDF you loaded previously and do a hard refresh (e.g. '''Ctrl+F5''') of the page.&lt;br /&gt;
* If all has gone to plan your PDF document should now have a coversheet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing your own Coversheet Template ==&lt;br /&gt;
* If you have downloaded the example coversheet template from http://files.eprints.org/1047/1/frontfile.odt you can adapt it for your own EPrints repository by editing it in [https://www.openoffice.org/download/index.html OpenOffice] or [https://www.libreoffice.org/download/libreoffice-fresh/ LibreOffice].  &lt;br /&gt;
** Unfortunately, you cannot edit this in Microsoft Office as the document needs to be saved in .odt format.&lt;br /&gt;
* Once you have opened the example coversheet template in OpenOffice or LibreOffice you can change the logos (images) used and the layout of the page as you choose fit.  &lt;br /&gt;
* Where a word is enclosed with '''##''' either side (e.g. ''##title##'').  Then this will be substituted with the appropriate EPrint attribute.  By default the following tags can be put into a template coversheet to be replaced by the value for that EPrint attribute:&lt;br /&gt;
** ##title## &lt;br /&gt;
** ##type## (e.g. article, conference item, book section, etc.)&lt;br /&gt;
** ##url## (to the EPrint on your EPrints repository)&lt;br /&gt;
** ##date## (of when the EPrint was published)&lt;br /&gt;
** ##citation## (of the EPrint as it would appear in an EPrints search result)&lt;br /&gt;
** ##creators## (list of authors/editors of the EPrint)&lt;br /&gt;
** ##doi_url##&lt;br /&gt;
* Once you have finished your design, before saving make you do not have any white space at the end of the document, as this may cause a blank page to be added between your coversheet and main document.&lt;br /&gt;
* After saving the file, you can upload to your EPrints repository as described in '''[[#Deploying Coversheets|Deploying Coversheets]]'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Adding Extra Coversheet Tags ===&lt;br /&gt;
Extra coversheet tags can be added by editing '''z_coversheet_tags.pl''' under the archives '''cfg/cfg.d/''' directory.&lt;br /&gt;
&lt;br /&gt;
=== Configuring 'Apply to' Options ===&lt;br /&gt;
Additional options (e.g. eprint_status, userid, series, publication, etc.) can be added to the '''$c-&amp;gt;{license_application_fields}''' in '''z_coversheet.pl''' under the archives '''cfg/cfg.d/''' directory.  This will cause these options to appear in the form for editing a particular coversheet.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
=== Troubleshooting whilst Designing your own Coversheet Template ===&lt;br /&gt;
==== Adding and formatting tags on your Coversheet Template ====&lt;br /&gt;
Make sure when you add tags (e.g. ##title##) to your coversheet template you type the whole string in one go.  Try to avoid copying and pasting tags about, especially avoid copy parts of tags.  Also be careful when changing the formatting (e.g. font size, colour, etc.) of a tag, making sure you change the format for the whole tag.  &lt;br /&gt;
&lt;br /&gt;
Not doing these things could lead to the underlying representing of the whole tag being broken up by styling elements, meaning that the coversheet package will no be able to find these tags to substitute them with the appropriate attribute from the EPrint.  So when you come to look at the coversheet for your document, you will see the tag rather than the substituted attribute.&lt;br /&gt;
&lt;br /&gt;
===Known issue with Centos 7===&lt;br /&gt;
/tmp folder on Centos 7 has unexpected behaviours, causing the generated coversheet to disappear. &lt;br /&gt;
&lt;br /&gt;
A solution is to change the tmp directory location to /opt/eprints3/tmp:&lt;br /&gt;
&lt;br /&gt;
in cfg.d/session.pl, add the following line to line 22:&lt;br /&gt;
 $ENV{'TMPDIR'} = &amp;quot;/opt/eprints3/tmp&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
create the directory:&lt;br /&gt;
 mkdir /opt/eprints3/tmp&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11961</id>
		<title>Installing EPrints on RHEL/Fedora/CentOS</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11961"/>
		<updated>2016-01-22T17:06:41Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Upgrade from previous 3.3 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
&lt;br /&gt;
* RedHat Enterprise/CentOS 7 (earlier versions may work)&lt;br /&gt;
&lt;br /&gt;
==Installing==&lt;br /&gt;
&lt;br /&gt;
Add the rpm.eprints.org repository key:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... the rpm.eprints.org EPrints repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/eprints/noarch/rpm-eprints-org-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 5.x only''' the rpm.eprints.org RHEL updates repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5Server/noarch/rpm-eprints-org-RHEL-5-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 6.x only''' install antiword if installing EPrints 3.2.x or earlier (from 3.3 onwards only used to as a Word -&amp;gt; PDF converter so not strictly necessary):&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/i386/antiword-0.37-1.i386.rpm&lt;br /&gt;
 # or for 64 bit:&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/x86_64/antiword-0.37-1.x86_64.rpm&lt;br /&gt;
&lt;br /&gt;
Upgrade your XML libraries:&lt;br /&gt;
&lt;br /&gt;
 yum upgrade libxml2 libxslt perl-XML-LibXML perl-XML-LibXSLT&lt;br /&gt;
&lt;br /&gt;
Install EPrints 3:&lt;br /&gt;
&lt;br /&gt;
 yum install eprints # 3.3.x and later&lt;br /&gt;
 yum install eprints3 # 3.2.x&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Other sources for dependencies===&lt;br /&gt;
&lt;br /&gt;
The following RPM repositories may be useful for finding other dependencies required by EPrints that aren't part of the core RHEL system.&lt;br /&gt;
&lt;br /&gt;
http://fedoraproject.org/wiki/EPEL - Fedora Extras for RHEL.&lt;br /&gt;
&lt;br /&gt;
http://pkgs.repoforge.org/rpmforge-release/ - RPMforge, which covers a very large range of Perl modules plus others.&lt;br /&gt;
&lt;br /&gt;
[http://www.imagemagick.org/script/binary-releases.php ImageMagick] provide an RPM for RHEL/CentOS 5. At time of writing the RPM requires fftw3, fltk, jasper and openexr which are available from ''RPMForge''. libwebp is available from [http://rpm.eprints.org/RHEL/5/ rpm.eprints.org].&lt;br /&gt;
&lt;br /&gt;
==SELinux==&lt;br /&gt;
&lt;br /&gt;
If you're using SELinux on your server you will need to give Apache read/write access to the documents directory for all repositories you create and the eprints var folder (indexer log, ticker files):&lt;br /&gt;
&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/archives/[repoid]/documents/&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/var/&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
&lt;br /&gt;
[[Getting Started with EPrints 3]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
=== Failed to parse XML file ===&lt;br /&gt;
&lt;br /&gt;
When installing EPrints on RHEL6 (may apply to other versions), If you get the error:&lt;br /&gt;
 Failed to parse XML file:&lt;br /&gt;
 /usr/share/eprints/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined age or title page. If there are more...&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
 sed -i 's/'''&amp;amp;'''nbsp;/ /g' /usr/share/eprints/lib/lang/en/phrases/system.xml&lt;br /&gt;
&lt;br /&gt;
then navigate to the root of your EPrints install (/opt/eprints or /usr/share/eprints) and run&lt;br /&gt;
 bin/generate_views *repository_id*&lt;br /&gt;
 bin/epadmin reload *repository_id*&lt;br /&gt;
&lt;br /&gt;
=== Upgrade from previous 3.3 ===&lt;br /&gt;
After a upgrading from previous 3.3, your existing repository's database may need updating. &lt;br /&gt;
 bin/epadmin update [arcid]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11960</id>
		<title>Installing EPrints on RHEL/Fedora/CentOS</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11960"/>
		<updated>2016-01-22T17:06:08Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
&lt;br /&gt;
* RedHat Enterprise/CentOS 7 (earlier versions may work)&lt;br /&gt;
&lt;br /&gt;
==Installing==&lt;br /&gt;
&lt;br /&gt;
Add the rpm.eprints.org repository key:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... the rpm.eprints.org EPrints repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/eprints/noarch/rpm-eprints-org-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 5.x only''' the rpm.eprints.org RHEL updates repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5Server/noarch/rpm-eprints-org-RHEL-5-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 6.x only''' install antiword if installing EPrints 3.2.x or earlier (from 3.3 onwards only used to as a Word -&amp;gt; PDF converter so not strictly necessary):&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/i386/antiword-0.37-1.i386.rpm&lt;br /&gt;
 # or for 64 bit:&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/x86_64/antiword-0.37-1.x86_64.rpm&lt;br /&gt;
&lt;br /&gt;
Upgrade your XML libraries:&lt;br /&gt;
&lt;br /&gt;
 yum upgrade libxml2 libxslt perl-XML-LibXML perl-XML-LibXSLT&lt;br /&gt;
&lt;br /&gt;
Install EPrints 3:&lt;br /&gt;
&lt;br /&gt;
 yum install eprints # 3.3.x and later&lt;br /&gt;
 yum install eprints3 # 3.2.x&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Other sources for dependencies===&lt;br /&gt;
&lt;br /&gt;
The following RPM repositories may be useful for finding other dependencies required by EPrints that aren't part of the core RHEL system.&lt;br /&gt;
&lt;br /&gt;
http://fedoraproject.org/wiki/EPEL - Fedora Extras for RHEL.&lt;br /&gt;
&lt;br /&gt;
http://pkgs.repoforge.org/rpmforge-release/ - RPMforge, which covers a very large range of Perl modules plus others.&lt;br /&gt;
&lt;br /&gt;
[http://www.imagemagick.org/script/binary-releases.php ImageMagick] provide an RPM for RHEL/CentOS 5. At time of writing the RPM requires fftw3, fltk, jasper and openexr which are available from ''RPMForge''. libwebp is available from [http://rpm.eprints.org/RHEL/5/ rpm.eprints.org].&lt;br /&gt;
&lt;br /&gt;
==SELinux==&lt;br /&gt;
&lt;br /&gt;
If you're using SELinux on your server you will need to give Apache read/write access to the documents directory for all repositories you create and the eprints var folder (indexer log, ticker files):&lt;br /&gt;
&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/archives/[repoid]/documents/&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/var/&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
&lt;br /&gt;
[[Getting Started with EPrints 3]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
=== Failed to parse XML file ===&lt;br /&gt;
&lt;br /&gt;
When installing EPrints on RHEL6 (may apply to other versions), If you get the error:&lt;br /&gt;
 Failed to parse XML file:&lt;br /&gt;
 /usr/share/eprints/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined age or title page. If there are more...&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
 sed -i 's/'''&amp;amp;'''nbsp;/ /g' /usr/share/eprints/lib/lang/en/phrases/system.xml&lt;br /&gt;
&lt;br /&gt;
then navigate to the root of your EPrints install (/opt/eprints or /usr/share/eprints) and run&lt;br /&gt;
 bin/generate_views *repository_id*&lt;br /&gt;
 bin/epadmin reload *repository_id*&lt;br /&gt;
&lt;br /&gt;
=== Upgrade from previous 3.3 ===&lt;br /&gt;
After a upgrading from previous 3.3, your existing repository's database may need updating. &lt;br /&gt;
 epadmin update [arcid]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11959</id>
		<title>Installing EPrints on RHEL/Fedora/CentOS</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11959"/>
		<updated>2016-01-22T15:44:34Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
&lt;br /&gt;
* RedHat Enterprise/CentOS 7 (earlier versions may work)&lt;br /&gt;
&lt;br /&gt;
==Installing==&lt;br /&gt;
&lt;br /&gt;
Add the rpm.eprints.org repository key:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... the rpm.eprints.org EPrints repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/eprints/noarch/rpm-eprints-org-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 5.x only''' the rpm.eprints.org RHEL updates repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5Server/noarch/rpm-eprints-org-RHEL-5-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 6.x only''' install antiword if installing EPrints 3.2.x or earlier (from 3.3 onwards only used to as a Word -&amp;gt; PDF converter so not strictly necessary):&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/i386/antiword-0.37-1.i386.rpm&lt;br /&gt;
 # or for 64 bit:&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/x86_64/antiword-0.37-1.x86_64.rpm&lt;br /&gt;
&lt;br /&gt;
Upgrade your XML libraries:&lt;br /&gt;
&lt;br /&gt;
 yum upgrade libxml2 libxslt perl-XML-LibXML perl-XML-LibXSLT&lt;br /&gt;
&lt;br /&gt;
Install EPrints 3:&lt;br /&gt;
&lt;br /&gt;
 yum install eprints # 3.3.x and later&lt;br /&gt;
 yum install eprints3 # 3.2.x&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Other sources for dependencies===&lt;br /&gt;
&lt;br /&gt;
The following RPM repositories may be useful for finding other dependencies required by EPrints that aren't part of the core RHEL system.&lt;br /&gt;
&lt;br /&gt;
http://fedoraproject.org/wiki/EPEL - Fedora Extras for RHEL.&lt;br /&gt;
&lt;br /&gt;
http://pkgs.repoforge.org/rpmforge-release/ - RPMforge, which covers a very large range of Perl modules plus others.&lt;br /&gt;
&lt;br /&gt;
[http://www.imagemagick.org/script/binary-releases.php ImageMagick] provide an RPM for RHEL/CentOS 5. At time of writing the RPM requires fftw3, fltk, jasper and openexr which are available from ''RPMForge''. libwebp is available from [http://rpm.eprints.org/RHEL/5/ rpm.eprints.org].&lt;br /&gt;
&lt;br /&gt;
==SELinux==&lt;br /&gt;
&lt;br /&gt;
If you're using SELinux on your server you will need to give Apache read/write access to the documents directory for all repositories you create and the eprints var folder (indexer log, ticker files):&lt;br /&gt;
&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/archives/[repoid]/documents/&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/var/&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
&lt;br /&gt;
[[Getting Started with EPrints 3]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
=== Failed to parse XML file ===&lt;br /&gt;
&lt;br /&gt;
When installing EPrints on RHEL6 (may apply to other versions), If you get the error:&lt;br /&gt;
 Failed to parse XML file:&lt;br /&gt;
 /usr/share/eprints/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined age or title page. If there are more...&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
 sed -i 's/'''&amp;amp;'''nbsp;/ /g' /usr/share/eprints/lib/lang/en/phrases/system.xml&lt;br /&gt;
&lt;br /&gt;
then navigate to the root of your EPrints install (/opt/eprints or /usr/share/eprints) and run&lt;br /&gt;
 bin/generate_views *repository_id*&lt;br /&gt;
 bin/epadmin reload *repository_id*&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=EPrints_3.3.15&amp;diff=11920</id>
		<title>EPrints 3.3.15</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=EPrints_3.3.15&amp;diff=11920"/>
		<updated>2015-12-21T14:36:21Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;EPrints 3.3.15 is a minor bugfix release.&lt;br /&gt;
&lt;br /&gt;
Highlights:&lt;br /&gt;
* Added ability to select default import/export plugin. (https://github.com/eprints/eprints/commit/31436002bc3f7f0420cc3db9659a15a3160e9c9c)&lt;br /&gt;
* New feature in epadmin script (https://github.com/eprints/eprints/commit/13c2c3f9ec0df82bf17515c4bf5190c0e139d681)&lt;br /&gt;
* Counter Compliance (https://github.com/eprints/eprints/issues/308)&lt;br /&gt;
* Fixed broken day-of-week and day-of-month logic  (https://github.com/eprints/eprints/commit/be6133d6897909f7fa5b6724429320995e601414)&lt;br /&gt;
* Improve rendering of possible DOI links (https://github.com/eprints/eprints/commit/c11e3bbfb8007b39ce6032caf51a28029b3221f1)&lt;br /&gt;
* Fixes manage deposit screen does not sort on maria db due to sub-query sorting changes. (https://github.com/eprints/eprints/commit/d9dc16acc8f42f233e7aa981821fdebe75be455d)&lt;br /&gt;
* Preview window location fix after the prototype 1.71 update. (https://github.com/eprints/eprints/commit/68307975d5cfcbcd7ec87963b5fc3890d40633f2)&lt;br /&gt;
* Additional checks to remove unnecessary log messages (cleaner log). &lt;br /&gt;
&lt;br /&gt;
For the complete change log, please see [https://github.com/eprints/eprints/compare/v3.3.14...v3.3.15 the Github Comparison Page].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://files.eprints.org/1073/ Download and more info from files.eprints.org]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=EPrints_3.3.15&amp;diff=11919</id>
		<title>EPrints 3.3.15</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=EPrints_3.3.15&amp;diff=11919"/>
		<updated>2015-12-21T11:19:10Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Created page with &amp;quot;EPrints 3.3.15 is a minor bugfix release.  For more information, see [https://github.com/eprints/eprints/compare/v3.3.14...v3.3.15 the Github Comparison Page].  [http://files....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;EPrints 3.3.15 is a minor bugfix release.&lt;br /&gt;
&lt;br /&gt;
For more information, see [https://github.com/eprints/eprints/compare/v3.3.14...v3.3.15 the Github Comparison Page].&lt;br /&gt;
&lt;br /&gt;
[http://files.eprints.org/1073/ Download and more info from files.eprints.org]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_Debian/Ubuntu&amp;diff=11912</id>
		<title>Installing EPrints on Debian/Ubuntu</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_Debian/Ubuntu&amp;diff=11912"/>
		<updated>2015-12-14T16:59:28Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Debian and Ubuntu]]&lt;br /&gt;
[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
=Video=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;youtube&amp;gt;vJ5vf_GXfOI&amp;lt;/youtube&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=APT Mirrors=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Add one of the following mirrors (2 lines) to your /etc/apt/sources.list file as the root user. Please ensure that there is only one set in the file or you may not experience the correct behaviour.&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==EPrints Latest==&lt;br /&gt;
&lt;br /&gt;
To install the testing build add the following to /etc/apt/sources.list:&lt;br /&gt;
&lt;br /&gt;
===Stable Builds===&lt;br /&gt;
&lt;br /&gt;
 deb http://deb.eprints.org/ stable/&lt;br /&gt;
&lt;br /&gt;
=Installing Eprints via apt-get&lt;br /&gt;
&lt;br /&gt;
To install Eprints and all its dependencies execute the following (as root):&lt;br /&gt;
&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install eprints&lt;br /&gt;
&lt;br /&gt;
=Setting up a Repository=&lt;br /&gt;
You should now have a working installation of eprints in /usr/share/eprints3/. Please follow the on-screen instructions to set up an eprints repository. You probably want to start with (as root):&lt;br /&gt;
&lt;br /&gt;
'''For more information about setting up an EPrints repository take a look at [[Getting Started with EPrints 3]]'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Read First: Known issues with the Debian/Ubuntu package can be found at [[Debian Known Issues]].&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 su eprints&lt;br /&gt;
 cd&lt;br /&gt;
 ./bin/epadmin create&lt;br /&gt;
 logout&lt;br /&gt;
 a2ensite eprints3&lt;br /&gt;
 apache2ctl restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you have any problems getting set up you can get free help and support from the EP-Tech mailing list. {{EPrintsTech}}&lt;br /&gt;
&lt;br /&gt;
== Setting up your crontab ==&lt;br /&gt;
&lt;br /&gt;
See [[Automating your maintenance]]&lt;br /&gt;
&lt;br /&gt;
=Getting and Compiling from Source (not required)=&lt;br /&gt;
&lt;br /&gt;
To install dependencies and retrieve the Eprints source execute the following:&lt;br /&gt;
&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get build-dep eprints&lt;br /&gt;
 apt-get source eprints&lt;br /&gt;
&lt;br /&gt;
The source will be saved to a tarball in the current directory.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Issues with Ubuntu 13/14 (Apache 2.3/2.4)=&lt;br /&gt;
&lt;br /&gt;
Apache 2.3+ and PERL v5.16+ introduce a few changes which break EPrints.&lt;br /&gt;
&lt;br /&gt;
A complete HOW-TO guide to install EPrints3 on Ubuntu 14.04 is available [http://wiki.unimas.my/unimaswiki//bin/view/HOW-TO,+Tutorial+&amp;amp;+User+Manual/HOW-TO+:+Install+Eprints+v3.3.12++on+Ubuntu+14.04+With+LDAP+Authentication here]&lt;br /&gt;
&lt;br /&gt;
Current patches on github are:&lt;br /&gt;
&lt;br /&gt;
* See last comment on https://github.com/eprints/eprints/issues/214  [ use of remote_ip ]&lt;br /&gt;
* https://github.com/eprints/eprints/issues/237 [ NameVirtualHost deprecated ]&lt;br /&gt;
* https://github.com/eprints/eprints/issues/236 [ Order allow,deny deprecated ]&lt;br /&gt;
* https://github.com/eprints/eprints/commit/157db0d27d423d38f9c0fc31ce47e519cd861d45 [ utf8::decode and URI parameters ]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ensure that mpm_prefork module is enabled in /etc/apache2/mods-enabled (among others).&lt;br /&gt;
&lt;br /&gt;
Complete list of modules for a working repository include the following (although some may be surplus to requirements e.g. php5 is not strictly necessary)&lt;br /&gt;
&lt;br /&gt;
*access_compat.load                    &lt;br /&gt;
*alias.conf                                     &lt;br /&gt;
*alias.load                               &lt;br /&gt;
*auth_basic.load                             &lt;br /&gt;
*authn_core.load&lt;br /&gt;
*authn_file.load&lt;br /&gt;
*authz_core.load&lt;br /&gt;
*authz_host.load&lt;br /&gt;
*authz_user.load&lt;br /&gt;
*autoindex.conf&lt;br /&gt;
*autoindex.load&lt;br /&gt;
*deflate.conf&lt;br /&gt;
*deflate.load&lt;br /&gt;
*dir.conf&lt;br /&gt;
*dir.load &lt;br /&gt;
*env.load&lt;br /&gt;
*filter.load&lt;br /&gt;
*mime.conf&lt;br /&gt;
*mime.load&lt;br /&gt;
*mpm_prefork.conf&lt;br /&gt;
*mpm_prefork.load&lt;br /&gt;
*negotiation.conf&lt;br /&gt;
*negotiation.load&lt;br /&gt;
*perl.load&lt;br /&gt;
*php5.conf&lt;br /&gt;
*php5.load&lt;br /&gt;
*setenvif.conf&lt;br /&gt;
*setenvif.load&lt;br /&gt;
*status.conf&lt;br /&gt;
*status.load&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Coversheets&amp;diff=11284</id>
		<title>Coversheets</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Coversheets&amp;diff=11284"/>
		<updated>2015-07-17T14:01:29Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Deploying Coversheets */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Bazaar Package]]&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The purpose of the Coversheets is to add a front and/or back covering page to a PDF document uploaded to an EPrint.&lt;br /&gt;
&lt;br /&gt;
Coversheets work by using a user-defined [https://www.openoffice.org/ Apache OpenOffice] coversheet template uploaded to your EPrints repository.  This template is then populated with the predefined attributes for the particular EPrint, before being attached to the front (or if specified, back) of any PDF documents uploaded for that EPrint.  To do this a number of dependencies need to be installed:&lt;br /&gt;
* '''Ghostscript''' or '''PDFtk''':  Either of these can be used to attach the coversheet to the rest of the PDF document.&lt;br /&gt;
* '''Apache OpenOffice''': This is used to open up the coversheet template, so that a coversheet for a particular EPrint can be created.&lt;br /&gt;
* '''Oracle (Sun) Java''': This is required to run the script to interact with OpenOffice and replace the templates tags with the appropriate EPrint attrubutes (title, authors, etc.).&lt;br /&gt;
* '''Perl Modules''': Needed for EPrints to interact with OpenOffice.&lt;br /&gt;
&lt;br /&gt;
The instructions below provide guidance on testing and using the Coversheets Bazaar package on an EPrints 3.3 repository running on either Debian or RedHat based Linux distributions.  These instructions are intended to be sufficiently generic to be interpreted for use when installing on other Linux distributions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Installing Dependencies==&lt;br /&gt;
&lt;br /&gt;
===GhostScript or PDFtk===&lt;br /&gt;
The Coversheets Bazaar package requires either '''PDFtk''' of '''Ghostscript''' to attach the generated coversheet to the rest of the PDF document.  For the more recent Linux distributions (e.g. Ubuntu 14.04, Debian 7 and RedHat/CentOS 7) Ghostscript is recommended as this is easier to install and more reliable, (e.g. it can reliably attach the coversheet without breaking the character encoding of the rest of the document, so you can still copy and paste out sections of the document).  However, it may be less straightforward to get Ghostscript working for Coversheets on earlier distributions of Linux (e.g. pre Ubuntu 12.04 and RedHat/CentOS 6)&lt;br /&gt;
&lt;br /&gt;
====Ghostscript====&lt;br /&gt;
Installing Ghostscript just requires a number of Linux packages.  As root or with sudo run the appropriate following command:&lt;br /&gt;
* Debian/Ubuntu:&lt;br /&gt;
  apt-get install ghostscript gsfonts gsfonts-other libgs9 libgs9-common&lt;br /&gt;
* RedHat/Fedora/CentOS:&lt;br /&gt;
  yum install ghostscript ghostscript-devel ghostscript-fonts ghostscript-gtk&lt;br /&gt;
&lt;br /&gt;
If you installed EPrints using the DEB or RPM package, it is likely many if not all of these packages will already be installed.&lt;br /&gt;
&lt;br /&gt;
====PDFtk====&lt;br /&gt;
'''N.B. If you have already installed Ghostscript you do not need to install PDFtk as well.'''&lt;br /&gt;
&lt;br /&gt;
As root or using sudo install '''gcj''', '''g++''' and '''make''' so you can compile '''pdftk'''.&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install gcj-jdk g++ make&lt;br /&gt;
* '''RedHat/Fedora/CentOS'''&lt;br /&gt;
  yum install gcc-java gcc-c++ make&lt;br /&gt;
&lt;br /&gt;
Next, download and compile '''pdftk''' and deploy it in '''/usr/bin/'''.&lt;br /&gt;
* Substitute '''LinuxDist''' for '''Debian''' on Debian/Ubuntu distributions and '''Redhat''' for RedHat/Fedora/CentOS distributions.&lt;br /&gt;
* If you are using '''MakeFile.Debian''' check your version of gcj (gcj --version).  You will then need to change '''VERSUFF''' in '''MakeFile.Debian''' to your version number but only the first two points of the version (e.g. 4.8.2 = 4.8).&lt;br /&gt;
  wget https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk-2.02-src.zip&lt;br /&gt;
  unzip pdftk-2.02-src.zip&lt;br /&gt;
  cd pdftk-2.02-dist/pdftk&lt;br /&gt;
  make -f Makefile.LinuxDist&lt;br /&gt;
  mv pdftk /usr/bin/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Oracle (Sun) Java===&lt;br /&gt;
Oracle (Sun) Java is required to make use of the Coversheets package.  By default this is not available in the standard package repositories of most Linux distributions.  Follow the instructions below (as the root user or with sudo) to install Oracle (Sun) Java on your Linux distribution:&lt;br /&gt;
&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install python-software-properties&lt;br /&gt;
  add-apt-repository ppa:webupd8team/java&lt;br /&gt;
  apt-get update&lt;br /&gt;
  apt-get install oracle-java8-installer&lt;br /&gt;
* When prompted agree to the license agreement.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''RedHat/Fedora/CentOS'''&lt;br /&gt;
** Go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html and agree to the licence conditions.&lt;br /&gt;
** Download the appropriate .rpm package (i.e. i586 or x64) for you system architecture.&lt;br /&gt;
** Install the RPM from the command line, (substitute for '''&amp;lt;version&amp;gt;''' and '''&amp;lt;arch&amp;gt;''' based on the filename of the RPM you actually downloaded):&lt;br /&gt;
  rpm -Uvh jdk-8u&amp;lt;version&amp;gt;-linux-&amp;lt;arch&amp;gt;.rpm&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Perl Modules===&lt;br /&gt;
Before installing the Perl modules make sure that '''make''' and '''gcc''' are installed as these are needed to build the OpenOffice Perl module.  Run the appropriate command below as root or using sudo.&lt;br /&gt;
* '''Debian/Ubuntu'''&lt;br /&gt;
  apt-get install make gcc&lt;br /&gt;
* '''RedHat/Fedora/Centos'''&lt;br /&gt;
  yum install make gcc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As the root user install the following Perl modules using CPAN.  Choose the default option for any prompted questions.&lt;br /&gt;
  cpan ExtUtils::MakeMaker OpenOffice::OODoc PDF::API2 ADAMK/Archive-Zip-1.30.tar.gz&lt;br /&gt;
&lt;br /&gt;
'''N.B.'''&lt;br /&gt;
# If you have not had to install any CPAN modules up to now ,you may be prompted to configure CPAN before installing these modules, if so always choose the default option provided.&lt;br /&gt;
# For Archive::Zip it is recommended to use the specific version 1.30 tarball (as specified above).  CPAN will download this specific tarball as part of the installation, like it would for non-version specific modules.  The reason for using this specific version is, that as of at least 28th April 2015 the latest CPAN module has a bug, which means it does not work as required for EPrints Coversheet purposes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apache OpenOffice===&lt;br /&gt;
Download the tarballed package of OpenOffice 3.4.1 for your Linux distribution. Later and some earlier versions of OpenOffice should work just as well but 3.4.1 is tried and tested.  Then extract your DEB or RPM packages and install as root (or with sudo) using  '''dpkg''' or '''rpm''' as appropriate.&lt;br /&gt;
 &lt;br /&gt;
* Debian/Ubuntu (64-bit):&lt;br /&gt;
  wget http://downloads.sourceforge.net/project/openofficeorg.mirror/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US.tar.gz&lt;br /&gt;
  tar -xzvf Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US.tar.gz&lt;br /&gt;
  mv en-US Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US&lt;br /&gt;
  dpkg -i Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-deb_en-US/DEBS/*.deb&lt;br /&gt;
  &lt;br /&gt;
* RedHat/Fedora/CentOS (64-bit):&lt;br /&gt;
  wget http://downloads.sourceforge.net/project/openofficeorg.mirror/stable/3.4.1/Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz&lt;br /&gt;
  tar -xzvf Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US.tar.gz&lt;br /&gt;
  mv en-US Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US&lt;br /&gt;
  rpm -Uvh Apache_OpenOffice_incubating_3.4.1_Linux_x86-64_install-rpm_en-US/RPMS/*.rpm&lt;br /&gt;
&lt;br /&gt;
* ''N.B. For 32-bit versions remove '-64' from each of the lines above.''  You can check this by running the following command.  If it returns something with '64' in it, it is 64-bit, if it does not, it is almost certainly 32-bit.&lt;br /&gt;
  uname -i&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Enabling Coversheets ==&lt;br /&gt;
* Login to the EPrints Archive as an administrator and go to the '''Admin''' page and under the '''System Tools''' tab, click on '''EPrints Bazaar''' button.&lt;br /&gt;
* On the EPrints Bazaar page scroll and click on '''Enable''' next to the '''OpenOffice Toolkit''' package.&lt;br /&gt;
* If the OpenOffice Toolkit package installs successfully, click on '''Enable''' next the '''Coversheets''' package.&lt;br /&gt;
* If the Coversheets package successfully installed.  Click on the '''Admin''' link in the top menu bar and under the '''System Tools''' tab click on '''Start OpenOffice'''.&lt;br /&gt;
* When the page reloads next click on '''Start Indexer''', if t is not already started.&lt;br /&gt;
* Coversheets should now be installed and ready to go.  You can test this by following the instructions under '''[[#Deploying Coversheets|Deploying Coversheets]]'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Deploying Coversheets ==&lt;br /&gt;
* Logged in as an adminstrator, click on '''Manage records''' then '''Coversheets'''.  If you cannot find the the '''Manage records''' link you can go straight to the list of coversheet records at (substituting '''example.eprints.org''' for the hostname of you Eprints repository):&lt;br /&gt;
  http://example.eprints.org/cgi/users/home?screen=Listing&amp;amp;dataset=coversheet&lt;br /&gt;
* Under the Coversheets page, click on '''Create New Coversheet'''.  Fill in the '''Name''' and Description fields under '''Apply to''' checked  the types you want to use a coversheet for.and set '''Priority''' to '''1'''.  If you wish to apply the coversheet to other types make sure they are checked as well.&lt;br /&gt;
* Then, under '''Documents''' -&amp;gt; '''Front Page(s)''' upload the template coversheet front page, which you can adapt from the template at the URL below, before clicking '''Update''' button at the button of the page:&lt;br /&gt;
  http://files.eprints.org/1047/2/frontfile-example.odt&lt;br /&gt;
* When the page reloads, click on the '''Exit'' button to go back to the Coversheet index page.&lt;br /&gt;
* On the Coversheet index page, click on the icon with a green tick next to the coversheet you just added and then click on the '''Activate''' button on the page that loads.&lt;br /&gt;
* Now follow the '''[[#Testing Coversheets|Testing Coversheets]]''' instructions to check that everything is configured and working as expected.&lt;br /&gt;
&lt;br /&gt;
== Testing Coversheets ==&lt;br /&gt;
* Now add an EPrint as usually, ensuring it is of one of the types you selected under '''Apply to''' earlier.&lt;br /&gt;
* Once you have deposited the EPrint and moved it to the repository.  Click on the link to download the PDF.  The PDF will load initially without a coversheet.&lt;br /&gt;
* Click back to go back to the EPrints web interface and click on the '''Admin''' link.&lt;br /&gt;
* On the Admin page click on the '''System Tools''' tab and then click on the '''Status''' button.&lt;br /&gt;
* On the Status page click on the link on the '''Background Task Queue'' row.  On the page that loads you should be able to see a ''''Document:AddCoversheet''' task pending.&lt;br /&gt;
* Once this task disappears from the list, go back to the PDF you loaded previously and do a hard refresh (e.g. '''Ctrl+F5''') of the page.&lt;br /&gt;
* If all has gone to plan your PDF document should now have a coversheet.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing your own Coversheet Template ==&lt;br /&gt;
* If you have downloaded the example coversheet template from http://files.eprints.org/1047/1/frontfile.odt you can adapt it for your own EPrints repository by editing it in [https://www.openoffice.org/download/index.html OpenOffice] or [https://www.libreoffice.org/download/libreoffice-fresh/ LibreOffice].  &lt;br /&gt;
** Unfortunately, you cannot edit this in Microsoft Office as the document needs to be saved in .odt format.&lt;br /&gt;
* Once you have opened the example coversheet template in OpenOffice or LibreOffice you can change the logos (images) used and the layout of the page as you choose fit.  &lt;br /&gt;
* Where a word is enclosed with '''##''' either side (e.g. ''##title##'').  Then this will be substituted with the appropriate EPrint attribute.  By default the following tags can be put into a template coversheet to be replaced by the value for that EPrint attribute:&lt;br /&gt;
** ##title## &lt;br /&gt;
** ##type## (e.g. article, conference item, book section, etc.)&lt;br /&gt;
** ##url## (to the EPrint on your EPrints repository)&lt;br /&gt;
** ##date## (of when the EPrint was published)&lt;br /&gt;
** ##citation## (of the EPrint as it would appear in an EPrints search result)&lt;br /&gt;
** ##creators## (list of authors/editors of the EPrint)&lt;br /&gt;
** ##doi_url##&lt;br /&gt;
* Once you have finished your design, before saving make you do not have any white space at the end of the document, as this may cause a blank page to be added between your coversheet and main document.&lt;br /&gt;
* After saving the file, you can upload to your EPrints repository as described in '''[[#Deploying Coversheets|Deploying Coversheets]]'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Adding Extra Coversheet Tags ===&lt;br /&gt;
Extra coversheet tags can be added by editing '''z_coversheet_tags.pl''' under the archives '''cfg/cfg.d/''' directory.&lt;br /&gt;
&lt;br /&gt;
=== Configuring 'Apply to' Options ===&lt;br /&gt;
Additional options (e.g. eprint_status, userid, series, publication, etc.) can be added to the '''$c-&amp;gt;{license_application_fields}''' in '''z_coversheet.pl''' under the archives '''cfg/cfg.d/''' directory.  This will cause these options to appear in the form for editing a particular coversheet.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
=== Troubleshooting whilst Designing your own Coversheet Template ===&lt;br /&gt;
==== Adding and formatting tags on your Coversheet Template ====&lt;br /&gt;
Make sure when you add tags (e.g. ##title##) to your coversheet template you type the whole string in one go.  Try to avoid copying and pasting tags about, especially avoid copy parts of tags.  Also be careful when changing the formatting (e.g. font size, colour, etc.) of a tag, making sure you change the format for the whole tag.  &lt;br /&gt;
&lt;br /&gt;
Not doing these things could lead to the underlying representing of the whole tag being broken up by styling elements, meaning that the coversheet package will no be able to find these tags to substitute them with the appropriate attribute from the EPrint.  So when you come to look at the coversheet for your document, you will see the tag rather than the substituted attribute.&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11145</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11145"/>
		<updated>2015-04-28T09:36:02Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Upgrade from 3.3.13 to 3.3.14 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Upgrade from 3.3.13 to 3.3.14==&lt;br /&gt;
&lt;br /&gt;
''' Note: This upgrade only applies if you installed EPrints using 3.3.13 tar.gz package. '''&lt;br /&gt;
&lt;br /&gt;
Download the upgrade patch file: http://files.eprints.org/1027/10/upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
Become eprints user and go to eprints installation directory:&lt;br /&gt;
 sudo su eprints&lt;br /&gt;
 cd /opt/eprints3&lt;br /&gt;
&lt;br /&gt;
Check if you are on version 3.3.13:&lt;br /&gt;
 cat VERSION&lt;br /&gt;
&lt;br /&gt;
Apply the patch only if you are on 3.3.13 &lt;br /&gt;
 patch -p1 &amp;lt; ./upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
You can safely ignore the missing debian related files during patch by press &amp;quot;Enter&amp;quot;. This is due to the patch generated by git.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Restart apache to take effect.&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11144</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11144"/>
		<updated>2015-04-28T09:23:28Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Upgrade from 3.3.13 to 3.3.14 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Upgrade from 3.3.13 to 3.3.14==&lt;br /&gt;
&lt;br /&gt;
You can upgrade to 3.3.14 from 3.3.13 without re-install EPrints. &lt;br /&gt;
&lt;br /&gt;
Download the upgrade patch file: http://files.eprints.org/1027/10/upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
Become eprints user and go to eprints installation directory:&lt;br /&gt;
 sudo su eprints&lt;br /&gt;
 cd /opt/eprints3&lt;br /&gt;
&lt;br /&gt;
Check if you are on version 3.3.13:&lt;br /&gt;
 cat VERSION&lt;br /&gt;
&lt;br /&gt;
Apply the patch only if you are on 3.3.13 &lt;br /&gt;
 patch -p1 &amp;lt; ./upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
You can safely ignore the missing debian related files during patch by press &amp;quot;Enter&amp;quot;. This is due to the patch generated by git.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Restart apache to take effect.&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11143</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11143"/>
		<updated>2015-04-28T09:21:58Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Upgrade from 3.3.13 to 3.3.14 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Upgrade from 3.3.13 to 3.3.14==&lt;br /&gt;
&lt;br /&gt;
You can upgrade to 3.3.14 from 3.3.13 without re-install EPrints. &lt;br /&gt;
&lt;br /&gt;
Download the upgrade patch file: http://files.eprints.org/1027/10/upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
Become eprints user and go to eprints installation directory:&lt;br /&gt;
 sudo su eprints&lt;br /&gt;
 cd /opt/eprints3&lt;br /&gt;
&lt;br /&gt;
Check if you are on version 3.3.13:&lt;br /&gt;
 cat VERSION&lt;br /&gt;
&lt;br /&gt;
Apply the patch only if you are on 3.3.13 &lt;br /&gt;
 patch -p1 &amp;lt; ./upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
You can safely ignore the missing debian related files during patch by press &amp;quot;Enter&amp;quot;. This is due to the git generates the patch.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Restart apache to take effect.&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11142</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Upgrading&amp;diff=11142"/>
		<updated>2015-04-28T09:21:29Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Created page with '==Upgrade from 3.3.13 to 3.3.14==  You can upgrade to 3.3.14 from 3.3.13 without re-install EPrints.   Download the upgrade patch file: http://files.eprints.org/1027/10/upgrade-3…'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Upgrade from 3.3.13 to 3.3.14==&lt;br /&gt;
&lt;br /&gt;
You can upgrade to 3.3.14 from 3.3.13 without re-install EPrints. &lt;br /&gt;
&lt;br /&gt;
Download the upgrade patch file: http://files.eprints.org/1027/10/upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
become eprints user and go to eprints installation directory:&lt;br /&gt;
 sudo su eprints&lt;br /&gt;
 cd /opt/eprints3&lt;br /&gt;
&lt;br /&gt;
Check if you are on version 3.3.13:&lt;br /&gt;
 cat VERSION&lt;br /&gt;
&lt;br /&gt;
Apply the patch only if you are on 3.3.13 &lt;br /&gt;
 patch -p1 &amp;lt; ./upgrade-3.3.13-3.3.14.patch&lt;br /&gt;
&lt;br /&gt;
You can safely ignore the missing debian related files during patch by press &amp;quot;Enter&amp;quot;. This is due to the git generates the patch.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Restart apache to take effect.&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11141</id>
		<title>Installing EPrints on RHEL/Fedora/CentOS</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11141"/>
		<updated>2015-04-22T11:13:26Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
&lt;br /&gt;
* RedHat Enterprise/CentOS 7 (earlier versions may work)&lt;br /&gt;
&lt;br /&gt;
==Installing==&lt;br /&gt;
&lt;br /&gt;
Add the rpm.eprints.org repository key:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... the rpm.eprints.org EPrints repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/eprints/noarch/rpm-eprints-org-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 5.x only''' the rpm.eprints.org RHEL updates repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5Server/noarch/rpm-eprints-org-RHEL-5-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 6.x only''' install antiword if installing EPrints 3.2.x or earlier (from 3.3 onwards only used to as a Word -&amp;gt; PDF converter so not strictly necessary):&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/i386/antiword-0.37-1.i386.rpm&lt;br /&gt;
 # or for 64 bit:&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/x86_64/antiword-0.37-1.x86_64.rpm&lt;br /&gt;
&lt;br /&gt;
Upgrade your XML libraries:&lt;br /&gt;
&lt;br /&gt;
 yum upgrade libxml2 libxslt perl-XML-LibXML perl-XML-LibXSLT&lt;br /&gt;
&lt;br /&gt;
Install EPrints 3:&lt;br /&gt;
&lt;br /&gt;
 yum install eprints3 # 3.2.x&lt;br /&gt;
 yum install eprints # 3.3.x and later&lt;br /&gt;
&lt;br /&gt;
===Other sources for dependencies===&lt;br /&gt;
&lt;br /&gt;
The following RPM repositories may be useful for finding other dependencies required by EPrints that aren't part of the core RHEL system.&lt;br /&gt;
&lt;br /&gt;
http://fedoraproject.org/wiki/EPEL - Fedora Extras for RHEL.&lt;br /&gt;
&lt;br /&gt;
http://pkgs.repoforge.org/rpmforge-release/ - RPMforge, which covers a very large range of Perl modules plus others.&lt;br /&gt;
&lt;br /&gt;
[http://www.imagemagick.org/script/binary-releases.php ImageMagick] provide an RPM for RHEL/CentOS 5. At time of writing the RPM requires fftw3, fltk, jasper and openexr which are available from ''RPMForge''. libwebp is available from [http://rpm.eprints.org/RHEL/5/ rpm.eprints.org].&lt;br /&gt;
&lt;br /&gt;
==SELinux==&lt;br /&gt;
&lt;br /&gt;
If you're using SELinux on your server you will need to give Apache read/write access to the documents directory for all repositories you create and the eprints var folder (indexer log, ticker files):&lt;br /&gt;
&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/archives/[repoid]/documents/&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/var/&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
&lt;br /&gt;
[[Getting Started with EPrints 3]]&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
When installing EPrints on RHEL6 (may apply to other versions), If you get the error:&lt;br /&gt;
 Failed to parse XML file:&lt;br /&gt;
 /usr/share/eprints/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined age or title page. If there are more...&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
 sed -i 's/'''&amp;amp;'''nbsp;/ /g' /usr/share/eprints/lib/lang/en/phrases/system.xml&lt;br /&gt;
&lt;br /&gt;
then navigate to the root of your EPrints install (/opt/eprints or /usr/share/eprints) and run&lt;br /&gt;
 bin/generate_views *repository_id*&lt;br /&gt;
 bin/epadmin reload *repository_id*&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11140</id>
		<title>Installing EPrints on RHEL/Fedora/CentOS</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Installing_EPrints_on_RHEL/Fedora/CentOS&amp;diff=11140"/>
		<updated>2015-04-22T11:12:48Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* SELinux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Installation]]&lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
&lt;br /&gt;
* RedHat Enterprise/CentOS 5.5 (earlier versions may work)&lt;br /&gt;
&lt;br /&gt;
==Installing==&lt;br /&gt;
&lt;br /&gt;
Add the rpm.eprints.org repository key:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/rpm-eprints-org-key-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... the rpm.eprints.org EPrints repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/eprints/noarch/rpm-eprints-org-1-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 5.x only''' the rpm.eprints.org RHEL updates repository:&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5Server/noarch/rpm-eprints-org-RHEL-5-1.noarch.rpm&lt;br /&gt;
&lt;br /&gt;
... on '''RHEL 6.x only''' install antiword if installing EPrints 3.2.x or earlier (from 3.3 onwards only used to as a Word -&amp;gt; PDF converter so not strictly necessary):&lt;br /&gt;
&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/i386/antiword-0.37-1.i386.rpm&lt;br /&gt;
 # or for 64 bit:&lt;br /&gt;
 rpm -ivh http://rpm.eprints.org/RHEL/5/x86_64/antiword-0.37-1.x86_64.rpm&lt;br /&gt;
&lt;br /&gt;
Upgrade your XML libraries:&lt;br /&gt;
&lt;br /&gt;
 yum upgrade libxml2 libxslt perl-XML-LibXML perl-XML-LibXSLT&lt;br /&gt;
&lt;br /&gt;
Install EPrints 3:&lt;br /&gt;
&lt;br /&gt;
 yum install eprints3 # 3.2.x&lt;br /&gt;
 yum install eprints # 3.3.x and later&lt;br /&gt;
&lt;br /&gt;
===Other sources for dependencies===&lt;br /&gt;
&lt;br /&gt;
The following RPM repositories may be useful for finding other dependencies required by EPrints that aren't part of the core RHEL system.&lt;br /&gt;
&lt;br /&gt;
http://fedoraproject.org/wiki/EPEL - Fedora Extras for RHEL.&lt;br /&gt;
&lt;br /&gt;
http://pkgs.repoforge.org/rpmforge-release/ - RPMforge, which covers a very large range of Perl modules plus others.&lt;br /&gt;
&lt;br /&gt;
[http://www.imagemagick.org/script/binary-releases.php ImageMagick] provide an RPM for RHEL/CentOS 5. At time of writing the RPM requires fftw3, fltk, jasper and openexr which are available from ''RPMForge''. libwebp is available from [http://rpm.eprints.org/RHEL/5/ rpm.eprints.org].&lt;br /&gt;
&lt;br /&gt;
==SELinux==&lt;br /&gt;
&lt;br /&gt;
If you're using SELinux on your server you will need to give Apache read/write access to the documents directory for all repositories you create and the eprints var folder (indexer log, ticker files):&lt;br /&gt;
&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/archives/[repoid]/documents/&lt;br /&gt;
 chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/var/&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
&lt;br /&gt;
[[Getting Started with EPrints 3]]&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
When installing EPrints on RHEL6 (may apply to other versions), If you get the error:&lt;br /&gt;
 Failed to parse XML file:&lt;br /&gt;
 /usr/share/eprints/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined age or title page. If there are more...&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
 sed -i 's/'''&amp;amp;'''nbsp;/ /g' /usr/share/eprints/lib/lang/en/phrases/system.xml&lt;br /&gt;
&lt;br /&gt;
then navigate to the root of your EPrints install (/opt/eprints or /usr/share/eprints) and run&lt;br /&gt;
 bin/generate_views *repository_id*&lt;br /&gt;
 bin/epadmin reload *repository_id*&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=EPrints_3.3.14&amp;diff=11139</id>
		<title>EPrints 3.3.14</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=EPrints_3.3.14&amp;diff=11139"/>
		<updated>2015-04-20T11:09:59Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: Created page with 'EPrints 3.3.14 is a minor release pulling together a number of stability improvements to the software.  For more information, see [https://github.com/eprints/eprints/compare/v3.3…'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;EPrints 3.3.14 is a minor release pulling together a number of stability improvements to the software.  For more information, see [https://github.com/eprints/eprints/compare/v3.3.13...v3.3.14 the Github Comparison Page].&lt;br /&gt;
&lt;br /&gt;
[http://files.eprints.org/1027/ Download on files.eprints.org]&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Generic_Linux_Installation&amp;diff=11138</id>
		<title>Generic Linux Installation</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Generic_Linux_Installation&amp;diff=11138"/>
		<updated>2015-04-17T14:48:21Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{development}}&lt;br /&gt;
{{manual}}&lt;br /&gt;
[[Category:Installation]]&lt;br /&gt;
==Installation==&lt;br /&gt;
(If you are upgrading an existing installation of eprints please see the section on upgrading elsewhere in this manual.)&lt;br /&gt;
&lt;br /&gt;
EPrints needs to be installed as the same user as the apache webserver runs as. We suggest you install it as user &amp;quot;eprints&amp;quot; and group &amp;quot;eprints&amp;quot;. Under some UNIX platforms, creating a user and group can be done using the &amp;quot;adduser&amp;quot; command. Otherwise refer to your operating system documentation.&lt;br /&gt;
&lt;br /&gt;
Unpack the eprints tar.gz file:&lt;br /&gt;
&lt;br /&gt;
 % gunzip eprints-3.something.tar.gz&lt;br /&gt;
 % tar xf eprints-3.something.tar&lt;br /&gt;
&lt;br /&gt;
Now run the &amp;quot;configure&amp;quot; script. This is a /bin/sh script which will attempt to locate various parts of your system such as the perl binary. It will also check your system for required components.&lt;br /&gt;
&lt;br /&gt;
 % cd eprints-3.something&lt;br /&gt;
 % ./configure&lt;br /&gt;
&lt;br /&gt;
By default the system installs as user and group &amp;quot;eprints&amp;quot;. You will need to change this if you are not installing as either &amp;quot;root&amp;quot; or &amp;quot;eprints&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The configure script accepts a number of options. &lt;br /&gt;
&lt;br /&gt;
; --help : List all the options (many are intended for compiled software and are ignored).&lt;br /&gt;
&lt;br /&gt;
Recommended:&lt;br /&gt;
&lt;br /&gt;
; --prefix=PREFIX : Where to install EPrints (or look for a version to upgrade). By default &amp;lt;tt&amp;gt;/opt/eprints3/&amp;lt;/tt&amp;gt;&lt;br /&gt;
; --with-smtp-server=[HOST] : Use HOST to deliver mail. If the server running EPrints has an MTA such as &amp;lt;tt&amp;gt;exim&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;sendmail&amp;lt;/tt&amp;gt;, you can specify '''localhost'''. If you do not specify this option, you will get a warning to configure it later.&lt;br /&gt;
; --with-user=[USER] : Install eprints to run as USER. By default &amp;quot;eprints&amp;quot;.&lt;br /&gt;
; --with-group=[GROUP] : Install eprints to run as GROUP. By default &amp;quot;eprints&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Optional:&lt;br /&gt;
&lt;br /&gt;
; --with-perl=[PATH] : Path of perl interpreter (in case configure can't find it, or you have more than one and want to use a specific one).&lt;br /&gt;
; --with-virtualhost=[VIRTUALHOST] : Use VIRTUALHOST rather than * for apache VirtualHost directives.&lt;br /&gt;
; --with-toolpath=[PATH] : An alternate path to search for the required binaries.&lt;br /&gt;
; --disable-diskfree : Disable disk free space calls. These can cause problems on some platforms, notably 64-bit. &lt;br /&gt;
&lt;br /&gt;
Deprecated:&lt;br /&gt;
&lt;br /&gt;
; --with-apache=1 : Use Apache 1.x.x instead of 2.x.x, but EPrints 3 does not support this.&lt;br /&gt;
&lt;br /&gt;
Once you are happy with your configuration you may install eprints by running install.pl:&lt;br /&gt;
&lt;br /&gt;
 % ./install.pl&lt;br /&gt;
&lt;br /&gt;
Now you should edit the configuration file for your copy of apache. This is often &amp;lt;tt&amp;gt;/usr/local/apache/conf/http.conf&amp;lt;/tt&amp;gt; or &amp;lt;tt&amp;gt;/etc/httpd/conf/httpd.conf&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add this line: (If you didn't install eprints in &amp;lt;tt&amp;gt;/opt/eprints3/&amp;lt;/tt&amp;gt; replace that with the location on your system).&lt;br /&gt;
 Include /opt/eprints3/cfg/apache.conf&lt;br /&gt;
Note that this file is only available after you created your archive via &amp;lt;tt&amp;gt;epadmin create&amp;lt;/tt&amp;gt;. See [[Getting_Started_with_EPrints_3#Running_epadmin|Running epadmin]] for more information on creating an archive.&lt;br /&gt;
&lt;br /&gt;
You need to make sure the apache user have read/write access to the installation directory (/opt/eprints3). The user ''must'' be the same as the user you installed eprints as. We recommend to configure your apache to run as:&lt;br /&gt;
&lt;br /&gt;
 User eprints&lt;br /&gt;
 Group eprints&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Ethos&amp;diff=10987</id>
		<title>Ethos</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Ethos&amp;diff=10987"/>
		<updated>2014-08-05T09:59:47Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Management]]&lt;br /&gt;
[[Category:Howto]]&lt;br /&gt;
See also: [[Files/EThOS_webservice_download_tool]]&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''Eprints 3 users - the OAI interface to expose UKETD_DC is already bundled with the Eprints 3 distribution. However, it is still necessary to configure your installation to allow entry of metadata conforming to EThOS requirements. To this end you may find the EPrints v3 Configuration Notes helpful.''&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page_ref_id=28 Guide to using an existing repository]&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page=EPrints+v3+Configuration+Notes EPrints v3 Configuration Notes]&lt;br /&gt;
&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page=The%20EThOS%20UKETD_DC%20application%20profile UKETD_DC: The metadata core set recommended by EThOS]&lt;br /&gt;
&lt;br /&gt;
=Mandatory Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Title&lt;br /&gt;
|title&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Author&lt;br /&gt;
|creators_name&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Awarding Institution&lt;br /&gt;
|institution&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Year of Award&lt;br /&gt;
|date&lt;br /&gt;
|Implicitly assumed that this is date on title page of thesis.&lt;br /&gt;
|-&lt;br /&gt;
|Type&lt;br /&gt;
|type&lt;br /&gt;
|Material type, i.e. Thesis&lt;br /&gt;
|-&lt;br /&gt;
|Qualification level&lt;br /&gt;
|thesis_type&lt;br /&gt;
|Default thesis_type values mix qualification level (eg. Masters) and qualification name (eg. PhD). Suggest refining thesis_type values and optionally adding new thesis_name field.&lt;br /&gt;
|-&lt;br /&gt;
|Qualification name&lt;br /&gt;
|thesis_name&lt;br /&gt;
|Not in EPrints default. Name of the degree, e.g. Ph.D., M.D.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Optional Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Alternative Title&lt;br /&gt;
|alt_title&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Supervisor(s)/advisor(s)&lt;br /&gt;
|advisor&lt;br /&gt;
|Not in EPrints defaults. Plugin expects single value text field. Suggest using default Contributors field instead (adjust plugin to look for contributors with Thesis advisor role).&lt;br /&gt;
|-&lt;br /&gt;
|Abstract&lt;br /&gt;
|abstract&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Language*&lt;br /&gt;
|language&lt;br /&gt;
|Not in EPrints defaults. ISO639-2 language code for the main language of the text, e.g eng&lt;br /&gt;
|-&lt;br /&gt;
|Sponsors/Funders*&lt;br /&gt;
|sponsors&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Grant number&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Institutional Repository URL*&lt;br /&gt;
|&lt;br /&gt;
|Link to the Institutional Repository page for the thesis. Note plugin uses both $eprint-&amp;gt;get_url and official_url for dc:isReferencedBy.&lt;br /&gt;
|-&lt;br /&gt;
|URL for digital object(s)*&lt;br /&gt;
|&lt;br /&gt;
|URL for the digital object (and any associated data files) for full-text harvesting by EThOS. Plugin uses $document-&amp;gt;get_url&lt;br /&gt;
|-&lt;br /&gt;
|Embargo date*&lt;br /&gt;
|date_embargo&lt;br /&gt;
|Not in EPrints defaults. Not to be confused with document.date_embargo.&lt;br /&gt;
|-&lt;br /&gt;
|Embargo Type*&lt;br /&gt;
|&lt;br /&gt;
|To be used if only part of the thesis is embargoed. Value = Partial&lt;br /&gt;
|-&lt;br /&gt;
|Rights*&lt;br /&gt;
|rights&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Subject keywords&lt;br /&gt;
|subjects&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|DDC&lt;br /&gt;
|&lt;br /&gt;
|Dewey Decimal Classification&lt;br /&gt;
|-&lt;br /&gt;
|LCC&lt;br /&gt;
|&lt;br /&gt;
|Library of Congress Classification&lt;br /&gt;
|-&lt;br /&gt;
|LCSH&lt;br /&gt;
|&lt;br /&gt;
|Library of Congress Subject Headings&lt;br /&gt;
|-&lt;br /&gt;
|MESH&lt;br /&gt;
|&lt;br /&gt;
|Medical Subject Headings&lt;br /&gt;
|-&lt;br /&gt;
|Author Affiliation&lt;br /&gt;
|department&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Work Identifier(s)&lt;br /&gt;
|&lt;br /&gt;
|Identifier(s) for the thesis e.g. DOI, ISBN, ISTC&lt;br /&gt;
|-&lt;br /&gt;
|Author Identifier(s)&lt;br /&gt;
|&lt;br /&gt;
|Identifiers for the author, e.g. HUSID, ISNI, ORCID&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; = Mandatory if applicable'''&lt;br /&gt;
&lt;br /&gt;
=Deprecated Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|File Format&lt;br /&gt;
|document.format&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|File Size&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Checksum&lt;br /&gt;
|checksum&lt;br /&gt;
|Not in EPrints defaults&lt;br /&gt;
|-&lt;br /&gt;
|File Version&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Other (not in Ethos spec)=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Editor?/Contributor?&lt;br /&gt;
|editors_name&lt;br /&gt;
|dc:contributor&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Ethos&amp;diff=10986</id>
		<title>Ethos</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Ethos&amp;diff=10986"/>
		<updated>2014-08-05T09:25:28Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Optional Fields */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Management]]&lt;br /&gt;
[[Category:Howto]]&lt;br /&gt;
See also: [[Files/EThOS_webservice_download_tool]]&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''Eprints 3 users - the OAI interface to expose UKETD_DC is already bundled with the Eprints 3 distribution. However, it is still necessary to configure your installation to allow entry of metadata conforming to EThOS requirements. To this end you may find the EPrints v3 Configuration Notes helpful.''&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page_ref_id=28 Guide to using an existing repository]&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page=EPrints+v3+Configuration+Notes EPrints v3 Configuration Notes]&lt;br /&gt;
&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page_ref_id=47 UKETD_DC: The metadata core set recommended by EThOS]&lt;br /&gt;
&lt;br /&gt;
=Mandatory Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Title&lt;br /&gt;
|title&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Author&lt;br /&gt;
|creators_name&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Awarding Institution&lt;br /&gt;
|institution&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Year of Award&lt;br /&gt;
|date&lt;br /&gt;
|Implicitly assumed that this is date on title page of thesis.&lt;br /&gt;
|-&lt;br /&gt;
|Type&lt;br /&gt;
|type&lt;br /&gt;
|Material type, i.e. Thesis&lt;br /&gt;
|-&lt;br /&gt;
|Qualification level&lt;br /&gt;
|thesis_type&lt;br /&gt;
|Default thesis_type values mix qualification level (eg. Masters) and qualification name (eg. PhD). Suggest refining thesis_type values and optionally adding new thesis_name field.&lt;br /&gt;
|-&lt;br /&gt;
|Qualification name&lt;br /&gt;
|thesis_name&lt;br /&gt;
|Not in EPrints default. Name of the degree, e.g. Ph.D., M.D.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Optional Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Alternative Title&lt;br /&gt;
|alt_title&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Supervisor(s)/advisor(s)&lt;br /&gt;
|advisor&lt;br /&gt;
|Not in EPrints defaults. Plugin expects single value text field. Suggest using default Contributors field instead (adjust plugin to look for contributors with Thesis advisor role).&lt;br /&gt;
|-&lt;br /&gt;
|Abstract&lt;br /&gt;
|abstract&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Language*&lt;br /&gt;
|language&lt;br /&gt;
|Not in EPrints defaults. ISO639-2 language code for the main language of the text, e.g eng&lt;br /&gt;
|-&lt;br /&gt;
|Sponsors/Funders*&lt;br /&gt;
|sponsors&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Grant number&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Institutional Repository URL*&lt;br /&gt;
|&lt;br /&gt;
|Link to the Institutional Repository page for the thesis. Note plugin uses both $eprint-&amp;gt;get_url and official_url for dc:isReferencedBy.&lt;br /&gt;
|-&lt;br /&gt;
|URL for digital object(s)*&lt;br /&gt;
|&lt;br /&gt;
|URL for the digital object (and any associated data files) for full-text harvesting by EThOS. Plugin uses $document-&amp;gt;get_url&lt;br /&gt;
|-&lt;br /&gt;
|Embargo date*&lt;br /&gt;
|date_embargo&lt;br /&gt;
|Not in EPrints defaults. Not to be confused with document.date_embargo.&lt;br /&gt;
|-&lt;br /&gt;
|Embargo Type*&lt;br /&gt;
|&lt;br /&gt;
|To be used if only part of the thesis is embargoed. Value = Partial&lt;br /&gt;
|-&lt;br /&gt;
|Rights*&lt;br /&gt;
|rights&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Subject keywords&lt;br /&gt;
|subjects&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|DDC&lt;br /&gt;
|&lt;br /&gt;
|Dewey Decimal Classification&lt;br /&gt;
|-&lt;br /&gt;
|LCC&lt;br /&gt;
|&lt;br /&gt;
|Library of Congress Classification&lt;br /&gt;
|-&lt;br /&gt;
|LCSH&lt;br /&gt;
|&lt;br /&gt;
|Library of Congress Subject Headings&lt;br /&gt;
|-&lt;br /&gt;
|MESH&lt;br /&gt;
|&lt;br /&gt;
|Medical Subject Headings&lt;br /&gt;
|-&lt;br /&gt;
|Author Affiliation&lt;br /&gt;
|department&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Work Identifier(s)&lt;br /&gt;
|&lt;br /&gt;
|Identifier(s) for the thesis e.g. DOI, ISBN, ISTC&lt;br /&gt;
|-&lt;br /&gt;
|Author Identifier(s)&lt;br /&gt;
|&lt;br /&gt;
|Identifiers for the author, e.g. HUSID, ISNI, ORCID&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt; = Mandatory if applicable'''&lt;br /&gt;
&lt;br /&gt;
=Deprecated Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|File Format&lt;br /&gt;
|document.format&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|File Size&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Checksum&lt;br /&gt;
|checksum&lt;br /&gt;
|Not in EPrints defaults&lt;br /&gt;
|-&lt;br /&gt;
|File Version&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Other (not in Ethos spec)=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Editor?/Contributor?&lt;br /&gt;
|editors_name&lt;br /&gt;
|dc:contributor&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=Ethos&amp;diff=10985</id>
		<title>Ethos</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=Ethos&amp;diff=10985"/>
		<updated>2014-08-05T09:11:05Z</updated>

		<summary type="html">&lt;p&gt;Jy2e08@ecs.soton.ac.uk: /* Mandatory Fields */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Management]]&lt;br /&gt;
[[Category:Howto]]&lt;br /&gt;
See also: [[Files/EThOS_webservice_download_tool]]&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''Eprints 3 users - the OAI interface to expose UKETD_DC is already bundled with the Eprints 3 distribution. However, it is still necessary to configure your installation to allow entry of metadata conforming to EThOS requirements. To this end you may find the EPrints v3 Configuration Notes helpful.''&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page_ref_id=28 Guide to using an existing repository]&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page=EPrints+v3+Configuration+Notes EPrints v3 Configuration Notes]&lt;br /&gt;
&lt;br /&gt;
[http://ethostoolkit.cranfield.ac.uk/tiki-index.php?page_ref_id=47 UKETD_DC: The metadata core set recommended by EThOS]&lt;br /&gt;
&lt;br /&gt;
=Mandatory Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Title&lt;br /&gt;
|title&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Author&lt;br /&gt;
|creators_name&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Awarding Institution&lt;br /&gt;
|institution&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Year of Award&lt;br /&gt;
|date&lt;br /&gt;
|Implicitly assumed that this is date on title page of thesis.&lt;br /&gt;
|-&lt;br /&gt;
|Type&lt;br /&gt;
|type&lt;br /&gt;
|Material type, i.e. Thesis&lt;br /&gt;
|-&lt;br /&gt;
|Qualification level&lt;br /&gt;
|thesis_type&lt;br /&gt;
|Default thesis_type values mix qualification level (eg. Masters) and qualification name (eg. PhD). Suggest refining thesis_type values and optionally adding new thesis_name field.&lt;br /&gt;
|-&lt;br /&gt;
|Qualification name&lt;br /&gt;
|thesis_name&lt;br /&gt;
|Not in EPrints default. Name of the degree, e.g. Ph.D., M.D.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Optional Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Alternative Title&lt;br /&gt;
|alt_title&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Supervisor(s)/advisor&lt;br /&gt;
|advisor&lt;br /&gt;
|Not in EPrints defaults. Plugin expects single value text field. Suggest using default Contributors field instead (adjust plugin to look for contributors with Thesis advisor role).&lt;br /&gt;
|-&lt;br /&gt;
|Subject keywords&lt;br /&gt;
|subjects&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Abstract&lt;br /&gt;
|abstract&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|DDC&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|LCC&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|LCSH&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|MESH&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|UDC&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Author Affiliation&lt;br /&gt;
|department&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Publisher&lt;br /&gt;
|publisher&lt;br /&gt;
|Note publisher not in default thesis workflow.&lt;br /&gt;
|-&lt;br /&gt;
|Sponsors&lt;br /&gt;
|sponsors&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Grant number&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Qualification name&lt;br /&gt;
|thesis_name&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Language&lt;br /&gt;
|language&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Institution item page URL&lt;br /&gt;
|&lt;br /&gt;
|Note plugin uses both $eprint-&amp;gt;get_url and official_url for dc:isReferencedBy.&lt;br /&gt;
|-&lt;br /&gt;
|Citations&lt;br /&gt;
|citations&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Included/Quoted work&lt;br /&gt;
|referencetext&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Rights&lt;br /&gt;
|rights&lt;br /&gt;
|Not in EPrints defaults.&lt;br /&gt;
|-&lt;br /&gt;
|Embargo Type&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Embargo date&lt;br /&gt;
|date_embargo&lt;br /&gt;
|Not in EPrints defaults. Not to be confused with document.date_embargo.&lt;br /&gt;
|-&lt;br /&gt;
|Embargo reasons&lt;br /&gt;
|embargo_reason&lt;br /&gt;
|Not in EPrints defaults. Plugin expects single value text field.&lt;br /&gt;
|-&lt;br /&gt;
|Identifier&lt;br /&gt;
|&lt;br /&gt;
|Plugin uses $document-&amp;gt;get_url&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Deprecated Fields=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|File Format&lt;br /&gt;
|document.format&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|File Size&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Checksum&lt;br /&gt;
|checksum&lt;br /&gt;
|Not in EPrints defaults&lt;br /&gt;
|-&lt;br /&gt;
|File Version&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Other (not in Ethos spec)=&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!Ethos Field name&lt;br /&gt;
!EPrints field used by Ethos plugin&lt;br /&gt;
!Comments&lt;br /&gt;
|-&lt;br /&gt;
|Editor?/Contributor?&lt;br /&gt;
|editors_name&lt;br /&gt;
|dc:contributor&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Jy2e08@ecs.soton.ac.uk</name></author>
		
	</entry>
</feed>