This might be a very niche feature, but currently in the UI, when a query string is built for a filter that allows a min and max value, the query for this range is inclusive of the min and max (i.e. the result is greater than or equal to the min, and less than or equal to the max). This is a default that's hardcoded into how MetacatUI constructs the query by using the square brackets, for example:
pubDate:[1999-01-01T00:00:00Z TO 2020-12-31T23:59:59Z]
Users may want to build a query that excludes the min and max (i.e. the result is greater than the min, and less than the max), like so:
pubDate:{1999-01-01T00:00:00Z TO 2020-12-31T23:59:59Z}
We could add an <inclusive> boolean element to numeric and date filters to define the behaviour of the filters more explicitly
This might be a very niche feature, but currently in the UI, when a query string is built for a filter that allows a min and max value, the query for this range is inclusive of the min and max (i.e. the result is greater than or equal to the min, and less than or equal to the max). This is a default that's hardcoded into how MetacatUI constructs the query by using the square brackets, for example:
pubDate:[1999-01-01T00:00:00Z TO 2020-12-31T23:59:59Z]
Users may want to build a query that excludes the min and max (i.e. the result is greater than the min, and less than the max), like so:
pubDate:{1999-01-01T00:00:00Z TO 2020-12-31T23:59:59Z}
We could add an
<inclusive>
boolean element to numeric and date filters to define the behaviour of the filters more explicitly