That makes sense and answers my question, thank you Tim. We'll use permissions to make it work. ~Amy
On Thursday, July 13, 2023 at 1:20:13 PM UTC-7 Tim Donohue wrote: > Hi Amy, > > I can verify this is correct behavior in DSpace 7 because the backend > (REST API) needs to apply access restrictions in a consistent manner. > > Simply put, in DSpace 7, you must have READ permissions in order to "see" > any object (including metadata about that object) from the REST API (and > therefore also the UI). So, if you make an entire community have an IP > restriction, then only those IPs will have that "READ" permission. At this > time, there's not a way to apply that READ permission differently for > top-level communities than for their sub-communities/collections/items. > "READ" always gives the permissions to see the object in DSpace 7. > > The only way (that I know of) to achieve the behavior you suggest in > DSpace 7 would be to only apply the READ restrictions to the > sub-communities/collections/items, and leave the Communities themselves as > READ Anonymous. However, that would result in empty looking Communities > (to anonymous users), but once you login you'd see their > sub-communities/collections/items. > > Simply put, we don't have a way to display *only metadata* for restricted > Communities/Collections at this time. Doing so would let users without READ > permissions see the entire "hierarchy" (as you'd be able to read the basic > metadata about all restricted Communities & Collections). So, in DSpace > 7, we had to make the definition more strict: if you don't have READ, then > the object is "hidden" to you. > > Tim > On Monday, July 10, 2023 at 7:20:08 PM UTC-5 [email protected] > wrote: > >> We want the names & text blurbs of our IP-restricted communities to be >> visible to all users on the home page & collections/communities page, even >> to anonymous / non-logged-in users. >> >> To put it another way, we want the IP restriction to apply to the >> sub-communities, collections, and items, but not to the top-level community >> name & news text. >> >> This info was visible to everyone in our DSpace6 install, but is not >> showing up at all in DSpace7. To the anonymous user, it's as if this >> community does not exist. >> >> Is this something we can control with authorizations or in the config >> file? >> >> Does it work differently in DSpace7 than in DSpace6? >> >> Thanks in advance to anyone who can advise. >> >> ~Amy >> >> -- 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 Technical Support" 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-tech/9cc957c0-4c93-4439-8bc1-22dcaa4260een%40googlegroups.com.
