-----Original Message----- From: openguides-london-bounces@openguides.org [mailto:openguides-london-bounces@openguides.org]On Behalf Of Earle Martin Sent: 17 May 2004 00:00 To: openguides-dev@openguides.org Cc: openguides-london@openguides.org Subject: [OpenGuides-London] Habituation is bad.
... How to remedy this situation, as far as I can see:
- Warn the users.
- Change the code so that nodes no longer have "Category" or "Locale" prepended to their names.
- Find all the pages that fit the pattern of "Fred" and
"Category Fred" and merge the latter into the former - automatically for cases where the former contains only a redirect, and manually for everything else (not many cases, hopefully). 4) Munge all links pointing to "Category X"/"Locale Y". 5) Erm, that's it? Did I miss anything?
I am in favour in principle of what you are suggesting. However, we need to be very careful. Consider an extreme case. Suppose we have a contributor called Victoria, working on the guide. Does she have to share her home node with the description of the place of the same name? Other related entries are distinguished in the node title: Queen_Victoria, Victoria_Station, (category) Victorian.
I think we need a metadata field called node type. This can take the following values for starters:
- Person - Category - Place - Locale
Note: a place has a pinpoint location, whereas a locale has an area.
If we put this in place, we could have different templates for each node type. Also, we could distinguish between Victoria(Place) and Victoria(Person).
My £0.02
Ivor.