Hi Vinicius,
It sounds like you have two possible options:
* Delete the group named "COLLECTION_33_DEFAULT_ITEM_READ" from the
original DSpace and do a re-export. However, you should be sure this
group is no longer needed. While it *sounds* like it should have been
associated with a now deleted Collection, it's possible you've reused
this group elsewhere.
* OR, in the *new* target site, simply temporarily create a group with
the literal name "ORPHANED_COLLECTION_GROUP_33_DEFAULT_ITEM_READ". It
sounds like some other group/EPerson depends on this one, which is why
you are getting a Crosswalk error in your target repository. Once your
restore completes, you can go back and delete the
ORPHANED_COLLECTION_GROUP_33_DEFAULT_ITEM_READ as needed.
Unfortunately, DSpace does not clean up *all* Community/Collection
groups when that Community/Collection is deleted. To be honest, it does
*try* to cleanup most of these groups. However, the "DEFAULT_ITEM_READ"
group is one that is specific to the XMLUI, and doesn't always get
cleaned up appropriately (at least not at this time).
- Tim
On 4/28/2016 7:15 AM, Vinicius Assef wrote:
Anybody there?
Please.
On 25 April 2016 at 15:44, Vinicius Assef <[email protected]
<mailto:[email protected]>> wrote:
Hi, there. I need your help.
I'm exporting a community using the AIP Backup and Restore feature
from our repository running DSpace 3.2.
When importing this community into the target repository I'm
facing this error:
org.dspace.content.crosswalk.CrosswalkInternalException: Cannot
restore Group permissions on object (type=BUNDLE, handle=null,
ID=46590). The Group named
'ORPHANED_COLLECTION_GROUP_33_DEFAULT_ITEM_READ' is missing from
DSpace. Please restore this group using the SITE AIP, or recreate it.
I found a reference to this problem here:
https://wiki.duraspace.org/display/DSDOC3x/DSpace+AIP+Format#DSpaceAIPFormat-ExampleofDSPACE-ROLESSchemaforaSITEAIP
This section explains why this problem arises: /If a Group name
includes a Community or Collection Internal ID (e.g.
"COLLECTION_45_SUBMIT"), and that Community or Collection no
longer exists, then the Group is considered "Orphaned"/
So, if I got this right, I must create a new collection with ID 45
to "give this orphaned group a new parent". But how can I recreate
a group forcing its internal id using DSpace?
Another solution I thought of is: edit the items with this problem
and point their permissions to a group with a valid parent. After
that, remove the orphaned group. But is there any command to point
these orphaned groups? I think it would be nice to know about
these problems before running an export.
In extend, how come DSpace allows it to happen? If a collection
does not exist anymore, it is because it was deleted. Why DSpace
allowed it to be deleted if there was a group related to it?
Thank you for any advice.
--
Vinicius Assef
--
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]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
