target dynament - alpha sort order

37 views
Skip to first unread message

Karthikeyan Sivanantham

unread,
Jul 26, 2011, 9:19:44 AM7/26/11
to RedDot CMS Users, bose...@gmail.com, kpoovalurs...@inautix.co.in
A Doubt in target dynament.

Iam trying to sort using "author name" of article [alpha sort -
ascending] but iam not able to sort it.When iam trying to sort using
date stuff it is sorting fine [both asc/desc].

Whether we need to add any extra parameter for alpha sorting? is alpha
sorting is possible in target dynament?

I have placed my code below. please let me know if you find any issues

<dynaments>
<ROOT-BLOG>
<rde-dm:target tag="blog-pages" item-tag="blog-page"
sortedby="author" sortorder="asc" chunksize="6" attributepath="Topic"
include-mode="context-tags,notag;content-info,notag;" context-
tags="title;article-title;search-title;Abstract;author;author-
url;author-title;author-company;external-author;external-author-
title;external-author-company;published-date;" content-info="name;" >
<rde-dm:constraint>
((content.ContentType EQ "xxx") and (content.Capablity EQ
"[#request:Capablity#]"))
</rde-dm:constraint>
</rde-dm:target>
</ROOT-BLOG>
</dynaments>

Tim D

unread,
Jul 26, 2011, 11:24:12 AM7/26/11
to reddot-c...@googlegroups.com, bose...@gmail.com, kpoovalurs...@inautix.co.in
Karthik,

I'd highly recommend you be on v10 or up for Target DM usage. There have been improvements. Prior to v9 you needed to specify attributes you wanted to sort by in the Edit Project Settings dialogs. There were I believe 4-6 that you could sort by.

In v9 and up it is suggested to use Redundant DB structures to use one you'd need to specify the db-structure ="{db structure}".

Anything you want to sort or constrain by should be part of an index on those redundant DB structures.  If you can put your constraints into the redundant db structure itself so there are fewer items in the structures they will perform better. So if you had say 3 ContentTypes then creating 3 redundant DB structures and selecting them dynamically would be higher performing than your current query. There is of course a tipping point of too much effort to setup vs performance return.
Reply all
Reply to author
Forward
0 new messages