Queryer is a standalone program enabling search and retrieval of documents in an mgpp collection. Even when using greenstone, it is useful for testing your collections. Queryer can be run like Queryer -f -t index and text files is the path to these files down to the collection name. eg if your text files are demo/index/text/demo.t, demo/index/text/demo.ti etc, then the text path is demo/index/text/demo similary for the index files. Commands available in the Queryer are: .q quit .h print the help message .i change the search level (enter the new level at the prompt) .l change the result level ( "" "" ) .b full text browse (enter a word or fragment at the prompt) .r0/.r1 ranking off/on .t0/.t1 query type some/all .c0/.c1 casefolding off/on .s0/.s1 stemming off/on .o0/.o1 short output off/on .p print a document (enter the docnum at the prompt) otherwise just enter a query The current query syntax involves the following: boolean operators: & AND | OR ! NOT, with () for precedence term modifiers: #icus /x - this is stemming, casefolding and weighting like in gsdl #i = case insensitive, #c = case sensitive #u = unstemmed, #s = stemmed /x = term weight (default = 1). eg computer#is/10 is computer, stemmed and casefolded, with a weight of 10 compared to other terms in the same query Proximity searching: NEARx this is used to specify the maximum distance apart two words must be to match eg dog NEAR4 cat - cat must be within 4 words either side of dog. NEAR by itself defaults to 20(??). fielded searching: [ terms]:Field eg [Witten]:Creator [Witten]:CR the field names need to be the names of the metadata elements in your collection. If the collection was built with greenstone, these names are the two letter codes found in the build.cfg file. Multiple terms inside the [] are ANDed together. Different fields can be combined using normal boolean stuff, eg [Witten]:CR & [Gigabytes]:TI Term modifiers can be included inside the [].