is the search on https://docs.djangoproject.com/en/1.3/ broken, or is it just me,
getting no results?
Thomas
--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de
afaik search on multiple terms has not been working for a long time:
compare
https://docs.djangoproject.com/search/?q=typed+choice+field&release=5
with
http://duckduckgo.com/?q=site%3Adocs.djangoproject.com+typed+choice
+field
--
regards
Kenneth Gonsalves
Thomas
--
creecode writes:
> I can't say for sure but for some time it seems to me that
> searching has become more difficult. I can't put my finger on any
> specifics. I have found that some phrases that are in my browser
> form field cache I've used in that past no longer return results.
> And I'm almost certain some of them were previously successful.
I *think* (though I'm really not sure) that the search used to work
through Google. Be that as it may, it used to be significantly
better. Were there legal problems with the old search?
If I searched for "queryset api", the first result was, well, the
QuerySet API. Now, it is the fifth. With just "queryset", it is
even position 9.
Tsch�,
Torsten.
--
Torsten Bronger Jabber ID: torsten...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
Ugh, I'm sorry. If you take some notes on what those searches are --
which ones aren't returning results you'd expect -- and let me know I
can tweak it.
> I *think* (though I'm really not sure) that the search used to work
> through Google. Be that as it may, it used to be significantly
> better. Were there legal problems with the old search?
No, not legal problems; technical -- I had all sorts of problems with
Google's search. You can't tweak it at all -- if you don't like what
you get, tough. It also would go down from time to time, and there was
never any help, ETAs, or info about when it'd be back up. Since it
works off a spider it'd pick up stuff that isn't content -- searching
for "documentation", for example, was useless since that word appears
in the nav. I could go on, but basically Google's search was a PITA.
So I may have taken a step backwards switching away from Google, but
now the control is in our hands -- we can tweak, tune, and otherwise
make it work better. If you want to help, see
https://github.com/django/djangoproject.com and look in
django_website/docs; it's built using Haystack.
> If I searched for "queryset api", the first result was, well, the
> QuerySet API. Now, it is the fifth. With just "queryset", it is
> even position 9.
Thank - I'll look into that particular search and see if I can boost
the right document to the top. If you find more like that drop a list
into this thread and I'll take a look.
Jacob
Ugh, I'm sorry. If you take some notes on what those searches are --
which ones aren't returning results you'd expect -- and let me know I
can tweak it.
it is using the default sphinx search which is limited to one word
searches.
--
regards
Kenneth Gonsalves
That's true of the documentation you build locally, but the search on
docs.djangoproject.com uses Haystack with the Xapian search engine.
It's a proper search engine -- just not tuned perfectly.
Jacob
thanks for the info - the search *has* improved, for example a search
for get_FOO_display used to fail, it now succeeds. But I still need
ddg's site search for multiword searches.
--
regards
Kenneth Gonsalves
Can you be a bit more specific? If there's a bug I'd like to fix it,
but I'm not having any issues with "multiword searches"; for example:
* https://docs.djangoproject.com/search/?q=form+wizard&release=5
* https://docs.djangoproject.com/search/?q=auth+middleware&release=5
* https://docs.djangoproject.com/search/?q=database+routers&release=5
Jacob
what happens here is that the search returns all the results for each
individual word - not the combination of words. Compare with ddg:
http://duckduckgo.com/?q=site%3Adocs.djangoproject.com+typed+choice
+field
http://duckduckgo.com/?q=site%3Adocs.djangoproject.com+choices+display
--
regards
Kenneth Gonsalves