Add "Keywords" to "Fallback localization"

[humdingerb]

Comma-separated keywords could help finding packages that don't have those keywords used in title, summary or description. Of course, HaikuDepot will have to be taught to look there as well.

[diversys]

How about adding another field where admins can add supported MIME types to packages so that HD can query those? Tracker can launch HD when opening unsupported file with filters applied to list apps that can be used to open this format.

[humdingerb]

I was thinking... Would it simplify things, if we just use a magic marker in the description field (and therefore "Fallback localization") like "%@Keywords@%", followed by a comma-separated list of keywords.

The HaikuDepot app then just has to ignore the whole line when outputting the description of a package. The listed keywords will still be found by the search function, but won't appear in the GUI.

[andponlin]

Hi Humdinger; something like this extra use of the field seem like an easy option, but will lead to a messy situation in the long term and can be time consuming to migrate out of. I would prefer to model the data properly in the database, query it in this way and relay the data back over to HD in a structured API. I'm currently working on other C++ side changes with a bug, but will try to come back to this after I have finished that.

In the meantime, can you let me know;

• Do the keywords need localization?
• Are the keywords a discrete set of values or can they be anything?
• Case insensitive?
• actual words or also phrases?

[humdingerb]

You're right, parsing magic keywords is quite ugly...

Do the keywords need localization?

Yes. People will look for certain terms in their own language, if they run their system in their non-English locale.

Are the keywords a discrete set of values or can they be anything?

Can be anything. Any words associated with a package that isn't already in Summary/Description can be listed.

Case insensitive?

Yes.

actual words or also phrases?

Words should do. I imagine people normally enter the first word they associate with the app they're looking for, then enter additional words if the result list is too large and needs more trimming.

I was also wondering if it were possible to intruduce some "fuzzying", so if people look for "themes" they also get a result if there's only the singular "theme" in keywords/summary/description. I suppose this would need to be language-specific, though...
Definitely something that can come at a later stage if possible, I think...

[andponlin]

I think for fuzzing or stemming etc... a more modern version of Postgres database server may need to be used. Otherwise Elastic, but that will also take a while to sort out. I will take a look later on.

[humdingerb]

No hurry. Plain keyword support alone would fantastic already. :)