[EP-tech] Re: Relevance ranking for Simple and Advanced Search

Andy Reid Andy.Reid at lshtm.ac.uk
Wed Sep 16 13:34:23 BST 2015


Watch out for the spelling - I assume they should all be relevance with
two e's ?:

>> $c->{search}->{simple}->{order_methods}->{byrelavance} = ''; 
>> $c->{search}->{simple}->{default_order} = 'byrelevance'; 
>> $c->{search}->{advanced}->{order_methods}->{byrelavance} = ''; 
>> $c->{search}->{advanced}->{default_order} = 'byrelevance';
>> 
>>> "Field A.N." <af05v at ecs.soton.ac.uk> 16 September 2015 12:52 >>>
I've had a word around the bay on this one, and we think that turning
on Xapian search should make relevance ordering happen by default.  You
shouldn't need to do what's below.

--
Adam Field
Business Relationship Manager and Community Lead
EPrints Services
+44 (0)23 8059 8814





On 2 Sep 2015, at 17:36, Tomasz Neugebauer wrote:

> Hi Adam,
> 
> Thank you.  However, that leaves the question of what to do about the
documentation for simple and advanced search?
> http://wiki.eprints.org/w/Search.pl
> If you follow that documentation, then you will not be seeing
relevance ranking by default.  These additional necessary settings need
to appear somewhere on this page.
> 
> Also, what about eprints_search_staff.pl?  I needed to add the
relevance option to that file as well, as it was not showing up by
default.
> Lastly, about the example of adding the following metafield to the
staff search { meta_fields => [ "documents.embargo_indefinitely" ] }
> that field (documents.embargo_indefinitely) doesn't' exist by
default, right?  
> I ask because: 
> 1)it would be nice for the staff search to contain an option for
documents with a permanent embargo - so if this isn't a default field,
what is the best way of adding that search option?
> 2) if the embargo_indefinitely field is not there by default, the doc
should mention that as its giving it as an example.
> 
> Tomasz
> 
> 
> 
> 
> -----Original Message-----
> From: eprints-tech-bounces at ecs.soton.ac.uk
[mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Field A.N.
> Sent: September-02-15 5:22 AM
> To: eprints-tech at ecs.soton.ac.uk
> Subject: [EP-tech] Re: Relevance ranking for Simple and Advanced
Search
> 
> I'd be shocked if you could.  It's a good idea to make changes in new
cfg.d files rather than modify existing ones.
> 
> --
> Adam Field
> Business Relationship Manager and Community Lead EPrints Services
> +44 (0)23 8059 8814
> 
> 
> 
> 
> 
> On 2 Sep 2015, at 09:41, Ajunk Pracetio wrote:
> 
>> I can't found file with that name on cfg.d folder. Is it for new
version?
>> 
>> On Wed, Sep 2, 2015 at 3:06 PM, Field A.N. <af05v at ecs.soton.ac.uk>
wrote:
>> Sorry, it took me a while to figure out what was going on.
>> 
>> For maintainability, as always, it's a good idea to make changes in
new cfg.d files rather than modify existing ones.  When you upgrade,
this will make it far easier normalise your cfg directory to the new
defaults.  You can achieve this by putting the following in
cfg.d/z_relevance_order_default.pl:
>> 
>> $c->{search}->{simple}->{order_methods}->{byrelavance} = ''; 
>> $c->{search}->{simple}->{default_order} = 'byrelevance'; 
>> $c->{search}->{advanced}->{order_methods}->{byrelavance} = ''; 
>> $c->{search}->{advanced}->{default_order} = 'byrelevance';
>> 
>> 
>> --
>> Adam Field
>> Business Relationship Manager and Community Lead EPrints Services
>> +44 (0)23 8059 8814
>> 
>> 
>> 
>> 
>> 
>> On 2 Sep 2015, at 04:48, Ajunk Pracetio wrote:
>> 
>>> Hi,
>>> Thank Brian...now my simple & advanced result set relevance as
default.
>>> 
>>> On Wed, Sep 2, 2015 at 12:18 AM, Tomasz Neugebauer
<Tomasz.Neugebauer at concordia.ca> wrote:
>>> I'm also using 3.3.12, and confirm the following:
>>> 
>>> 1) Relevance sort was not the default sort option on simple search,
but it did show up as an option in the dropdown.  Users had to manually
switch to relevance sort.  So my setting for eprints_search_simple.pl
doesn't have this:
>>> "byrelevance"    => "",
>>> But I did need to add the following:
>>> default_order => "byrelevance",
>>> 2) Relevance sort was not even listed as an option on advanced
search, until I changed the setting to Brian's suggestion.  Now it
appears, and the default is set to relevance.
>>> 
>>> Tomasz
>>> 
>>> 
>>> -----Original Message-----
>>> From: eprints-tech-bounces at ecs.soton.ac.uk 
>>> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Brian D.

>>> Gregg
>>> Sent: September-01-15 12:19 PM
>>> To: eprints-tech at ecs.soton.ac.uk
>>> Subject: [EP-tech] Re: Relevance ranking for Simple and Advanced 
>>> Search
>>> 
>>> Adam,
>>> 
>>> Agreed, If Xapian is working then you should at least get an option
to order by relevance, but I was not and it also was not set as the
default sort either for simple or advanced search.  If there is
something in the code that was supposed to do this then it is not doing
it at least in the version I'm using 3.3.12.  This is what caused me to
come up with the config changes that I posted.  Obviously Tomasz had a
similar issue.
>>> 
>>> So what I would assume (in a perfect scenario) should happen is
that if the Xapian search engine is found to be installed, it should:
>>>   a.) Add an order by relevance to both the simple and advanced
search.
>>>   b.) Set the order by relevance as default for both the simple and
advanced search as this is what users expect to find.
>>> 
>>> -Brian.
>>> 
>>> -----Original Message-----
>>> From: eprints-tech-bounces at ecs.soton.ac.uk
[mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Field A.N.
>>> Sent: Tuesday, September 01, 2015 11:49 AM
>>> To: eprints-tech at ecs.soton.ac.uk
>>> Subject: [EP-tech] Re: Relevance ranking for Simple and Advanced 
>>> Search
>>> 
>>> I'm not sure this will work.  In any case, if Xapian is working,
you should get an option to order by relevance.  If Xapian isn't
working, it can't possibly do you any good.
>>> 
>>> --
>>> Adam Field
>>> Business Relationship Manager and Community Lead EPrints Services
>>> +44 (0)23 8059 8814
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 1 Sep 2015, at 16:29, Tomasz Neugebauer wrote:
>>> 
>>>> Dear Brian,
>>>> 
>>>> Thank you for this information!  I was having trouble getting the
advanced search to use relevance sort, and your post solved it for me.
>>>> I think that relevance sort is what users expect as a default
sort.
>>>> Should we update the simple and advanced search config examples
here: http://wiki.eprints.org/w/Search.pl to use relevance sort by
default?
>>>> 
>>>> Tomasz
>>>> 
>>>> 
>>>> ________________________________________________
>>>> Tomasz Neugebauer
>>>> Digital Projects & Systems Development Librarian Libraries / 
>>>> Bibliothèques Concordia University / Université Concordia
>>>> 
>>>> 
>>>> 
>>>> From: eprints-tech-bounces at ecs.soton.ac.uk
>>>> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Brian
D.
>>>> Gregg
>>>> Sent: August-27-15 12:21 PM
>>>> To: 'eprints-tech at ecs.soton.ac.uk' <eprints-tech at ecs.soton.ac.uk>
>>>> Subject: [EP-tech] Relevance ranking for Simple and Advanced 
>>>> Search
>>>> 
>>>> All,
>>>> 
>>>> Just passing this along in case anyone has been looking at
searching (simple and advanced) and wondering about how to make
relevance ranking results the default for at least the 3.3.12 (version
we are running) of Eprints.  As usual. your millage may vary.
>>>> 
>>>> In our Eprints 3.3.12 instance we changed the following files and
ran 'epadmin reload {archive}' to make the changes stick.
>>>> 
>>>> cfg/cfg.d/eprints_search_simple.pl:
>>>> 
>>>>	    preamble_phrase => "cgi/search:preamble",
>>>>	    title_phrase => "cgi/search:simple_search",
>>>>	    citation => "result",
>>>>	    page_size => 20,
>>>>	    order_methods => {
>>>>			    "byrelevance"    => "",
>>>>			    "byyear" 	    =>
"-date/creators_name/title",
>>>>			    "byyearoldest"   =>
"date/creators_name/title",
>>>>			    "byname" 	    =>
"creators_name/-date/title",
>>>>			    "bytitle" 	   =>
"title/creators_name/-date"
>>>>	    },
>>>>	    #default_order => "byyear",
>>>>	    default_order => "byrelevance",
>>>>	    show_zero_results => 1,
>>>> 
>>>> cfg/cfg.d/eprints_search_advanced.pl:
>>>> 
>>>>	    preamble_phrase => "cgi/advsearch:preamble",
>>>>	    title_phrase => "cgi/advsearch:adv_search",
>>>>	    citation => "result",
>>>>	    page_size => 20,
>>>>	    order_methods => {
>>>>			    "byrelevance"    => "",
>>>>			    "byyear" 	    =>
"-date/creators_name/title",
>>>>			    "byyearoldest"   =>
"date/creators_name/title",
>>>>			    "byname" 	    =>
"creators_name/-date/title",
>>>>			    "bytitle" 	   =>
"title/creators_name/-date",
>>>>			    "byid" 		  => "eprintid",
>>>>	    },
>>>>	    #default_order => "byyear",
>>>>	    default_order => "byrelevance",
>>>>	    show_zero_results => 1,
>>>> 
>>>> By adding the "byrelevance" line to the order_methods and setting
the default_order to "byrelevance" we now have relevance ranking search
results for both our simple and advanced searches by default.
>>>> 
>>>> Hope this helps,
>>>> Thanks,
>>>> Brian.
>>>> 
>>>> Brian D. Gregg
>>>> Solutions Architect | Manager Systems Development University of 
>>>> Pittsburgh | University Library System
>>>> Address: 7500 Thomas Blvd.  Room 129 Pittsburgh, PA 15208
>>>> Tel: (412) 648-3264 | Email: bdgregg at pitt.edu | Fax: (412) 
>>>> 648-3585
>>>> 
>>>> *** Options:
>>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>>> *** Archive: http://www.eprints.org/tech.php/
>>>> *** EPrints community wiki: http://wiki.eprints.org/
>>>> *** EPrints developers Forum: http://forum.eprints.org/
>>> 
>>> 
>>> *** Options: 
>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>> *** Archive: http://www.eprints.org/tech.php/
>>> *** EPrints community wiki: http://wiki.eprints.org/
>>> *** EPrints developers Forum: http://forum.eprints.org/
>>> 
>>> *** Options: 
>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>> *** Archive: http://www.eprints.org/tech.php/
>>> *** EPrints community wiki: http://wiki.eprints.org/
>>> *** EPrints developers Forum: http://forum.eprints.org/
>>> 
>>> *** Options: 
>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>> *** Archive: http://www.eprints.org/tech.php/
>>> *** EPrints community wiki: http://wiki.eprints.org/
>>> *** EPrints developers Forum: http://forum.eprints.org/
>>> 
>>> 
>>> 
>>> --
>>> Life isn't valuable if you don't have someone to care
>>> *** Options: 
>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>> *** Archive: http://www.eprints.org/tech.php/
>>> *** EPrints community wiki: http://wiki.eprints.org/
>>> *** EPrints developers Forum: http://forum.eprints.org/
>> 
>> 
>> *** Options: 
>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>> *** Archive: http://www.eprints.org/tech.php/
>> *** EPrints community wiki: http://wiki.eprints.org/
>> *** EPrints developers Forum: http://forum.eprints.org/
>> 
>> 
>> 
>> --
>> Life isn't valuable if you don't have someone to care
>> *** Options: 
>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>> *** Archive: http://www.eprints.org/tech.php/
>> *** EPrints community wiki: http://wiki.eprints.org/
>> *** EPrints developers Forum: http://forum.eprints.org/
> 
> 
> *** Options:
http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/
> 
> *** Options:
http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/


*** Options:
http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20150916/6ef25c25/attachment-0001.html 


More information about the Eprints-tech mailing list