Features
The categoryi module allows you to structure your site and to organize content
with categories. The features that help you to do this are:
- Categories and containeris are created as nodes
- All entities created by the category module are nodes. A node is the basic unit of data in Drupal, and having something exist as a node brings with it many advantages. For example: a node can have a body of content (which may be versioned); it can be commented on; it can have workflow settings; and it can have files attached to it. The category module defines two node types: a category and a container. These are roughly equivalent to the respective term and vocabulary entities in the taxonomy module, which are not node types. This page is itself a category node, and its parenti is a container node.
- Content can be assigned to categories
- Categories and containers are designed to be used for static, hierarchical content, much like book pages in the book module. However, categories can also be assigned (or tagged) to other nodes, such as stories and forum topics, much like terms can be assigned to nodes in the taxonomy module. Categories are generally assigned to dynamic content, although they can be assigned to any node, including other categories or containers. A category displays a list of all nodes that are assigned to it.
- Categories can be structured within a container
- You can organise your categories hierarchically within a container, and you can even give your categories multiple parent categories.
- Categories and containers can be structured anywhere
- If simply arranging categories within a container isn't enough for you, it's dead easy to give your containers one or more parents. A container can have any other category or container within your site as its parent. And if you're still not satisfied, it's even possible (although not usually necessary) to give a category some parents that are outside of its enclosing container. This allows you to create a complex site structure that matches almost any architecture you could possibly think up.
- RSS feeds available for categories and containers
- As with terms in the taxonomy module, all categories (and containers) that display a list of assigned nodeis have RSS feeds available.
- Extensible architecture
- The category module has been designed specifically to be easily extended by other modules. Most of this extensibility comes automatically, from using nodes as the basic unit of data for everything: using nodes provides the advantage of many flexible hooks and other programming interfaces being available. Where the node system falls short, the category module provides its own hooks to let other modules directly interact with it.
- Wrapper modules for backwards-compatibility
- The category module is based on both the book and the taxonomy modules. There are a large number of contributed Drupal modules that depend on interacting with these two modules (particularly with taxonomy) in order to function. Unfortunately, these contributed modules are not compatible with the category module, as it uses a new (and in many ways different) architecture. This is why the category module comes bundled with wrapperi modules for both book and taxonomy; the wrappers provide a compatibility layer, and thus bridge the gap between old and new. By using the wrappers, taxonomy- and book-dependent modules are able to communicate with the 'old modules' (at least, what they think are the old modules), but to actually interact with the new category system.
If you are looking for some visual illustrations of these features, have a look at the screenshots section of the site's image galleries.
You might also like to read about the features of the other modules in the category package. The features for each of these modules can be found in the pages below.
Tree-like hierarchy
I have a huge problem in realising a tree-likei hierarchyi with the categoryi-module. For a site dealing with photo, i have a structre like this:
- gallery
-- motives (containeri)
--- motive A (category)
--- motive B (category)
-- locations (container)
--- country A (category)
---- city A (category)
---- city B (category)
--- country B ...and so on
There is no problem in the motiv-section. But in the listing of country A, every sub-category ist listet too! And in the listing of each city, the category of the city itself appears in the listing of the nodes too!
I am going crazy and not able to deal with this module. Please help!
Agree, examples would really help
When to use containeris versus categories has me scratching my head.
For example, in a site about plants, I need to categorise something like Family -> Genus -> Species - > Plant. Being more used to relational databases, in a db I would create 4 tables, each with a relationship to the next.
I'm not sure if I should create a container "Families" and add each (of thousands!) of families as categories within that container. Or, should each individual family also be a container rather than a categoryi, for genus?
me too?
me too! does anyone know of any they can point us too?
this is post on drupal is a list of comments looking for similar stuff...
http://drupal.org/node/90308#comment-164989
im also looking for this kind of tutorial
im also looking for this kind of tutorial, currently i working on my site and it's been two days now and still can't figure out how to manage my navagation.
Is free tagging available
Category Module and Tagadelic
Does the categoryi module work with tagadelic.module?
If not, is there any way to generate tag clouds with category content?
Thanks,
Chapman
Access Control Issue
I have recently installed categories and am confused by a simple concept. Say I use cac_lite to restrict a certain containeri from a certain user role.
Now when I goto create content to create a page, it shows me a list of categories to which this node can belong. But it also shows me the categories that I am not allowed to view. Is there a way to restrict what categories a user can see under "Create content", when adding a page, story etc?
Thanks
AutomatedImport-CategoryTableLoadingFacilityFromXML/Excel?
One feature of the categoryi module that I have not noticed yet (maybe I'm missing something) is an import facility that populates category tables from an external source. I am in the position of starting a new website for a legal aid group that wants to categorize using a standard pre-existing coding system which is hundreds of rows. The taxonomy module does have an add-on that loads from XML and this works but involves quite a bit of programming to get the data into the appropriate input format. Is there such a facility that will populate large category systems directly into category tables -- or would I have to load into the taxonomy and import to category from that?
I'm starting to understand containers vs. categories, but...
... When I try to add pages on my test site they turn up on the strangest places. I have tried to fiddle with the "Allow other content types to be:" settings, but I can't seem to be able to contol wether a page turns up as a containeri or a categoryi. I turned it off, going for the dedicated container and category node types. But when I add pages to a category the category displays "There are currently no posts in this category." even though it lists them on the page.
I'm confused and feel stupid :-)
... and I do think the/admin/category is confusing
My test entries are listed in /admin/categoryi, but they all have the link "edit containeri" even if I have tried not to make them into containers, but rather categories. Are the containers, or might they be categories in stead.
I also find it confusing that the heading of this list is "Categories" when(/if) it in fact lists containers. Thats probably my largest concerns with the module too - that the name, Category is used along with both "containers" and "categories".
Just my thoughts
... just one more comment
What is really the difference between choosing the Container information/Parent and Categories/ in the node editing form? I seems that changing the first options to something different than removes the node from the primary menu and adds it to the list of nodes in the chosen Parent. The second option seems to control wether it turns up and is shown in full in the chosen categoryi. Is the first list a TOC?
I kind of feel that it is obvious, but still don't get it.
Category Module does this?
Category Module does this?
http://www.ubercart.org/jquery_dynamic_form/18
How?
Is it working? or are on development?
I saw your DEMO and I tried create a story content and didn't work.
I saw a lot of bugs reports in Drupal 5.1? I am praying to "Category module" works soon because all Drupal Community is looking for this.
Anyone know a website runnig with "Category module"?
The "Screenshots" link is broken
Click on it and you will see what I mean :)
Motivation needed
I haven't found anywhere on the site, apart from a very short section on the front page about the top-level benefits of categoryi. Stuff about containeris and categories is all very good, but that's not top-level because it assumes some understanding of how Category works. I need the benefits in a way I can explain to a client who has no knowledge of Category...
I installed it, to test it for a client, but gave up on it because it was complex for me to use, and I couldn't persuage myself that the benefits I know about were worth the pain my customer would endure trying to understand Category. Perhaps I don't know all the benefits, and the pain would be worthwhile if I did. Here's the list I know of:
-----
Category is a drop-in replacement for the Drupal taxonomy module. It lets you create more sophisticated categorization schemes than Drupal taxonomy module allows. Being drop-in means that all your modules that work with taxonomy, continue to work seamlessly with Category.
Category allows you to structure all of your site as a hierarchical tree, in the same way that the Book module does but it allows the same page to appear in more than one branch of the tree.
Category can use your categorization scheme to automatically generate menus that match the categorization scheme. You won't have to maintain menus by hand once you've categorized a page.
Category provides breadcrumbs from the way the pages map into the categorization scheme. All pages in a category share the same consistent breadcrumb, and the breadcrumb matches your arbitrary classification scheme.
Category allows you to have separate but related categorizations. It's not possible in the Taxonomy module to make this explicit, but it is in Category. [Is this right? I'm thinking of distant parentiis.] This lets you make your categorization scheme more natural and stops people from categorizing things in ways that aren't possible. [An example required.]
----
What else? Or is that it?
I think this list or something like it should be on the front page of the Category site.
I should have said
That this page has something to say about benefits.
just a thought
It might be helpful to add a "real" example of using categories to give people a clearer understanding of it's value. I think i have seen something simialr to what i am referring in a tox handbook???
Basically a description of an example site and how it is "categorized", e.g.:
Company Info:
- latest news
- contact us
- company profile
Services:
- plumbing
- carpentry
- cabinet making
- house building
- the Smith's project
Porfolio
- the Smith's project
- UofO drain backed up
and then map this into what would be containeris, categories, etc... and make it complex enough (which this likely isn't) to show all the features of categories.