I will have content nodes for various football/soccer clubs
Man Utd
Arsenal
Real Madrid
I will also be creating products for tickets to games relating to these clubs
Man Utd vs Real Madrid - $90
Man Utd vs Arsenal - $80
Arsenal vs Real Madrid - $100
When I display a club page I want to be able to list the tickets that relate to the club.
So for the Man Utd. club page I would see
Man Utd vs Real Madrid - $90
Man Utd vs Arsenal - $80
I was thinking that in order to do this I would create a
multi-content picker data type and add that to the product definition of
my ticket product which would enable me to pick the clubs that the
ticket is related to.
At the moment you can't add custom data types to uCommerce (it's something I really want to get in there though). What I'd suggest instead is turn the relationship around and do a macro, which pull out products from a given category.
Basically add that category picker to each team page and have it list products from the category as part of the content. You just need a string so the ghetto version of this would be to add a short text and paste in the category name or you could do an actual picker if you've got the time to do the more user friendly solution.
I'll create categories for each club Man Utd, Arsenal, Real Madrid. Then for example I'll add the 'Man Utd vs Arsenal - $80' product to the Man Utd category but also add it to the Arsenal category as well by ticking that category on the 'Categories' tab when creating the product. I can see how that would work.
I do however have another requirement that is presenting questions about how best to architect it all.
I will have some site nodes to store information about the stadium venues where these football matches take place:
Old Trafford
Emirates
Santiago Bernabéu
I was planning to create a property in the Ticket product definition so that when I'm creating creating a football ticket product like 'Man Utd vs Arsenal - $80' I could assign the correct stadium venue, Old Trafford to it. This would enable me lookup and display details about that stadium when the shopper looked at the ticket product.
I am guessing that to do this I would have to create an Enum product definition property that mirrored the stadium venues nodes that had been created and just do a lookup based on name.
This is OK but it would mean maintaining two lists of venues.
I am wondering if there is any advantage to be gained by re-architecting it so that the stadium venues are products in uCommerce rather than normal content nodes and how that would work?
You could move the venues to uCommerce as either products or categories and use relations to show what's available. The advantage to doing this is that you can create other types of listings quite easily just by relating or associating products to other products or categories.
The advantage is maintainability and the ability to create some nice custom listings.
The disadvantage is less options for data types to add to the venues.
I'd probably go with categories myself as that will give you a ready made custom listing as part of the catalog structure.
I've been playing all day with creating my various content nodes as products and relating them but I've come to the conclusion that it's not the answer. The restriction of the data types, in particular the limited functionality of the RichText editor wouldn't be enough for the editor. It's OK for basic product text but not for a whole pages content.
I'll just create categories for the items I need to assign prices to and link to others by name.
How to relate a product to a content node?
I am debating how to architect my site.
I will have content nodes for various football/soccer clubs
I will also be creating products for tickets to games relating to these clubs
When I display a club page I want to be able to list the tickets that relate to the club.
So for the Man Utd. club page I would see
I was thinking that in order to do this I would create a multi-content picker data type and add that to the product definition of my ticket product which would enable me to pick the clubs that the ticket is related to.
However I don't think this is possible is it?
Hi Matt,
At the moment you can't add custom data types to uCommerce (it's something I really want to get in there though). What I'd suggest instead is turn the relationship around and do a macro, which pull out products from a given category.
Basically add that category picker to each team page and have it list products from the category as part of the content. You just need a string so the ghetto version of this would be to add a short text and paste in the category name or you could do an actual picker if you've got the time to do the more user friendly solution.
OK Soren, I think I understand.
I'll create categories for each club Man Utd, Arsenal, Real Madrid.
Then for example I'll add the 'Man Utd vs Arsenal - $80' product to the Man Utd category but also add it to the Arsenal category as well by ticking that category on the 'Categories' tab when creating the product. I can see how that would work.
I do however have another requirement that is presenting questions about how best to architect it all.
I will have some site nodes to store information about the stadium venues where these football matches take place:
I was planning to create a property in the Ticket product definition so that when I'm creating creating a football ticket product like 'Man Utd vs Arsenal - $80' I could assign the correct stadium venue, Old Trafford to it. This would enable me lookup and display details about that stadium when the shopper looked at the ticket product.
I am guessing that to do this I would have to create an Enum product definition property that mirrored the stadium venues nodes that had been created and just do a lookup based on name.
This is OK but it would mean maintaining two lists of venues.
I am wondering if there is any advantage to be gained by re-architecting it so that the stadium venues are products in uCommerce rather than normal content nodes and how that would work?
You could move the venues to uCommerce as either products or categories and use relations to show what's available. The advantage to doing this is that you can create other types of listings quite easily just by relating or associating products to other products or categories.
The advantage is maintainability and the ability to create some nice custom listings.
The disadvantage is less options for data types to add to the venues.
I'd probably go with categories myself as that will give you a ready made custom listing as part of the catalog structure.
I've been playing all day with creating my various content nodes as products and relating them but I've come to the conclusion that it's not the answer.
The restriction of the data types, in particular the limited functionality of the RichText editor wouldn't be enough for the editor.
It's OK for basic product text but not for a whole pages content.
I'll just create categories for the items I need to assign prices to and link to others by name.
Thanks.
Thanks for reporting your findings on the two approaches.
is working on a reply...