The LAKEsuperior dataset is by default fully contained in a folder. This means that only the data, configuration and code are needed for it to run. No Postgres, Redis, or such. These folders can be moved around as needed.
Migration is the process of importing and converting data from a different
Fedora or LDP implementation into a new LAKEsuperior instance. This process
uses the HTTP/LDP API of the original repository. A command-line utility is
available as part of the lsup-admin
suite to assist in such operation.
A repository can be migrated with a one-line command such as:
./lsup-admin migrate http://source-repo.edu/rest /local/dest/folder
For more options, enter
./lsup-admin migrate --help
The script will crawl through the resources and crawl through outbound links within them. In order to do this, resources are added as raw triples (i.e. no consistency checks are made).
Note: the consistency check tool has not yet been implemented at the moment but its release should follow shortly. This will ensure that all the links between resources are consistent in regard to referential integrity.
This script will create a full dataset in the specified destination folder, complete with a default configuration that allows to start the LAKEsuperior server immediately after the migration is complete.
Two approaches to migration are possible:
http://repo.edu/rest/prod
you can add
the -s /prod
option to the script to avoid migrating irrelevant branches.
Note that the script will still reach outside of the starting point if
resources are referencing other resources outside of it.A back up of a LAKEshore repository consists in copying the RDF and non-RDF
data folders. The location of these folders is indicated in the application
configuration. The default commands provided by your OS (cp
, rsync
,
tar
etc. for Unix) are all is needed.