Thanks very much,

Mark

The best option for an email list might be the SWORD-APP-TECH email list:

– https://lists.sourceforge.net/lists/listinfo/sword-app-tech

Packaging in SWORD is a big can of worms, and one that personally I think we need to raise again. For example OAI-PMH works well, because you know that you can always get unqualified Dublin Core out of it (at a minimum). SWORD needs a documented and agreed simple packaging standard that we can all support as a minimum. Without that, if we accept different packaging formats, we’ll never achieve the levels of interoperability that we desire. It just so happens that DSpace / Fedora / EPrints all accept the SWAP/METS mix after it was first developed for SWORD in DSpace, but there is no compulsion for repositories to support it.

Thanks,

Stuart

On the other hand, none of the Structural Requirements in the DSpace profile actually say that conforming documents MUST contain a MODS description; requirement 13 says “at least one dmdSec containing the metadata record for the entire DSpace item” but the closest the profile comes to being prescriptive about MODS is in the Descriptive Metadata section, where it says “As declared in Structural Requirements #16, DSpace requires just one MODS record that describes the entire item” (requirement 16 deals with how DSpace implementations should deal with sourceMD attributes, not about descriptive metadata so it is possible this reference is an editorial slip).

The reason I am digging out this requirement is that I am considering developing a proof of concept SWORD server for CONTENTdm, and I’d like to know if I need to worry about crosswalking submissions from MODS or just SWAP (at the beginning, anyway).

See: http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile#Scholarly_Works_Application_Profile

Thanks,

Stuart

I have a question about the use of SWAP. Neither the SWORD 1.3 spec nor the DSpace METS SIP Profile mention it, yet it appears to be handled by all the SWORD server implementations I have looked at (DSpace, ePrints, Fedora). Where is the use of SWAP described in relation to the SWORD spec?

The application has been playing up slightly this morning. I’ve done two things which may help (changed the way the transfer works to not use chunked transfer, and set a Content-Length header). I’ve also restarted the web server which seems to have made it a bit better.

Could you email me a screen shot of the page that fails if it still doesn’t work for you?

Thanks,

Stuart

A little further information on the problem. Actually, the package is being uploaded, and I see it when I look at my submissions within DSpace. But I still get the 200 error code in the Sword Facebook App, and I cannot see my submission from within the it.

Thanks,
Jason

I have updated to 1.5.2 and after adjusting a few options in my config file, I have gotten close with getting the Facebook app to work with my repository. I can now submit the package, and I can see the atom entry generated when I tail the logs. Unfortunately, I now get a code 202 error from the app.

Any suggestions?

Really, really nice app, though. Love the work you’re doing with SWORD. All of it has serious potential at integrating a DSpace submission step into the regular workflow of normal people.

Which version of DSpace are you using? It will only work with 1.5.2.

Thanks,

Stuart