OpenAtlas » OpenAtlas Discovery

+ 10

Feature of faceted search is very necessary when there is a lot of data. In case of OpenAtlas I propose to implement first in discovery frontend web over Table, Network and Map pages.

It would probably be appropriate for each project to define filters that make sense for the existing data and to help the user. This means that somewhere in the administration it will be necessary to be able to define the filter settings. Some examples of filters:

• people, of the type (or group) merchants who have lived in Freistadt
• people who have participated in certain events
• Places where someone has been
• and always with the filter by date ranges

The user interface of these filters should allow you to navigate the hierarchy of events and subevents, places and subplaces, types and subtypes.

I'm adding some references, but I understand that when implementing this functionality there must be reflection on how to fit it into the technology. For projects of mine from years ago I implemented the Exhibit from https://www.simile-widgets.org/exhibit3/ (and it still works)

• https://en.wikipedia.org/wiki/Faceted_search
• https://zeo.org/resources/blog/what-is-faceted-navigation-and-how-does-it-work
• https://developers.google.com/search/blog/2014/02/faceted-navigation-best-and-5-of-worst

• https://github.com/itemsapi/itemsjs
• https://eikes.github.io/facetedsearch/
• https://github.com/stereobooster/facets
• https://documentcloud.github.io/visualsearch/ (impressive light UI, too much depoendencies)

• https://pythonhosted.org/Flask-WhooshAlchemy/
• https://pypi.org/project/Flask-Filter/
• https://flask-restless.readthedocs.io/en/latest/filtering.html
• https://flask-diamond.readthedocs.io/en/latest/models/#only-the-model-controls-the-data

and ElasticSearch...

• https://demo.kerko.whiskyechobravo.com/bibliography/
• https://pypi.org/project/Kerko/

Issues related:
https://redmine.openatlas.eu/issues/998
https://redmine.openatlas.eu/issues/2520