When searching releases by specific Release Date, the search engine returns releases where exact release date is unknown. For example, searching by “2019-01-10” returns releases with release date “2019” or “2019-01”. Is there any way to exclude such records from search results? Because of this issue my application has to process much more records than necessary.
Thanks, ok got it but its definently counter intuitive. So if you enter 2019-01-10 and it will return 2019-01-10 and 2019-01 but not 2019-01-11.
I don’t know if it is designed on purpose to support partial dates but it should not, it makes no sense. Of course the other way round is okay, if you just enter 2019 it should indeed return any date that includes 2019.
It’s interesting that in the previous version of the search engine it worked as expected - it was returning only exact matches when searching by full date. The current behavior turned up after migrating to the new version of the search engine in July 2018. I agree with ijabz that current behavior is counter intuitive.
From practical point of view, when my application wants to retrieve all releases issued on specific date of 2018, it has to make 18-20 requests to retrieve 1800-2000 records (one request can’t return more than 100 records) where most of the records are irrelevant and useless. Previously it had to make only 2 or 3 requests.
This still seems to be the case?
I’d be interested in searching “releases today”, which would be date:02-07 and that just doesn’t work at all.
Reason: most “music released this day” et.al. websites just use straight up Rolling Stone and other magazine’s listings for classic albums and those lists are just incredibly narrow in scope (didn’t find Troublegum by Therapy? anywhere and the obviously everyone has their own personal favourites).
