On the CollectionVersion page we have a repository dropdown, but on in the Dependencies tab we provide a link to one repo, but it could be in many repos, or perhaps zero repos if you are syncing from a system that didn’t check deps.

Also when deleting a CollectionVersion, the api response given to the UI does not list out each repository the dependency is located in, the delete operation is system wide and does not care about repositories.

In these 2 cases should we try to list each repo a dependency exists in? Or could it be helpful to have a /ui/<namespace>/<collection_name> page in the UI that just listed repos that contain CollectionVersions for the Collection, then link to the Collection scoped to the repo?