I've got a request to categorise content that's extant in a site - some by date, some by custom categories, due to a large volume of content making the content difficult to navigate.
The site is relatively large and I'm concerned that changing the data structure is going to involve re-writing more databinding than I have time to do.
So I suppose my question is, how does the 'virtual' alphabet structure work in the members section? Is this replicable in the content tree? Does the autofolders/datefolders package(s) affect node traversal (I assume they do)?
In addition to this, we're only running IIS6 on the production server, so I can't use ASP.NET 4.0 packages.
My other concern is this - imagine I'm currently getting articles by date, I want to display the latest three, and I put them into named subcategory folders. To get the latest, I'm going to need to open all the folders, add all the nodes to a list, sort by date and pluck out the latest three - I know this could be approached in a better way using XSLT, but ultimately I'm struggling to find a pleasant way of doing this.
All I want is for the nodes to display differently in the content tree without changing the data itself!
Content tree structure works quite different from the member section, as there's relations involved between the nodes (parent/child relation)- whereas member nodes aren't related to each other, so replicating the 'virtual alpabet' is quite some work, and not recommended imho...
you could however build a custom section and present the nodes in a different way as opposed to the content section.... it'll require some work, but it could be done.
Don't quite understand your 2nd concern, using xslt you could traverse the content tree in many ways, probably including how you'd like it to traverse based on your requirements... so not sure what your problem is then?
Thank you for your reply! You have confirmed my suspicions about this task - I have had a look at the tree API and adding a new tree in this section would appear to be a good option.
My other concern relates to making changes to a large amount of the site - any solution that changes the data structure will mean rewriting the XSLT etc. that pulls out this data - the site works perfectly fine, and we're loath to make what amounts to siginificant data structure changes for the sake of a UI component.
I think treating this as a UI, not a data structure problem will be the answer here - do you know of any articles that would be a good starting point for creating a new tree? I am entering uncharted waters here...
Virtual folder structure (a la Members section)
Hi all,
I've got a request to categorise content that's extant in a site - some by date, some by custom categories, due to a large volume of content making the content difficult to navigate.
The site is relatively large and I'm concerned that changing the data structure is going to involve re-writing more databinding than I have time to do.
So I suppose my question is, how does the 'virtual' alphabet structure work in the members section? Is this replicable in the content tree? Does the autofolders/datefolders package(s) affect node traversal (I assume they do)?
In addition to this, we're only running IIS6 on the production server, so I can't use ASP.NET 4.0 packages.
My other concern is this - imagine I'm currently getting articles by date, I want to display the latest three, and I put them into named subcategory folders. To get the latest, I'm going to need to open all the folders, add all the nodes to a list, sort by date and pluck out the latest three - I know this could be approached in a better way using XSLT, but ultimately I'm struggling to find a pleasant way of doing this.
All I want is for the nodes to display differently in the content tree without changing the data itself!
Content tree structure works quite different from the member section, as there's relations involved between the nodes (parent/child relation)- whereas member nodes aren't related to each other, so replicating the 'virtual alpabet' is quite some work, and not recommended imho...
you could however build a custom section and present the nodes in a different way as opposed to the content section.... it'll require some work, but it could be done.
Don't quite understand your 2nd concern, using xslt you could traverse the content tree in many ways, probably including how you'd like it to traverse based on your requirements... so not sure what your problem is then?
Cheers,
/Dirk
Hi Dirk,
Thank you for your reply! You have confirmed my suspicions about this task - I have had a look at the tree API and adding a new tree in this section would appear to be a good option.
My other concern relates to making changes to a large amount of the site - any solution that changes the data structure will mean rewriting the XSLT etc. that pulls out this data - the site works perfectly fine, and we're loath to make what amounts to siginificant data structure changes for the sake of a UI component.
I think treating this as a UI, not a data structure problem will be the answer here - do you know of any articles that would be a good starting point for creating a new tree? I am entering uncharted waters here...
is working on a reply...