EPrints Technical Mailing List Archive

Message: #05599

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] problem migrating documents

If you open the XML file, you'll see that it has a path in the file section of the document.  If you modify that path to point to somewhere local, then put a copy of the file in that place, it should work.

What are you actually trying to accomplish.  Is this a step in a bigger job?  What's the bigger job?

 

Jisc

Adam Field
SHERPA services analyst developer

From: <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of "holger.berth@mdc-berlin.de" <holger.berth@mdc-berlin.de>
Reply-To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
Date: Monday, 25 April 2016 10:48
To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
Subject: Re: [EP-tech] problem migrating documents

Hi Thomas,

i have exported one publication with


bin/export edoc eprint XML 15166 > 15166.xml

and imported it into the new system

bin/import edoc eprint XML --enable-file-imports --enable-import-fields
--force --verbose /home/user/15166.xml

But if i export the publication from the new system, the file entry is not
in the xml file.

I think this does not overwrite the data. Or do i have to start a another
script after importing?

Best,
Holger

-----Ursprüngliche Nachricht-----
[mailto:eprints-tech-bounces@ecs.soton.ac.uk] Im Auftrag von Thomas Lauke
Gesendet: Freitag, 15. April 2016 11:19
Betreff: Re: [EP-tech] problem migrating documents

what is  the best way to migrate the documents.
hard to say, depends on many boundary conditions

I only copied (rsync) the documents from one server to the next,
imported the mysql database and started the upgrade with "epadmin upgrade
reponame"
could work, if all paths for eprint stuff are exactly the same; 'upgrade' is
an independent issue Of course, the most easy way!

How can i export all without documents?
export repoID  eprint XML <badID0..badIDn> will do that by default settings

And how can import this
import repoID eprint XML --enable-file-imports --enable-import-fields
updatedPipedExportFile overwrites even existing entries ...

Check if a correction of bad entries is useful, otherwise start from
scratch.
Testing on a sandbox is _no_ bad idea :)

Hand
Thomas
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.