Re: [greenstone-devel] re Sort order of search result list and browse list

From Katherine Don
DateFri, 26 Sep 2003 09:59:54 -0600
Subject Re: [greenstone-devel] re Sort order of search result list and browse list
In-Reply-To (67081476-c91fb81e-81c8400-expms3-cites-uiuc-edu)
hi Xiao

The index order of mgpp is the order that documents are listed in the
archives.inf file - that is the order that they are processed by the
greenstone building code, and that is the order that mg or mgpp will
receive them.
mgpp does not sort by date. So if a 'some' query was done, the results
are ordered by rank, if an 'all' query was done, the results are listed
in the same order as they appear in the archives.inf file.

if you want unranked documents to be in date order, perhaps you can
modify the building code to process documents in that order.

regards,
katherine don

>Hi Stephen and Michael,
>
>Thank you very much for your kind responses. So the order of mgpp indexing and the order of AZCompactlist are reverse, dispite both of them sort by Date. ( I believe the index order of mgpp is sort by Date too, please see my example in the original message.)
>
>I think it will be better if the two can have the same sequence. However, it seems that modifying mgpp should be hard. So if someone of us knows how the classifiers sort by Date, we may find a way to reverse the order of the leaves in classifers.
>
>Is that feasible?
>
>Thank you for all the help!
>
>Xiao
>
>---- Original message ----
>
>
>>Date: Fri, 26 Sep 2003 11:39:51 +1200
>>From: Michael Dewsnip <mdewsnip@cs.waikato.ac.nz>
>>Subject: Re: [greenstone-devel] re Sort order of search result list and browse list
>>To: Stephen.DeGabrielle@cdu.edu.au
>>Cc: greenstone-devel@list.scms.waikato.ac.nz
>>
>>Hi Stephen,
>>
>>Thanks very much for your answer.
>>
>>In regards to the ordering of the search results, it depends on whether a
>>boolean or ranked query is being performed. For a ranked query the search
>>results are ordered according to how closely they match the query (as you
>>would expect). For a boolean query, a document either matches or doesn't, so
>>there is no scope for ordering. Therefore, the documents are simply listed
>>based on the order they were indexed by MG/MGPP, as you guessed.
>>
>>Regards,
>>
>>Michael
>>
>>
>>
>>Stephen.DeGabrielle@cdu.edu.au wrote:
>>
>>
>>
>>>Hi,
>>>I only know half the answer;
>>>AZCompactList.pm is used at runtime to create this classification as per
>>>your collect.cfg file. If you open AZCompactList.pm in a text editor and
>>>search for 'sort' you should be able to find the bit of code that tells
>>>that specifies it to sort by date (AZCOmpactList.pm doesn't do the sorting
>>>- it uses another routine to do that - it just sets a flag so the leaves
>>>get sorted- by date is the default)
>>>
>>>As for the results of a search - I don't know - but I'd love to find out. I
>>>can only guess the sort order is what we get is from mg/mgpp.
>>>
>>>--
>>>Subject: [greenstone-devel] Dear All,
>>>
>>>One of my colleague just found that the sort order of search result list
>>>and that of the browse list are reverse. For example, when I searched a
>>>person's name: "Ahmed, Junaid", I got the following result:
>>>
>>> May_7_1993
>>> April_30_1993
>>> April_16_1993
>>> March_12_1993
>>> February_26_1993
>>>
>>>When I browsed the "people A-Z" classifier, which is a AZCompactList, I got
>>>this list under "Ahmed, Junaid":
>>>
>>> February_26_1993
>>> March_12_1993
>>> April_16_1993
>>> April_30_1993
>>> May_7_1993
>>>
>>>Does anyone know the mechanism of the two sorting methods? Is it possible
>>>to make the two indentical?
>>>
>>>Thanks a bunch!
>>>
>>>