YaCy: Unterschied zwischen den Versionen
imported>Burghardt |
imported>Burghardt (→Goal) |
||
| Zeile 1: | Zeile 1: | ||
| + | == Search engine advantages == |
||
| − | == Goal == |
||
| − | + | We try to implement a Search Engine for all of our Computer Science related web sites at our University. |
|
Of course you can always use Google, but you will either get more hits than you want or you set a filter ("<tt>site:uni-goettingen.de</tt>") and miss relevant content from other local resources off of <tt>*.uni-goettingen.de</tt>. So the main goal for ''this'' Search Engine is to ''restrict'' the search namespace to relevant sites. |
Of course you can always use Google, but you will either get more hits than you want or you set a filter ("<tt>site:uni-goettingen.de</tt>") and miss relevant content from other local resources off of <tt>*.uni-goettingen.de</tt>. So the main goal for ''this'' Search Engine is to ''restrict'' the search namespace to relevant sites. |
||
| Zeile 15: | Zeile 15: | ||
We can index public pages only. This is unfortunate as especially locked down areas like group Wikis and project sites would benefit from a central search engine even more than these public pages. This problem may be solved later... |
We can index public pages only. This is unfortunate as especially locked down areas like group Wikis and project sites would benefit from a central search engine even more than these public pages. This problem may be solved later... |
||
| − | |||
== Implementation == |
== Implementation == |
||
Version vom 2. November 2017, 14:09 Uhr
Search engine advantages
We try to implement a Search Engine for all of our Computer Science related web sites at our University.
Of course you can always use Google, but you will either get more hits than you want or you set a filter ("site:uni-goettingen.de") and miss relevant content from other local resources off of *.uni-goettingen.de. So the main goal for this Search Engine is to restrict the search namespace to relevant sites.
The next try after leaving Google is to use the integrated search engine embedded on www.uni-goettingen.de. This has two major problems for us:
- You get too many hits. There is no integrated way to restrict the search to pages below (for example) www.informatik.uni-goettingen etc. because all content is in the single GCMS mechanism. There is no separate namespace for each Institute for Faculty.
- On the other hand this search engine does not include GCMS-external but relevant sites like http://www.swe.informatik.uni-goettingen.de, http://www.math-cs.uni-goettingen.de etc.
The kind of content we are preparing this search engine for is unrestricted and language agnostic
- Study related pages
- Research related pages including external "project"-pages
- University infrastructure pages - if there is a relationship regarding "our" Computer Science
- Technical infrastructure pages - if there is a relationship regarding "our" Computer Science
We can index public pages only. This is unfortunate as especially locked down areas like group Wikis and project sites would benefit from a central search engine even more than these public pages. This problem may be solved later...
Implementation
- Virtual machine (hosted at Gwdg ) running Debian GNU/Linux
Help us make this engine actually usable
Please check the search results for your own area of interest. If you find something relevant missing please communicate the URLs to include in the index -- User:Burghardt
See also
- ...
Links
- http://yacy.net/
- http://search.informatik.uni-goettingen.de -- plain Search
- http://search.informatik.uni-goettingen.de/Status.html -- some additional information