The Development Prioritization subteam reviewed this ticket during its meeting on 9/3/2024. The team recommend passing this ticket for development.

This could be an option on a user record that allows for selecting from the list of repositories available to the user.

The repo selection will not be retained once the browser is closed. We have had a few hosted archives/libraries ask for what Valerie outlines below in the Sept. 21 comment.

Commenting because I have since learned (and tested) that AS logs you back into the repo you were in last. So if you primarily work in one, your experience should be more seamless than implied by this ticket.

In my testing I created a new user in the Sandbox and assigned that user the same permissions in two different repos, repo 6 and repo 12.

I logged in as that user, selected repo 12, clicked Log Out, logged back in, and was back in 12. I repeated the steps for the opposite and it also worked.

I would like to bump up this ticket on behalf of a hosted client at Atlas (reference #28237). In review of the comments I worked with our customer to bolster the user story here, and we have these suggestions for consideration:

To control the default for all users:
Each individual repo record could have a Boolean field that allows a sys admin to mark whether the repo currently selected is the default for all users. ASpace would have to have a constraint that only one checkbox in only one repo record can be checked at one time, or else having two or more such check boxes would bring AS into conflict.

This would allow a sys admin to set the default repo for all users. If a user does not have access to the default repo, they would see the usual "You do not have access to this repo" message upon logging in with the default set. That scenario can be handled by the additional suggestion, below.

To override the default for a particular user:
With the default repo set for all users, a particular user may prefer to default to a different repo than the one selected as the default, or may not have access to the repo set as the default. In this case, the archives supervisor could override the default repo for an individual user from the individual user's account page. The individual user account page could have a menu with each repo listed and the sys admin would have the ability to check which repo is the default for that user. This setting would override the default set in System > Manage Repositories > individual repo record