Tuesday 11 October 2005 5:56:41 am
I'd say that using the enhanced object relation would be a better idea, but I'm slighly biased ;) I've been able to explain the difference between locations and related objects, some of my customers even understood it, but the reverse relation has always proved be a nightmare. I know you can use either relations or relations, that you can have more than one location to confuse them a wee bit more, but from a conceptual point of view, they don't address the same need, and that isn't that complicated to explain that. locations= "belongs to", relations = "see also". On most of the cases, it works well: "staff" goes under "about us" and that's easy to understand. For the 10% more complex where you can have several ways of categorizing a page, you decide of what's the main one and you force them to stick to it. On the real live, lots of things have more that one way to be stored (eg a book could be stored by its author name, by topic, by title...). If they are able to find a book on a library shelf, they should be able to understand how it works on ez! On some cases, the choosen classification system is better than the others only because it's the choosen one and everyone is going to apply it. Coherency is the key for everyone. Use the location for the main classification, related objects for the rest and after a lot of scream, pain and cry, you are going to have a fucking mess of a website ;) Good luck... X+
http://www.sydesy.com
|