esp. what data is there that is useful for an external developer (as opposed to the maintainers of the deken search)
Why are you not interested in data that is useful for the maintainers of the deken search?
simple: because that is practically only me (kudos to you of course, but in reality there have not been many contributions by others in the last decade) and I do not need to *publish* statistics about the queries, because i can access them just so. obviously i haven't done that myself, so this entire thread is a good motivation :-)
but if I were to invest time to publish such data, I would like to see benefits for other people that they can act on (short of nagging other people).
On 8/28/25 10:18, Christof Ressi wrote:
Clearly people are searching for 'freeverb' - why is it not returning the freeverb external? The intent of the user is obvious. How can the tool be updated to better serve the user?
Yes. I think this is a good argument for using wildcard search by default. We can add a checkbox for people who only want exact matches.
indeed. i do want people to be able to do exact matches (with wildcards and what not). but allowing the user to check whether they want to do a fuzzy search or an exact search sounds like the best idea.
should a fuzzy search also allow for soundex? (that's going to be more tricky. there's a tcl module in the tcllib, but we don't ship this with Pd; if we want to do the soundex matching on the server, we need to signal that in the query... it's easy, but right now the query is even trivial :-))
gfdmsr IOhannes