[
https://jira.duraspace.org/browse/DS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22234#comment-22234
]
Tim Donohue commented on DS-1005:
---------------------------------
Hi Richard,
Thanks for clarifying this. I think this is all starting to make some sense.
My main concerns were around who was going to "own" and maintain this code (I
didn't want us to be accidentally re-licensing this code, without prior
approval of the SWORD project/JISC).
I can think of two ways forward here (there may be more):
[Option #1] Leave everything as it currently is, with all of the SWORD v.2
code in Trunk. This is relatively straightforward & has the benefit of leaving
all the SWORD v.2 stuff "together" in one place. But, it does make it slightly
more difficult for any other Java software to "depend" on the generic
(non-DSpace-specific) SWORD code. Other Java software can still use those
dependencies in Maven, but they are based on DSpace releases & only updated on
the next DSpace release. It looks like both Foresite and the dspace-sword2-api
(Java SWORD server) actually don't include any custom DSpace code (unless I
overlooked it), so they may or may not be generically useful.
[Option #2] Pull out the non-DSpace Specific Stuff (Foresite & Java SWORD
Server) and release them on their own into Maven Central (and add them as
DSpace dependencies once released). This obviously means they are released
separately from DSpace releases & would need to be managed separately. But, it
makes it easier to update them *between* DSpace releases, which may be useful
if other Java software/platforms would want to use these same common libraries
& see more rapid releases to bugs/patches, etc. If we went this route, I'd
actually wonder if we would want to put them under their *own* Maven domain
named 'org.swordapp' (to make it clear they are generic SWORD java libraries,
and not DSpace specific). Though we could still release them under 'org.dspace'
in Maven. Obviously, the big question with this option would be around ongoing
management & maintenance. In Option #1, the maintenance obviously falls to the
DSpace Committer Team. But, with this option, we'd have to figure out who
would maintain these generic libraries (DSpace folks? SWORD folks? DuraSpace
folks? or a combination of all of them?).
It's also very possible to start out with Option #1 (for current simplicity in
1.8), and then perhaps move more towards Option #2 once the SWORD team figures
out ongoing funding & maintenance. (As a sidenote, if you are looking for a
more "generic place" for common libraries/code to be stored/managed, feel free
to get in touch with DuraSpace. Maybe we can work something out, or figure out
a way to at least provide some infrastructure (Jira, etc) if it'd be of help to
the SWORD team.)
The more I think about this (and the fact that we are late in the 1.8 game), I
personally wonder if Option #1 is the way to go for now. But, for the longer
term, if the SWORD project is able to locate some ongoing funding/support,
Option #2 may be a better way to manage common libraries, and allow for
multiple java platforms (DSpace, Fedora, others) to use those libraries, report
bugs, submit patches, etc.
- Tim
> 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
