Monika,
My colleague has been experimenting with a number of DSpace tools to
replicate hierarchy and content from PROD to TEST. We can do this safely
because we are refreshing our TEST instance.
His advice is listed below. Based on this recommendation, I think this
would be risky to run in production. I would likely write a script to
rearrange the hierarchy from the command line one node at a time.
--
The export process should be straightforward. I would use the recursive
hierarchy export outlined in the DSpace docs.
https://wiki.duraspace.org/display/DSDOC4x/AIP+Backup+and+Restore#AIPBackupandRestore-ExportingAIPHierarchy
In all cases I would backup the assetstore and database first and try
restoring from that backup on a separate instance. Only once she's
confident that the backup is functioning would I proceed.
The import into a production instance requires a bit more thought than
export. The *submission mode* has *several critical warnings* that make me
think it is *not to be used in production*, especially the part where it
says item mappings may not be retained.
https://wiki.duraspace.org/display/DSDOC4x/AIP+Backup+and+Restore#AIPBackupandRestore-SubmittinganAIPHierarchy
The *default restore mode*, however, seems to preserve handles and item
mappings. If any handle in the hierarchy already exists in the production
dspace instance, all changes will be rolled back, which is a nice safety
feature.
https://wiki.duraspace.org/display/DSDOC4x/AIP+Backup+and+Restore#AIPBackupandRestore-DefaultRestoreMode
If there is no handle conflict, everything is fine.
If the default restore mode produces an error that a handle already exists,
then it's a matter of deciding how to resolve the conflict. One can try to
import the objects that don't conflict and skip the ones that do (-k "keep
existing"). Then she will have to manually add the conflicting objects and
assign new handles to them.
The last option is very dangerous (-f "force replace") and not to be used
on a production instance as it can lead to loss of data.
On Mon, Jun 22, 2015 at 1:00 PM, Monika C. Mevenkamp <moni...@princeton.edu>
wrote:
> Hi
>
> I have set up a community / collection hierarchy in my test instance.
> Once this is approved I will have to create the same hierarchy in
> production. Is there an easy way to export / import the hierarchy ?
>
> Monika
> '
>
> —
> Monika Mevenkamp
> Digital Repository Infrastructure Developer
> Phone: 609-258-4161
> 333C 701 Carnegie, Princeton University, Princeton, NJ 08544
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://www.library.georgetown.edu/lit/code
425-298-5498 (Seattle, WA)
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
