Hi Tanya,
Yes, of course there could be a middle ground between 5 at a time, and 100s. I honestly just don't know what the right middle ground would be. The number 5 was chosen as we made a guess
that people would use the facet-specific searchbox if they wanted to find a facet value not near the top of list. But that guess sounds like it has been proven incorrect by real-life user behavior. So, if 5 is the wrong number, then we'd need to find
a new number (10? 20?). Or maybe maybe it needs to be made configurable? (My response about performance issues was only to say that one solution that
won't work is simply displaying every facet value after clicking "view more". There must be some fixed number we stop at, otherwise performance could be a problem if there are a very large number of facet values.)
I guess I'm pointing out here that as institutions who use DSpace all of you have feedback into this. If you have an idea of how to create better behavior, I'd encourage you to either create a DSpace issue ticket (
https://github.com/DSpace/dspace-angular/issues)
describing the better behavior you'd propose. Or, maybe bring this up for discussion with the DSpace Community Advisory Team (DCAT) who can combined create such a recommendation. I'm here to help explain
why we chose the current behavior...but I will fully admit that we may never be able to get it perfect the first time, so it's important to get this feedback & ideas for improvements.
Anne has already created a few tickets (she linked to) which I've pulled over to our development work board. I don't yet know what release they'd be fixed in, but they are now on that board and will get prioritized/analyzed there (alongside all other reported
issues). We also always accept code contributions/donations from anyone... so if an issue is really bothering you, and you can either help fix it, or pay a service provider to fix it, that's is often the
quickest way to a solution.
Glad to provide more advice as needed,
Tim