Changeset 19606

Show
Ignore:
Timestamp:
27.05.2009 10:47:15 (10 years ago)
Author:
anna
Message:

use 'index file' when refer to physical file.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • gli/trunk/classes/dictionary.properties

    r19545 r19606  
    8080CDM.BuildTypeManager.Title:Select the Indexer 
    8181CDM.BuildTypeManager.mg:MG 
    82 CDM.BuildTypeManager.mg_Description:This is the original indexer used by Greenstone, developed mainly by Alistair Moffat and described in the classic book Managing Gigabytes. It does section level indexing, and searches can be boolean or ranked (not both at once). For each index specified in the collection, a separate physical index is created. For phrase searching, Greenstone does an "AND" search on all the terms, then scans the resulting hits to see if the phrase is present. It has been extensively tested on very large collections (many GB of text). 
     82CDM.BuildTypeManager.mg_Description:This is the original indexer used by Greenstone, developed mainly by Alistair Moffat and described in the classic book Managing Gigabytes. It does section level indexing, and searches can be boolean or ranked (not both at once). For each index specified in the collection, a separate index file is created. For phrase searching, Greenstone does an "AND" search on all the terms, then scans the resulting hits to see if the phrase is present. It has been extensively tested on very large collections (many GB of text). 
    8383CDM.BuildTypeManager.mgpp:MGPP 
    84 CDM.BuildTypeManager.mgpp_Description:This new version of MG (MG plus plus) 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/section levels and text/metadata fields are all handled by the one index. For collections with many indexes, this results in a smaller collection size than using MG. For large collections, searching may be a bit slower due to the index being word level rather than section level. 
     84CDM.BuildTypeManager.mgpp_Description:This new version of MG (MG plus plus) 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 file is created for a Greenstone collection: document/section levels and text/metadata fields are all handled by one index file. For collections with many indexes, this results in a smaller collection size than using MG. For large collections, searching may be a bit slower due to the index being word level rather than section level. 
    8585CDM.BuildTypeManager.lucene:Lucene 
    86 CDM.BuildTypeManager.lucene_Description: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, range searching and sorting of search results by metadata fields. It was added to Greenstone to facilitate incremental collection building, which MG and MGPP can't provide. 
     86CDM.BuildTypeManager.lucene_Description: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 index files. It provides a similar range of search functionality to MGPP with the addition of single-character wildcards, range searching and sorting of search results by metadata fields. It was added to Greenstone to facilitate incremental collection building, which MG and MGPP can't provide. 
    8787CDM.BuildTypeManager.Current_Type:Indexer in use: {0} 
    8888CDM.BuildTypeManager.Change:Change...