Test the exports for correctness if imports fail

The imports will fail if the exports are not correct. Use the following to setup a script to check the exports for correctness on the new server.

Create export check script

Open the export check script for editing as follows:

nano /root/scripts/collection-check

Copy and paste the following to open editor:

#!/bin/bash

# Setup the configs.
. config

# Clean out the old logs.
rm /root/test.log

# Go thru the collections
for i in `cat collections` ; do
    echo $i > /tmp/map
    ECID=`cat /tmp/map | awk -F',' '{ print $1 }'` 
    ICID=`cat /tmp/map | awk -F',' '{ print $2 }'`
    echo "Checking items in collection:$ECID"
    LIST=`ls $IMPORT/$ECID`
    
    for i in $LIST ; do
	ITM=$i
	cd  $IMPORT/$ECID/$ITM
	if [ ! -e dublin_core.xml ] ; then
	echo "Item: $ITM, No dublin core." >> /root/test.log
	fi
	if [ ! -e handle ] ; then
	echo "Item: $ITM, No handle." >> /root/test.log
	fi
	if [ ! -e contents ] ; then
	echo "Item: $ITM, No contents file." >> /root/test.log
	fi
	if [ ! -e license.txt ] ; then
	echo "Item: $ITM, No license." >> /root/test.log
	fi
	ls $IMPORT/$ECID/$ITM | grep pdf > /tmp/pdf.log
	if [ $? -ne 0 ] ; then
	echo "Item: $ITM, No PDF file." >> /root/test.log
	fi
    done
    cat /root/test.log | mail -s "Exported collections test log" $PERSON
    echo "Check complete and report emailed to dspace admin user"
done

Save the file and exit the editor.

Now make the script executeable as follows:

chmod 0775 /root/scripts/collection-check

Do the exports check

Type the following to do the check:

/root/scripts/collection-check

Now check your email, you should have one with details of the test log.

If there are errors, fix them on the old server. Delete the exports on the old server and do a new export after everything is fixed. Bascially start the export and import over again. At least you now have the scripts to do it over again.

Help Info

/home/dspace/bin/export

It takes the following parameters:

-d,--dest     destination collection directory
-h,--help     help
-i,--id       collection/item ID
-n,--number   sequence number to begin exporting items with
-m,--migrate  strips out any per-repository-specifics
-t,--type     type: COLLECTION or ITEM

/home/dspace/bin/import

It takes the following parameters:

-s,--source        source collection directory
-c,--collection    destination collection handle
-e,--eperson       email of authorised person
-m,--mapfile       collection/item map file name 
-a,--add           add items
-d,--delete        delete items listed in mapfile
-r,--replace       replace items listed in mapfile 
-w,--workflow      send submission through collection's workflow
-p,--template      apply template
-t,--test          test run - do not actually import items
-R,--resume        resume a failed import (add only)
-h,--help          help

References

Command Line Help

Go to: http://www.ubuntu.sun.ac.za/wiki/index.php/SelfHelp for more help about the command line programs used in this procedure.

Back to IR Help

SUNScholar/Export and Import Artifacts

Contents

Test the exports for correctness if imports fail

Create export check script

Do the exports check

Help Info

/home/dspace/bin/export

/home/dspace/bin/import

References

Command Line Help

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools