[EP-tech] Re: Some questions about SWORDv2/CRUD endpoint
richard at cottagelabs.com
Sat Aug 29 11:04:29 BST 2015
I've made a little more progress, and just have one specific question I
wonder if someone can point me in the right direction on.
I've found an Atom.xsl stylesheet in EPrints/Plugins/Import/XSLT which
seems to imply that there /is/ a default atom import plugin. My sword
deposit contains atom metadata, so this stylesheet should work nicely to
create a new eprint with the relevant metadata. The only thing is, it
doesn't appear to get called during deposit. In Eprints/Apache/CRUD.pm,
there's this code (Line 762 in sub import_plugins):
my @plugins = $self->repository->get_plugins(
type => "Import",
can_produce => $self->accept_type,
and it's being called with an accept_type of "application/atom+xml;
type=entry". My guess is that the Atom.xsl stylesheet is not being
understood as the plugin which can handle this format.
I read through this documentation:
And it appears to suggest that the XSLT plugins need a wrapper around them
for the specific mimetype that they need to work with - is this right? Or
is there some way to get the XSLT import plugin to run as is?
If there's some other documentation that I've overlooked so far, any links
On 28 August 2015 at 09:50, Richard Jones <richard at cottagelabs.com> wrote:
> Actually, I see an AtomMultipart.pm in the EPrints/Plugin directory, and
> it in turn tries to load a plugin which supports application/atom+xml, but
> I can't find a plugin that supports that particular format. I think this
> is probably the same issue, then, as my (1) below - there doesn't appear to
> be a default atom plugin - is that right?
> On 28 August 2015 at 09:32, Richard Jones <richard at cottagelabs.com> wrote:
>> Hi Folks,
>> We're currently working on a new version of the Jisc Publications Router,
>> and am looking into how best to put the content into an EPrints via
>> SWORDv2. I'm encountering a few oddities, though, and I wonder if someone
>> can clarify how that endpoint works for me?
>> 1/ Posting an atom entry document to /id/content should result in the
>> creation of a new eprint populated with the metadata from that document,
>> but instead it creates an eprint with no metadata and the atom xml attached
>> as a file called "main.bin". Perhaps I'm missing some crosswalk
>> 2/ My service document says:
>> But when I PUT a file of this format tot he media resource I get a
>> "package format not supported" error.
>> Also, it does not say that it supports SimpleZip, but if I PUT a
>> SimpleZip it works fine. Is there a place that I can customise the
>> accept/acceptPackaging entries in the service document?
>> 3/ Completing deposit doesn't appear to work. When I POST to the
>> eprint's Edit-IRI, I get a 405 Method Not Allowed, but it should update the
>> Looking at the code, with my limited Perl skills, it looks like the full
>> SWORDv2 protocol is not supported - is there some documentation that will
>> tell me what features are supported? For example, does multipart deposit
>> Any tips/pointers much appreciated.
>> Richard Jones,
>> Founder, Cottage Labs
>> t: @richard_d_jones, @cottagelabs
>> w: http://cottagelabs.com
>> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>> *** Archive: http://www.eprints.org/tech.php/
>> *** EPrints community wiki: http://wiki.eprints.org/
>> *** EPrints developers Forum: http://forum.eprints.org/
> Richard Jones,
> Founder, Cottage Labs
> t: @richard_d_jones, @cottagelabs
> w: http://cottagelabs.com
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/
Founder, Cottage Labs
t: @richard_d_jones, @cottagelabs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Eprints-tech