Hi Andrew, Unfortunately you have hit one of the limitations with the current DSpace SWORD implementations. Due to the way DSpace currently works, it does not generate an item handle until the item has completed its journey through the workflow(s). And to compound this problem, the media link will not return anything for items that are due to go through a workflow. It is probably worth submitting this as a bug in JIRA (jira.dspace.org) so that we can assess it for future releases. The first of these issues (and therefore the second too) may get fixed in 1.6 if we can find the effort required to port some previous work on the identifier system to 1.6 to ensure that all items are given item identifiers. If this work does not get incoroporated in 1.6, we could look at adding a new DSpace table to associate a new SWORD deposit ID with the final ID and return that to the user via the media link. We get around this issue at Auckland in one of two ways. 1) If our SWORD submission system *must* go through a workflow, we generate them an ID on the client side, and carry that through to DSpace and our internal workflows. We then link the items up once workflow has been completed via manual processes. 2) If a DSpace identifier is needed immediately, we don't set a workflow, and process the item a.s.a.p. once we get the email informing us that a new item has been submitted. Neither are great solutions, but they work for now. Thanks, Stuart Lewis Digital Services Programmer 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/ <https://webmail.lbr.auckland.ac.nz/exchweb/bin/redir.asp?URL=http://www.library.auckland.ac.nz/>
________________________________ From: Andrew Bai [mailto:[email protected]] Sent: Mon 01/06/2009 17:36 To: [email protected] Subject: [Dspace-tech] SWORD: Polling for Handle Availibility When a"accept/reject'' Workflow Process Required for the CollectionDeposit Hi All, My apology if you received this post the second time. This is a resend of the previous post since I didn't see my email coming to myself or showing up in the forum. I just joined the community and not yet familiar with the posting rules. Thanks Andrew Bai Senior Application Developer ResearchMaster Pty Ltd ________________________________ From: Andrew Bai Sent: Monday, 1 June 2009 9:23 AM To: '[email protected]' Subject: SWORD: Polling for Handle Availibility When a "accept/reject'' Workflow Process Required for the Collection Deposit Hi all, I'm trying to write code to enable DSpace deposit from our research software. I can successfully deposit to DSpace using SWORD. However if the COLLECTION in DSpace requires an "accept/reject" workflow step, I can't get the handle immediately in the SWORD response. I've looked into SWORD and ATOMPUB profile carefully and found no support for status polling. To discourage me more, I found that in the response I received from the deposit, the "atom entry" doesn't even have a unique id. Instead it just has the following url that points to the homepage of the DSpace JSP user interface: http://vm:12:8080/jspui. It also doesn't have a "atom:content" entry which is required according to SWORD profile 1.3.1. By the way, I'm testing agaist the latest DSpace 1.5.2 release. Could anyone help me to point out a direction on how to poll the status of a deposit from a third party product pragmatically? Thank you. The following xml code is the response I got with my test deposit. <?xml version="1.0" encoding="UTF-8" ?> - <file:///C:/Projects/104%20-%20DSpace/deposit_response_rmpl_withworkflow.xml##> <atom:entry xmlns:atom="http://www.w3.org/2005/Atom"; xmlns:sword="http://purl.org/net/sword/";> <atom:id>http://vm12:8080/jspui</atom:id> - <file:///C:/Projects/104%20-%20DSpace/deposit_response_rmpl_withworkflow.xml##> <atom:author> <atom:name>[email protected]</atom:name> </atom:author> <atom:generator uri="http://www.dspace.org/ns/sword/1.3.1"; version="1.3" /> <atom:published>2001-02</atom:published> <atom:summary type="text">Dispersed repeat elements contribute to genome instability by de novo insertion and unequal recombination between repeats. To study the dynamics of these processes, we have developed single DNA molecule approaches to detect de novo insertions at a single locus and Alu-mediated deletions at two different loci in human genomic DNA. Validation experiments showed these approaches could detect insertions and deletions at frequencies below 10(-6) per cell. However, bulk analysis of germline (sperm) and somatic DNA showed no evidence for genuine mutant molecules, placing an upper limit of insertion and deletion rates of 2 x 10(-7) and 3 x 10(-7), respectively, in the individuals tested. Such re-arrangements at these loci therefore occur at a rate lower than that detectable by the most sensitive methods currently available.</atom:summary> <atom:title type="text">Attempts to detect retrotransposition and de novo deletion of Alus and other dispersed repeats at specific loci in the human genome</atom:title> <atom:updated>2009-05-28T02:35:02Z</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>[2009-05-28 12:34:50.796] Initialising verbose deposit; [2009-05-28 12:34:50.812] Performing deposit using location: http://vm12:8080/sword/deposit/123456789/2; [2009-05-28 12:34:50.812] Location resolves to collection with handle: 123456789/2 and name: First Collection; [2009-05-28 12:34:50.812] User is authorised to submit to collection; [2009-05-28 12:34:50.812] Authenticated user: [email protected]; [2009-05-28 12:34:50.812] Initialising depositor for an Item in a Collection; [2009-05-28 12:34:50.812] DSpace will store an original copy of the deposit, as well as ingesting the item into the archive; [2009-05-28 12:34:50.812] Loaded ingester: org.dspace.sword.SWORDMETSIngester; [2009-05-28 12:34:50.812] Using package manifest format: METS; [2009-05-28 12:34:50.812] Loaded package ingester: org.dspace.content.packager.DSpaceMETSIngester; [2009-05-28 12:35:02.875] Workflow process started; [2009-05-28 12:35:02.875] Updated date added to response from item metadata where available; [2009-05-28 12:35:02.953] Ingest successful; [2009-05-28 12:35:02.953] Item created with internal identifier: 11; [2009-05-28 12:35:02.953] No external identifier available at this stage (item in workflow); [2009-05-28 12:35:02.953] Archive ingest completed successfully; [2009-05-28 12:35:03.125] Original package stored as sword-2009-05-28.original, in item bundle org.dspace.content.bun...@11a20af; [2009-05-28 12:35:03.125] Initialising ATOM entry generator for an Item; [2009-05-28 12:35:03.140] Total time for deposit processing: 12344 ms;</sword:verboseDescription> <sword:noOp>false</sword:noOp> <sword:packaging>http://purl.org/net/sword-types/METSDSpaceSIP</sword:packaging> </atom:entry> Thanks, Andrew Bai Senior Application Developer ResearchMaster Pty Ltd
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
