Difference between revisions of "EPrints 3 Configuration orientation for EPrints 2 administrators"

From EPrints Documentation
Jump to: navigation, search
(ARCHIVEID.xml)
(ARCHIVEID.xml)
Line 19: Line 19:
  
 
* server configuration (host, port, aliases..) - [[10_core.pl]]
 
* server configuration (host, port, aliases..) - [[10_core.pl]]
* database configuration (db name, db user..) [[database.pl]]
+
* database configuration (db name, db user..) - [[database.pl]]
 
* administrator email - [[adminemail.pl]]
 
* administrator email - [[adminemail.pl]]
 
* default/supported languages - [[languages.pl]]
 
* default/supported languages - [[languages.pl]]

Revision as of 13:36, 1 February 2007

Warning This page is under development as part of the EPrints 3.0 manual. It may still contain content specific to earlier versions. Manuals for previous versions of EPrints are also available.

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:

/opt/eprints2/archives/ARCHIVEID/cfg
/opt/eprints3/archives/ARCHIVEID/cfg

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

ARCHIVEID.xml

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

ArchiveConfig.pm

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 (or another named module) 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:

/opt/eprints3/archives/ARCHIVEID/cfg/cfg.d/

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.

ArchiveMetadataFieldsConfig.pm

ArchiveOAIConfig.pm

ArchiveRenderConfig.pm

ArchiveValidateConfig.pm

ArchiveTextIndexing.pm