>> Yeah, having a Wiki for the LSR data sounds great. However, what's >> still needed IMHO is an equivalent to the current search engine, >> i.e., something that brings up images if you search for given >> terms. AFAIK, this is not offered by Wikis, which are text-based, >> and public Web search engines are not good at that either. Maybe >> I'm wrong, and I'd really love to be corrected. Perhaps the search >> engine code used for commons.wikimedia.org could be massaged >> accordingly? > > This is certainly nice to have but is it necessary?
Let's say it would be tremendously helpful – the exact terms for describing music with text are sometimes value or imprecise, but with an image you can in most cases see immediately whether a snippet fits or doesn't fit. > Over the past few days, I've been tinkering with this, and here > is the result: > > https://wiki.lilypond.community This is great! Thanks a lot for your efforts. > If people like this, I'm willing to do the remaining things > to get it off the ground, like writing help pages, then keep > it running and pay for the server costs. I like it, and maybe there are hooks into the MediaWiki search engine to also show, say, the first image of a page (or a marked one) for a search result. > I'm not currently willing to involve myself much more than that, > though — this includes upgrading of snippets to newer LilyPond > versions in the future, and also updating the makelsr.py script (I > just don't have the energy to fight the doc build again, sorry...). I will most certainly take care of the `makelsr.pl` script. It will take some time to get acquainted with the MediaWiki API, though. Werner
