Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

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

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

Please note that while this collection is hidden, its information and items in it 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, except to authorized users. For those users and for Meera herself it is visually identified in the community list and in the search results as a hidden collection.

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


  1. This feature would allow for a production collection handle to be provisioned for use in code.  After custom themes/facets are deployed, the collection would be made visible.

  2. This sounds more like an Administrative UI use case, as the primary actor in this situation would be an Administrator, Community Admin or Collection Admin. Moving this over to "Admin UI" section.

    This may also be a subfunction of a more general "Access Rights" Use Case, in that we should allow this same level of access rights (public / private / limited access) on all levels of objects (Community / Collection / Item / Bitstream) within the system.

  3. In addition to not being visible/accessible to end users, such a collection/community should also be hidden from OAI and search engine harvesters - and become exposed to them when it goes live.

  4. I wonder if a permission category could be added for displaying a node in the hierarchy.