By nutkenz on

I'm still new to the taxonomy and CCK concepts, but I'll be using either one of them very soon for a real estate website I'm working on: http://www.immo-egypte.be

The amenities are usually boolean values, and I think the tagging system for taxonomy might be the easiest/fastest way to add these to properties when I add them on the site. However, CCK seems more correct because taxonomy in my mind means categorizing and that's not really what I'm doing.

These are some examples:

PUBLIC FACILITIES
Hotel usage
Supermarket
Health center
Parking
Spa / jacuzzi
Lift / elevator
Disabled
Barbecue
Security 24/7
Cleaning service
Tours & excursions
Local Transportation
Rental management
Doctor
Pharmacy
Restaurant
Swimming pool

SPORTS FACILITIES
Swimming
Gymnasium
Tennis
Snorkeling
Diving
Water skiing
Sailing
Horse riding
Squash

UNIT FACILITIES
Internet Broadband
Cable/Satellite TV
Telephone
Safety box
Air-conditioning prep
Air-conditioning units
Central Heating

AMENITIES
Seafront
Promenade
Private beach
Public beach

How would you do this? What do you think the pros and contras for each method are?

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

Take a look at http://drupal.org/project/content_taxonomy and read its presentation.

It is possible to use a CCK field *and* take advantage of taxonomy (a) for managing the terms and (b) for making them available to other modules which rely on taxonomy. You may need it, for example, for using a taxonomy-based module which handles user subscriptions/notifications for some specific features.

nutkenz’s picture

nutkenz commented

This seems pretty complicated... The terms I created in the Taxonomy will be used by CCK to display the information on the node or something? I tried finding a good tutorial, but haven't found any. Why is this better than just using taxonomy by itself exactly?

cog.rusty’s picture

cog.rusty commented

Because you will have the category available as a field to use in your views, or you may find it easier to customize where the category selection appears in the node editing form.

Of course if you don't need a field you don't need to do that.

I don't see any difficulty, but that may be subjective. The main difference is that, instead of telling your vocabulary that it applies to that content type and therefore it should add a selection list in it, you tell your content type to use the vocabulary simply by providing it with that field.