EPrints 3 Configuration orientation for EPrints 2 administrators

From EPrints Documentation
Revision as of 14:04, 1 February 2007 by Tmb (talk | contribs) (ArchiveTextIndexing.pm)
Jump to: navigation, search
Warning This page is under development as part of the EPrints 3.4 manual. It may still contain content specific to earlier versions.

Whereas EPrints 2 had comparatively fewer (but larger) configuration files, EPrints 3 splits these up into several smaller files (with filenames that make finding specific configuration options much easier!). The configuration directory structure has also been reshuffled to organise the configuration files more logically. The migration tool converted your EPrints 2 configuration automatically - this orientation guide is intended to help you re-orient yourselves in your new EPrints 3 set up.

Where did my configuration settings go?

Both EPrints 2 and EPrints 3 store the repository configuration settings in the same place:


This section covers each EPrints 2 configuration file in turn, describing where the settings can now be found in EPrints 3.


The configuration settings in the top level repository settings file have been split into several EPrints 3 files:


The main ArchiveConfig.pm module from EPrints 2 has also been split into several smaller files.

The way in which the configuration files are loaded has also changed. In EPrints 2, ArchiveConfig.pm was responsible for loading the other configuration files. EPrints 3 makes this process simpler by automatically loading all the configuration files in the main repository configuration directory:


ArchiveConfig.pm contained lots of different configuration settings, some of which are more likely to have been changed than others:

In EPrints 2 you may have changed:

You probably didn't change:

And there are still some miscellaneous bits left over in misc.pl.

Submission customisation (the submission_stage_skip and submission_hide_* options} is now defined within the deposit workflow itself. Also, entities like archivename and base_url are no longer created; instead the {..} notation is used to include configuration strings in the site template, phrases and static content pages.


In EPrints 2, the ArchiveMetadataFieldsConfig.pm file defined the relevant metadata for eprints, users and documents, and also the default and derived (automatic) values. In EPrints 3, these definitions have been split into individual files for each type.

eprint metadata

user metadata

document metadata


The settings for the OAI 2.0 interface have been moved from ArchiveOAIConfig.pm to oai.pl. OAI 1.1 is no longer supported.

The mapping between the repository metadata and Dublin Core (any other metadata schemas you may have added support for) are now defined using export plugins.


The configuration file responsible for rendering the individual information pages for each eprint (the abstract pages) and user (user record pages) has been split into eprint_render.pl and user_render.pl accordingly.



The text indexing settings have been moved to indexing.pl.