<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> 3. Re: people schema (Jean Gazis)<br> 4. Re: linking the categories (Cog Rusty)
<br> 5. Re: linking the categories (Cog Rusty)</blockquote><div><br>Jean<br>re people schema<br>thanks for heads up, I ll wait for that before building extensions<br><br>Dear Rusty Cog<br>thanks for advice<br>I ll have to sit down and study it all (takes time)
<br>Thing is, that even building custom code, needs expertise and a clear<br>schema/data model, I need to develop that considering the constraint <br>of drupal implementation. will take into account your great advice and will consult you furthe after I come up with something
<br>thanks<br>PDM<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>categories = terms = tags<br>vocabulary is the containing entity
<br><br><br>> I think this can be done by creating a hierarchy of vocabularies/categories<br>><br>> so what I wonder is<br>> can I make a category become the parent or child of another category?<br>> at the moment I dont see this option (I can see that I can make a term
<br>> become the child or parent of another term, but what I need is a group<br>> of terms to be the parent of another group of terms)<br><br>The way the system is designed, there is no direct way to create a<br>hierarchy of vocabularies. You could of course create a
<br>"meta-vocabulary" containing your vocabularies as categories, but that<br>would be hardly useful. Neither tagging nor listing would be possible<br>without custom code. Categories are designed for tagging and listing
<br>nodes, and categories are not nodes..<br><br>So, I would suggest looking for a solution which does not need a<br>hierarchy of vocabularies.<br><br><br>> The reason why I need this, its because the drop down menus at the
<br>> moment are toooo long. For each term, I have say 10 child terms, which<br>> in turn have 10 child terms so its very difficult to select the right<br>> one(s) cause one gets lost before finding the right category
<br>> Plus I cannot selectively make one term mandatory, say a parent, and<br>> the children optional (for those who may want to have more granular<br>> keywords)<br><br>You will need to design for effective tagging and user convenience
<br>based on the available methods. For example:<br><br>Case 1: A very badly designed vocabulary. Allows errors and is cumbersome.<br><br>Tags (vocabulary)<br>------------------------<br>Sections<br>-- Section 1<br>-- Section 2
<br>Topics<br>-- Topic 1<br>-- ...<br>-- Topic 1000<br><br>Applies to all content types.<br>Mandatory, mutiple select<br><br>Case 2: A somehow better design<br><br>Sections (vocabulary)<br>-----------------<br>Section 1<br>
Section 2<br><br>Applies to all content types<br>Mandatory, single select<br><br>Topic 1 (vocabulary)<br>-------------<br>-- Subtopic 1<br>-- ....<br>-- Subtopic 10<br><br>Applies only to content type "topic1"<br>
Mandatory, single or multiple select<br><br>Topic 2 (vocabulary)<br>-------------<br>-- Subtopic 1<br>-- ....<br>-- Subtopic 10<br><br>Applies only to content type "topic2"<br>Mandatory, single or multiple select
<br><br>Now, the user will have 2 manageable category selection lists. The<br>second one will be shorter and different based on the content type.<br><br>Or else, you could create different content types for each section, so
<br>that you can use the taxonomy_defaults module<br>(<a href="http://drupal.org/project/taxonomy_defaults">http://drupal.org/project/taxonomy_defaults</a>) to assign a specified<br>section category to each so that the user won't see a second selection
<br>list.<br><br>Notice that content types are not only for adding different fields.<br>They are also used for workflow (different publishing options and<br>different associated vocabularies). So, you can use that to move some
<br>of the users' burden to yourself (having to manage 20 content types<br>vs. having the users manage 1000 terms in an error-prone way).<br><br><br>> So one way of doing that (perhaps) would be for each parent term have a new
<br>> 'category', so that each parent term can be made mandatory (hence<br>> creating a superstructure) and then making one or more children<br>> optional, and then linking a freeflowing tags to that.<br>
> Has someone implemented a nice complex hierarchy using taxonomy module<br>> and has advice ?<br>><br>> thanks<br>><br>><br>><br>> --<br>> Paola Di Maio<br>> School of IT<br>> <a href="http://www.mfu.ac.th">
www.mfu.ac.th</a><br>> *********************************************<br>> --<br>> [ Drupal support list | <a href="http://lists.drupal.org/">http://lists.drupal.org/</a> ]<br>><br><br><br>------------------------------
<br><br>Message: 5<br>Date: Sun, 9 Sep 2007 03:03:46 +0300<br>From: "Cog Rusty" <<a href="mailto:cog.rusty@gmail.com">cog.rusty@gmail.com</a>><br>Subject: Re: [support] linking the categories<br>To: <a href="mailto:support@drupal.org">
support@drupal.org</a><br>Message-ID:<br> <<a href="mailto:a08ea0280709081703n78b658cme6d3a77accb56f4@mail.gmail.com">a08ea0280709081703n78b658cme6d3a77accb56f4@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1
<br><br>On 9/9/07, Cog Rusty <<a href="mailto:cog.rusty@gmail.com">cog.rusty@gmail.com</a>> wrote:<br>> On 9/8/07, <a href="mailto:paola.dimaio@gmail.com">paola.dimaio@gmail.com</a> <<a href="mailto:paola.dimaio@gmail.com">
paola.dimaio@gmail.com</a>> wrote:<br>...snip...<br>I should add that by using different content types, besides the<br>shorter selection lists, as a bonus you get neat links like<br>"node/add/[type]" which you can place in any "section page" or block.
<br><br><br>------------------------------<br><br>--<br>[ Drupal support list | <a href="http://list.drupal.org/">http://list.drupal.org/</a> ]<br><br>End of support Digest, Vol 57, Issue 12<br>***************************************
<br></blockquote></div><br><br clear="all"><br>-- <br>Paola Di Maio <br>School of IT<br><a href="http://www.mfu.ac.th">www.mfu.ac.th</a><br>*********************************************