Faceted searching in a certain order generates an error

[carsonicator]

Faceting by name works fine:

Faceting by name and medical subjects works fine:

Including a facet on ATP-binding cassette works:

Turning off the name facet works:

But if I add a name facet again I get an unnamed error:

[jpastva]

A somewhat related suggestion - when selecting one facet, if the search results are automatically updated, perhaps the facet values should update based on the new results? Otherwise there's the impression results are available for that facet, when there may not be. (Looks like this is how Zenodo works currently, but I don't like it!)

[fenekku]

Haha! There is never a "right" answer for search user experience, but here are the 3 main factors in the decision to have other filters not update when one is selected:

1- Convention: Zenodo does it this way, so we do it this way. It keeps the experience the same. But Zenodo does it this way, because it tries to keep the same experience as other ElasticSearch backed faceting. ElasticSearch pushes this approach and it is how it does things. 2- ElasticSearch does it this way to combat loss of context: if clicking a single filter changes all the others, it is jarring and the user loses overview of options. Then if they want to go back (because of jarring effect or because of filter not working out), they have to move their cursor to the back button rather than stay in place to assess other options. 3- Much more effort to break the convention here.

[jpastva]

Fair enough, I'll get over it 🙂