Editing Migration (section)

=== Import the data ===

To import the subjects and users do:
 /opt/eprints3/bin/import_subjects --verbose --force --xml ARCHIVEID subjects.xml
 /opt/eprints3/bin/import --verbose --migration ARCHIVEID user XML users.xml
If something goes wrong with subjects or users, use epadmin erase_data to empty the database and start again.

To import the EPrints do:
 /opt/eprints3/bin/import --verbose --migration ARCHIVEID eprint XML eprints.xml
If something goes wrong with importing the eprints, use epadmin erase_eprints, to just erase the eprints data so you don't need to redo subjects and users.

the --migration option tells the importer to:
* skip are-you-sure? messages.
* use the eprintid and userid from the XML rather than assigning them.
* use the "datestamp" from the XML rather than assign it.
* load files from the local file system (normally this would be a security hole)

You may encounter some issues with badly formed XML. This is due to non correctly encoded data creeping into your database. It should all be utf-8 but earlier versions of EPrints didn't always check... If your EPrints 2 server is running perl 5.8 you can install the Perl module Encode which will clean up your data, but on our system our EPrints 2 was running on a machine with an older version of Perl and we didn't want to risk upgrading.