Request: Guidance on Our Tagging System
Author: greg
12
Jun
We’re working to make some adjustments to the tagging system in Social Roots. The problem is that there are a number of different approaches to tagging as it stands. I’ll dump them into two categories:
- Delicious Model - this approach pretty much doesn’t allow spaces in tags but does allow you to combine tags and to have nice, usable URLs. This is the model we have used.
- Flickr Model - this approach allows for more “wordy” tags but also doesn’t really give the option to combine them.
Of course, now that we have been letting some people use the system, we’re seeing lots of interesting behavior in the tagging input that has happened. We find now that we’re want some guidance from the community as to what we should consider the right behavior.
- Tags will be converted to all lowercase
- Tags are delimited by spaces - commas are converted automatically to spaces
- Tags can contain any alphanumeric character and the hyphen, underscore, and colon
Commas and plusses are converted to spaces automatically
- Tags are limited to 10 for a specific profile
Have you worked on a system like this? Do you have preferences for how it should work? Let us know.
Filed under: Social Roots
3 Responses for "Request: Guidance on Our Tagging System"
Youtube has spaces delimiting their tags. I did not realize how many people were on youtube until i saw a lot of kids on campus (college age) checking it out. I think the preferences of the core group of your users should be taken into consideration.
Thanks Vic. I think you make a good point. We are definitely supporting the space now. I don’t see us really changing that unless lots of people request it.
I’ve been working on an enterprise intranet system with tags, and the users definitely and clearly expected to use commas to separate their keywords. So, I think the context is pretty important.
In general, I’d guess that corporate users will have more experience with using keyword / tagging methods that expect commas to delimit keywords.
One other thing: if you think your users will commonly want to use phrases rather than just words (which, can be a common need within an organization, e.g., project names, policy names, etc.), this also might skew you towards commas. But, if single words are more common, you’ll be fine with space delimiting.
Leave a reply