[
https://jira.duraspace.org/browse/DS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22235#comment-22235
]
Richard Jones commented on DS-1005:
-----------------------------------
Hi Tim,
I would very much like it if the DSpace specific SWORD code is owned by the
DSpace Community. The DSpace implementation is absolutely specific to DSpace,
and I think it is right and proper that it's the community's property, not that
of a JISC project - it's just being written with JISC funding, like many odd
bits of DSpace :)
I only just realised when reading your comment and re-examining the code that
the sword common library has also been bundled in as source too (I'm still
catching up since getting back from holiday!).
I've already updated the pom in the sword-app version of this code and
submitted a request to sonatype to allow me to publish it as a stand-alone
artefact. I also already did similar work for Foresite, but I'm not sure what
will happen when I try to take this to fruition, as I don't control the
org.dspace domain that is the groupId for this project. There is nothing in
either of these libraries which is specific to DSpace - they are simply
libraries that the DSpace implementation of SWORD depends on to function, just
as the rest of the DSpace codebase relies on external libraries. The SWORD
common code will need to be maintained by the repository community itself,
which is welcome to involve members of the DSpace/DuraSpace community, plus
anyone else who is interested in that code, but I don't see that as being any
different to having a dependency on any other externally maintained open source
project - it is maintained by the people who care enough about it to be involved
.
I will keep you posted with progress with sonatype, but for the time being
Option 1 will work if you're happy with it. If I can get through the maven
publishing process in time, we can pull all that code out.
I'm not too concerned about the ongoing funding for SWORD. As an open source
project, we have to look at ways that we'll take the development forward and
have some of the same challenges as DSpace to rise to! Perhaps there is an
interesting angle that we could look at, if DuraSpace would be interested in
having closer involvement in SWORD development - maybe we should start that
discussion in a different thread.
Cheers,
Richard
> SWORD v2 implementation for DSpace
> ----------------------------------
>
> Key: DS-1005
> URL: https://jira.duraspace.org/browse/DS-1005
> Project: DSpace
> Issue Type: New Feature
> Components: SWORD
> Reporter: Stuart Lewis
> Assignee: Robin Taylor
> Fix For: 1.8.0
>
> Attachments: dspace-swordv2.zip, swordv2.patch
>
>
> Ticket for the addition of SWORD v2 to DSpace 1.8. When building, you'll
> need to make sure you update dspace.cfg to include the new config options.
> Before 1.8 launch, we'll move these into modules/swordv2.cfg
> To test:
> 1) Apply patch
> 2) Unzip zip file to create new dspace-swordv2 module
> 3) Do the maven dance, deploy, visit /swordv2/servicedocument, enter DSpace
> username and password, check a service document is shown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
