Hello Community! We've been using DSpace for a consortial repository since 2017, with about 64 different campuses sharing the space--each campus as a top-level community. During that time, we managed the admins as campus groups, assigning admin users to each campus community, which gave them access to create subcommunities and collections within their top-level campus communities, but did not give them access to other top-level communities.
Since our migration from DSpace version 6.3 to 7.4, we are seeing a lot of odd things happening. Most of the old campus admin groups were wiped from the top-level communities and I had to create new campus admin groups. However, these are not working as they once did. I'm finding that newly added campus community admins have access to edit and create top-level communities and subcommunities/collections throughout the repository, not only within their own campus areas. At the same time, these newly created admins are unable to add items to already existing collections in their own campus communities. Is this normal behavior for version 7.x? Do I need to do a thorough audit of all permissions in this (very large) repository? Does anyone out there have experience running DSpace in a consortial environment in this way? Thank you for any and all input! Sincerely, Yvonne Kester Repositories Manager SUNY Library Services -- 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 Community" 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-community/CAKZKP2D87gUGRj4gSMLJQmhRTynseKS7y46ZGkdgMVMpUct4yg%40mail.gmail.com.
