From: Ling He <li...@yo...> - 2012-10-11 18:54:19
|
Hi Richard, The one you are using is the Edit Media IRI (EM-IRI), but you want the Edit-IRI, which will be like http://[swordbaseurl]/edit/[item id] ------------------------------------------------ I tried this, but I only got a deposit receipt without 200 OK Location: [Edit-IRI] (I should get the HTTP status code according to Sec 9.3 Sword 2.0 profile, right?) And my item is still in workspace, is it supposed to generate a handle ID and move from "Unfinished submissions" to "Archived submissions" once deposit completed? My curl command is like this: curl -u "username:password" -H "In-Progress: false" -H "Content-Length: 0" http://[swordbaseurl]/edit/[item id] And I have two other questions regarding sword deposit. When I first retrieved the service document, I got error. I found the reason is that one of our collection name included the letter " <http://pi.library.yorku.ca/dspace/handle/10315/18071>É", is sword v2 designed to support utf-8? Or may some of my configurations are wrong? I used SimpleDCEntryIngester to ingest DC metadata, but during my testing, simpleDC mapping for simpledc.creator has to be dc.creator, if I mapped todc.contributor.author, I got error. Do you have any idea what this problem is? Thanks so much for all your assistance! Ling On 11/10/2012 12:36 PM, Richard Jones wrote: > Hi Ling > >> 2/ send your metadata separately, embedded in an Atom Entry. If this >> is dc metadata, the SimpleDCEntryIngester will suffice, otherwise >> you'd need to write another entry ingester. >> >> ------------------------------------------------------------- >> Yes, I successfully ingested the metadata and the file into our test env >> using Easydeposit. My question is if I can ingest objects in batch, >> Easydeposit can only submit and ingest one record at a time. > Ah, no, so SWORDv2 is a single item deposit protocol, you will only be > able to do one item at a time over the API. > >> If the SWORD deposit comes with an In-Progress: false header, it will >> automatically be injected into the workflow; the items then follow the >> standard workflow/archive process for DSpace. So when you are >> finished depositing, just send a "complete" request (spec section 10 - >> all of the clients support this I think). >> >> ------------------------------------------------------- >> By "complete" request, you mean send " In-Progress: false" to SWORD Edit IR? >> Does SWORD Edit IR mean http://[swordbaseurl]/edit-media/[workspace ID] for >> DSpace? I tried curl, but always got a 400 response. > The one you are using is the Edit Media IRI (EM-IRI), but you want the > Edit-IRI, which will be like > > http://[swordbaseurl]/edit/[item id] > > Cheers, > > Richard > >> Thanks, >> Ling >> >> On 03/05/2012 10:23 AM, Richard Jones wrote: >> >> Hi Ling, >> >> On 3 May 2012 14:28, Ling He<li...@yo...> wrote: >> >> Hi, >> >> I have been testing how to deposit items into DSpace Workspace using >> Sword2 for weeks. From my testing, SwordMETSContentIngester will direct >> ingest the package into archive and generate the external identifier, so >> if I want my items stay in workspace first, I can't really use mets >> ingester, right? I tested BinaryContentIngester and >> SimpleZipContentIngester, they can ingest the items into workspace, but >> only for the bitstream not metadata, so how can I put my metadata in? Do >> I need to write my own ingester and client to do it or any other >> existing ingesters I can use? >> >> You have a couple of options: >> >> 1/ If you have a custom package format which contains your metadata >> you need to write an ingester for it which will create DSpace Items >> from your packaged content/metadata. The METS ingester for SWORDv2 is >> experimental, and I wouldn't use it. >> >> 2/ send your metadata separately, embedded in an Atom Entry. If this >> is dc metadata, the SimpleDCEntryIngester will suffice, otherwise >> you'd need to write another entry ingester. >> >> You can see which protocol operations are available to you by looking >> at the spec, here: >> http://swordapp.github.com/SWORDv2-Profile/SWORDProfile.html >> >> Also, take a look at the swordv2-server.cfg in the >> dspace/config/modules directory, which has some comments inline which >> show how to use the plugins for content ingesters. >> >> And how can I move the items from >> workspace to archive, if later on the workspace item is approved to >> deposit into our DSpace permanently? Will every workspace item have to >> go through the DSpace submission workflow or is there a quick way to do it? >> >> If the SWORD deposit comes with an In-Progress: false header, it will >> automatically be injected into the workflow; the items then follow the >> standard workflow/archive process for DSpace. So when you are >> finished depositing, just send a "complete" request (spec section 10 - >> all of the clients support this I think). >> >> Cheers, >> >> Richard >> >> Thanks, >> >> -- >> Ling He >> Digital Services Librarian >> York University Libraries >> Scott Library, 4700 Keele St. Room 105D, Toronto ON M3J 1P3 >> Email: li...@yo... >> Phone: 416-736-2100 x20461 >> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> sword-app-tech mailing list >> swo...@li... >> https://lists.sourceforge.net/lists/listinfo/sword-app-tech >> >> >> >> -- >> Ling He >> Digital Services Librarian >> York University Libraries >> Scott Library, 4700 Keele St. Room 105D, Toronto ON M3J 1P3 >> Email: li...@yo... >> Phone: 416-736-2100 x20461 >> > > -- Ling He Digital Services Librarian York University Libraries Scott Library, 4700 Keele St. Room 105D, Toronto ON M3J 1P3 Email: li...@yo... Phone: 416-736-2100 x20461 |