EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #00882
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: We are at our wits end,
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: We are at our wits end,
- From: Jose Martin <J.Martin@ulcc.ac.uk>
- Date: Thu, 26 Jul 2012 10:05:58 +0000
I think Seb’s suggestions should have you on the right track, but in case it helps, and being a search that does not behave itself when a word ending with an
‘s’ is involved, looks like stemming might have a say in this. As far as I know, the same stemming configuration is used for both searching and indexing, so re-indexing the record should have worked... But you can anyway have a look at “cfg.d/indexing.pl” and temporarily place the following lines near the end of the script, just before “return( \@g , \@b );” use Data::Dumper; print STDERR " *** Indexing: $text\n"; print STDERR " *** GOODs:\n"; print STDERR Dumper(\@g); print STDERR " *** BADs:\n"; print STDERR Dumper(\@b); That will (insistently) display in the log file the words that are being discarded and the ones that are finally used. Best, Jose. From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Phil Yes I have re indexed multiple times, my confusion comes from the fact that the index tables are correct, we are at 3.3.X
Does the debugger in sql output to a logfile? From:
eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of sf2 Hi Phil, For info, which EPrints version are you using? Worth a try: - have you tried to reindex the eprint dataset? (bin/epadmin reindex <archive_id> eprint) - have you tried debugging the search to see which SQL statement gets executed (**) ? Seb (**) to enable SQL debugging, edit perl_lib/EPrints/Search/Condition.pm, look at the end of "sub sql" for: #print STDERR "\nsql=$sql\n\n"; Un-comment the line above, restart apache and re-run the problematic search - feel free to copy/paste the SQL query here so we can have a look. On Wed, 25 Jul 2012 22:12:26 +1000, "Phil" <philpearson@iinet.net.au> wrote:
|
- Follow-Ups:
- [EP-tech] Re: We are at our wits end,
- From: Tim Brody <tdb2@ecs.soton.ac.uk>
- [EP-tech] Re: We are at our wits end,
- References:
- [EP-tech] We are at our wits end,
- From: "Phil" <philpearson@iinet.net.au>
- [EP-tech] Re: We are at our wits end,
- From: sf2 <sf2@ecs.soton.ac.uk>
- [EP-tech] Re: We are at our wits end,
- From: "Phil" <philpearson@iinet.net.au>
- [EP-tech] We are at our wits end,
- Prev by Date: [EP-tech] Re: next weeks EPrints workshops
- Next by Date: [EP-tech] Re: We are at our wits end,
- Previous by thread: [EP-tech] Re: We are at our wits end,
- Next by thread: [EP-tech] Re: We are at our wits end,
- Index(es):