Hi Germán,
Probably not what you were looking for, but if you control both servers,
why not give the second server access to the database and filesystem. You
could give it read only permissions.
But to support a fully automated replica mode I haven't seen that. But it
would be useful, especially if you wanted to guarantee a level of
preservation. (You would have to be cautious that someone deleting the
master node, would cascade and delete the slave/replica.)
Another option, depending on your use case, could be to use the rest API.
I've built a simple user interface that communicates via rest (rails,
play!), that let you build a remote user interface to the repository. You
could setup some type of mirror process that saves the data locally, though
not really DSpace anymore, just whatever is efficient for holding content.
I suppose one could build a population script that stashed that data that
you got from rest, and ingested it into the second DSpace.
The rest API won't give you ALL the information though, such as restricted
content, full users/ groups/ permissions.
On Sep 8, 2014 6:19 PM, "Germán Biozzoli" <[email protected]> wrote:
> Hi everybody
>
> I'm asking if is there some way to maintain a remote repository
> completely synchronized with a central one (both DSpace's), including
> changes in communities/collection structure additionally to consume the
> items added. I've seen a presentation that combines OAI-ORE and SWORD,
> anybody is doing something like this?
>
> Regards
> German
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
