[Tagdb] Over tagging fields?

[ogjunk-tagdb at yahoo.com]

 If you prefer power and flexibility, keep things separate.
If you are using RDBMS for your system, also think about how large your tags table(s) will be.
Even if you have a common place/table for your tags, you could add a 'type' identifier to each record, so you can narrow searches/joins to a specific type, which may or may not speed thngs up, at least in RDBMS world, depending on your DB, your indices, etc.

Otis
 
----- Original Message ---- 
From: Joshua Lippiner  
To: tagdb at lists.tagschema.com 
Sent: Tuesday, March 21, 2006 10:27:39 AM 
Subject: [Tagdb] Over tagging fields? 
 
    Hello  All, 
   
 I am new to this  group and checked the archive but didn't really find any direct answers to this  question: 
   
 In Web 2.0  Applications, should any group of items ever have more then one  tag field? 
   
 In the last post,  Colin mentioned tags for articles, sponsors and products.  It made me start  wondering about rules for too much tagging.  As an example, take book  cataloging.  When developing a tag system for books should you only allow  tags on the book level or should you also allow tags at the  author level?  Doing both would allow users to describe a book AND  authors separately but then how do you deal with tag searching?  Does the  user have to specify that they only want to search the book tags or author tags  or do you search everything together?   
   
 Before figuring out  the schema for my tagging system, I need to figure out this more fundamental  issue.  It seems it is a critical aspect of Web 2.0 tagging  applications.    
   
 What is everyone's  thoughts on this? 
   
 Thanks, 
   
 Josh 
_______________________________________________ 
Tagdb mailing list 
Tagdb at lists.tagschema.com 
http://lists.tagschema.com/mailman/listinfo/tagdb