Hi,
I suggest having a "season" field (or whatever you might want to call it)
using DateRangeField but simply use a nominal year value. So basically all
durations would be within this nominal year. For some docs that span
new-years, this might mean 2 durations and that's okay. Also it's okay if
You can write an Update Request Processor which takes a pair of date field
value and creates a season code value for a separate field, which could be
multivalued for date ranges spanning seasons. Similarly you could have
another generated multivalued field which listed the months when the data
was
