Hi Veronica, Am 08.10.21 um 11:57 schrieb Veronica Fernandez:
I try to migrate a very big repository to a new fresh install of 6.3, but I'didn't get it because I cannot "cut" it into communities because the import of them return me errors of dependencies at collections administrative groups. You cannot restore collections if groups doesn´t exists but how can i get all epersons and groups created ?? If I try to export the entire site I have a lot of problems of memory and timeout. I think a posibility is to export excluding boundles or something similar, the target is to get the same "structural information" in both installationsHas somebody experience with packager and a big repository?
[…]
I think you have to split !I've done this 3 years ago during an upgrade from 1.7.x, and this took a around a week (on 3500 items) w/o split.
However, I did this lately more often with the beta of DSpace 7, and it was horrible (~6000 items).
I have a lengthy description on behalf of a part of our disaster recovery, and its weird.
Try with the sitewide.zip w/o recursive (-a), this should give you the groups and the epersons (at least they are in the mets.xml).
Then try from top to bottom the first level communities.If you have added own metadata fields, create them first in the empty repository, else DSpace 6 will fail (in contrast to DSpace 5, which will autocreate them).
Hope this helps, Michael -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx--- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/aaff5b4b-7de4-68bc-e3ec-5bbe83f5045f%40bibliothek.uni-kassel.de.
smime.p7s
Description: S/MIME Cryptographic Signature
