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

From Stefan Boddie
DateFri, 26 Sep 2003 16:12:21 +1200
Subject Re: [greenstone-devel] re Sort order of search result list and browse list
In-Reply-To (3F737CC7-F49C7E6C-cs-waikato-ac-nz)
What Michael says about the ordering of search results is true. That is, a
ranked (or "some") query will rank the results while a boolean (or "all")
query will display them (in theory) in build order.

One problem is that there seems to be a bug causing a boolean query to
return hits in REVERSE build order. The bug appears to be in the
sort_doc_results() function of gsdl/src/colservr/mgqueryfilter.cpp. If you
have the source code and comment out the call to sort_doc_results() at
around line 344 of mgqueryfilter.cpp you'll find that the results of a
boolean search will be displayed in correct build order. This is true of
collections built using MG, not sure about MGPP.

Anyway, I don't know this particular part of the code very well and don't
have time to look closely at it. Someone should probably try to work out
what sort_doc_results() is meant to do sometime, remove it if it's doing
nothing useful or fix it if it is.

Stefan.

----- Original Message -----
From: "Michael Dewsnip" <mdewsnip@cs.waikato.ac.nz>
To: <Stephen.DeGabrielle@cdu.edu.au>
Cc: <greenstone-devel@list.scms.waikato.ac.nz>
Sent: Friday, September 26, 2003 11:39 AM
Subject: Re: [greenstone-devel] re Sort order of search result list and
browse list


> 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!
> >
> > _______________________________________________
> > greenstone-devel mailing list
> > greenstone-devel@list.scms.waikato.ac.nz
> > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel
>
>
> _______________________________________________
> greenstone-devel mailing list
> greenstone-devel@list.scms.waikato.ac.nz
> https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel
>