Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Title (Goal)Configure hidden communities that will not be visible to users without access
Primary ActorSystem | Human | External System
Scope 
Level 
Story (A paragraph or two describing what happens)

The repository administrator, John, is preparing a new collection for the Biology department which will start using the repository in the near future. While John is still configuring the new collection, he has chosen to only show the new collection to administrators and specific users. The collection is hidden for everyone else. John has done so by restricting access to the "Default read access" role.

Please note that while this collection is hidden, it's information and items are also not available in the OAI-PMH endpoints and in the REST API. Furthermore, the collection is not shown on the home page or on the community list.

Once John has finished configuring the collection, he removes the restriction on the "Default read access" role. Anonymous users can now see the collection and view associated items.

When creating a community or collection, allow inaccessible collections and communities to be hidden from users who will not have access to the contents.

  • For deployment testing, create a collection that is only visible/accessible to repository administrators
  • Allow collection owners to develop a new collection that is not visible on the community list page to end users