Thanks, Ed. On 28 April 2016 at 18:35, Ed Goulet <[email protected]> wrote:
> Vinicius, > > Please don't send tech questions to the community group, it is simply the > wrong place to ask the question. > > Your idea of creating a new group and assigning ID 45 would probably work. > And your second idea with valid parent is also likely to work. You would > probably need to create the proper SQL statement to modify your database > and change the IDs as you require. > > As to why this happens, it was probably a bug (just my guess). DSpace 3.2 > is getting a bit old now. > On 4/28/2016 6:15 AM, Vinicius Assef wrote: > > Anybody there? > > Please. > > > On 25 April 2016 at 15:44, Vinicius Assef <[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> >> 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 Community" 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-community. > For more options, visit https://groups.google.com/d/optout. > > > -- 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.
