Consistent ordering between tag and folder services

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Tag pages in a folder
2. Retrieve pages via tag
3. Retrieve pages via folder

What is the expected output? What do you see instead?

Expected system to render both sets, with the most recently created first. 

System rendered sets with different ordering. 

See <http://staging.vosao.org/test/tag-index>.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ted.husted on 11 Jul 2010 at 4:19

[GoogleCodeExporter]

As a note, I'm working on a portal site, and I would like to provide a short 
list of the most recent items posted to a given tag. The portal will cover 
multiple topics, with there being a standard set of content types within each 
topic (news, articles, reviews, blogs, ...). 

In some cases, I would want to pull everything for topic, and in other cases, 
everything for a content type. My thought was to organize the folders by 
topic/content-type and then tag the content-types. 

The page methods, like findPageByChildren, seem to be sorting by publish date, 
and the tag methods seem to be unsorted. 

For the tags to be used as feeds of the latest updates, we should be able to 
pull pages by tags, most recently published first. 

-Ted.

Original comment by ted.husted on 11 Jul 2010 at 11:52

• Changed state: New

[GoogleCodeExporter]

This may be a separate issue, but should 

 $service.tag.getPagesByPath

return children of the given path 

Right now, if there is a tag tree like 

/feed
/feed/news
/feed/article
/feed/review

and one or more pages have been tagged for news, article, and review (but not 
feed) 

$service.tag.getPagesByPath("/feed") 

returns an empty set. 

Is this behavior by design? 

Should we also tag by "feed" to pull everything under "/feed", or does the 
hierarchy imply "feed"?

Original comment by ted.husted on 11 Jul 2010 at 12:31

[GoogleCodeExporter]

Current implementation doesn't work with hierarchy in page selection. But will 
do.

Original comment by kinyelo@gmail.com on 11 Jul 2010 at 3:53

• Changed state: Accepted
• Added labels: Milestone-Release-0.7

[GoogleCodeExporter]

> Current implementation doesn't work with hierarchy in page selection. But 
will do.

Thanks. Being able to pull everything in a tag tree would be useful. 

I'm also seeing a need for pulling a set of tags. A common usage is to tag an 
item for a subject-area (like "content management") and a content-type (like 
"news"), and then pull "content management" AND "news", or just "news" and get 
news items for all the subject-areas. For an AND, we'd also want to be sure the 
set of pages is distinct. Could the path be a comma-delimited list? 

I thought about also use the page tree to help with some retrievals, but I'm 
finding that it complicates the hierarchy, and we would also want to optimize 
the page tree for security. 

Original comment by ted.husted on 11 Jul 2010 at 5:07

[GoogleCodeExporter]

Implemented:
1. Page ordering by PublishDate.
2. $service.tag.getPageByPath(String tagPaths) traverses all children tags.
3. $service.tag.getPagessByPath(String tagPaths) can do logical AND operations 
for comma delimited tag paths list.

Original comment by kinyelo@gmail.com on 17 Jul 2010 at 4:33

• Changed state: Fixed