[DuraSpace JIRA] (DS-3590) Implement ResourceSync for DSpace

13 views
Skip to first unread message

Andrea Bollini (DuraSpace JIRA)

unread,
May 6, 2017, 10:27:00 AM5/6/17
to dspace-...@googlegroups.com
Andrea Bollini created an issue
 
DSpace / New Feature DS-3590
Implement ResourceSync for DSpace
Issue Type: New Feature New Feature
Assignee: Unassigned
Components: DSpace API, new-REST
Created: 06/May/17 9:26 AM
Priority: Major Major
Reporter: Andrea Bollini

The Next Generation Repositories Working Group from COAR has recently released the first draft of its outcome report presenting 12 user stories that outline priority functionalities for repositories (see http://comment.coar-repositories.org/). The update following the public comment phase is forthcoming.

Several user stories, primarily "8. Resource syncing and notification" rely on the ResourceSync protocol as enabling technologies / strategy

I propose to implement the ResourceSync Framework Specification in DSpace, see http://www.openarchives.org/rs/toc

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.3#73014-sha1:d5be8da)
Atlassian logo

Claudia Jürgen (DuraSpace JIRA)

unread,
May 8, 2017, 10:05:01 AM5/8/17
to dspace-...@googlegroups.com
Claudia Jürgen commented on New Feature DS-3590
 
Re: Implement ResourceSync for DSpace

This would be an asset and prior to Z39.99 some efforts have been made see

https://github.com/CottageLabs/DSpaceResourceSync

Hardy Pottinger (DuraSpace JIRA)

unread,
May 10, 2017, 3:43:00 PM5/10/17
to dspace-...@googlegroups.com
Hardy Pottinger updated an issue
Change By: Hardy Pottinger
Status: Received Volunteer Needed

Bram Luyten (Atmire) (DuraSpace JIRA)

unread,
Jun 29, 2017, 8:45:00 PM6/29/17
to dspace-...@googlegroups.com

Sounds interesting. At the open repositories conference, there is talk about the potential of ResourceSync being a future replacement for OAI-PMH. 

There are reasons to believe that it could scale better for very large repositories. cfr, sitemap based indexing VS relying on resumption tokens.

Andrea Bollini (4Science) (DuraSpace JIRA)

unread,
Feb 27, 2018, 12:20:01 PM2/27/18
to dspace-...@googlegroups.com

I’m glad to announce that our proposal to enhance the interoperability of several open source platforms has been awarded by OpenAIRE, see https://www.4science.it/en/2018/02/23/4science-awarded-by-openaire/
In our proposal we have included the implementation in DSpace of the ResourceSync framework, more specifically we will

  • Support for the ResourceSync core capabilities: ResourceList, CapabilityList, ChangeList with discoverability and fixity (audit)
  • Support for packaging ResourceDump and ChangeDump

The implementation will be released for version 5 and version 6 of DSpace to guarantee an easier, broad, and potentially immediate, adoption. Moreover, a Pull Request against the master branch of DSpace (upcoming version 7) will be opened to facilitate an official adoption of the ResourceSync framework by the DSpace community. The project fulfillment is expected by May 2018

Andrea Bollini (4Science) (DuraSpace JIRA)

unread,
May 4, 2018, 9:24:00 AM5/4/18
to dspace-...@googlegroups.com

Andrea Bollini (4Science) (DuraSpace JIRA)

unread,
May 15, 2018, 5:50:01 PM5/15/18
to dspace-...@googlegroups.com
Andrea Bollini (4Science) assigned an issue to Luigi Andrea Pascarelli (4Science)
 

Our project with OpenAIRE is over and an implementation of ResourceSync for DSpace versions: 5, 6 and 7 (master) is available here

https://github.com/4Science/DSpaceResourceSync

The implementation is based on the original work from Richard Jones (https://github.com/CottageLabs/DSpaceResourceSync) updated to reflect the latest framework specification 1.1 and adding support for multiple capability list.

Each community and collection can be exposed as a separate capability list other than the whole site allowing easy partial synchronization. Moreover, for each container (Site, community, collection) a double version is available one exposing only metadata, one exposing also the fulltext.

The changelist and changelistdump makes use of new SOLR core, resourcesync where the events (CREATE, UPDATE, DELETE) of resourcesync resources (Item, Bitstream) are keeped using a new DSpace consumer.

The Dump capabilities (Change and Resource)Dumps can be produced in advance for optimal performance as in the original Richard code or produced and streamed on the fly avoiding the need for additional storage.

We have already reach Richard Jones to discuss about copyright issue and he will be happy to waive the copyright in favor of an open source license with proper attribution to have this work continued, this is the sense of our existent PRs

https://github.com/CottageLabs/ResourceSyncJava/pull/1 

https://github.com/CottageLabs/DSpaceResourceSync/pull/2

 

I'm strongly convinced that resource sync should be implemented out-of-box by dspace similarly to oai-pmh and sword so I suggest the following action

1) Tim Donohue should finalize the transfer of the original ResourceSyncJava to the DSpace organization and the DSpaceResourceSync repository to DSpace-Labs

2) we will create PRs for DSpace packaging the content of the DSpaceResourceSync repository as a maven module of the DSpace project similarly to what is done for all the other webapps simplifying deployement

We will be happy to work on this issue to improve the implementation as needed to have it accepted out-of-box in DSpace!

 

Assignee: Luigi Andrea Pascarelli (4Science)
Status: Volunteer Needed Accepted / Claimed

Luigi Andrea Pascarelli (4Science) (DuraSpace JIRA)

unread,
May 16, 2018, 9:22:01 AM5/16/18
to dspace-...@googlegroups.com

Anonymous (DuraSpace JIRA)

unread,
May 19, 2018, 5:19:01 PM5/19/18
to dspace-...@googlegroups.com
Issue was automatically transitioned when Andrea Bollini created pull request #2065 in GitHub
Change By: Andrea Bollini
Status: Accepted / Claimed Code Review Needed

Kim Shepherd (DuraSpace JIRA)

unread,
Jul 31, 2018, 7:53:01 PM7/31/18
to dspace-...@googlegroups.com
Kim Shepherd commented on New Feature DS-3590

Hi Andrea Bollini (4Science), Luigi Andrea Pascarelli (4Science) , I've been trying to build + deploy the ResourceSync (DSpace 6 branch) from https://github.com/4Science/DSpaceResourceSync/tree/D4CRIS-506-D6 but something seems not quite right... it's looking for the jar artifact too early I think?

 

[ERROR] Failed to execute goal on project dspace-resourcesync: Could not resolve dependencies for project org.dspace:dspace-resourcesync:war:1.1-SNAPSHOT: Could not find artifact org.dspace:resourcesync:jar:1.1-SNAPSHOT -> [Help 1]

I'm building it with dspace 6.3, using the instructions in the README. The pom in this one has DSpace 5.9 snapshot referenced in teh pom although the README says it's the one for 6.x so I've changed that to the 6.3 release.  I don't think that's related though.

Are there any other ResourceSync apps I should be trying?

 

This message was sent by Atlassian JIRA (v7.10.0#710001-sha1:0399717)

Luigi Andrea Pascarelli (4Science) (DuraSpace JIRA)

unread,
Aug 11, 2018, 11:27:02 AM8/11/18
to dspace-...@googlegroups.com

Hello Kim Shepherd please use the DSpace 6.x with ResourceSync integration available at https://github.com/4Science/DSpace/tree/dspace-6-rs

The 4Science/DSpaceResourceSync repository was born to track change with the original https://github.com/CottageLabs/DSpaceResourceSync that now with 4Science modification has been transfert on https://github.com/DSpace/DSpaceResourceSync

The branch https://github.com/4Science/DSpaceResourceSync/tree/D4CRIS-506-D6  could contains, as you see errors or not final version of the code, because this source code has been merged into the ready to use branch https://github.com/4Science/DSpace/tree/dspace-6-rs

Hope this helps you.

 

Tim Donohue (LYRASIS JIRA)

unread,
Aug 4, 2021, 12:47:01 PM8/4/21
to dspace-...@googlegroups.com
Tim Donohue closed an issue as Duplicate
 

Closing this old ticket as a "Duplicate".  It's been moved to GitHub Issues: https://github.com/DSpace/DSpace/issues/3358   All future discussion should happen in GitHub

Change By: Tim Donohue
Resolution: Duplicate
Status: Code Review Needed Closed
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages