[
https://jira.duraspace.org/browse/DS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22233#comment-22233
]
Richard Jones commented on DS-1005:
-----------------------------------
Hi Folks,
We haven't had time to discuss the SWORD v2 module and its relationship to
DSpace - apologies that this has happend in a rush while I was lazing around on
holiday. This is a sort of round-up of responses to the various
questions/comments/issues above.
It was my assumption that this code would be of interest, particularly as it
will be shipping as standard in the next versions of EPrints and Fedora, but
that is a decision for the DSpace community, and not one for me to press upon
you. Contrary to Mark's opinion, I'd say that there is benefit to SWORDv2
being part of the dspace trunk for the following reasons:
1/ If it is not released synchronously then I'd expect fewer people to use it
2/ Until DSpace has a well developed "add on" mechanism for external modules
(see, for example, the EPrints Bazaar), I'm not sure how well releasing modules
separately is going to go. Perhaps there is some other guidance on this that
I've not yet seen, though?
3/ At the end of the SWORDv2 project we do not have any immediately prepared
funding for ongoing development. This means that we won't have the resources
to manage our own external module in perpetuity. A better solution for the
code is for it to be owned by the DSpace community, while we seek further
funding to manage the specification and the common libraries (this is underway,
fyi).
4/ EPrints and Fedora will provide SWORDv2 support as standard in their
upcoming releases this year.
SWORD v2 has a number of external dependencies, and the SWORD team have also
provided common code libraries for generic server and client operations, for
the ease of all SWORD developers, not just the DSpace ones. It is our aim to
put these into the central maven repository, but this has not yet happen
primarily due to time constraints, and I am currently working on submitting the
libraries to sonatype, which could take some time due to the vetting procedures
and requirements that they have (including control of the domain, and the
relationship between the version control location and the org.swordapp domain).
I'm not sure that having common libraries which work for a multiple
environments should be considered a problem - this is good code re-use, and
gives other SWORD developers a leg up to deal with the boring bits that are the
same everywhere. The code base is not forked, it is simply that there is a
DSpace implementation of the common library's interfaces; this is good design
as far as I'm concerned. Is there a particular issue with the DSpace
implementation relying on external common libraries?
The Foresite library, which is currently included as source in the DSpace
SWORDv2 module, has already had its pom prepared for submission to the central
maven repository, but I couldn't submit myself it as I don't control the
org.dspace domain that the code lives under. A way forward on this or any
assistance would be gratefully received.
With regard to licensing, the code can be considered in this case to be a code
contribution to the DSpace Community, and if it is to be part of the standard
distribution then we are very happy for it to use the standard DSpace licence.
It only doesn't have a licence at this time due to lack of a discussion around
it rather than any intent on our part. If we do not wish to accept SWORDv2 as
a part of the out-of-the-box DSpace, the SWORD team would just licence it
appropriately (and probably under the same licence as DSpace anyway).
It's worth adding that I'm not a maven expert (I rely on it exclusively for
dependency resolution generally), so would very much appreciate some guidance
in the aspects discussed above which are regarded as "easy" by the experts here.
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
