Jump to content
Wiki Home
EPrints Home
Bazaar
Files
Main menu
Main menu
move to sidebar
hide
Navigation
Front Page
EPrints 3 Manual
EPrints Training Course
EPrints Glossary
Installing EPrints
How-to Configure EPrints
EPrints 3.2+ API
EPrints 3 Reference
EPrints Plugins
Wiki
All categories
Recent changes
Main Page
Help
EPrints Documentation
Search
Search
Appearance
Log in
Request account
Personal tools
Log in
Request account
Pages for logged out editors
learn more
Contributions
Talk
Editing
Files/EPrints 2 to 3 toolkit
(section)
Page
Discussion
British English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
= EPrints version 2.3 to 3.0 migration toolkit = Download at: http://files.eprints.org/135/ Currently v0.1 Running # ep2to3config.pl ARCHIVEID on your EPrints 2.3 system will generate a directory called ARCHIVEID_ep3cfg which will contain some cfg files for EPrints 3.0 and a notes.txt file with some additional comments in. == What the current release does == Creates config files for: * phrases (english only) * workflows * namedsets * eprint and user fields configuration Plus notes.txt with some notes of any tweaks it's made (it will remove or rename or otherwise modify some fields) == What the current version doesn't do, but later releases should == * citations * searches * views * export script to export in the EPrints 3.0 XML import format (including files). (this is nearly complete). * spotting issues it can't handle and at least giving some advice on what needs to be done by hand * converting document types into mime types would be nice, to make it more EPrints 3 ish. == What the toolkit will (probably) never do == These will need to be done by hand * handling for render_single type options in fields * copying the template (you're better off re-doing it, as so many options have changed) * the ArchiveRenderConfig methods will need porting, but that shouldn't be *too* hard, we've put in a hell of a lot of back compatability methods to smooth this. * custom bits like LDAP based login * You'll probably want to tweak the workflow to use the new features like autocomplete and multifield components etc.
Summary:
Please note that all contributions to EPrints Documentation may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
EPrints Documentation:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)