Cross-referencing pages Options
sbparsons
Posted: Monday, December 10, 2007 3:58:11 PM
Rank: Newbie

Joined: 12/5/2007
Posts: 6
Hi all,

I'm new to Umbraco and have been attempting to get to grips with the concepts without a set of focussed documentation. I have managed to get to the stage where I am happy enough with the basics but now require a slightly more complicated structure. Hopefully someone here can advise:

I am developing a site that will offer information on health products. The page will be divided into 3 parts:
Left = product list (hyperlinks)
Right = ailments (hyperlinks)
Centre = information about either product or ailment.

I have created the products and ailments document types and templates.

What I now require is to cross reference products with ailments (and vice versa) so that when a visitor clicks a product in the left, a list of related ailments that the product may help with appear in the right.
Alternatively if a user clicks an ailment in the right, a list of products that may help with that ailment may appear in the left.

How would this linking of product to ailment typically be performed by a content manager and how would I set up Umbraco to offer this? Would I have to go the usercontrol route?

Apologies for the long post but I hope that my query is clear.

Thanks,
Sean
neehouse
Posted: Monday, December 17, 2007 1:49:52 AM

Rank: Umbracoholic

Joined: 7/20/2006
Posts: 1,074
Location: Charleston, West Virginia, United States
Hi Sean,

You can go about cross-referencing in a multitude of ways. Here are the two thoughts I have right off.

Usage of a multiple content picker (i believe there are a couple floating around) on each document type to associate links each way.

Use a separate document type to cross-reference the node with a content picker for each, the product and the ailment. This would be the easiest to set up, but a bit tedious to implement, but could be used to associate in xslt easily.

Case

• 2007/2008 MVP • 2008/2009 MVP • Certified • Licensing • Support • Development • Hosting •
neehouse
Posted: Monday, December 17, 2007 1:59:55 AM

Rank: Umbracoholic

Joined: 7/20/2006
Posts: 1,074
Location: Charleston, West Virginia, United States
Sean,

Another though, and this is a simplistic option.

Due to the structure of xml, and the hierarchical structure, you could have a simple document type (reference) that is a single content picker (referenced node). By creating the reference doc type below the ailment or product. You could then just run the child nodes.

You would not have to do both, as the reference could be achieved from one set, using reverse logic. IE, a macro to list the child nodes pulling the related (ailment) content, and a macro to find the parent nodes (products) where the child nodes (relation pointing to the ailment) match the current node (ailment)

I think I made that sound confusing, but, you have a few options to consider.


• 2007/2008 MVP • 2008/2009 MVP • Certified • Licensing • Support • Development • Hosting •
sbparsons
Posted: Saturday, December 22, 2007 11:30:56 PM
Rank: Newbie

Joined: 12/5/2007
Posts: 6
Thanks again, Casey

I have landed up by using a multi-content picker for the products to identify which ailments they work on. I am keeping it simple as I'm still learning :)

I am then using xslt to list the ailments if a product is selected, and your suggestion of reverse logic to select the products that relate to a selected ailment based on its id.

Sorry for the late reply - this is an after-hours project :p
Users browsing this topic
Guest


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.