The problem is that Solr thinks you're doing a fielded search because of the colon. The easiest workaround is to put the query in double quotes.
(A more complex solution, which might be worth considering, would be to give VuFind the ability to distinguish valid vs. invalid Solr fields and process the query accordingly... but that could get complicated, especially now that we've added dynamic fields; this might actually be something that Extended DisMax can take care of, though I still haven't had time to experiment with that yet).
From: Michelle Suranofsky [email@example.com]
Sent: Friday, January 27, 2012 1:17 PM
Subject: [VuFind-Tech] Problem with searching for call numbers with a colon
Can anyone tell me if there is a known problem with searching for a call number that contains a colon? I'm running into the exception pasted below and I've tried a couple of public VuFind implementations like the vufind test site and the problem seems to exist there as well....(assuming it is the same problem because of the "There seems to be a problem with your search query." message)
Produces this error:
SEVERE: org.apache.solr.common.SolrException: undefined field 1.13
Any suggestions for fixing/working around are greatly appreciated!!!