Hi Stuart,
As per your suggestion, I raised logging level to DEBUG and attempted a manual deposit using CURL. (SWORD 1.3, Dspace 1.5.2) Got the following debug /error messages in dspace.log file that seemed odd: (The whole log file is attached) ERROR org.purl.sword.server.DepositServlet @ X_NO_OP value is null (found something similar in your post in jira http://jira.dspace.org/jira/browse/DS-199 about the error of X_NO_OP being "true" and yet the deposit being successful. Why are we getting null instead of true? Not sure if this affects our deposit and if this leads to the following error messages or not) 12:45:50,190 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query "select * from handle where handle = ? " with parameters: posit/123456789/2 (notice the parameter value is "posit/123456789/2" instead of "deposit/123456789/2") 12:45:50,192 ERROR org.purl.sword.server.DepositServlet @ org.purl.sword.base.SWORDErrorException: The deposit URL does not resolve to a valid deposit target I also want to add that I tried the deposit using DSpace SWORD 1.3 that did not have the patches for Article Authoring and yet the same error occurred. Need to move beyond this with your help. Thanks a lot, -Deb From: Stuart Lewis [mailto:[email protected]] Sent: Tuesday, September 29, 2009 6:53 PM To: Debashree Pati Cc: [email protected] Subject: Re: [Dspace-tech] OfficeSWORD Hi Deb. Here's some more information, regarding the failed sword post, that might help detect the problem: Messages Panel output for the failed post: status: Setting the username/password: [email protected] password status: Posting file to: http://75.101.130.190/sword/deposit/123456789/2 status: Unable to access resource. Is there any information in [dspace]/log/dspace.log? Try raising the logging level to DEBUG if nothing is shown normally. I'm not sure what 'Unable to access resource' is referring to. You could try depositing manually using CURL to see what happens in case this is a problem with the client rather than the server. curl --basic --user "[email protected]:your-password" -i --data-binary "@/path/to/example.zip" -H "Content-Type: application/zip" -H "X-Packaging: http://purl.org/net/sword-types/METSDSpaceSIP"; -vvv http://75.101.130.190/sword/deposit/123456789/2 The extra logging information you sent was related to the parsing of the service document. It highlighted one small issue where DSpace is not setting the atom:generator element which according to the spec is SHOULD (not MUST), and since we are setting it in deposit responses I've patched 1.6 to fix this issue. However this wouldn't cause this problem. http://jira.dspace.org/jira/browse/DS-328 Thanks, Stuart Lewis IT Innovations Analyst and Developer Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: 64 9 373-7599 x81928 http://www.library.auckland.ac.nz/
dspace_log.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
