Exact date search broken?

MicahE

It looks like the exact date search is broken in both providence and pawtucket2, but before filing an issue, I'd like to confirm that I'm doing it correctly.

The Search Syntax docs say:

You can restrict matching to items with dates that are completely encompassed by your search date by prepending a “#” to your search data. Eg. “#May 10 2005”

However, I get 0 results whenever I try this approach. I tested this out on a fresh CollectiveAccess installation just to be sure and took this approach:

Created an object with a date of 2020-2025
Created another object with a date of 2021
Used pawtucket advanced search to search the date field for "2021" and got both objects as expected
Changed date field to "#2021" and got no records

I also tried using the simple search field in both pawtucket2 and providence:

I get both records as expected with: ca_objects.date.dates_value:2021
I get 0 records with: ca_objects.date.dates_value:#2021

I don't see anything in search.conf about this. Is there something else I'm missing?

monica

MicahE I have never tried searching on dates like that, but can confirm it returns nothing for me too.

seth

The docs are wrong. It changed some months ago to a set of operators allowing for different operations. The operations are:

#eq# (exact)
#gt= (greater than or equal to)
#gt# (greater than)
#lt= (less than or equal to)
#lt# (less than)

Please try ca_objects.date.dates_value:#eq#2021 and see if that works as you expect.

MicahE

Thanks for this info @seth -- that worked as expected.