|
incorrect tag for option indexValue.yearOnly
|
|
14-04-2013, 15:59
Post: #6
|
|||
|
|||
RE: incorrect tag for option indexValue.yearOnly
(14-04-2013 15:40)winxi Wrote: Yes, I want to merge these and I already use ReleaseDate:Date in aliasTags. This gives me the desired result and it works just great. My only concern is that I want to show also for the OriginalDate indexTag just YYYY instead of YYYY-MM-DD. I would be very happy with either your proposed approaches. I'm sorry for confusing releaseDate and originalDate in my previous post. I meant to ask if you want to have separate indexes for OriginalDate and Date. From this reply, I presume you do want separate indexes and you don't want to send the OriginalDate value to the control point. In this case, I think the simplest solution is for MinimServer to allow indexValue.yearOnly to be applied to any tag in indexTags, without overloading this with any other semantics. Quote:I think I still didn't get the point in the difference between a displayValue and an indexValue option and also in the difference between displayFormat and indexFormat in the tagFormat property. I might have missed this in the user guide. Could you please point me in the right direction concerning these differences? Thanks! The indexValue and indexFormat options control what appears in the MinimServer index, and they don't affect what XML data is sent to the control point. The displayFormat, displayRoles and display options control what XML data is sent to the control point, and they don't affect what appears in the MinimServer index. The sortValue and sortTags options control the sort order that MinimServer uses for index lists and lists sent to the control point. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



