en:user:searching
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:user:searching [2017/04/09 21:52] – [Cross-collection searching] kjdon | en:user:searching [2023/03/13 01:46] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | |||
====== Searching ====== | ====== Searching ====== | ||
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 20: | ||
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 115: | Line 126: | ||
===== Partition Indexes ===== | ===== Partition Indexes ===== | ||
- | <!-- id:144 --> | + | Indexes are built on particular text or metadata sources. |
- | <!-- id:145 --> | + | The " |
" | " | ||
For more on how to create partitions, visit the [[en: | For more on how to create partitions, visit the [[en: | ||
Line 123: | Line 134: | ||
===== Searching a collection ===== | ===== Searching a collection ===== | ||
- | <TABAREA tabs="Greenstone3, | + | <tabbox |
- | <TAB> | + | |
Greenstone3 offers three different search page options, offering increasing | Greenstone3 offers three different search page options, offering increasing | ||
levels of granularity: | levels of granularity: | ||
Line 130: | Line 140: | ||
* **Form Search** presents all search options available for the collection, and multiple text boxes for query words/ | * **Form Search** presents all search options available for the collection, and multiple text boxes for query words/ | ||
* **Advanced Search** provides multiple text boxes for query words/ | * **Advanced Search** provides multiple text boxes for query words/ | ||
- | </TAB> | + | <tabbox Greenstone2> |
- | <TAB> | + | |
{{ : | {{ : | ||
Searching can be performed from the about page (depending on the search preference settings) and the search page of a collection. | Searching can be performed from the about page (depending on the search preference settings) and the search page of a collection. | ||
Line 143: | Line 152: | ||
- | </TAB> | + | </tabbox> |
- | </ | + | |
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 220: | Line 228: | ||
</ | </ | ||
- | ===== <!-- id:380 -->Cross-collection searching ===== | + | ===== Cross-collection searching ===== |
- | <!-- id:381 -->Greenstone has a facility for “cross-collection searching, | + | Greenstone has a facility for “cross-collection searching, |
- | <TABAREA tabs="Greenstone3, | + | <tabbox |
- | <TAB> | + | |
of your library allows you to search all collections at once. Collections do not have to be built with | of your library allows you to search all collections at once. Collections do not have to be built with | ||
the same indexer; however, if collections //are// built with different indexers, results may not be ranked correctly, | the same indexer; however, if collections //are// built with different indexers, results may not be ranked correctly, | ||
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 '' | ||
< | < | ||
< | < | ||
</ | </ | ||
- | </TAB> | + | <tabbox Greenstone2> |
- | <TAB> | + | |
Cross-collection searching is done by specifying a list of other collections | Cross-collection searching is done by specifying a list of other collections | ||
to be searched along with the current one. | to be searched along with the current one. | ||
Line 251: | Line 257: | ||
The Preferences page allows you to choose which collections are included in the searches. | The Preferences page allows you to choose which collections are included in the searches. | ||
- | <!-- id:382 -->Cross-collection searching is enabled by a line in the collection Configuration file: | + | Cross-collection searching is enabled by a line in the collection Configuration file: |
< | < | ||
Line 257: | Line 263: | ||
</ | </ | ||
- | <!-- id:383 -->where the collections involved are called //col_1//, //col_2//, … The same line should appear in the configuration file of every collection that is involved. | + | where the collections involved are called //col_1//, //col_2//, … The same line should appear in the configuration file of every collection that is involved. |
- | </TAB> | + | </tabbox> |
- | </ | + | |
===== Formatting cross-collection search results ===== | ===== Formatting cross-collection search results ===== | ||
- | <TABAREA tabs="Greenstone3, | + | <tabbox |
- | <TAB> | + | |
In greenstone3, | In greenstone3, | ||
Line 283: | Line 287: | ||
</ | </ | ||
- | Modify | + | You can modify |
- | </TAB> | + | |
- | <TAB> | + | 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 | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | 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. | ||
+ | <tabbox Greenstone2> | ||
In greenstone2, | In greenstone2, | ||
- | </TAB> | + | </tabbox> |
- | </ | + | |
===== SQL Search forms ===== | ===== SQL Search forms ===== | ||
There are 2 SQL search forms: simple and advanced. | There are 2 SQL search forms: simple and advanced. | ||
Line 308: | Line 349: | ||
- | <TABAREA tabs="Greenstone3, | + | <tabbox |
- | <TAB> | + | |
The [[http:// | The [[http:// | ||
- | </TAB> | + | <tabbox Greenstone2> |
- | <TAB> | + | |
The [[http:// | The [[http:// | ||
- | </TAB> | + | </tabbox> |
- | </ | + |
en/user/searching.1491774773.txt.gz · Last modified: 2017/04/09 21:52 by kjdon