See the Mailing Lists Page for how to subscribe and unsubscribe.
eprints_tech messages
Please note: this page shows emails that have been sent to the eprints_tech mailing list. Some of these may be spam emails we have failed to filter.
[EP-tech] Re: Limitations of search API?
From: Stephen Shorrock <sms67 AT cam.ac.uk>
Date: Mon, 10 Nov 2008 13:38:24 +0000
| Threading: | ↑ [EP-tech] Limitations of search API? from sms67 AT cam.ac.uk • This Message |
http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** EPrints community wiki - http://wiki.eprints.org/ Thanks for the reply Tim, Thanks for the explanation re use of index tables. I managed to solve B by creating a new MetaField and doing a few overrides. S > http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech > *** EPrints community wiki - http://wiki.eprints.org/ > On Fri, 2008-11-07 at 14:28 +0000, Stephen Shorrock wrote: > >> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >> *** EPrints community wiki - http://wiki.eprints.org/ >> For clarity, >> >>> I'd like to be able to do a couple of things: >>> >>> A, Include non-word characters in my search queries (eg underscore ↵ _ >>> asterix *) >>> >>> >> This seems to work with "EX" and "EQ" but not with ↵ "IN" as the match. >> > > EX is "exact" which performs a SQL equals against the raw value. > > IN compares against the values in the index tables, which are ↵ "terms" > derived from the raw value. > > I'm afraid the ability to determine what's indexed is quite restricted. > In cfg.d/indexing.pl is an "extract_words" which is applied to ↵ all text > fields (and derived types). > > At the moment there's no way to perform per-field term extraction. > > All the best, > Tim. > >
[index] [prev] [next] [options] [help]