Exploring the collections in a data repository can be difficult, because we have many collections that most users don't care about in various contexts, and those often overwhelm the ones they do care about:

• other users' personal collections;
• RUN collections from processing runs (or Gen2 conversions or curated calibrations) that should usually be accessed only via a CHAINED or CALIBRATION collection;

While we could make some progress filtering collections by name patterns, I think it'd be better to have a separate column in the collection table that indicates its visibility. That might just be a boolean, but we should consider whether there are more states we might want.