This mixin provides an easy way for adding tagging capabilities (also known as folksonomy) to your active record objects. It allows you to add tags to your objects as well as search for tagged objects.
It assumes you are using a fully-normalized tagging database schema. For that, you need a table (by default, named tags) to hold all tags in your application and this table must have a primary key (normally a id int autonumber column) and a name varchar column. You must also define a model class related to this table (by default, named Tag).
svn: http://dev.rubyonrails.com/svn/rails/plugins/legacy/acts_as_taggable
Check the ActsAsTaggablePluginHowto for info on how to use it.
This is for the plugin.
Here is another usefull link to a post about docs for the plugin.
http://rails.co.za/articles/2006/06/04/acts_as_taggable-plugin-docs
—
It doesn’t look like acts_as_taggable currently supports the :include key in ActiveRecord.find. For example, this fails: Product.find(:all, :include => :tags) where Product is an acts_as_taggable model. Anyone know how to fix this?
—
NOTE: The above is DHH’s example acts_as_taggable plugin and DOES NOT use the directions below. Use the acts_as_taggable gem until docs come out for DHH’s work.
See also acts_as_taggable rdocs.
an excellent intro to using acts_as_taggable is located at http://noobonrails.blogspot.com/2005/11/using-actsastaggable-in-rails-quick.html (care of Curtis Edmond’s NoobOnRails Blog)
—
Per-user tagging
If you’re interested in updating the plugin to associate a particular tagging with a user, here’s a
tutorial:
http://blog.aisleten.com/2007/02/25/acts_as_taggable-per-user-from-slashdotslash-plus-a-few-fixes/
This mixin provides an easy way for adding tagging capabilities (also known as folksonomy) to your active record objects. It allows you to add tags to your objects as well as search for tagged objects.
It assumes you are using a fully-normalized tagging database schema. For that, you need a table (by default, named tags) to hold all tags in your application and this table must have a primary key (normally a id int autonumber column) and a name varchar column. You must also define a model class related to this table (by default, named Tag).
svn: http://dev.rubyonrails.com/svn/rails/plugins/legacy/acts_as_taggable
Check the ActsAsTaggablePluginHowto for info on how to use it.
This is for the plugin.
Here is another usefull link to a post about docs for the plugin.
http://rails.co.za/articles/2006/06/04/acts_as_taggable-plugin-docs
—
It doesn’t look like acts_as_taggable currently supports the :include key in ActiveRecord.find. For example, this fails: Product.find(:all, :include => :tags) where Product is an acts_as_taggable model. Anyone know how to fix this?
—
NOTE: The above is DHH’s example acts_as_taggable plugin and DOES NOT use the directions below. Use the acts_as_taggable gem until docs come out for DHH’s work.
See also acts_as_taggable rdocs.
an excellent intro to using acts_as_taggable is located at http://noobonrails.blogspot.com/2005/11/using-actsastaggable-in-rails-quick.html (care of Curtis Edmond’s NoobOnRails Blog)
—
Per-user tagging
If you’re interested in updating the plugin to associate a particular tagging with a user, here’s a
tutorial:
http://blog.aisleten.com/2007/02/25/acts_as_taggable-per-user-from-slashdotslash-plus-a-few-fixes/