yacy_search_server/htroot/ConfigHeuristics_p.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <title>YaCy '#[clientname]#': Heuristics Configuration</title>
    #%env/templates/metas.template%#
  </head>
  <body id="ConfigNetwork">
    #%env/templates/header.template%#
    #%env/templates/submenuSearchConfiguration.template%#
    <h2>Heuristics Configuration</h2>
    <p>
    A <a href="http://en.wikipedia.org/wiki/Heuristic">heuristic</a> is an 'experience-based technique that help in problem solving, learning and discovery' (wikipedia). The search heuristics that can be switched on here are techniques that help the discovery of possible search results based on link guessing, in-search crawling and requests to other search engines.
    When a search heuristic is used, the resulting links are not used directly as search result but the loaded pages are indexed and stored like other content. This ensures that blacklists can be used and that the searched word actually appears on the page that was discovered by the heuristic.
    </p>
    
    <form action=""><fieldset>
    The success of heuristics are marked with an image (<img width="16" height="9" src="/env/grafics/heuristic_redundant.gif" title="heuristic:&lt;name&gt; (redundant)" style="width:16px; height:9px;" alt="heuristic:&lt;name&gt; (redundant)"/>/<img width="16" height="9" src="/env/grafics/heuristic_new.gif" title="heuristic:&lt;name&gt; (new link)" style="width:16px; height:9px;" alt="heuristic:&lt;name&gt; (new link)"/>) below the favicon left from the search result entry:
    <dl>
        <dt>
          <img width="16" height="9" src="/env/grafics/heuristic_redundant.gif" title="heuristic:&lt;name&gt; (redundant)" style="width:16px; height:9px;" alt="heuristic:&lt;name&gt; (redundant)"/>
        </dt>
        <dd>
          The search result was discovered by a heuristic, but the link was already known by YaCy
        </dd>
        <dt>
          <img width="16" height="9" src="/env/grafics/heuristic_new.gif" title="heuristic:&lt;name&gt; (new link)" style="width:16px; height:9px;" alt="heuristic:&lt;name&gt; (new link)"/>
        </dt>
        <dd>
          The search result was discovered by a heuristic, not previously known by YaCy
        </dd>
    </dl></fieldset></form>
    
    <form id="HeuristicFormSite" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">
    <fieldset>
      <legend>
        <input type="checkbox" name="site_check" id="site" onclick="window.location.href='ConfigHeuristics_p.html?#(site.checked)#site_on=::site_off=#(/site.checked)#'" value="site"#(site.checked)#:: checked="checked"#(/site.checked)# />
        <label for="site">'site'-operator: instant shallow crawl</label>
      </legend>
      <p>
      When a search is made using a 'site'-operator (like: 'download site:yacy.net') then the host of the site-operator is instantly crawled with a host-restricted depth-1 crawl.
      That means: right after the search request the portal page of the host is loaded and every page that is linked on this page that points to a page on the same host.
      Because this 'instant crawl' must obey the robots.txt and a minimum access time for two consecutive pages, this heuristic is rather slow, but may discover all wanted search results using a second search (after a small pause of some seconds).
      </p>
    </fieldset>
    </form>
    
    <form id="HeuristicFormSearchResult" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">
        <fieldset>
            <table>
                <tr>
                    <td>
                        <legend>
                            <input type="checkbox" name="searchresult_check" id="searchresult" onclick="window.location.href='ConfigHeuristics_p.html?#(searchresult.checked)#searchresult_on=::searchresult_off=#(/searchresult.checked)#'" value="searchresult"#(searchresult.checked)#:: checked="checked"#(/searchresult.checked)# />
                            <label for="searchresult">search-result: shallow crawl on all displayed search results</label>
                        </legend>
                    </td>
                    <td>
                        <legend>
                            <input type="checkbox" name="searchresultglobal_check" id="searchresultglobal" onclick="window.location.href='ConfigHeuristics_p.html?#(searchresultglobal.checked)#searchresultglobal_on=::searchresultglobal_off=#(/searchresultglobal.checked)#'" value="siteresultglobal"#(searchresultglobal.checked)#:: checked="checked"#(/searchresultglobal.checked)# />
                            <label for="searchresultglobal">add as global crawl job</label>
                        </legend>
                    </td>
                </tr>
            </table>
      <p>
      When a search is made then all displayed result links are crawled with a depth-1 crawl.
      This means: right after the search request every page is loaded and every page that is linked on this page.
      If you check 'add as global crawl job' the pages to be crawled are added to the global crawl queue (remote peers can pickup pages to be crawled).
      Default is to add the links to the local crawl queue (your peer crawls the linked pages).
      </p>
    </fieldset>
    </form>
    
    <form id="HeuristicFormTwitter" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">
    <fieldset>
      <legend>
        <input type="checkbox" name="twitter_check" id="twitter" onclick="window.location.href='ConfigHeuristics_p.html?#(twitter.checked)#twitter_on=::twitter_off=#(/twitter.checked)#'" value="twitter"#(twitter.checked)#:: checked="checked"#(/twitter.checked)# />
        <label for="twitter">twitter: load external search result list from <a href="http://search.twitter.com">twitter</a></label>
      </legend>
      <p>
      When using this heuristic, then every search request line is used for a call to twitter.
      50 results are taken from twitter and loaded simultanously, parsed and indexed immediately.
      </p>
    </fieldset>
    </form>
    
    <form id="HeuristicFormBlekko" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">
    <fieldset>
      <legend>
        <input type="checkbox" name="blekko_check" id="blekko" onclick="window.location.href='ConfigHeuristics_p.html?#(blekko.checked)#blekko_on=::blekko_off=#(/blekko.checked)#'" value="blekko"#(blekko.checked)#:: checked="checked"#(/blekko.checked)# />
        <label for="blekko">blekko: load external search result list from <a href="http://blekko.com">blekko</a></label>
      </legend>
      <p>
      When using this heuristic, then every search request line is used for a call to blekko.
      20 results are taken from blekko and loaded simultanously, parsed and indexed immediately.
      </p>
    </fieldset>
    </form>

    <fieldset>
      <form id="HeuristicFormOpenSearch" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">
        <legend>
          <input type="checkbox" name="opensearch_check" id="opensearch" onclick="window.location.href='ConfigHeuristics_p.html?#(opensearch.checked)#opensearch_on=::opensearch_off=#(/opensearch.checked)#'" value="opensearch"#(opensearch.checked)#:: checked="checked"#(/opensearch.checked)# />
          <label for="opensearch">opensearch load external search result list from active systems below</label>
        </legend>
        <p>
        When using this heuristic, then every search request line is used for a call to listed opensearch systems until enough results to fill the current search page are available.
        20 results are taken from remote system and loaded simultanously, parsed and indexed immediately.
        To find out more about OpenSearch see <a href="http://www.opensearch.org" target="_blank">OpenSearch.org</a>
        </p>
      </form>

    <form action="ConfigHeuristics_p.html" method="post" enctype="multipart/form-data" accept-charset="UTF-8">
      <div>
      <b>Available/Active Opensearch System</b>
      <table class="sortable" border="0" cellpadding="2" cellspacing="1">
      <tr class="TableHeader" valign="bottom">
        <td>Active</td>
        <td>Title</td>
        <td>Comment</td>
        <td>Url <small>(format opensearch <a href="http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_URL_template_syntax" target="_blank">Url template syntax</a>)</small></td>
        <td>delete</td>
      </tr>
      #{osdcfg}#
      <tr class="TableCell#(dark)#Light::Dark#(/dark)#">
        <td align="center"><input type="checkbox" name="ossys_#[title]#" value="checked" #(checked)#::checked="checked"#(/checked)#/></td>
        <td align="left"><b><a href="#[urlhostlink]#" target="_blank">#[title]#</b></a> </td>
        <td align="left">#[comment]#</td>
        <td align="left"><input type="text" name="ossys_url_#[title]#" value="#[url]#" size="70"/></td>
        <td align="center"><input type="checkbox" name="ossys_del_#[title]#" value="checked" #(delchecked)#::checked="checked"#(/delchecked)#/></td>
      </tr>
      #{/osdcfg}#
      <tr>
        <td><small>new</small></td>
        <td><input type="text" name="ossys_newtitle"/></td>
        <td><input type="text" name="ossys_newcomment"/></td>
        <td><input type="text" name="ossys_newurl" size="70"/></td>
        <td><input type="submit" name="addnewosd" value="add"/></td>
      </tr>
      </table>
      </div>
      <div>
        <input type="submit" name="setopensearch" value="Save" class="submitready"/>
        <span style="color:red">#[osderrmsg]#</span>
      </div>
      <br>
      <div>
        <div style="float:right">
        <input type="submit" name="discoverosd" id="discoverosd" value="discover from index" class="submitready" onclick="return confirm('start background task, depending on index size this may run a long time')"/>
        </div>
        With the button "discover from index" you can search within the metadata of your local index (Web Structure Index) to find systems which support the Opensearch specification.
        The task is started in the background. It may take some minutes before new entries appear (after refreshing the page).
        Alternatively you may <a href="?copydefaultosdconfig=">copy &amp; paste a example config file</a> located in <i>defaults/heuristicopensearch.conf</i> to the DATA/SETTINGS directory.
        For the discover function the <i>web graph</i> option of the web structure index and the fields <i>target_rel_s, target_protocol_s, target_urlstub_s</i> have to be switched on in the <a href="IndexSchema_p.html?core=webgraph">webgraph Solr schema</a>.
        #{osdsolrfieldswitch}#<input type="submit" name="switchsolrfieldson" value="switch Solr fields on" class="submitready" onclick="return confirm('modify Solr Schema')"/>#{/osdsolrfieldswitch}#
      </div>
    </form>
    </fieldset>

    #%env/templates/footer.template%#
  </body>
</html>
added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">`
			`<html xmlns="http://www.w3.org/1999/xhtml">`
			`<head>`
Added German translation for ConfigHeuristics_p.html to de.lng Fixed Network -> Heuristics title tag of the page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6963 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`<title>YaCy '#[clientname]#': Heuristics Configuration</title>`
added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`#%env/templates/metas.template%#`
			`</head>`
			`<body id="ConfigNetwork">`
			`#%env/templates/header.template%#`
moved HTCache, Heuristics and Parser servlet to a more appropriate menu location 12 years ago			`#%env/templates/submenuSearchConfiguration.template%#`
added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`<h2>Heuristics Configuration</h2>`
			`<p>`
			`A <a href="http://en.wikipedia.org/wiki/Heuristic">heuristic</a> is an 'experience-based technique that help in problem solving, learning and discovery' (wikipedia). The search heuristics that can be switched on here are techniques that help the discovery of possible search results based on link guessing, in-search crawling and requests to other search engines.`
			`When a search heuristic is used, the resulting links are not used directly as search result but the loaded pages are indexed and stored like other content. This ensures that blacklists can be used and that the searched word actually appears on the page that was discovered by the heuristic.`
			`</p>`
ConfigHeuristics_p.html: XHTML 1.0 Strict Changes - added empty action tag to form - replaced name tags with id (name is not a valid tag in XHTML 1.0 Strict) - changed label for target (so now clicking on the labels also activates the checkboxes) de.lng: Test with Subversion properties #2 git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6982 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago
			`<form action=""><fieldset>`
added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`The success of heuristics are marked with an image (<img width="16" height="9" src="/env/grafics/heuristic_redundant.gif" title="heuristic:<name> (redundant)" style="width:16px; height:9px;" alt="heuristic:<name> (redundant)"/>/<img width="16" height="9" src="/env/grafics/heuristic_new.gif" title="heuristic:<name> (new link)" style="width:16px; height:9px;" alt="heuristic:<name> (new link)"/>) below the favicon left from the search result entry:`
			`<dl>`
			`<dt>`
			`<img width="16" height="9" src="/env/grafics/heuristic_redundant.gif" title="heuristic:<name> (redundant)" style="width:16px; height:9px;" alt="heuristic:<name> (redundant)"/>`
			`</dt>`
			`<dd>`
			`The search result was discovered by a heuristic, but the link was already known by YaCy`
			`</dd>`
			`<dt>`
			`<img width="16" height="9" src="/env/grafics/heuristic_new.gif" title="heuristic:<name> (new link)" style="width:16px; height:9px;" alt="heuristic:<name> (new link)"/>`
			`</dt>`
			`<dd>`
			`The search result was discovered by a heuristic, not previously known by YaCy`
			`</dd>`
			`</dl></fieldset></form>`
ConfigHeuristics_p.html: XHTML 1.0 Strict Changes - added empty action tag to form - replaced name tags with id (name is not a valid tag in XHTML 1.0 Strict) - changed label for target (so now clicking on the labels also activates the checkboxes) de.lng: Test with Subversion properties #2 git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6982 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago
			`<form id="HeuristicFormSite" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">`
added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`<fieldset>`
			`<legend>`
			`<input type="checkbox" name="site_check" id="site" onclick="window.location.href='ConfigHeuristics_p.html?#(site.checked)#site_on=::site_off=#(/site.checked)#'" value="site"#(site.checked)#:: checked="checked"#(/site.checked)# />`
ConfigHeuristics_p.html: XHTML 1.0 Strict Changes - added empty action tag to form - replaced name tags with id (name is not a valid tag in XHTML 1.0 Strict) - changed label for target (so now clicking on the labels also activates the checkboxes) de.lng: Test with Subversion properties #2 git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6982 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`<label for="site">'site'-operator: instant shallow crawl</label>`
added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`</legend>`
			`<p>`
			`When a search is made using a 'site'-operator (like: 'download site:yacy.net') then the host of the site-operator is instantly crawled with a host-restricted depth-1 crawl.`
			`That means: right after the search request the portal page of the host is loaded and every page that is linked on this page that points to a page on the same host.`
			`Because this 'instant crawl' must obey the robots.txt and a minimum access time for two consecutive pages, this heuristic is rather slow, but may discover all wanted search results using a second search (after a small pause of some seconds).`
			`</p>`
			`</fieldset>`
			`</form>`
add search result heuristic. adding a crawl job with depth-1 for every displayed search result (crawling every external linked page of displayed search result pages) 13 years ago
			`<form id="HeuristicFormSearchResult" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">`
			`<fieldset>`
			`<table>`
			`<tr>`
			`<td>`
			`<legend>`
			`<input type="checkbox" name="searchresult_check" id="searchresult" onclick="window.location.href='ConfigHeuristics_p.html?#(searchresult.checked)#searchresult_on=::searchresult_off=#(/searchresult.checked)#'" value="searchresult"#(searchresult.checked)#:: checked="checked"#(/searchresult.checked)# />`
			`<label for="searchresult">search-result: shallow crawl on all displayed search results</label>`
			`</legend>`
			`</td>`
			`<td>`
			`<legend>`
			`<input type="checkbox" name="searchresultglobal_check" id="searchresultglobal" onclick="window.location.href='ConfigHeuristics_p.html?#(searchresultglobal.checked)#searchresultglobal_on=::searchresultglobal_off=#(/searchresultglobal.checked)#'" value="siteresultglobal"#(searchresultglobal.checked)#:: checked="checked"#(/searchresultglobal.checked)# />`
			`<label for="searchresultglobal">add as global crawl job</label>`
			`</legend>`
			`</td>`
			`</tr>`
			`</table>`
			`<p>`
			`When a search is made then all displayed result links are crawled with a depth-1 crawl.`
			`This means: right after the search request every page is loaded and every page that is linked on this page.`
			`If you check 'add as global crawl job' the pages to be crawled are added to the global crawl queue (remote peers can pickup pages to be crawled).`
			`Default is to add the links to the local crawl queue (your peer crawls the linked pages).`
			`</p>`
			`</fieldset>`
			`</form>`

added twitter search heuristic 12 years ago			`<form id="HeuristicFormTwitter" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">`
			`<fieldset>`
			`<legend>`
			`<input type="checkbox" name="twitter_check" id="twitter" onclick="window.location.href='ConfigHeuristics_p.html?#(twitter.checked)#twitter_on=::twitter_off=#(/twitter.checked)#'" value="twitter"#(twitter.checked)#:: checked="checked"#(/twitter.checked)# />`
			`<label for="twitter">twitter: load external search result list from <a href="http://search.twitter.com">twitter</a></label>`
			`</legend>`
			`<p>`
			`When using this heuristic, then every search request line is used for a call to twitter.`
			`50 results are taken from twitter and loaded simultanously, parsed and indexed immediately.`
			`</p>`
			`</fieldset>`
			`</form>`

- added http://blekko.com as search heuristic (like scroogle). This was easy since they deliver their search results also as rss feed - renamed YaCys search result modifications keywords for RECENT, NEAR and language: to the blekko slashtag naming scheme. YaCy now supports the following blekko-like slash built-in slashtags: /date - for search results ordered by date (most recent up) /near - for search results where search words appear near to each other (closest up) /language/<lang> - for a sorting by language where the wanted language gets up. Example: /language/de git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7350 6c8d7289-2bf4-0310-a012-ef5d649a1542 14 years ago			`<form id="HeuristicFormBlekko" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">`
			`<fieldset>`
			`<legend>`
fix in heuristics config git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7707 6c8d7289-2bf4-0310-a012-ef5d649a1542 14 years ago			`<input type="checkbox" name="blekko_check" id="blekko" onclick="window.location.href='ConfigHeuristics_p.html?#(blekko.checked)#blekko_on=::blekko_off=#(/blekko.checked)#'" value="blekko"#(blekko.checked)#:: checked="checked"#(/blekko.checked)# />`
- added http://blekko.com as search heuristic (like scroogle). This was easy since they deliver their search results also as rss feed - renamed YaCys search result modifications keywords for RECENT, NEAR and language: to the blekko slashtag naming scheme. YaCy now supports the following blekko-like slash built-in slashtags: /date - for search results ordered by date (most recent up) /near - for search results where search words appear near to each other (closest up) /language/<lang> - for a sorting by language where the wanted language gets up. Example: /language/de git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@7350 6c8d7289-2bf4-0310-a012-ef5d649a1542 14 years ago			`<label for="blekko">blekko: load external search result list from <a href="http://blekko.com">blekko</a></label>`
			`</legend>`
			`<p>`
			`When using this heuristic, then every search request line is used for a call to blekko.`
			`20 results are taken from blekko and loaded simultanously, parsed and indexed immediately.`
			`</p>`
			`</fieldset>`
			`</form>`
add search result heuristic. adding a crawl job with depth-1 for every displayed search result (crawling every external linked page of displayed search result pages) 13 years ago
Adding heuristic to get search results from configured systems which support opensearch specification - any system supporting opensearch specification can be configured - search query is only forwarded to remote system if not enough results available on local peer - discover function provided, checking the local Solr index for links to opensearchdescription files, to add to the config - sample config file with some general search engines with opensearch support 12 years ago			`<fieldset>`
			`<form id="HeuristicFormOpenSearch" method="post" action="ConfigHeuristics_p.html" enctype="multipart/form-data" accept-charset="UTF-8">`
			`<legend>`
			`<input type="checkbox" name="opensearch_check" id="opensearch" onclick="window.location.href='ConfigHeuristics_p.html?#(opensearch.checked)#opensearch_on=::opensearch_off=#(/opensearch.checked)#'" value="opensearch"#(opensearch.checked)#:: checked="checked"#(/opensearch.checked)# />`
			`<label for="opensearch">opensearch load external search result list from active systems below</label>`
			`</legend>`
			`<p>`
			`When using this heuristic, then every search request line is used for a call to listed opensearch systems until enough results to fill the current search page are available.`
			`20 results are taken from remote system and loaded simultanously, parsed and indexed immediately.`
			`To find out more about OpenSearch see <a href="http://www.opensearch.org" target="_blank">OpenSearch.org</a>`
			`</p>`
			`</form>`

			`<form action="ConfigHeuristics_p.html" method="post" enctype="multipart/form-data" accept-charset="UTF-8">`
			`<div>`
			`<b>Available/Active Opensearch System</b>`
			`<table class="sortable" border="0" cellpadding="2" cellspacing="1">`
			`<tr class="TableHeader" valign="bottom">`
			`<td>Active</td>`
			`<td>Title</td>`
			`<td>Comment</td>`
			`<td>Url <small>(format opensearch <a href="http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_URL_template_syntax" target="_blank">Url template syntax</a>)</small></td>`
			`<td>delete</td>`
			`</tr>`
			`#{osdcfg}#`
			`<tr class="TableCell#(dark)#Light::Dark#(/dark)#">`
			`<td align="center"><input type="checkbox" name="ossys_#[title]#" value="checked" #(checked)#::checked="checked"#(/checked)#/></td>`
			`<td align="left"><b><a href="#[urlhostlink]#" target="_blank">#[title]#</b></a> </td>`
			`<td align="left">#[comment]#</td>`
			`<td align="left"><input type="text" name="ossys_url_#[title]#" value="#[url]#" size="70"/></td>`
			`<td align="center"><input type="checkbox" name="ossys_del_#[title]#" value="checked" #(delchecked)#::checked="checked"#(/delchecked)#/></td>`
			`</tr>`
			`#{/osdcfg}#`
			`<tr>`
			`<td><small>new</small></td>`
			`<td><input type="text" name="ossys_newtitle"/></td>`
			`<td><input type="text" name="ossys_newcomment"/></td>`
			`<td><input type="text" name="ossys_newurl" size="70"/></td>`
			`<td><input type="submit" name="addnewosd" value="add"/></td>`
			`</tr>`
			`</table>`
			`</div>`
			`<div>`
			`<input type="submit" name="setopensearch" value="Save" class="submitready"/>`
			`<span style="color:red">#[osderrmsg]#</span>`
			`</div>`
			`<br>`
			`<div>`
			`<div style="float:right">`
			`<input type="submit" name="discoverosd" id="discoverosd" value="discover from index" class="submitready" onclick="return confirm('start background task, depending on index size this may run a long time')"/>`
			`</div>`
adjust Opensearch discover function to new webgraph Solr schema 12 years ago			`With the button "discover from index" you can search within the metadata of your local index (Web Structure Index) to find systems which support the Opensearch specification.`
Adding heuristic to get search results from configured systems which support opensearch specification - any system supporting opensearch specification can be configured - search query is only forwarded to remote system if not enough results available on local peer - discover function provided, checking the local Solr index for links to opensearchdescription files, to add to the config - sample config file with some general search engines with opensearch support 12 years ago			`The task is started in the background. It may take some minutes before new entries appear (after refreshing the page).`
			`Alternatively you may <a href="?copydefaultosdconfig=">copy & paste a example config file</a> located in <i>defaults/heuristicopensearch.conf</i> to the DATA/SETTINGS directory.`
adjust Opensearch discover function to new webgraph Solr schema 12 years ago			`For the discover function the <i>web graph</i> option of the web structure index and the fields <i>target_rel_s, target_protocol_s, target_urlstub_s</i> have to be switched on in the <a href="IndexSchema_p.html?core=webgraph">webgraph Solr schema</a>.`
Adding heuristic to get search results from configured systems which support opensearch specification - any system supporting opensearch specification can be configured - search query is only forwarded to remote system if not enough results available on local peer - discover function provided, checking the local Solr index for links to opensearchdescription files, to add to the config - sample config file with some general search engines with opensearch support 12 years ago			`#{osdsolrfieldswitch}#<input type="submit" name="switchsolrfieldson" value="switch Solr fields on" class="submitready" onclick="return confirm('modify Solr Schema')"/>#{/osdsolrfieldswitch}#`
			`</div>`
			`</form>`
			`</fieldset>`

added a configuration page for search heuristics. currently you can switch on there: - a site-operation heuristic that loads all direct links from a portal page if the site-operator is used - a direct crawl for search results from scroogle for the given search terms The configuration page can be found directly beside the network configuration page git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@6951 6c8d7289-2bf4-0310-a012-ef5d649a1542 15 years ago			`#%env/templates/footer.template%#`
			`</body>`
Scroogle is not comming back, remove dead code Conflicts: source/net/yacy/search/Switchboard.java 13 years ago			`</html>`