Skip to content

Latest commit

 

History

History
108 lines (84 loc) · 3.44 KB

README.md

File metadata and controls

108 lines (84 loc) · 3.44 KB
Raw

scripts

Repo for various robertson library scripts.

Currently the drush scripts are being migrated to use tuque. Any scripts that have been updated have been moved to the drupal7 folder. Ideally only one version the scripts should be installed on a server as there maybe conflicts if both versions exist on the same server.

Setup

To make the Drush commands accessible to Drush, make a shortcut to them in the .drush directory in your home directory, e.g.,

# If this repository is located in ~/dev/scripts.
mkdir ~/.drush
ln -s ~/scripts/drush/drupal7 ~/.drush/islandora
# Force drush to reload its list of commands
drush cc drush

Data Migration Drush Commands

In order to migrate content between repositories that is protected by XACML POLICY streams you can now use the 'islandora-export-objects' and 'islandora-import-objects'.

An example export / import workflow would look like:

On the computer hosting the source repository:

# Go to the site directory of the Drupal site that has Islandora pointed to the source repository
cd /var/www/html/drupal/sites/default/

# Given a list of PIDs in a file called pids.txt
drush --user=1 islandora-export-objects --pids-file-dir=/home/yourhome/export --pids-filename=pids.txt  --include-datastreams=TRUE

"--include-datastreams" will export the profile data and file objects of all of the exported objects' datastreams.

The output of exporting the datastreams will look like this:

bdh_4805      
 - TN.profile.json
 - DC.profile.json
 - RELS-INT.profile.json
 - RELS-INT
 - POLICY.profile.json
 - TN
 - MODS
 - RELS-EXT
 - JP2.profile.json
 - MODS.profile.json
 - RELS-EXT.profile.json
 - OBJ
 - JPG.profile.json
 - TECHMD
 - JPG
 - OBJ.profile.json
 - POLICY
 - JP2
 - TECHMD.profile.json
 - DC
bdh_4805.json 
bdh_4805.xml

Move the files to the destination host and then run the following to import:

drush --user=1 islandora-import-objects --foxml-files-dir=/home/userdir/export --foxml-files-list=/home/userdir/export/bdh_remaining_files.txt --use-exported-datastreams=TRUE

migrate.py Import and export in one step

Set up drush site aliases

The migrate.py command takes advantage of Drush's site aliases to save you typing the same options for source and destinatinon connection over and over again.

migrate.py assumes that the 'source' Islandora site is a remote connection and the destination Islandora site is accessible locally.

So your ~/.drush/aliases.drushrc.php file would look something like this:

<?php
/**
 * Development alias
 * Set up each entry to suit your site configuration
 */
$aliases['prod'] = array (
  'uri' => 'www.yourislandorasite.ca',
  'root' => '/var/www/html/drupal',
  'remote-user' => 'sshuser',
  'remote-host' => 'yourislandorasite.ca',
);
$aliases['local'] = array(
  'url' => 'local.test',
  'root' => '/Users/myuser/Sites/drupal',
);

And an example migrate commadn would look like this:

python3 migrate.py -a @prod -d @local -s yourislandorasite.ca -u sshuser --pids=example:1,example:2,example:3 --verbose

The python script is not parsing the drush aliases, just passing them directly to drush, hence the need to supply the source ssh address on the command line for now.

migrate.py is a wrapper for the drush commands islandora-export-objects and islandora-import-objects which have their own documentation in this repository's main README.md.