The current way of supplying facet limits to Solr in BL will fail if the facet value being used as a limit has chars in it that need to be escaped. Erik Hatcher suggests a better way as below:

jrochkind: erikhatcher: ping?
[12:14pm] jrochkind: erikhatcher: if you see this. A couple times we've talked about changing the way BL supplies facet limits, using the {} syntax thing that I don't completely understand, to deal with escaping issues etc. If you file a JIRA ticket in the BL jira, assign it to me, and supply a couple lines of detials (like a sample of what it should look like), that would be very helpful!
[12:22pm] erikhatcher: jrochkind: you mean instead of doing fq=some_facet:"some crazy value"?
[12:22pm] jrochkind: i think so, yeah. I have trouble keeping track of the details, is why I could use a JIRA, heh.
[12:22pm] erikhatcher: yes, do this instead: fq={!raw f=some_facet}some crazy value
[12:22pm] jrochkind: yes, that's it!
[12:23pm] jrochkind: you can still have multiple fq's?
[12:23pm] erikhatcher: it's in my preconf slides, i posted those, right?
[12:23pm] erikhatcher: yeah, all that does is change how the query string is parsed
[12:23pm] jrochkind: Probably. If you don't have time, that's cool, but if you can make a JIRA in BL jira and assign it to me, it would be super helpful.
[12:23pm] jrochkind: I guess I can do it myself right now and just put the cut-and-paste of this IRC log in there, heh.
[12:23pm] jrochkind: okay, I'll do that.