Hi Stuart

Thanks for your help with this - not really being up to using the command line 
(child of Microsoft I'm afraid) I'm really reliant on a client (though I'm 
currently playing with Ubuntu so will have a go!); might there be an issue with 
the client I'm using - 
http://sourceforge.net/projects/sword-app/files/SWORD%20Client/Release%201.1/ ?

I've just tried again into http://demo.dspace.org/ with a freshly configured 
download with the same error so I'm a little confused as I know this client 
works with an IMS package into intraLibrary and it also seems to have pushed 
the METS package into eprints albeit without metadata.

You may have picked up that I have been working with Robert Hardy of York St 
John (Cc'd) who is a bit more clued-up than me on the command-line and that I 
know has recently posted to the list about issues he's having testing with a 
SWORD implementation in ArchivalWare (I pointed him to the same client that 
I've been using which similarly wouldn't work for him - though he has also 
succeeded using curl from the command line.)

Ultimately what we hope to achieve is a web-based client (probably using 
EasyDeposit) that will deposit into Jorum (DSpace), EPrints at the University 
of Leeds, ArchivalWare at York St John and intraLibrary here at Leeds Met.

Thanks again for your help.

Nick


-----Original Message-----
From: Stuart Lewis [mailto:s.le...@auckland.ac.nz]
Sent: 21 July 2011 08:19
To: Sheppard, Nick
Cc: sword-app-tech@lists.sourceforge.net; Taylor, Michael; Double; Phil Franks; 
Robert Hardy
Subject: Re: [sword-app-tech] Depositing a METS package to DSpace / EPrints

Hi Nick,

I have tried depositing your package to my local development server, and to 
http://demo.dspace.org/ which is running DSpace 1.7.2.

They both worked fine**.  Here is the command I used to to test demo.dspace.org:

curl -i --data-binary "@Test_package.zip" -H "Content-Disposition: 
filename=myDSpaceMETSItem.zip" -H "Content-Type: application/zip" -H 
"X-Packaging: http://purl.org/net/sword-types/METSDSpaceSIP"; --user 
dspacedemo+ad...@gmail.com:{PASS****} 
http://demo.dspace.org/sword/deposit/10673/39403
HTTP/1.1 100 Continue

HTTP/1.1 201 Created
Server: Apache-Coyote/1.1
Location: http://demo.dspace.org/sword/media-link/10673/44743/bitstream/2080
Content-Type: application/atom+xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 21 Jul 2011 07:10:43 GMT

<?xml version="1.0" encoding="UTF-8"?>
<atom:entry xmlns:atom="http://www.w3.org/2005/Atom"; 
xmlns:sword="http://purl.org/net/sword/";>
   <atom:id>http://hdl.handle.net/10673/44743</atom:id>
   <atom:author>
      <atom:name>dspacedemo+ad...@gmail.com</atom:name>
   </atom:author>
   <atom:content type="application/octet-stream" 
src="http://demo.dspace.org/xmlui/bitstream/10673/44743/3/myDSpaceMETSItem.zip"/>
   <atom:generator uri="http://www.dspace.org/ns/sword/1.3.1"; version="1.3"/>
   <atom:link 
href="http://demo.dspace.org/xmlui/bitstream/10673/44743/1/Romeo_with_ajax.pdf"; 
rel="part" type="application/pdf"/>
   <atom:link href="http://hdl.handle.net/10673/44743"; rel="alternate" 
type="text/html"/>
   <atom:published>2010-09-27</atom:published>
   <atom:rights 
type="text">http://demo.dspace.org/xmlui/bitstream/10673/44743/2/license.txt 
</atom:rights>
   <atom:summary type="text">Some simple overviews of using the RoMEO API 
within a web page, to provide live responses</atom:summary>
   <atom:title type="text">Using the RoMEO API with AJAX</atom:title>
   <atom:updated>2011-07-21T07:10:42Z</atom:updated>
   <sword:treatment>The package has been deposited into DSpace. Each file has 
been unpacked and provided with a unique identifier. The metadata in the 
manifest has been extracted and attached to the DSpace item, which has been 
provided with an identifier leading to an HTML splash page.</sword:treatment>
   <sword:verboseDescription/>
   <sword:noOp>false</sword:noOp>
   <sword:userAgent>curl/7.19.6 (i386-apple-darwin10.0.0) libcurl/7.19.6 
OpenSSL/0.9.8r zlib/1.2.5</sword:userAgent>
   
<sword:packaging>http://purl.org/net/sword-types/METSDSpaceSIP</sword:packaging>
</atom:entry>

N.B.: Note in the curl command where it says {PASS****}.  This needs to be 
replaced, without the braces, by the demo.dspace.org pass****, which is the 
name of the repository software, all lower case.

** - Actually, my development copy didn't work initially, and I got the 415 
error too.  This is because I am running our bleeding-edge development version 
which will become version 1.8, and one of the things we are doing is 
re-organising the way all the configuration files work.  This highlighted a bug 
where SWORD now has its own configuration file, but the line which specified 
acceptable packaging types is not being read properly.  I will ensure this gets 
fixed a.s.a.p., but in the mean time can be fixed by putting the relevant line 
back in the normal dspace.cfg file:

sword.accept-packaging.METSDSpaceSIP.identifier = 
http://purl.org/net/sword-types/METSDSpaceSIP
sword.accept-packaging.METSDSpaceSIP.q = 1.0

So to conclude, that package looks fine, it is likely to be a misconfiguration 
of DSpace if it is failing to accept that package.

Thanks,


Stuart Lewis
Digital Development Manager
Te Tumu Herenga The University of Auckland Library
Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand
Ph: +64 (0)9 373 7599 x81928



On 21/07/2011, at 12:51 AM, Sheppard, Nick wrote:

> I am experimenting with depositing a simple METS package into DSpace and 
> EPrints. The test package that I am using was given to me by the folk at 
> EDINA; originally used in testing by Ian Stewart of OA-RJ into Jorum (DSpace) 
> and I also successfully deposited into Jorum using the client from 
> Sourceforge. I'm unable to test with Jorum at the moment until management is 
> fully transferred to Mimas but recently posted to the list about problems I 
> was having depositing into the NDLR in Ireland (also DSpace). Stuart Lewis 
> has been helping me out but I have since tried to deposit the same package 
> intohttp://demo.dspace.org/ but that is also failing with a similar message 
> to the NDLR (415, Unsupported Media Type).
>
> I *have* successfully deposited the package to an EPrints install though no 
> metadata has been picked up from mets.xml (I'm a bit out of my depth but it's 
> my understanding that a .zip comprising a file - in this case PDF - and 
> mets.xml should go into a repository as a full item with metadata record?)
>
> If anyone is able to help you can get the package I've just deposited from 
> http://training1.eprints.org/112/ (though this is a training install so may 
> be reset at any time!).
>
> As we want to deposit into EPrints and DSpace repositories I'm particularly 
> interested in whether a single package format will work with both.
>
> Thanks
>
> Nick
>
>
> Nick Sheppard
> Repository Developer
> The Headingley Library
> James Graham Building
> Leeds Metropolitan University
> Beckett Park
> Leeds
> LS6 3QS
> Tel: 0113 812 4731
> email: n.e.shepp...@leedsmet.ac.uk
> blog: http://repositorynews.wordpress.com/
>
> Technical Officer - UK Council of research Repositories (UKCoRR) - 
> http://www.ukcorr.org/
>
>
>
> To view the terms under which this email is distributed, please go to 
> http://disclaimer.leedsmet.ac.uk/email.htm
>
> ------------------------------------------------------------------------------
> 10 Tips for Better Web Security
> Learn 10 ways to better secure your business today. Topics covered include:
> Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
> security Microsoft Exchange, secure Instant Messaging, and much more.
> http://www.accelacomm.com/jaw/sfnl/114/51426210/_______________________________________________
> sword-app-tech mailing list
> sword-app-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech




To view the terms under which this email is distributed, please go to 
http://disclaimer.leedsmet.ac.uk/email.htm

------------------------------------------------------------------------------
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC can 
improve internal communications as well as offer faster, more efficient ways
to interact with customers and streamline customer service. Learn more!
http://www.accelacomm.com/jaw/sfnl/114/51426253/
_______________________________________________
sword-app-tech mailing list
sword-app-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sword-app-tech

Reply via email to