incorrect tag for option indexValue.yearOnly

[simoncn]

(14-04-2013 14:35)winxi Wrote:  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.

Do you have an index for ReleaseDate and a separate index for Date? If you are happy to merge these indexes, the simplest solution is to use aliasTags to rename ReleaseDate tags to Date.

If you do want these indexed separately, which of them are you expecting to be sent to the control point in the <dc:date> XML tag?

Quote: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.

I agree that this would cause extra complexity. I'd prefer to find a simpler solution to your requirement.

Quote: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.

This would be a displayValue option, not an indexValue option.