[Dspace-tech] Dspace -sakai integartion

Wed, 26 Dec 2007 21:23:16 -0800 

HI
    Need help on  Dspace -Sakai integration(*Windowsxp*), any documentation
or steps guide is available ? if so pls send me  the links .

   - As of now I am following the steps  given in the document(attched).
   - I have successfully completed the installations of  Sakai  and
   Dspace separately.
   - But i have a problem in applying the Caret patches to Dspace i.e.
   Step 2 & 3 of the Dspace section
   -  And in step 4 of Configuration section where Xml format is not
   proper

*Note: Pls refer the attched document*
Thanks in Advance
Vikram
Title: dspace/Sakai Integration


dspace/Sakai Integration

DSpace / Sakai Integration

What is it?

The integration work is to develop a "live link" between a "Resources" tool on a external link: Sakai workspace and a running external link: DSpace instance on the same or another server machine. The link allows Sakai to interrogate DSpace's hierarchic archive for "Communities", "Collections" and "Items", and to display them in the familiar file-and-folder layout of Sakai's own resources tree. Furthermore, the tree of items in a single Resources tool can show simultaneously the resources held in more than one DSpace instance, and indeed those stored in other filesystems and archives external to Sakai. The framework for broadly representing external resources inside Sakai's Resources tool reuses earlier work done at external link: CARET: Content Hosting Handlers.

A DSpace instance can be exposed in a read-only fashion through Sakai, or read-write through Sakai's access control mechanisms. In either case, Sakai connects to DSpace as a single "EPerson" and if that account lacks submit privileges in DSpace, the functionality of Sakai's interface will be limited to reading from the digital repository.

Screenshot of the Resources Tool, showing a mounted filesystem home directory and DSpace Instances

Prerequisities

  1. Sakai 2.4 (or later). The Content Hosting Handler is an extension to 2.4 (trunk) and will not be back-ported to Sakai 2.3 or 2.2.
  2. The ContentHostingHandler tool, obtained from CARET's SVN repository
  3. DSpace 1.4.1 (or later)
  4. Larry Stone's Leightweight Network Interface (LNI) adapter for the DSpace source (which is an incomplete implementation -- see patches below)
  5. CARET patch for DSpace 1.4.1: database connection resource-leak-under-load patch
  6. CARET patch for DSpace 1.4.1: implements more of the LNI protocol by adding commands for writing to DSpace: make-collection and delete community/collection/item/bitstream

Installation

Sakai

  1. Get an SVN checkout of Sakai 2.4 trunk: 
    svn co external link: 
                        
                          https://source.sakaiproject.org/svn/sakai/trunk/
  2. In the source directory, get the ContentHostingHandler tool: 
    svn co external link: 
                        
                          https://saffron.caret.cam.ac.uk/svn/projects/Content/trunk/contenthostinghandlers/
  3. Modify your pom.xml file so Maven 2 knows to build the ContentHostingHandler extensions: 
    <modules>
   …
   <module>contenthostinghandlers</module>
   …
</modules>
  4. Build Sakai using Maven 1 or 2. For example, using Maven 2: 
    mvn -Dmaven.test.skip=true -Dmaven.tomcat.home=/path/to/your/tomcat/ clean install sakai:deploy

DSpace

  1. Get a CVS checkout of the DSpace 1.4.1 code (recommended), or simply download the (older) tar file in this CamTools worksite Resources: 
    tar xjf ../dspace141-pre-lni.tar.bz2
  2. Apply the DSpace/LNI patch (see file in Resources tool): 
    cd dspace-1.4.1-source
patch -p0 < lni-1.4-diffs.txt
unzip lni-1.4-new.zip
  3. Apply the CARET patches to DSpace (files in the Resources section, and also in your SVN checkout of ContentHostingHandlers from CARET's SVN repository): 
    patch -p0 < dspace-resource-leak.patch
patch -p0 < dspace-lni-delete-mkcol.patch
cd ..
  4. Compile and deploy DSpace using Apache Ant: 
    cd dspace-1.4.1-source
ant clean
ant build_wars
ant lni_client
cd ..
cp dspace-1.4.1-source/build/*.war /path/to/your/tomcat/webapps/

Start-Up

Start your DSpace server and Sakai server. It does not matter which you start first, and Sakai will not bork if DSpace goes away and comes back while a Sakai server is up. Should DSpace be unavailable when someone looks at a Sakai Resource tool which has been configured to interrogate DSpace, the folder hierarchy in Sakai will be empty.

Configuration

Content Hosting Handlers are configured using file uploads in Sakai. These files are (very) short XML documents and are normal Resources in the Sakai terminology. After uploading one of these specially formed XML documents, revising its properties and setting the "Activate Mountpoint" property causes it to appear as a Collection containing, in this case, a virtual hierarchy obtained by querying DSpace. The procedure will be familiar to anyone who has mounted unix filesystems, or indeed has used Microsoft's Distributed File System to mount remote filesystems into an NTFS v5 filesystem.

  1. Log on to your Sakai instance and navigate to the Resources tool on the worksite where the DSpace archive is to be displayed. Navigate into the tree of Sakai Collections to the point where DSpace should be mounted.
  2. Create a DSpace EPerson with permissions appropriate for the degree of access you wish to give Sakai users.
  3. Determine the DSpace handle of the Community or Collection which should form the root of the virtual file system view of DSpace. You do not have to export an extire DSpace archive; you can start anywhere in the hierarchy.
  4. Copy/Paste the following XML into a temporary file on your workstation and update the username (noting that the @ character in an email address has to be URL-encoded to %40), password, hostname, and initial handle as appropriate. 
                            <mountpoint
  endpoint="http://johnf%40caret.cam.ac.uk:[EMAIL PROTECTED]:8081/dspace-lni/lni/DSpaceLNI"
  baseHandle="123456789/45"
  searchable="false"
/>
  5. Upload the temporary file to Sakai's Resources tool. It does not matter what name you chose to give the resource. You can set the appear and withdraw dates; the entire virtual hierarchy representing DSpace will appear/disappear on the dates specified. Save the resource
  6. Revise the resource, expand the Optional Properties (bottom of the screen).
  7. In the Activate Mountpoint box, enter: 
    uk.ac.cam.caret.ContentHostingHandlerImplDSpace.0000
    and save the resource.

Your DSpace archive should be displayed in the Sakai Resources tool. If not, consult your Sakai Tomcat's logfile for indications of the reasons for any failures. Common errors include malformed XML and incorrect usernames, passwords, or hostnames for the DSpace instance. 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to