Lelelo1
commented
2 years ago Following needs to addressed
- hit weight
- sqlite in have
If I am going to mix my repos, this is determent of wether how much users in SeeNav seem to need a default standard geo based initial setup of hits around. Meaning client just fetches any places via geolocation, possibly radius. Is that case there is also some weight and priority of tags that should be the recommended
Autocomplete tags
Instead of identifying tags semantically, tags can be found by autocompletion. You then end up with a possible query to make.
So looking at #14 the letters entered would hit on keys and values, locally installed in a sqlite database. b would hit on beauty and beer. There has to be a translation feature. Also, tags need to ranked to importance and so on, just like a more conventional text search that I initially was after.
When comes to semantic I think it can still be added, but should be considered enhancement. It can be discussed wether not this feature is only for text input, and semantic match is for whole words match - in practice meaning dictation in the client or otherwise needing a text input requiring whole word to be entered, and submitted - which is not common. So semantic is for dictation and Autcomplete tags is for text input in the client basically