Filtering content based on year in a front-end yearly archive.

I have content that have a duration (example: 2022–02–03 to 2023–01–05), how can I filter these on year? Imagine a front-end having a yearly archive, so the example should not show up if you're on

2024

but if you're on

2022

or

2023

it should.

You could use the

string::split()

function to split on

-

and get the first index:

Potential downside is that the year param probably needs to be handled as a string.

You can also replace the

string::split()

predicate with:

This would filter the year 2023.

thanks for your reply geoff! I'm curious, since it's a duration rather than just a simple date:
isn't it a bit more complicated?
🤔

That may be different from the question I thought I was answering, which was about filtering by year, yearly archives, etc. I may have misunderstood you.

I think you could still use the comparison operators, but the

>=

would be against

duration.start

and

<

would be against

duration.end

. Does that accomplish what you’re after?

chat gpt helped me out 🙂

GROQ string comparisons are using lexicographic ordering rules, just as in JavaScript.
That means that timestamps in the standard RFC 3339 and ISO 8601 formats, such as:

are lexicographically ordered, if they're in the same time zone.

In other words,

laterDateTime > newerDateTime

is always true. The same goes for

>=

,

<

,

<=

.
This is because lexicographic ordering ensures

2

>

1

and so on. Since such timestamps are written with the most significant part (year) first, and each part is always equally long, they are comparable:
This also means you can omit any trailing part when using

<=

and

>=

. For example,

"2023-03-02T00:00:00Z" >= "2023"

will be true, and also true for any date past the year 2023.
It seems hacky, but it actually isn't when you think about it. And it's fast. The

string::split()

trick also works, but is not optimized to an efficient filter operation.