EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #05569
< 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
- To: eprints-tech@ecs.soton.ac.uk
- Subject: Re: [EP-tech] problem migrating documents
- From: Thomas Lauke <th.lauke@arcor.de>
- Date: Fri, 15 Apr 2016 11:19:07 +0200 (CEST)
> 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
- Prev by Date: Re: [EP-tech] problem migrating documents
- Next by Date: Re: [EP-tech] Review Filters
- Previous by thread: Re: [EP-tech] problem migrating documents
- Next by thread: Re: [EP-tech] problem migrating documents
- Index(es):