Such an engine might conceivably have a deeper coverage of your repositories than Google, and it would only be a matter of thirty minutes to test such a notion. But it might be nice to test the coverage of a small DuckDuckGo CSE for a unified search across all the repositories at a university (the main theses repo, the eprints repo, various OJS installations, the law-school repos and journals, etc). On the downside, the DuckDuckGo index doesn’t yet have the range and depth of Google Search, especially when it comes to small academic journals and sites of the sort in JURN. searching the full when you only want to search So it may be a preferable choice for some, provided that it indexes all your CSE’s target URLs and doesn’t forcibly truncate (e.g. DuckDuckGo is excellent on speed, relevancy ranking (especially with its image search) and on general navigational searches. DuckDuckGo is a non-tracking and privacy-centric search engine, and use doesn’t require a sign in to DuckDuckGo. It’s certainly nice to have an alternative option when making a small CSE, and there are various reasons why one might prefer this to Google. DuckDuckGo Search Box now offers the ability to input and search multiple sites in a Custom Search Engine (CSE), something I don’t remember DuckDuckGo offering the last time I looked.
0 kommentar(er)
