|
@@ -0,0 +1,44 @@
|
|
|
|
|
+# Migration Guide
|
|
|
|
|
+
|
|
|
|
|
+A command-line utility is available as part of the `lsup-admin` suite
|
|
|
|
|
+to migrate contents from a Fedora implementation to LAKEsuperior.
|
|
|
|
|
+
|
|
|
|
|
+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:
|
|
|
|
|
+
|
|
|
|
|
+1. By providing a starting point on the source repository. E.g. if the
|
|
|
|
|
+ repository you want to migrate is at `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.
|
|
|
|
|
+2. By providing a file containing a list of resources to migrate. This is
|
|
|
|
|
+ useful if a source repository cannot produce a full list (e.g. the root node
|
|
|
|
|
+ has more children than the server can handle) but a list of individual
|
|
|
|
|
+ resources is available via an external index (Solr, triplestore, etc.).
|
|
|
|
|
+ The resources can be indicated by their fully qualified URIs or paths
|
|
|
|
|
+ relative to the repository root. (*TODO latter option needs testing*)
|
|
|
|
|
+
|
|
|
|
|
+
|
Stefano Cossu