From: Tim M. <tmm8@Lehigh.EDU> - 2009-04-10 17:54:55
|
I'm back from a long hiatus, and just installed VuFind RC1 from SVN. I'm getting the error DB_DataObject Error: Unable to load schema for database and table (turn debugging up to 5 for full error message) on the root page. I have no records in yet, I just wanted to see that the installation worked fine before importing records. I'm happy to turn debugging up, but I can't find that configuration setting. Where is it? Thanks, Tim -- Tim McGeary Team Leader, Library Technology Lehigh University 610-758-4998 tim...@le... Google Talk: timmcgeary Yahoo IM: timmcgeary |
From: Tim M. <tmm8@Lehigh.EDU> - 2009-04-10 19:28:21
|
Actually, I found out from Andrew that because I had a database named something different than vufind, it caused this problem. I had to rename vufind.ini to the name of my database. But you're right that there are more than one debug line and I wasn't quite sure which one to play with. Tim Tim McGeary Team Leader, Library Technology Lehigh University 610-758-4998 tim...@le... Google Talk: timmcgeary Yahoo IM: timmcgeary Roy Zimmer wrote: > Tim: > > Looks like you need to access /home/vufind/local/vufind/web/conf/config.ini > There's more than one debug line in there. > I haven't mucked with this, so if this isn't right, don't hold it against me > > Roy > > Roy Zimmer----->Waldo Library----->Library Stuff & Information Herding-----> > Western Michigan University----->Kalamazoo, Michigan USA > localsystem=P3 ICBM=(útal:GPS error 51) RF=KB8UBA AF="Hey you!" QRM! > roy dot zimmer at wmich dot edu-----Wherever you go, there you are! > > > >>> Tim McGeary <tmm8@Lehigh.EDU> 4/10/2009 1:36 PM >>> > I'm back from a long hiatus, and just installed VuFind RC1 from SVN. > I'm getting the error > > DB_DataObject Error: Unable to load schema for database and table > (turn debugging up to 5 for full error message) > > on the root page. I have no records in yet, I just wanted to see that > the installation worked fine before importing records. I'm happy to > turn debugging up, but I can't find that configuration setting. Where > is it? > > Thanks, > Tim > > -- > Tim McGeary > Team Leader, Library Technology > Lehigh University > 610-758-4998 > tim...@le... > Google Talk: timmcgeary > Yahoo IM: timmcgeary > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Eric L. M. <em...@nd...> - 2009-04-13 16:59:59
|
How do I configure VuFind to do "and" versus "or" queries? I have changed the value of the defaultOperator attribute of the solrQueryParser element in my various schema.xml files to AND, but queries still seem to be defaulting to "or". Does the PHP code explicitly create "or" queries? -- Eric Lease Morgan University of Notre Dame |
From: Andrew N. <as...@gm...> - 2009-04-13 17:04:04
|
Eric - Yes, VuFind does explicity create AND and OR queries. This is something that will most likely change in an upcoming release of vufind. Im currently working on migrating all of the VuFind query parsing code to use the DisMax query handler in Solr. This will allow for queries to work better as well as be easier to customize. For now, the code is in web/sys/Solr.php Andrew On Mon, Apr 13, 2009 at 12:59 PM, Eric Lease Morgan <em...@nd...> wrote: > > How do I configure VuFind to do "and" versus "or" queries? > > I have changed the value of the defaultOperator attribute of the > solrQueryParser element in my various schema.xml files to AND, but > queries still seem to be defaulting to "or". Does the PHP code > explicitly create "or" queries? > > -- > Eric Lease Morgan > University of Notre Dame > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |
From: Eric L. M. <em...@nd...> - 2009-04-13 17:20:18
|
On Apr 13, 2009, at 1:03 PM, Andrew Nagy wrote: > Eric - Yes, VuFind does explicity create AND and OR queries. This > is something that will most likely change in an upcoming release of > vufind. Im currently working on migrating all of the VuFind query > parsing code to use the DisMax query handler in Solr. This will > allow for queries to work better as well as be easier to customize. > > For now, the code is in web/sys/Solr.php Thank you for the prompt reply. I have tweaked line #388 of web/sys/ Solr.php. Specifically, I changed $orQuery to $andQuery, thus: 'allfields:(' . $andQuery . ')'; // Catch All This tweak, in combination of the editing of the sysconfig.xml file, is good enough for me, right now. Thank you. open_source_software++ Personally I have found the following query munging to be helpful. Suppose a person enters a multiple-word query, such as dorothy day. In applications I have written, I have trapped this query before sending along to the indexer and converted into the following Boolean query: ("dorothy day") OR (dorothy AND day) I figure this is more explicit, and I hope phrase searches rank higher than not. If the person entered the query including syntactical sugar such as Boolean operator or a field designation, then I don't munge the query but pass it along figuring they know what they are doing. FWIW. -- Eric Morgan (574) 631-8604 |
From: Andrew N. <as...@gm...> - 2009-04-13 17:25:38
|
> > Personally I have found the following query munging to be helpful. > Suppose a person enters a multiple-word query, such as dorothy day. In > applications I have written, I have trapped this query before sending > along to the indexer and converted into the following Boolean query: > > ("dorothy day") OR (dorothy AND day) > > I figure this is more explicit, and I hope phrase searches rank higher > than not. If the person entered the query including syntactical sugar > such as Boolean operator or a field designation, then I don't munge > the query but pass it along figuring they know what they are doing. > I fully agree - and this is why I'm working on the migration to the Dismax handler as it handles this logic for us automatically. Andrew |
From: Till K. <kin...@gb...> - 2009-04-29 12:23:52
|
I just read this discussion today (just going through my mailinglist backlogs...), so sorry for picking that up again that late: Andrew Nagy wrote: > Eric - Yes, VuFind does explicity create AND and OR queries. That's one of the features we love in VuFind. For example, because you get hits like "Internet: Growth dynamics of the World-Wide Web" highly ranked (if you adjust weights) as result to a query for 'dynamic growth www': https://finden.nationallizenz.de/prototyp/Search/Home?lookfor=dynamic+growth+www&submit=Find (the index term www is nowhere in that index document!). I think big result sets are not a problem, if they are "usefully ranked" (whatever that is, we found someone who will evaluate ranking results on our data using customized VuFind, so maybe more on that in the future). One thing we changed, though, was to use OR queries only when the user's query contains 3 or more search terms. I had a short discussion with Stephen Elfstrand from PALS about these OR queries in VuFind last week at the ELAG09 conference in Bratislava, where he presented the VuFind deployment as a consortium catalogue (http://plus.mnpals.net/), because in his presentation he mentioned those as one thing they kicked out of their installation. In the end we came to the conclusion, it might be nice to have it as an configuration option whether these OR queries should be used or not. But it seems this discussion is obsolete anyway: > This is > something that will most likely change in an upcoming release of > vufind. Im currently working on migrating all of the VuFind query > parsing code to use the DisMax query handler in Solr. As I understand the DisMax handler (I haven't played much with it yet), it has an "enhanced ORing" strategy: "For the dismax handler, 1 and 2 word queries require that all of the optional clauses match, but for 3-5 word queries one missing word is allowed..." (http://wiki.apache.org/solr/DisMaxRequestHandler). First looks at search results using DisMax on our data look promising, although I haven't played much with weights or other parameters of the DisMax handler. Andrew, do you have an idea when mainstream VuFind will use DisMax? I haven't found anything of DisMax yet in the current svn checkout. Is it planned for the 1.0 release or a later version? I'm asking because we need some orientiation what to do with our customized version of Solr.php (optimize it further or switch to DisMax soon)... Can we help getting DisMax into VuFind? Regards, Till -- Till Kinstler Verbundzentrale des Gemeinsamen Bibliotheksverbundes (VZG) Platz der Göttinger Sieben 1, D 37073 Göttingen kin...@gb..., +49 (0) 551 39-13431, http://www.gbv.de |
From: Andrew N. <as...@gm...> - 2009-04-29 13:57:40
|
On Wed, Apr 29, 2009 at 8:23 AM, Till Kinstler <kin...@gb...> wrote: > Andrew, do you have an idea when mainstream VuFind will use DisMax? I > haven't found anything of DisMax yet in the current svn checkout. Is it > planned for the 1.0 release or a later version? I'm asking because we > need some orientiation what to do with our customized version of > Solr.php (optimize it further or switch to DisMax soon)... Can we help > getting DisMax into VuFind? > I'd love some help :) I do have some of the code changed - let me review it to see if it is ready to check in. I did want to have this done before the 1.0 launch since I think it will be more stable this way. Andrew |
From: Till K. <kin...@gb...> - 2009-05-06 11:52:33
|
Andrew Nagy schrieb: > I'd love some help :) OK, how can I help? What we will do anyway is fine tuning of DisMax parameters to fit our index schema and content. So testing and tuning parameters come to my mind... Does it make sense to have DisMax parameters (query fields, weights/boosts, "pf", adding boost functions, ... whatever, DisMax offers a lot) somehow configurable through a configuration file? Is anyone else interested in changing/tuning those values? Of course one can always twiddle those parameters in the PHP source, but one result of my discussion with Stephen Elfstrand was, that configurable query options might be useful... Any opinions? Till -- Till Kinstler Verbundzentrale des Gemeinsamen Bibliotheksverbundes (VZG) Platz der Göttinger Sieben 1, D 37073 Göttingen kin...@gb..., +49 (0) 551 39-13431, http://www.gbv.de |