[
https://jira.duraspace.org/browse/DS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24047#comment-24047
]
Tim Donohue commented on DS-1105:
---------------------------------
I've documented this as a "Known Issue" in the 1.8.x AIP Backup & Restore
documentation. I've also added information about the two possible workarounds
(mentioned in the above description & first comment)
See the "Missing Groups or EPeople cannot be created when submitting an
individual Community or Collection AIP" warning box at the end of this section:
https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore#AIPBackupandRestore-SubmittinganAIPHierarchy
> Submitting individual Collection/Community AIP(s) fails when there is an
> associated access-control Group
> --------------------------------------------------------------------------------------------------------
>
> Key: DS-1105
> URL: https://jira.duraspace.org/browse/DS-1105
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.8.0, 1.8.1
> Reporter: Tim Donohue
> Priority: Major
>
> This issue was first reported to dspace-tech (see
> http://www.mail-archive.com/[email protected]/msg15966.html
> ), but I've verified it is a bug.
> Essentially, when running the AIP Backup & Restore packager in Submit mode
> (-s), you cannot submit a individual Community or Collection AIP(s) which
> have associated Access Control Group (e.g. COMMUNITY_*_ADMIN,
> COLLECTION_*_ADMIN, COLLECTION_*_SUBMIT).
> The reason for the failure are that the METSRightsCrosswalk and RoleCrosswalk
> (& associated RoleIngester) are unable to fully (re-)create any associated
> Access Control Groups without access to the main SITE AIP (which stores all
> EPeople information).
> The errors commonly seen include:
> * "Unable to translate Handle to Internal ID in group named ..." (caused
> by and thrown via the METSRightsCrosswalk)
> * "EPerson ____ not found, not added to [group name]" (thrown by the
> RoleCrosswalk)
> The only known workaround is to do the following:
> (1) Temporarily disable the RoleCrosswalk & METSRightsCrosswalk in your
> dspace.cfg file by adding the following settings
> mets.dspaceAIP.ingest.crosswalk.METSRIGHTS = NIL
> mets.dspaceAIP.ingest.crosswalk.DSPACE-ROLES = NIL
> (2) Re-run your Packager command to submit your Community or Collection AIP
> (there is no need to restart Tomcat, as you are running this from the
> commandline). This command is similar to:
> [dspace]/bin/dspace packager -s -a -t AIP -e [eperson] -p
> [parent-handle] [full-path-to-AIP]
> For more details see:
> https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore
> (3) Finally, remove those above settings from your dspace.cfg
> The above steps will let you successfully submit a Community or Collection
> AIP to a new DSpace install. However, NONE of the associated access control
> groups (or EPeople in those groups) will be recreated. You will need to
> create any necessary access controls *after* the Community or Collection has
> been created successfully.
> Currently, a code fix/patch for this is unknown. It may be that running in
> "submit" mode means that EPeople/Group/Permissions just cannot be created
> successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
