Open flooie opened 3 weeks ago
OK, yeah, a couple things weird about that, eh?
It shouldn't eliminate the citation from the query and return "" when the only thing there is the citation.
But did it do that? Somehow it still returned results.
Looking it up by citation works:
But like this does not:
But, lo, this works (with the space moved):
I think the whitespace is the heart of the issue here, but we can put this on Alberto's backlog to dig in.
Got another instance of this today where whitespace doesn't seem to be the issue:
https://www.courtlistener.com/?q=101%20So.%20844&type=o&order_by=score%20desc&stat_Published=on
But 101 So. 844
does exist:
https://www.courtlistener.com/opinion/3239863/u-s-salvage-sales-co-v-weber/
As we're fixing this, Rebecca dropped this meme into our Slack:
So maybe if it makes sense, we should also make pure citation searches just take people where they want to go when we do this (if it doesn't add too much complexity or time).
https://www.courtlistener.com/opinion/595912/go/#fn-s_ref
When querying for the preceding case in Elastic using the citation, I receive the following message:
However, filtering by a portion of the case name confirms that both the case and citation are indeed present in the system, as shown below:
https://www.courtlistener.com/?q=980%20F.2d%20737&type=o&order_by=score%20desc&case_name=Ann%20Franco%20v.%20National%20Van%20Lines&stat_Published=on&stat_Unpublished=on
It appears there may be an issue with citation-based retrieval in Elastic.