-
Notifications
You must be signed in to change notification settings - Fork 38
Rfc1: more search functionality
The current search functionality enables the user to search through an ArcGIS generated geocoder and an OpenLS geocoder. To enlarge the possibilities for searching, I submit the following changes.
There changes will consist of several new functionalities.
There will be more searchentries:
- A manual list
- Based on a featuresource (it can be configured on which attributes the query must be done)
At each search entry the admin can determine which layers must be active (if it's not active, it will be activated). This goes two ways: a dataset can only be searched when the layers is switched on.
Via a textfield the result of the searchaction can be determined.
The goal for this functionality is to provide the admin a way to configure a searchfunctionality with only one input, but on the backend it searches through multiple datasets. Combined with this is the possibility to provide auto-suggest when the users types it's search query.
In the viewer-admin it will be possible to manage datasets through which can be searched. Of each source (ie. WFS service, JDBC source, etc.) the admin must configure what the fields are which must be queried, and which fields are the result fields. The viewer-admin will create a index based on the configuration of the admin. This index can be updated manually or it can be configured to update automatically on a regular interval.
The changes needed for the completion of this functionality are described here.
The modules which are affected by these changes are split in the viewer and viewer-admin
- In the viewer, the search component must be changed to honour the new layout configured at the viewer-admin.
- For the new possibilities, the search component must be able to execute the new ways of searching.
- For auto-suggest the input box must be able to handle suggestions
Building an index and the possibility to use auto-suggest requires the use of a third-party component: Solr. This is a indexing and searching application. It will be configured and managed via the viewer-admin.
- In the viewer-admin there will be menu item for managing the datasets for searching:
Adding and removing datasets
Manual updating of the index
Automatic updating of the index - In the layoutmanager it must be possible to configure the searchcomponent with all the new options
We foresee no incompatibility with older version. All the old configurations will be kept and remain functional.
The functionality is being implemented in the following branch: https://github.com/flamingo-geocms/flamingo/tree/feat/solrsearch
The proposal is accepted with the +1's from the PMC.
- André Weijmer +1
- Marten Terpstra +1
- Roy Braam +1
- Meine Toonen +1 Thanks to Ron Wardenier for his input from the user side of Flamingo4.