Hello there! I recently launched a statewide repository as part of a state grant that the state then took down while they determine if it’s in violation of any of the EO’s that have come down the pike. While unfortunate, it did lead to an interesting issue I’m wondering if you have guidance on.
The site is now unpublished, but there are two other sites created by others that are still up and online. The state department of ed wants to give some people view rights (Which I’ve now figured out from the closed forum from 2023) but they also want to make sure people with the rights to view only can only see sites we let them see. Essentially, the other two Omeka S sites are up because they’re separate projects that we chose to house on the same server. They want their reviewers to only see THEIR site to avoid bringing unwanted attention to the OTHER sites. (Does this make sense?)
As long as those sites are published the users with Viewer access to the unpublished site will be able to see the published one in the site list and to see their public manifestation. There is currently not a way to hide sites in the administrative interface for logged-in users.
What would you recommend for our reviewing issue? (The state department of ed wants to review the site in its entirety vs just looking at the item collections, and wants the site to remain unpublished and inaccessbile to the public until they complete their review)
Did not anticipate a primary source access project for teachers to end up in the crossfire of a Day 1 EO on partriotic education.
I would say, that you should give them a viewer role on the site, have them log in. Then have them launch the site from in another tab, rather than navigating to the site list in the admin (Just give them the link to paste into the browser). They’ll be able to see everything as if it were public.
They’ll be able to see all the public sites too, but they won’t encounter that stuff unless they go digging around in the admin after they log in.
It’s not elegant, but it might keep them from going astray.
There is also a module from the University of Illinois Urbana-Champaign called “Teams” which may be relevant. It is not listed on the main Omeka modules pages but it serves a useful purpose of allowing multiple research project sites to be hosted without the items and sets for those projects being visible to other projects. Not sure if that is relevant to your question.
You can find the teams module on GitHub and they also wrote an article about it in Code4Lib. I’m not sure why they have not made it available via the Omeka modules page as it looks very useful: we are looking at implementing it on our own installation.
