- a solr field collection_sxt can be used to store a set of crawl tags
- when this field is activated, a crawl tag can be assigned when crawls
are started
- the content of the collection field can be comma-separated, all of
them are assigned to the documents when they are indexed as result of
such a crawl start
- a search result can be drilled down to a specific collection; this is
currently only available in the solr interface and also in the gsa
interface using the 'site' option
- this adds a mandatory field for gsa queries (the google api demands
that field all the time)
A crawl result can be tagged with names which are candidates for a collection request. These tags can be selected with the <ahref="/gsa/search?q=www&site=#[collection]#">GSA interface</a> using the 'site' operator. To use this option, the 'collection_sxt'-field must be switched on in the <ahref="/IndexFederated_p.html">Solr Schema</a>
</td>
</tr>
<!--
<trvalign="top"class="TableCellDark">
<td>Exclude <em>dynamic</em> Stop-Words</td>
@ -314,8 +323,8 @@
</td>
</tr>
-->
<trvalign="top"class="TableCellLight">
<tdcolspan="5"><inputtype="submit"name="crawlingstart"value="Start New Crawl"/></td>
<trvalign="top"class="TableCellSummary">
<tdcolspan="5"><inputtype="submit"name="crawlingstart"value="Start New Crawl"class="submitready"/></td>
// optional values, not part of standard YaCy handling (but useful for external applications)
collection_sxt(SolrType.string,true,true,true,"tags that are attached to crawls/index generation to separate the search result into user-defined subsets"),
csscount_i(SolrType.integer,true,true,false,"number of entries in css_tag_txt and css_url_txt"),
css_tag_txt(SolrType.text_general,true,true,true,"full css tag with normalized url"),
css_url_txt(SolrType.text_general,true,true,true,"normalized urls within a css tag"),