sword-app-tech — Mailing list for discussion of SWORD implemenation and development.

[sword-app-tech] New Book: The Open Revolution - rewriting the rules of the information age

[Rufus P. <ruf...@ok...>]

If you are not able to see this mail, click http://3lgi9.r.ah.d.sendibm4.com/z0lerpu13f.htmlThe Open Revolution: rewriting the rules of the information age
 
Hi &lt,
 
This is one-off email to share with you the release of my book, The Open Revolution: rewriting the rules of the information age.     
       [ Get the book on OpenRevolution.net » ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/mGnLQVCn8-m2GOJcZg0wXf9HIkjUVg5T0vsobD59Tg_tOliDlrzmyoWlMrnS8h0IXZs6lbwkWAwSTx6jEPHFrWFtXZ1MO_TyHne3NmRTb-sVL4EP9Q )       
 

This book is about something bigger than tech itself. It’s about information, ownership and control in a digital age. It talks directly to a number of lives issues, ranging from access to medicines, to the future of work and privacy, digital monopolies and power in a connected world.     


[  ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/JYQua6ifIKU27lwPkn8az4RHeiP-UB6-DKe8M-OmtrFBwp57BR46K4g1sxi_rsZl3paJOXUB3l1qG6RCEdQENQ_Ou6ywdxvXmrK17YNA7nYXSPmE1w )

 
Will the digital revolution give us digital dictatorships or digital democracies? Forget everything you think you know about the digital age. It’s not about privacy, surveillance, AI or blockchain—it’s about ownership. Because in a digital age, who owns information controls the future.

 
Today’s “Closed” digital economy is the source of problems ranging from the power of a handful of tech monopolies to control how we think and vote, to unaffordable medicines, to growing inequality. The solution is not technological but political: a choice between making information Open, shared by all, or making it Closed, exclusively owned and controlled.
 
By choosing Open we can make a more equitable, innovative and profitable future for all.     
       [ Find out more on OpenRevolution.net » ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/aQ5JCLiqM6h8a8PlEXa-NqBORxbgy41Aoe1yWhguWhYlxg9nMxRVYaSqxNFzyccRU_UFcotXka3F5A13peyqWT_dOUvi0yCQatKZOkAzoqDR_Wm52g )       
 
Order directly on [ Amazon UK ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/IVOR9AGQzjgRuIBBuB4fSxYISifT5mH16_Z7MIpAiWzJZJObk4vsmaAVsY5k9CTGUwxvRwtvb9k6A5hd2uhydSIb3IWTvV7N-HiQg5f5HZ_BhHbWUw ) - [ Amazon US ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/ogmZJzM0TDbIKxT7S7OcuKnXl79_XzeukpJh4JczMRU8DWOHIFo0RQXaSqj-oDS5vbcPeDhZ7dM5LVxsi9cskdetJ3BpqprjW9P1yD5elxPRipcrAw )
 
I also warmly invite you to share this book and its ideas. We will only realize an Open world when more people are present to its potential. The book is itself openly licensed so you are free to share and reuse it however you wish!
 

Post for sharing on [ Facebook ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/kNHfWsasIkuPnJVXPAICJbBEtE-KCde266i4Ta3c0k9ygHq5DAXvnFjTekd-Svk6P0g8wXkab0RMBKT1IK-s8uLff5sIkT4ajzngtmp3cVBDgbtR1Q ) - [ Twitter ]( http://3lgi9.r.ah.d.sendibm4.com/mk/cl/xFck5GIUfuiS4WAsHz0IJl3SMd8lX_BkvjHaF1ZnlW_uFTdbGjgR6-wpRy1An66HeSEKLKbT7mvqjoV0RSKwMEie8MqKouh12Xp0s9rLPdqIUCCr0Q )

Thank you,

Yours,

Rufus Pollock
–
Building wise societies and an information age that works for everyone - https://rufuspollock.com/
Founder and President of Open Knowledge - https://okfn.org/
Co-Founder, Art / Earth / Tech - https://artearthtech.com/manifesto
Shuttleworth and Ashoka Fellow
Previously Mead Fellow in Economics at the University of Cambridge    If you wish to unsubscribe from our newsletter, click http://3lgi9.r.ah.d.sendibm4.com/z0lerpu13g.html

Re: [sword-app-tech] Documentation

[Richard J. <ri...@co...>]

Hi Florian,

Just to +1 what Ralf said: the swordapp.org website is the best place to
start for resources.

Depending on what version of the spec you are after, you may find these two
pages in particular useful:

SWORDv1: http://swordapp.org/sword-v1/the-specification/
SWORDv2: http://swordapp.org/sword-v2/sword-v2-specifications/

There is also some information about the upcoming version that we are
working on right now, here: http://swordapp.org/swordv3/

Hope that helps.

All the best,

Richard


On 4 January 2018 at 08:21, Ralf Claussnitzer <
ral...@sl...> wrote:

> Hi Florian,
>
> you may want to check out http://swordapp.org/
>
> Regards,
> Ralf
>
> On 12/31/2017 10:22 AM, Florian Wille wrote:
>
> Hello List,
> I am looking for some Documentation for the SWORD Protocol where there ist
> described which commands exist, how to issue them and what kind of answers
> to expect, something like:
> https://www.openarchives.org/OAI/openarchivesprotocol.html
> only for SWORD maybe not in that depths but like it...
> Could someone point me to the right direction I can't seem to find
> something usefull to me in that manner.
> Kind Regards and
> best wishes for the upcoming year
> Florian
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> sword-app-tech mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>
>


-- 
Richard Jones,
Founder, Cottage Labs
https://cottagelabs.com || @cottagelabs

Lantern: https://lantern.cottagelabs.com
Repository Solutions: https://cottagelabs.com/repository

Re: [sword-app-tech] Documentation

[Ralf C. <ral...@sl...>]

Hi Florian,

you may want to check out http://swordapp.org/

Regards,
Ralf


On 12/31/2017 10:22 AM, Florian Wille wrote:
> Hello List,
> I am looking for some Documentation for the SWORD Protocol where there 
> ist described which commands exist, how to issue them and what kind of 
> answers to expect, something like:
> https://www.openarchives.org/OAI/openarchivesprotocol.html
> only for SWORD maybe not in that depths but like it...
> Could someone point me to the right direction I can't seem to find 
> something usefull to me in that manner.
> Kind Regards and
> best wishes for the upcoming year
> Florian
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech

[sword-app-tech] Documentation

[Florian W. <wi...@ub...>]

Hello List,
I am looking for some Documentation for the SWORD Protocol where there 
ist described which commands exist, how to issue them and what kind of 
answers to expect, something like:
https://www.openarchives.org/OAI/openarchivesprotocol.html
only for SWORD maybe not in that depths but like it...
Could someone point me to the right direction I can't seem to find 
something usefull to me in that manner.
Kind Regards and
best wishes for the upcoming year
Florian

Re: [sword-app-tech] Sample Client

[Richard J. <ri...@co...>]

Hi Florian,

As Phis says, there's nothing for testing quite as you describe.

The best option you have for a quick test of your interface is to use the
Java Client's SpecTests which aim to test that a given server meets the
specification.  The code is here:

https://github.com/swordapp/JavaClient2.0/blob/master/src/test/java/org/swordapp/client/test/SpecTests.java

You just need to provide your own config for it, like this one:

https://github.com/swordapp/JavaClient2.0/blob/master/src/test/resources/spectests.properties

There are similar tests in the python client here:

https://github.com/swordapp/python-client-sword2/blob/master/tests/spec/test_spec.py

You may want to extend these tests for your particular packaging and
metadata formats, of course.

Cheers,

Richard




On 20 December 2017 at 15:47, Philip Durbin <phi...@ha...>
wrote:

> If there's a generic, standalone SWORD client that "just works" I'm
> not aware of it (but would like to know about it!).
>
> I think you're right that you have go write your own solution using
> one of the toolkits mentioned at
> http://swordapp.org/sword-v2/sword-v2-implementations/
>
> Phil
>
> On Wed, Dec 20, 2017 at 9:00 AM, Florian Wille <wi...@ub...>
> wrote:
> >
> > Hello List,
> > can someone recommend me a sample SWORD Client for testing my DSpace
> > instance? Is the sth. like a ready to use GUI or Web Client, or do I
> kind of
> > have to make my own from the Java/Ruby/Python/PHP Toolkits?
> > Best Regards
> > Florian
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > sword-app-tech mailing list
> > swo...@li...
> > https://lists.sourceforge.net/lists/listinfo/sword-app-tech
> >
>
>
>
> --
> Philip Durbin
> Software Developer for http://dataverse.org
> http://www.iq.harvard.edu/people/philip-durbin
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>



-- 
Richard Jones,
Founder, Cottage Labs
https://cottagelabs.com || @cottagelabs

Lantern: https://lantern.cottagelabs.com
Repository Solutions: https://cottagelabs.com/repository

Re: [sword-app-tech] Sample Client

[Philip D. <phi...@ha...>]

If there's a generic, standalone SWORD client that "just works" I'm
not aware of it (but would like to know about it!).

I think you're right that you have go write your own solution using
one of the toolkits mentioned at
http://swordapp.org/sword-v2/sword-v2-implementations/

Phil

On Wed, Dec 20, 2017 at 9:00 AM, Florian Wille <wi...@ub...> wrote:
>
> Hello List,
> can someone recommend me a sample SWORD Client for testing my DSpace
> instance? Is the sth. like a ready to use GUI or Web Client, or do I kind of
> have to make my own from the Java/Ruby/Python/PHP Toolkits?
> Best Regards
> Florian
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>



-- 
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[sword-app-tech] Sample Client

[Florian W. <wi...@ub...>]

Hello List,
can someone recommend me a sample SWORD Client for testing my DSpace 
instance? Is the sth. like a ready to use GUI or Web Client, or do I 
kind of have to make my own from the Java/Ruby/Python/PHP Toolkits?
Best Regards
Florian

[sword-app-tech] SWORDV3 Project - Stakeholder Call

[Richard J. <ri...@co...>]

Hi Folks,

The SWORD protocol was created in 2007 to allow simple machine-to-machine
deposit of papers into repositories. Approximately five years later,
SWORDV2 added the ability to update previously transferred objects along
with more use-case specific extensions to AtomPub.

The SWORDV3 project has been funded by Jisc with two key aims for the next
generation of the SWORD Protocol:


   -

   To bring SWORD up-to-date with the developments in the repository sphere
   in the last 5 years, with alignment to new protocols such as
   OAI-ResourceSync and new use-cases such as data publishing and complex
   objects.
   -

   To establish community and governance mechanisms for the standard and
   supporting code libraries to ensure ongoing maintenance and evolution. This
   will include a technical validation process to allow third party libraries
   to be hosted under the SWORD brand.



The project was formally announced at PASIG 2017 in Oxford and the RDA 10th
Plenary in Montreal in the last two weeks. We are looking for expressions
of interest in becoming involved as stakeholders in the project: to make
suggestions, review activities and meet as required over the coming months.
In particular, we are interested in making contact with people who may wish
to develop SWORD V3 libraries for their preferred platforms or languages
since we aim to provide some support for such activities during the
project. Please contact one of the project team (ideally by mid-October) if
you are interested in participating, and indicate if you are interested in
the technical or community aspects of the project (or both!).

The key members of the project team are:


   -

   Dom Fripp - Jisc (Funder) - Project Manager, SWORD user through the Jisc
   Research Data Shared Service
   -

   Richard Jones - Cottage Labs Ltd - Technical Lead, SWORD contributor and
   implementer
   -

   Neil Jefferies - Bodleian Libraries, University of Oxford - Community
   Lead, SWORD user through Data2paper project (and internally within the
   Bodleian Library)


On the technical side, we are creating a document that brings together the
change requests and new use cases that have collected since the release of
SWORDV2, culled from the github site, message posts and preliminary
discussions with some stakeholders earlier this year. This has also
suggested a way forward that breaks with SWORD’s AtomPub roots in order to
provide a more up-to-date and flexible protocol. We will circulate this to
stakeholders soon.

On the community side, we will circulate a similar document outlining
possible models for developing the SWORD community in the future. This is a
much more open set of choices since the SWORD user-base has expanded
considerably since its first conception, and we are open to further
suggestions! The final arrangements must be aligned with community wishes
in order to be an effective sustainable solution.


Neil Jefferies (neil.jefferies[at]bodleian.ox.ac.uk)

Dom Fripp (dom.fripp[at]jisc.ac.uk)

Richard Jones (richard[at]cottagelabs.com)


-- 
Richard Jones,
Founder, Cottage Labs
https://cottagelabs.com || @cottagelabs

Lantern: https://lantern.cottagelabs.com
Repository Solutions: https://cottagelabs.com/repository

Re: [sword-app-tech] Asynchronous Deposit

[Richard J. <ri...@co...>]

Hi Sebastian,

One thing you could do in this situation is send back a deposit receipt as
soon as you can with a 202 (Accepted) header.  This at least means you can
continue to process the deposit asynchronously after the client has
finished sending data.  You may need to prepare all the relevant URIs, like
the Edit-IRI, and ensure that they return some suitable responses while the
item is still processing.

Technically, this status code is outside of the bounds of the spec, but we
did recommend a while back to introduce this as a feature and I hope that a
revision of the specification will be happening later this year where we
can make that change.

The other model I've come across is in use by DANS, which uses the
In-Progress header to allow you to send chunks of a full zip file in
successive, smaller, requests.  You can see their documentation for that
process here:

https://github.com/DANS-KNAW/easy-sword2#continued-deposit

The other thing I'd note is that multipart deposit hasn't turned out to
work very well for a lot of servers, so I'd avoid that mechanism if at all
possible.  Best approach, if you have an entry document, would be to send
the create with the entry document first, and then add the package later
via the edit media link.

Hope that helps.

Cheers,

Richard




On 21 June 2017 at 13:21, Sebastian Hofmann <hof...@un...> wrote:

> Hi,
>
> i used the JavaServer2.0 library to add Sword support to MyCoRe (
> http://mycore.de/) . We need Sword to transfer Files from Goobi (
> https://www.intranda.com/digiverso/goobi/) to MyCoRe based repositories.
> The implementation already works for small deposits, but we found some
> problems when we want to transfer bigger .zip Files up to 100gb+. We
> currently use the Multipart Deposit mechanism described in
> http://swordapp.github.io/SWORDv2-Profile/SWORDProfile.html.
> Our repository now needs much time to process these large deposits and
> send a deposit receipt back to the Client. For a 70gb .zip filled with
> uncompressed tif files our test repository needs 5 hours to validate,
> process and send back the deposit receipt. The connection is now 5 hours
> open without sending any data.
>
> Is there a best practice for sending such large deposits ? Should the
> client better send the .tiff sequential per .zip, or is there a way to send
> back a incomplete receipt with a "in proccessing" status ?
>
> Any suggestions would be great.
>
> Thanks
> Sebastian
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>
>


-- 
Richard Jones,
Founder, Cottage Labs
https://cottagelabs.com || @cottagelabs

Lantern: https://lantern.cottagelabs.com
Repository Solutions: https://cottagelabs.com/repository

[sword-app-tech] Asynchronous Deposit

[Sebastian H. <hof...@un...>]

Hi,

i used the JavaServer2.0 library to add Sword support to MyCoRe (http://mycore.de/ <http://mycore.de/>) . We need Sword to transfer Files from Goobi (https://www.intranda.com/digiverso/goobi/ <https://www.intranda.com/digiverso/goobi/>) to MyCoRe based repositories.
The implementation already works for small deposits, but we found some problems when we want to transfer bigger .zip Files up to 100gb+. We currently use the Multipart Deposit mechanism described in http://swordapp.github.io/SWORDv2-Profile/SWORDProfile.html <http://swordapp.github.io/SWORDv2-Profile/SWORDProfile.html>. 
Our repository now needs much time to process these large deposits and send a deposit receipt back to the Client. For a 70gb .zip filled with uncompressed tif files our test repository needs 5 hours to validate, process and send back the deposit receipt. The connection is now 5 hours open without sending any data.

Is there a best practice for sending such large deposits ? Should the client better send the .tiff sequential per .zip, or is there a way to send back a incomplete receipt with a "in proccessing" status ?

Any suggestions would be great.

Thanks
Sebastian

Re: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

[Julio P. A. <jul...@bi...>]

Hi John, you were right was that the server when making the deposit gave 
an error, I saw the error and I could solve it.

Thanks for your help

regards


El 12/06/2017 a las 23:13, John Salter escribió:
> I've had a bit more of a dig into this, this looks like the line of code that is generating the error:
> https://github.com/swordapp/swordapp-php-library/blob/a1ddeaac8708b7ad863538cb4811c39aeff3fbfb/swordappclient.php#L126
>
> That block of code handles the scenario where the response status is not a 2xx response.
> The document returned is parsed as XML, but in your case I think the page being returned is a 'standard' Tomcat error page, that has a <hr> an then 'Apache Tomcat [version]' - but is *not* valid XHTML / XML.
>
> The error handling looks like it would report the error message, but not the $sac_status, or the $sac_response - which might be helpful to work out why the SWORD endpoint is failing.
>
> Cheers,
> John
>
>
>
>
> -----Original Message-----
> From: John Salter [mailto:J.S...@le...]
> Sent: 12 June 2017 15:41
> To: Julio Pemau Alonso <jul...@bi...>; swo...@li...
> Subject: Re: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error
>
> Hi Julio,
> I'm not sure if I'm quite reading the error message properly, but it looks like there's a non-closed <HR> tag in the data:
> <HR size="1" noshade="noshade">
> To be valid XML, this would need to be self-closing:
> <HR size="1" noshade="noshade" />
> much like <br /> and <img ... /> tags.
>
> Cheers,
> John
>
> -----Original Message-----
> From: Julio Pemau Alonso [mailto:jul...@bi...]
> Sent: 12 June 2017 11:35
> To: swo...@li...
> Subject: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error
>
> Hi, I'm using the EasyDeposit SWORD tool, when trying to make a deposit,
> in the final part, I get the following error.
>
> ERROR - 2017-06-12 11:36:45 --> Severity: Warning  -->
> SimpleXMLElement::__construct(): Entity: line 1: parser error : Opening
> and ending tag mismatch: HR line 1 and body
> C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php
> 126
> ERROR - 2017-06-12 11:36:45 --> Severity: Warning  -->
> SimpleXMLElement::__construct(): ento.&lt;/u&gt;&lt;/p&gt;&lt;HR
> size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;h3&gt;Apache
> Tomcat/7.0.61&lt;/h3&gt;&lt;/body&gt;
> C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php
> 126
>
> Any suggestions?
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech

Re: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

[John S. <J.S...@le...>]

I've had a bit more of a dig into this, this looks like the line of code that is generating the error:
https://github.com/swordapp/swordapp-php-library/blob/a1ddeaac8708b7ad863538cb4811c39aeff3fbfb/swordappclient.php#L126 

That block of code handles the scenario where the response status is not a 2xx response.
The document returned is parsed as XML, but in your case I think the page being returned is a 'standard' Tomcat error page, that has a <hr> an then 'Apache Tomcat [version]' - but is *not* valid XHTML / XML.

The error handling looks like it would report the error message, but not the $sac_status, or the $sac_response - which might be helpful to work out why the SWORD endpoint is failing.

Cheers,
John




-----Original Message-----
From: John Salter [mailto:J.S...@le...] 
Sent: 12 June 2017 15:41
To: Julio Pemau Alonso <jul...@bi...>; swo...@li...
Subject: Re: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

Hi Julio,
I'm not sure if I'm quite reading the error message properly, but it looks like there's a non-closed <HR> tag in the data:
<HR size="1" noshade="noshade">
To be valid XML, this would need to be self-closing:
<HR size="1" noshade="noshade" />
much like <br /> and <img ... /> tags.

Cheers,
John

-----Original Message-----
From: Julio Pemau Alonso [mailto:jul...@bi...] 
Sent: 12 June 2017 11:35
To: swo...@li...
Subject: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

Hi, I'm using the EasyDeposit SWORD tool, when trying to make a deposit, 
in the final part, I get the following error.

ERROR - 2017-06-12 11:36:45 --> Severity: Warning  --> 
SimpleXMLElement::__construct(): Entity: line 1: parser error : Opening 
and ending tag mismatch: HR line 1 and body 
C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php 
126
ERROR - 2017-06-12 11:36:45 --> Severity: Warning  --> 
SimpleXMLElement::__construct(): ento.&lt;/u&gt;&lt;/p&gt;&lt;HR 
size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;h3&gt;Apache 
Tomcat/7.0.61&lt;/h3&gt;&lt;/body&gt; 
C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php 
126

Any suggestions?


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
sword-app-tech mailing list
swo...@li...
https://lists.sourceforge.net/lists/listinfo/sword-app-tech

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
sword-app-tech mailing list
swo...@li...
https://lists.sourceforge.net/lists/listinfo/sword-app-tech

Re: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

[John S. <J.S...@le...>]

Hi Julio,
I'm not sure if I'm quite reading the error message properly, but it looks like there's a non-closed <HR> tag in the data:
<HR size="1" noshade="noshade">
To be valid XML, this would need to be self-closing:
<HR size="1" noshade="noshade" />
much like <br /> and <img ... /> tags.

Cheers,
John

-----Original Message-----
From: Julio Pemau Alonso [mailto:jul...@bi...] 
Sent: 12 June 2017 11:35
To: swo...@li...
Subject: [sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

Hi, I'm using the EasyDeposit SWORD tool, when trying to make a deposit, 
in the final part, I get the following error.

ERROR - 2017-06-12 11:36:45 --> Severity: Warning  --> 
SimpleXMLElement::__construct(): Entity: line 1: parser error : Opening 
and ending tag mismatch: HR line 1 and body 
C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php 
126
ERROR - 2017-06-12 11:36:45 --> Severity: Warning  --> 
SimpleXMLElement::__construct(): ento.&lt;/u&gt;&lt;/p&gt;&lt;HR 
size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;h3&gt;Apache 
Tomcat/7.0.61&lt;/h3&gt;&lt;/body&gt; 
C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php 
126

Any suggestions?


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
sword-app-tech mailing list
swo...@li...
https://lists.sourceforge.net/lists/listinfo/sword-app-tech

[sword-app-tech] SimpleXMLElement::__construct(): Entity: line 1: parser error

[Julio P. A. <jul...@bi...>]

Hi, I'm using the EasyDeposit SWORD tool, when trying to make a deposit, 
in the final part, I get the following error.

ERROR - 2017-06-12 11:36:45 --> Severity: Warning  --> 
SimpleXMLElement::__construct(): Entity: line 1: parser error : Opening 
and ending tag mismatch: HR line 1 and body 
C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php 
126
ERROR - 2017-06-12 11:36:45 --> Severity: Warning  --> 
SimpleXMLElement::__construct(): ento.</u></p><HR 
size="1" noshade="noshade"><h3>Apache 
Tomcat/7.0.61</h3></body> 
C:\xampp\htdocs\EasyDeposit\application\libraries\swordapp-php-library\swordappclient.php 
126

Any suggestions?

Re: [sword-app-tech] tomcat - multipart/related - Content-Disposition: attachment

[David L. <dav...@uc...>]

Hi Phil
Yes, there still is a problem. I went back to the original version of 
SwordAPIEndpoint, which I had modified in this code. The original form 
has the same problem, the name attachment results in the Items 
(multiparts) not being selected. Running the original with form-data has 
an exception because the Headers values are null. This code uses: 
org.apache.commons.fileupload. There is a reasonable possibility that 
this code worked using fileupload but that code changed.

If possible I'd still like to find a solution using HttpServletRequest 
if there is one.

Thanks
David

On 6/13/2016 9:22 AM, Philip Durbin wrote:
> I don't mind the duplicate email but it's unclear to me if you are
> still having a problem. I sort of assume you are. This thread seems
> related: http://www.mail-archive.com/swo...@li.../msg00324.html
>
> Nice to see some activity on this list! It's been too quiet for over a year. :)
>
> Phil
>
> On Fri, Jun 10, 2016 at 6:04 PM, David Loy <dav...@uc...> wrote:
>> Sorry, this may be a duplicate submitted under a different work email id.
>>
>> On 6/10/2016 11:44 AM, David Loy wrote:
>>> I am developing a sword server using org.swordapp : sword2-server.
>>>
>>> The java servlet is being run on tomcat.
>>>
>>> I have successfully been able to run PUT multipart/related requests with:
>>>      Content-Disposition: form-data; name="payload";
>>> filename="114_archive.zip"
>>> however, using the SWORD standard form:
>>>      Content-Disposition: attachment; name="payload";
>>> filename="114_archive.zip"
>>> fails.
>>>
>>> The failure is caused because the HttpServletRequest#getParts will
>>> only return content using the Content-Disposition: form-data. In fact,
>>> the documentation for HttpServletRequest indicates that it only
>>> supports multipart/form-data.
>>>
>>> I'm interested in what mechanisms people have found for getting
>>> multipart/related with Content-Disposition: attachment; to work on
>>> tomcat hopefully without locally having to parse the HTTP request.
>>>
>>> Any suggestions would be great.
>>> Thanks
>>> David
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>> _______________________________________________
>> sword-app-tech mailing list
>> swo...@li...
>> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>
>

Re: [sword-app-tech] tomcat - multipart/related - Content-Disposition: attachment

[Philip D. <phi...@ha...>]

I don't mind the duplicate email but it's unclear to me if you are
still having a problem. I sort of assume you are. This thread seems
related: http://www.mail-archive.com/swo...@li.../msg00324.html

Nice to see some activity on this list! It's been too quiet for over a year. :)

Phil

On Fri, Jun 10, 2016 at 6:04 PM, David Loy <dav...@uc...> wrote:
> Sorry, this may be a duplicate submitted under a different work email id.
>
> On 6/10/2016 11:44 AM, David Loy wrote:
>> I am developing a sword server using org.swordapp : sword2-server.
>>
>> The java servlet is being run on tomcat.
>>
>> I have successfully been able to run PUT multipart/related requests with:
>>     Content-Disposition: form-data; name="payload";
>> filename="114_archive.zip"
>> however, using the SWORD standard form:
>>     Content-Disposition: attachment; name="payload";
>> filename="114_archive.zip"
>> fails.
>>
>> The failure is caused because the HttpServletRequest#getParts will
>> only return content using the Content-Disposition: form-data. In fact,
>> the documentation for HttpServletRequest indicates that it only
>> supports multipart/form-data.
>>
>> I'm interested in what mechanisms people have found for getting
>> multipart/related with Content-Disposition: attachment; to work on
>> tomcat hopefully without locally having to parse the HTTP request.
>>
>> Any suggestions would be great.
>> Thanks
>> David
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech



-- 
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[sword-app-tech] tomcat - multipart/related - Content-Disposition: attachment

[David L. <dav...@uc...>]

Sorry, this may be a duplicate submitted under a different work email id.

On 6/10/2016 11:44 AM, David Loy wrote:
> I am developing a sword server using org.swordapp : sword2-server.
>
> The java servlet is being run on tomcat.
>
> I have successfully been able to run PUT multipart/related requests with:
>     Content-Disposition: form-data; name="payload"; 
> filename="114_archive.zip"
> however, using the SWORD standard form:
>     Content-Disposition: attachment; name="payload"; 
> filename="114_archive.zip"
> fails.
>
> The failure is caused because the HttpServletRequest#getParts will 
> only return content using the Content-Disposition: form-data. In fact, 
> the documentation for HttpServletRequest indicates that it only 
> supports multipart/form-data.
>
> I'm interested in what mechanisms people have found for getting 
> multipart/related with Content-Disposition: attachment; to work on 
> tomcat hopefully without locally having to parse the HTTP request.
>
> Any suggestions would be great.
> Thanks
> David

[sword-app-tech] tomcat - multipart/related - Content-Disposition: attachment

[David L. <dav...@uc...>]

I am developing a sword server using org.swordapp : sword2-server.

The java servlet is being run on tomcat.

I have successfully been able to run PUT multipart/related requests with:
     Content-Disposition: form-data; name="payload"; 
filename="114_archive.zip"
however, using the SWORD standard form:
     Content-Disposition: attachment; name="payload"; 
filename="114_archive.zip"
fails.

The failure is caused because the HttpServletRequest#getParts will only 
return content using the Content-Disposition: form-data. In fact, the 
documentation for HttpServletRequest indicates that it only supports 
multipart/form-data.

I'm interested in what mechanisms people have found for getting 
multipart/related with Content-Disposition: attachment; to work on 
tomcat hopefully without locally having to parse the HTTP request.

Any suggestions would be great.
Thanks
David

[sword-app-tech] Should we extend the Repository API beyond SWORD?

[Philip D. <phi...@ha...>]

Hello! We love us some SWORD over in Dataverse land but in an upcoming
workshop we're going to be brainstorming about the future of how users
deposit data into our repository and we're considering alternatives.

I'm writing to invite everyone in the SWORD community to join us in this
brainstorming. Ideally you'd show up in Boston in June for the workshop but
more realistically we can have a nice discussion on this mailing list or
wherever* you like! :)

Things to think about:

- Does SWORD do everything you need?
- What are the pain points with SWORD, if any?
- Can repositories agree on a common deposit API standard? (Have they
already agreed on SWORD?)

Please see the workshop announcement below (also at
http://projects.iq.harvard.edu/dataverse-community-meeting/premeeting-workshop
) and the attached slide asking, "Should we extend the Repository API
beyond SWORD?" from a recent talk:
http://datascience.iq.harvard.edu/presentations/data-publishing-workflows-dataverse-0

Happy depositing! I'm curious what everyone thinks!

Phil

* I tend to prefer freenode IRC:
http://community.dataverse.org/community-groups/api.html . Here's a public
Google Doc for brainstorming:
https://docs.google.com/document/d/1vd5eLGhMqWB0R2_3jvprt5yZTDpaSev8cUOnCCK2hqQ/edit?usp=sharing

---------- Forwarded message ----------
From: Eleni Castro
Date: Mon, May 4, 2015 at 4:11 PM
Subject: [Dataverse-Users] Pre-Meeting Workshop: Common Models and APIs for
Data Publishing and Citation (June 9)
To: dat...@go...

Hi Dataverse Community,

On June 9, prior to the Dataverse Community Meeting (June 10-11), we are
hosting the *Common Models and APIs for Data Publishing and Citation
Workshop* at Harvard University, which is organized by Tim Clark, Sünje
Dallmeier-Tiessen, Mercè Crosas and the Dataverse team. This workshop will
focus on defining and improving standards for APIs, metadata profiles and
workflows across repositories, publishers’ systems and other data services
to achieve better interoperability (see agenda
<http://projects.iq.harvard.edu/dataverse-community-meeting/premeeting-workshop#agenda>
).

The day will be divided into two main sessions: (1) the first half will be
presentations on what has been done so far towards improving
interoperability of data systems, which then will be followed by (2) an
extensive panel discussion session, with active audience participation, on
the main challenges of interoperability, and what the next steps are based
on the different needs of the various stakeholder groups. By the end of
this workshop, we aim to have a set of action items and recommendations for
next steps on how we can best move towards common APIs and metadata so data
repositories, publishers’ systems, and data services can better talk to
each other.

This event is free and open to all, including researchers, librarians,
archivists, publishers, funders, and software developers. Space is limited,
so if you haven't already registered for the Community Meeting, please
register
<http://projects.iq.harvard.edu/dataverse-community-meeting/register> at
your earliest convenience.

A tentative agenda is listed below with specific questions that we would
like all attendees of this workshop to review ahead of time and help us
answer, so please let us know <su...@da...> if you have any
questions.

---------

*Common Models and APIs for Data Publishing and Citation Agenda (June 9)*

*Morning session* (moderator: Mercè Crosas)
9:00am-12:30pm - each talk is 30 min, with a short introduction by Mercè

*Question for Presenters: What are the current steps towards common APIs
and metadata so data repositories, publishers’ systems, and data services
(registrations, cataloging, discovering tools, research tools, ...) can
talk to each other?*

9:30-10:00am - Tim Clark - Data Citation Implementation guidelines
10:00-10:30am - John Kunze - Persistent Identifier services and their
metadata

10:30-11:00am - *Coffee break*

11:00-11:30am - Debbie Lapeyre - Including Data in the Standardized Markup
for Journal Articles (NISO JATS)
11:30am-12:00pm - Mark Wilkinson - Metadata Profiles for repositories: the
Meta-metadata
12:00-12:30pm - Sünje Dallmeier-Tiessen - Common Data Publishing workflows

12:30-1:30pm - *Lunch*

1:30-1:45pm - Eleni Castro (or Elizabeth Quigley) and Phil Durbin - Towards
a Common Deposit API (the Dataverse example)

*Panel Discussion* (moderated by Sünje Dallmeier-Tiessen and Tim Clark)
2:00-4:30pm - 5 min each (no slides), with panelists representing various
stakeholders: publishers, domain and general repositories, funding,
researchers, and industry, followed by an open discussion with the audience.

*Questions for Panel Discussion: What do various stakeholders want/need
from common APIs and metadata from repositories? What should be addressed
next (as a follow up of the talks about what's currently being addressed)?*

Panelists:
- Anita de Waard (publisher)
- funder panelist (to be confirmed...)
- repository panelist (to be confirmed...)
- August Muench (research & publishing, astronomy)
- Piotr Sliz (research, system biology)
- industry panelist (to be confirmed...)


Looking forward to seeing you all there.


Best,
Eleni

-- 

Eleni Castro

Research Coordinator, Data Acquisition and Archiving, Data Science

IQSS, Harvard University

http://www.iq.harvard.edu/people/eleni-castro




~Check out our new Dataverse 4.0! <https://dataverse.harvard.edu/>~

-- 
You received this message because you are subscribed to the Google Groups
"Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to dat...@go....
To post to this group, send email to dat...@go....
To view this discussion on the web visit
https://groups.google.com/d/msgid/dataverse-community/5b8f9dc3-3709-4028-a05a-9e8d76c3bc4f%40googlegroups.com
<https://groups.google.com/d/msgid/dataverse-community/5b8f9dc3-3709-4028-a05a-9e8d76c3bc4f%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.



-- 
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[sword-app-tech] Should we extend the Repository API beyond SWORD?

[Philip D. <phi...@ha...>]

Hello! We love us some SWORD over in Dataverse land but in an upcoming
workshop we're going to be brainstorming about the future of how users
deposit data into our repository and we're considering alternatives or
enhancements to SWORD.

I'm writing to invite everyone in the SWORD community to join us in
this brainstorming. Ideally you'd show up in Boston in June for the
workshop but more realistically we can have a nice discussion on this
mailing list or wherever* you like! :)

Things to think about:

- Does SWORD do everything you need?
- What are the pain points with SWORD, if any?
- Can repositories agree on a common deposit API standard? (Have they
already agreed on SWORD?)

Please see the workshop announcement below (also at
http://projects.iq.harvard.edu/dataverse-community-meeting/premeeting-workshop
) and slide 15 asking, "Should we extend the Repository API beyond
SWORD?" from a recent talk:
http://datascience.iq.harvard.edu/presentations/data-publishing-workflows-dataverse-0

Happy depositing! I'm curious what everyone thinks!

Phil

* I tend to prefer freenode IRC:
http://community.dataverse.org/community-groups/api.html . Here's a
public Google Doc for brainstorming:
https://docs.google.com/document/d/1vd5eLGhMqWB0R2_3jvprt5yZTDpaSev8cUOnCCK2hqQ/edit?usp=sharing

p.s. Apologies if you received this email twice! The first version was
in HTML and had an attachment and didn't show up in the archives so
I'm trying again.

---------- Forwarded message ----------
From: Eleni Castro
Date: Mon, May 4, 2015 at 4:11 PM
Subject: [Dataverse-Users] Pre-Meeting Workshop: Common Models and
APIs for Data Publishing and Citation (June 9)
To: dat...@go...

Hi Dataverse Community,

On June 9, prior to the Dataverse Community Meeting (June 10-11), we
are hosting the Common Models and APIs for Data Publishing and
Citation Workshop at Harvard University, which is organized by Tim
Clark, Sünje Dallmeier-Tiessen, Mercè Crosas and the Dataverse team.
This workshop will focus on defining and improving standards for APIs,
metadata profiles and workflows across repositories, publishers’
systems and other data services to achieve better interoperability
(see agenda).

The day will be divided into two main sessions: (1) the first half
will be presentations on what has been done so far towards improving
interoperability of data systems, which then will be followed by (2)
an extensive panel discussion session, with active audience
participation, on the main challenges of interoperability, and what
the next steps are based on the different needs of the various
stakeholder groups. By the end of this workshop, we aim to have a set
of action items and recommendations for next steps on how we can best
move towards common APIs and metadata so data repositories,
publishers’ systems, and data services can better talk to each other.

This event is free and open to all, including researchers, librarians,
archivists, publishers, funders, and software developers. Space is
limited, so if you haven't already registered for the Community
Meeting, please register at your earliest convenience.

A tentative agenda is listed below with specific questions that we
would like all attendees of this workshop to review ahead of time and
help us answer, so please let us know if you have any questions.

---------

Common Models and APIs for Data Publishing and Citation Agenda (June 9)

Morning session (moderator: Mercè Crosas)
9:00am-12:30pm - each talk is 30 min, with a short introduction by Mercè

Question for Presenters: What are the current steps towards common
APIs and metadata so data repositories, publishers’ systems, and data
services (registrations, cataloging, discovering tools, research
tools, ...) can talk to each other?

9:30-10:00am - Tim Clark - Data Citation Implementation guidelines
10:00-10:30am - John Kunze - Persistent Identifier services and their metadata

10:30-11:00am - Coffee break

11:00-11:30am - Debbie Lapeyre - Including Data in the Standardized
Markup for Journal Articles (NISO JATS)
11:30am-12:00pm - Mark Wilkinson - Metadata Profiles for repositories:
the Meta-metadata
12:00-12:30pm - Sünje Dallmeier-Tiessen - Common Data Publishing workflows

12:30-1:30pm - Lunch

1:30-1:45pm - Eleni Castro (or Elizabeth Quigley) and Phil Durbin -
Towards a Common Deposit API (the Dataverse example)

Panel Discussion (moderated by Sünje Dallmeier-Tiessen and Tim Clark)
2:00-4:30pm - 5 min each (no slides), with panelists representing
various stakeholders: publishers, domain and general repositories,
funding, researchers, and industry, followed by an open discussion
with the audience.

Questions for Panel Discussion: What do various stakeholders want/need
from common APIs and metadata from repositories? What should be
addressed next (as a follow up of the talks about what's currently
being addressed)?

Panelists:
- Anita de Waard (publisher)
- funder panelist (to be confirmed...)
- repository panelist (to be confirmed...)
- August Muench (research & publishing, astronomy)
- Piotr Sliz (research, system biology)
- industry panelist (to be confirmed...)


Looking forward to seeing you all there.


Best,
Eleni

--

Eleni Castro

Research Coordinator, Data Acquisition and Archiving, Data Science

IQSS, Harvard University

http://www.iq.harvard.edu/people/eleni-castro




~Check out our new Dataverse 4.0!~

--
You received this message because you are subscribed to the Google
Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to dat...@go....
To post to this group, send email to dat...@go....
To view this discussion on the web visit
https://groups.google.com/d/msgid/dataverse-community/5b8f9dc3-3709-4028-a05a-9e8d76c3bc4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



-- 
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

Re: [sword-app-tech] SWORD test client WAR file?

[Pottinger, H. J. <Pot...@mi...>]

Hmm... I've been meaning to look and see if anyone had thrown together a PHP interpreter that can be deployed in Tomcat, and sure enough, someone has:

https://netwolfuk.wordpress.com/2008/09/03/php-and-mysql-in-tomcat-with-quercus/

Be afraid, be very afraid. ;-)

--Hardy
________________________________________
From: LEWIS Stuart [Stu...@ed...]
Sent: Wednesday, March 04, 2015 2:10 PM
To: Pottinger, Hardy J.; swo...@li...
Subject: Re: [sword-app-tech] SWORD test client WAR file?

Hi Hardy,

If you don't mind PHP rather than Java/Tomcat, take a peek at:

 -
https://github.com/swordapp/swordappv2-php-library/tree/master/test/website

This might do what you want.

Thanks,


Stuart Lewis
Head of Research and Learning Services
Deputy Director Library & University Collections, Information Services
University of Edinburgh
Stu...@ed...





On 26/02/2015 17:00, "Pottinger, Hardy J." <Pot...@mi...>
wrote:

Ha, don't get excited, I'm not announcing anything, I'm mostly just
wondering if anyone has gone through the trouble of assembling a simple
client webapp for SWORD v2 webapp testing purposes? I'm thinking along the
lines of the terribly useful Psi Probe [1] for testing whether Tomcat is
working correctly, only in this case, we'd have a webapp for confirming
whether a SWORD server is working correctly. If such a WAR file existed,
it would be lovely to include it into development toolkits, such as
Vagrant-DSpace [2]

I'm taken with this idea enough I might chase it a while. If anyone has
ever "whipped up" a Java webapp client for SWORD v2, and you wouldn't mind
sharing your code, we should have a chat. Thanks!

[1] https://code.google.com/p/psi-probe/
[2]  https://github.com/DSpace/vagrant-dspace
---------------------------------------------------------------------------
---
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for
all
things parallel software development, from weekly thought leadership blogs
to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
sword-app-tech mailing list
swo...@li...
https://lists.sourceforge.net/lists/listinfo/sword-app-tech


--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: [sword-app-tech] SWORD test client WAR file?

[LEWIS S. <Stu...@ed...>]

Hi Hardy,

If you don't mind PHP rather than Java/Tomcat, take a peek at:

 - 
https://github.com/swordapp/swordappv2-php-library/tree/master/test/website

This might do what you want.

Thanks,


Stuart Lewis
Head of Research and Learning Services
Deputy Director Library & University Collections, Information Services
University of Edinburgh
Stu...@ed...





On 26/02/2015 17:00, "Pottinger, Hardy J." <Pot...@mi...>
wrote:

Ha, don't get excited, I'm not announcing anything, I'm mostly just
wondering if anyone has gone through the trouble of assembling a simple
client webapp for SWORD v2 webapp testing purposes? I'm thinking along the
lines of the terribly useful Psi Probe [1] for testing whether Tomcat is
working correctly, only in this case, we'd have a webapp for confirming
whether a SWORD server is working correctly. If such a WAR file existed,
it would be lovely to include it into development toolkits, such as
Vagrant-DSpace [2]

I'm taken with this idea enough I might chase it a while. If anyone has
ever "whipped up" a Java webapp client for SWORD v2, and you wouldn't mind
sharing your code, we should have a chat. Thanks!

[1] https://code.google.com/p/psi-probe/
[2]  https://github.com/DSpace/vagrant-dspace
---------------------------------------------------------------------------
---
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for
all
things parallel software development, from weekly thought leadership blogs
to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
sword-app-tech mailing list
swo...@li...
https://lists.sourceforge.net/lists/listinfo/sword-app-tech


-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: [sword-app-tech] SWORD test client WAR file?

[Philip D. <phi...@ha...>]

Sorry, I've only worked on a minimal SWORD *server* proof-of-concept in
Java: https://github.com/dvn/swordpoc

(We've since shipped actual SWORD support:
http://guides.dataverse.org/en/3.6.2/dataverse-api-main.html#data-deposit-api
.)

I like the idea though. And we have a related open issue to implement a
SWORD client in Java: https://github.com/IQSS/dataverse/issues/1346 :)

Phil

On Thu, Feb 26, 2015 at 12:00 PM, Pottinger, Hardy J. <
Pot...@mi...> wrote:

> Ha, don't get excited, I'm not announcing anything, I'm mostly just
> wondering if anyone has gone through the trouble of assembling a simple
> client webapp for SWORD v2 webapp testing purposes? I'm thinking along the
> lines of the terribly useful Psi Probe [1] for testing whether Tomcat is
> working correctly, only in this case, we'd have a webapp for confirming
> whether a SWORD server is working correctly. If such a WAR file existed, it
> would be lovely to include it into development toolkits, such as
> Vagrant-DSpace [2]
>
> I'm taken with this idea enough I might chase it a while. If anyone has
> ever "whipped up" a Java webapp client for SWORD v2, and you wouldn't mind
> sharing your code, we should have a chat. Thanks!
>
> [1] https://code.google.com/p/psi-probe/
> [2]  https://github.com/DSpace/vagrant-dspace
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> sword-app-tech mailing list
> swo...@li...
> https://lists.sourceforge.net/lists/listinfo/sword-app-tech
>



-- 
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[sword-app-tech] SWORD test client WAR file?

[Pottinger, H. J. <Pot...@mi...>]

Ha, don't get excited, I'm not announcing anything, I'm mostly just wondering if anyone has gone through the trouble of assembling a simple client webapp for SWORD v2 webapp testing purposes? I'm thinking along the lines of the terribly useful Psi Probe [1] for testing whether Tomcat is working correctly, only in this case, we'd have a webapp for confirming whether a SWORD server is working correctly. If such a WAR file existed, it would be lovely to include it into development toolkits, such as Vagrant-DSpace [2]

I'm taken with this idea enough I might chase it a while. If anyone has ever "whipped up" a Java webapp client for SWORD v2, and you wouldn't mind sharing your code, we should have a chat. Thanks!

[1] https://code.google.com/p/psi-probe/
[2]  https://github.com/DSpace/vagrant-dspace

Re: [sword-app-tech] Fw: Question re Sword v2 server implementation in DSpace v4.2

[TAYLOR R. <Rob...@ed...>]

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.