Comment 3 for bug 1264331

I'm in agreement with Thomas on this one. Although parts are localized to a system, when staff creates one, the part is assigned to the bib record and is available for other libraries to use, similar to the way that a bib record is initially created for one library, but then available for other libraries to use. Updating a part is likely to affect several libraries that have mapped their items to that part. Deleting a part would also affect multiple libraries, though I assume (hope?) users would be unable to delete the part as long as those mappings exist.

I also agree that mapping a part should be available at any depth in the org tree. I performed a quick test, and found that if staff have the map permission assigned at the system level, they are able to successfully assign an existing part to a copy.

I would say the permissions are working as expected. However, I can see why this permission would be a source of confusion, particularly the CREATE permission, since most front-line catalogers have a need to use it. Would it make sense to improve documentation by adding a note to the permission's description field when the permission must be set at the Consortium level to work?