incorrect tag for option indexValue.yearOnly

[winxi]

(14-04-2013 08:48)simoncn Wrote:  At the moment, this option is limited to the Date tag only. This is because Date is handled specially in various ways (validation and formatting as well as indexing).

To allow indexValue.yearOnly to be applied to other tags, I'd need to do one of the following:

1) Apply all the special processing for Date to any other tags that have the indexValue.yearOnly option

2) Apply the indexValue.yearOnly rule to these other tags, but don't apply any other special processing

I'll think about which of these approaches would work best. Do you have a strong preference between them?

No, I don't have a strong preference between these two approaches, as with both I could easily achieve the desired display. With option 2) I think I would just have to reverse the list sort order for the OriginalDate index tag.
As for option 2), I think it might lead to confusion if there is applied special processing also to other tags than date. My view is that the most generic way would be that even Date is treated as every other tag. There could be an additional tag option 'treatAsDate' which applies all the special processing. By default, MinimServer could set tagOption to Date.treatAsDate, and indexTag to -Date to reverse the sort order. However, this may lead to extra complexity.

As an additional suggestion, it would be worth considering that the indexValue.yearOnly option should also apply when using $date in a format item in the tagFormat property. Taking the example from the user guide and presuming a DATE tag value 1970-05-08,
Title.displayFormat={$title^$date^ [^]}
now results in
Let It Be [1970-05-08]
even when Date.indexValue.yearOnly is set in tagOptions.