en:user:searching
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:user:searching [2016/08/28 23:49] – [Search Results] kjdon | en:user:searching [2019/07/09 04:16] – [Faceted Search Results] anupama | ||
---|---|---|---|
Line 2: | Line 2: | ||
In Greenstone, you can dictate how users will be able to search each | In Greenstone, you can dictate how users will be able to search each | ||
- | collection. You can select | + | collection. You can select |
you can create indexes based on any number of metadata fields and the text of the documents. | you can create indexes based on any number of metadata fields and the text of the documents. | ||
Line 17: | Line 17: | ||
These indexers are available: | These indexers are available: | ||
- | * **[[http:// | + | * **MG**: MG the original indexer used by Greenstone, developed mainly by Alistair Moffat and described in the classic book [[http:// |
- | * **[[http:// | + | |
- | * **[[http://lucene.apache.org/core/|Lucene]]**: Lucene was developed by the Apache Software Foundation. It handles field and proximity searching, but only at a single level (e.g. complete documents or individual sections, but not both). Therefore document and section indexes for a collection require two separate indexes. It provides a similar range of search functionality to MGPP with the addition of single-character wildcards and range searching. It was added to Greenstone to facilitate [[incremental building | incremental collection building]], which MG and MGPP can't provide. | + | * [[nzdl:mg | More info about MG ]] |
+ | * **MGPP**: MGPP (MG plus plus), the new version of MG, was developed by the New Zealand Digital Library Project. It does word level indexing, which allows fielded, phrase and proximity searching to be handled by the indexer. Boolean searches can be ranked. Only a single index is created for a Greenstone collection: document/ | ||
+ | * [[http://files.greenstone.org/technical/mgpp_user.pdf|MGPP user guide]] | ||
+ | * **Lucene**: Lucene was developed by the Apache Software Foundation. It handles field and proximity searching, but only at a single level (e.g. complete documents or individual sections, but not both). Therefore document and section indexes for a collection require two separate indexes. It provides a similar range of search functionality to MGPP with the addition of single-character wildcards and range searching. It was added to Greenstone to facilitate [[incremental building | incremental collection building]], which MG and MGPP can't provide. | ||
+ | * [[ |lucene web site]] | ||
+ | * [[en: | ||
+ | * **SOLR**: Available in Greenstone3. | ||
+ | * [[en: | ||
+ | * | ||
Changing the indexer affects how the indexes are built, and may affect search functionality. | Changing the indexer affects how the indexes are built, and may affect search functionality. | ||
The following table compares the indexers' | The following table compares the indexers' | ||
Line 206: | Line 214: | ||
In Greenstone 3, if you use SOLR as your search indexer, you can have faceted searching. This means you can filter search results based on other metadata. The facet options need to be set up manually in the collectionConfig.xml file as GLI does not allow you to enter them manually yet. | In Greenstone 3, if you use SOLR as your search indexer, you can have faceted searching. This means you can filter search results based on other metadata. The facet options need to be set up manually in the collectionConfig.xml file as GLI does not allow you to enter them manually yet. | ||
- | Add < | + | Add < |
< | < | ||
Line 222: | Line 230: | ||
===== <!-- id:380 --> | ===== <!-- id:380 --> | ||
- | <!-- id:381 --> | + | <!-- id:381 --> |
<TABAREA tabs=" | <TABAREA tabs=" | ||
Line 230: | Line 238: | ||
as each indexer ranks results differently. | as each indexer ranks results differently. | ||
- | If you create a new [[en: | + | If you create a new [[en:user: |
the CrossCollectionSearch serviceRack to the site's '' | the CrossCollectionSearch serviceRack to the site's '' | ||
< | < | ||
Line 262: | Line 270: | ||
</ | </ | ||
+ | ===== Formatting cross-collection search results ===== | ||
+ | <TABAREA tabs=" | ||
+ | <TAB> | ||
+ | In greenstone3, | ||
+ | |||
+ | Open up the file '' | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <!-- this format is used for the search results --> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | You can modify the format statement in almost the same way you do any format statement. You can use < | ||
+ | |||
+ | Links to the greenstone version of the document look like: | ||
+ | *library/ | ||
+ | |||
+ | You can construct this using eg | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | Links to a source file look like | ||
+ | * sites/ | ||
+ | |||
+ | You can construct this using eg | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | To put a link to the PDF (or other source file) file, dependent on whether there is a PDF or not, use the following: | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | This uses < | ||
+ | |||
+ | If you have collections with images too, you may link to add in the thumbnail linked to the original image. In this case, replace < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | This will output thumbicon metadata if it exists, otherwise will output srcicon metadata. | ||
+ | </ | ||
+ | <TAB> | ||
+ | In greenstone2, | ||
+ | </ | ||
+ | </ | ||
===== SQL Search forms ===== | ===== SQL Search forms ===== | ||
There are 2 SQL search forms: simple and advanced. | There are 2 SQL search forms: simple and advanced. |
en/user/searching.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1