More than one Taxonomy Menu Per Install

samdeskin,

I think that what you are asking is whether you can have different Indexes. If so, then yes it is possible. You need to go to your Taxonomy and create a new entry named "Legal Practice" and set it up appropriately.

Administer > Content management > Taxonomy

Now, if you have 647,000 nodes, you may run in a little problem in regard to updating the node assignment between that new taxonomy and your existing nodes. If you know the terms that you want to add the the Legal Practice index and these are simply words that exist in your nodes, then you may need a module such as the MO Auto add terms module.

Let me know whether this is what you are looking for.

Thank you.
Alexis Wilke

Hi Alexis,

MO Auto add terms may be useful - I will check it out. Some issues that I have is that I have about 3000 terms and 640,000 pages. It is talking about doing 10 pages at a time - and that is a bit of a joke for my volume. Any settings to update that?

The immediate problem I have to get a grip on before I add terms is that I am not certain I completely understand what you have written above as fixing my issue.

What I would like to do is have multiple taxonomy VTN instances - I think.

So, for example, if you visit: http://XXX.org/browse > XXX.org/taxonomy_vtn

You see that it sends users to many of the pages on our website. We would like to build another taxonomy_vtn page that has:
- The data sorted in different ways - e.g. by company name, by company type, by laws being used - this is where MO Auto Add terms comes handy.
- Legal Practice Areas that sends users to completely different pages on our website - as yet to be built.

But these taxonomy_vtn pages would not be on the same page as the browse page above - I would want them separate, e.g. taxonomy_vtn_1.

Just so I am clear, F., F.1d., F.2d., and US are all separate vocabularies. I understand that I can add more vocabularies and make them - not show up on this page - but I don't know if I can add vocabularies and make them show up on another page.

Is there a way to do that?

Sam

Hi Sam,

In regard to the number of items to work on whenever CRON calls the MO Auto add terms I also have someone who asked me to turn off the feature completely! I will offer a counter that you can put to 0 (do nothing) or any other numbers (depending on how slow/fast it gets on your web server...) I choose 10 because some people run their CRON once a minute and if it runs for too long they don't get their other features to run properly. Now... 10/min. = 14,400 pages a day, 100,800/week, about 302,400/month or ~5.2M/year (whether or not you add yet other terms, I will not rework the same pages until I worked on all pages at least once) And I think that's not too bad.

Otherwise, I ran into a problem with the Views support of the Taxonomy module. They actually do not support a way to display a parent/child view properly. Only of nodes, not just of terms. So I looked around to find a way to handle that and could not find anything. Thus I finally added a couple of parameters to the display function of the Taxonomy VTN and there I was! It worked like a charm!

At this time, the support is real weak, but what you can do with it is create a parent/child relation of your terms.

For instance, if you want a VTN for all your page marked as F1, F2, F3, to F999, then put all of those terms inside the "group" F (i.e. make them all the child of the term F.) Then the path:

/taxonomy_vtn/voc/1/3001

(assuming the term F is number 3001) will display all the terms in that group! (you can also limit the depth)

I want to create a new module to generate such groups in an automated way so for instance you could get one VTN page per letter without having to yourself create each parent/child relationship!

The result is very straight forward and uses the existing Drupal infrastructure the way it is so I do like the idea!

I have a test case here:

http://linux.m2osw.com/taxonomy_vtn/voc/1/241

http://linux.m2osw.com/taxonomy_vtn/voc/1/241/1

The first link shows you all the operating systems terms.

The second link shows you only the "root" operating systems (the Terms root is named Operating Systems and is not shown, it is term 241.)

Note that if you check out the entire taxonomy #1, you will see quite a bit more terms:

http://linux.m2osw.com/taxonomy_vtn/voc/1

And if you search for the letter O, you will find the "operating systems" term there.

Do you think that this would work better for you than separate Taxonomies?

Thank you.
Alexis Wilke

Alexis,

In re: MO Auto add terms - can you make it so that it is possible to ask it to identify a word and if it sees that word it applies another word as the taxonomy? Also, is it possible to bulk upload a list of terms that should be made into taxonomy - Let's say I have hundreds of terms I want to search for, Can I upload this list and let it go? And associate those terms to the proper vocabulary?

About the VTN issue, I am not seeing how I create a group. I see the ability to group letters, but not the ability to create groups of Vocab. Can you tell me where I can find this?

I am using: Taxonomy Menu 6.x-1.02 - not quite the latest and Taxonomy VTN 6.x-1.2

Thanks,

Sam

Sam,

• MO Auto add terms

I'm not sure I understand your request in regard to MO Auto add terms. That module is to automatically assign terms from one or more taxonomy vocabularies to a node. If you upload (do you have a module to do that?) a large number of terms in a taxonomy vocabulary, assign that taxonomy vocabulary to a node type and maybe change the CRON setup to run over 100 or even 1000 nodes at a time (see how slow/fast it is by going to http://www.example.com/cron.php) Remember that one run of cron.php is allowed about 1h. When you go over the limit it will get killed, so limit yourself to 30 or 45min. Then after a little while your nodes will all have been assigned all the matching terms automatically. Once you have all the assigned terms, you may want to reduce the number of nodes to be checked depending on the speed.

Note that it perfectly supports two (or more) taxonomies with the same terms. If both are marked as automatic (MO Auto add terms checkbox ticked), then both terms will be assigned to the node as expected.

The module also checks the synonyms. When a synonym matches, then the corresponding term will be assigned to the node. Maybe that's what you are referencing? My idea behind supporting synonyms was first for plurals. Thus, you can create the term 'bench' and enter 'benches' as a synonym. Automatically, the term 'bench' will be assigned to a node that includes 'benches'.

At this time there is no cross taxonomy vocabulary capabilities, but I also thought of that. If I keep the synonyms as is, using a term such as the verb 'have', can generate a "weird" list of synonyms... (hast, has, had, I'm, am, hasn't, haven't, etc.) This may not be desirable. There are two solutions here: (1) have a link between two taxonomy and when I find 'have' in one taxonomy, I use the term 'have' of the other taxonomy; and (2) have another field to enter plurals and conjugated verbs. That way, synonyms can stay "clean" for the default purpose of that feature.

• Taxonomy VTN

This is not obvious. I may not have explained the new feature in enough detail. Sorry!

You may want to conduct a test on some website other than your main website. You will need to get the -dev version too if I recall I did not make that parent/child a.k.a. grouping a plain version yet.

So...

1) Create a taxonomy

2) Add some terms (about 10 should suffice)

Say the terms are: "Group A", "A1", "A2", "A3", "A4", "Group B", "B1", "B2", "B3", "B4"

3) Make parent child connections (i.e. A1 to A4 are children of Group A, B1 to B2 of Group B.)

4) Create a few nodes and assign terms A1 to A4 or B1 to B4 to these nodes (just make sure you have some with A and some with B, 2 nodes suffice, but I suggest you try with 4 or more.)

5) Now you should have a few nodes in Group A and a few nodes in Group B. To see those in the Taxonomy VTN, use a path like this:

http://www.example.com/taxonomy_vtn/voc/1/1

http://www.example.com/taxonomy_vtn/voc/1/2

where the first 1 is the vocabulary number (so if it is not your first vocabulary, don't use 1 but whatever the correct number is.)

And the second number (1 or 2 in my links here) are the numbers of the parents: term "Group A" and "Group B".

The first link should show you the nodes in group A (as assigned in point 4, all the nodes with terms A1 to A4) and the second link should show you the nodes in group B (as assign in point 4, all the nodes with terms B1 to B4).

As you can imagine, it is possible for one node to appear in multiple groups by assigning multiple terms to the node, each term being in a different group. And also you can assign multiple parents to one term. Isn't that fun?!

Alexis,

Thanks for the explanation.

I am duplicating my database and going to install the new Taxonomy VTN onto the new database. If you have a newer/better update to the -dev version, let me know.

I also plan on testing your MO Auto Add Terms out on that database as well. You answered my questions. Thanks.

Sam

Alexis,

Comments on the -dev version:

- Description of new vocabulary was empty but somehow got the Description from another vocab. I gave it a Description and it took my new Description in it's place.
- Created Parent/Child Relationship, but it was ignored when going to: taxonomy_vtn/voc/7 . Children were there as if they were same as Parent.
- Going to taxonomy_vtn/voc/7/1963 shows Parent's Children, but no way to get there from taxonomy_vtn/voc/
- I am also trying separate the new vocabulary from the other "old" vocabulary. The new vocab is completely unrelated to the old vocabulary. I can "Exclude vocabularies by identifiers:" and type 7. But how do I create a new taxonomy_vtn/voc/ page? And include 7 and other vocabularies on that page as well?

If you want to see what is going on go the URL in my original post and then go to /D-NEW/

Thanks Alexis,

Sam

Sam,

> Created Parent/Child Relationship, but it was ignored when going to: taxonomy_vtn/voc/7 .
> Children were there as if they were same as Parent.

The old functionality is still the normal functionality of the module. I did not yet implement anything to support parent/child other than the list of terms it self.

If you have a limited number of parents, you can create a page or a menu with them in the taxonomy with links such as taxonomy_vtn/voc/7/1963.

> Going to taxonomy_vtn/voc/7/1963 shows Parent's Children, but no way to get there from taxonomy_vtn/voc/

Again that's not yet implemented. If the list you see in taxonomy_vtn/voc/7/1963 is what you are looking for, then I can look into a way to automate some menu to get you at the right place.

> I am also trying separate the new vocabulary from the other "old" vocabulary. [...]

With a new menu and the use of Alias URL you can really create whatever you want and/or need.

Thank you.
Alexis

>> Created Parent/Child Relationship, but it was ignored when going to: taxonomy_vtn/voc/7 .
>> Children were there as if they were same as Parent.

>The old functionality is still the normal functionality of the module. I did not yet implement anything to support parent/child other than the list of terms it self.

Are you planning on implementing functionality to support parent child?

>If you have a limited number of parents, you can create a page or a menu with them in the taxonomy with links such as taxonomy_vtn/voc/7/1963.

I am going to have lots of them. We don't do anything "limited." How do I create a menu in the taxonomy?

>> Going to taxonomy_vtn/voc/7/1963 shows Parent's Children, but no way to get there from taxonomy_vtn/voc/

>Again that's not yet implemented. If the list you see in taxonomy_vtn/voc/7/1963 is what you are looking for, then I can look into a way to automate some menu to get you at the right place.

However you think the most proper way to do it is. I have lots of pages I don't want to be messing around with doing things half-ass - so I will follow your lead.

>> I am also trying separate the new vocabulary from the other "old" vocabulary. [...]

>With a new menu and the use of Alias URL you can really create whatever you want and/or need.

How do you suggest that I create a new menu?

Can I make a new request that will add tons of value?

Vocabulary pages have a teaser that goes on the taxonomy_vtn/voc page. They should also have an option to show a body on the taxonomy_vtn/voc/7 page (before the terms); and
Term pages should have an option for a teaser for the taxonomy_vtn/voc/7 page and an option for a body as well for their own page.
Nodes should have an option to show teasers on the the term page.

What do you think of that??

sam

Sam,

> Are you planning on implementing functionality to support parent child?

Yes. But right now I wanted to know whether this was a good solution for your current problem (i.e. does the output look like what you had in mind for a multi-taxonomy VTN output support?). If the answer is yes, then I can move forward.

Thank you.
Alexis

Alexis,

> Does the output look like what you had in mind for a multi-taxonomy VTN output support?

What would be ideal would be to give the flexibility to be able to set it up like this:

The taxonomy_vtn page would be able to be sectioned for the different vocabulary: http://drupal.org/files/tax-vtn.png You currently have it set up so that you can turn them on or off. The advancement that I would make is to be able to turn them on or off for different sections.

This would be a the Parent Terms for the Vocabulary "Jurists": http://drupal.org/files/vocab.png You currently have it set up so that we have Vocabulary and Terms. The advancement I am suggesting makes it so the Parent Terms have their own page with a body at the top so that you can describe these terms

This would be a Child Term for the Term "Supreme Court of the United States": http://drupal.org/files/child-term.jpg Within the Parent Term, you have Children. Each Child has a short description (I think from Taxonomy). The VTN page would allow you to give these Children a description at the top as well.

The page with the Nodes would be a similar page as the Child Term page, with a body on top and links to the nodes that are associated with that Child term.

This way each page of VTN is more than merely a directory, it is also a guide to the vocab/terms/nodes that follow.

Does that sound good?

Sam

Alexis,

What do you think about what I have written, above? Do you think that this is feasible or am I asking for too much?

Sam

Sam,

The paragraph at the top of the terms would be easy enough.

Would the parent (or for the top-most VTN, the vocabulary) description work for you? You mention having another box and I would think that using the existing description should suffice, right?

As for your tax-vtn.png, it sounds as if you would want to have multiple layers of parent/child terms. That's what I wanted to do, but I think there will be a problem in your situation because the same term when browsing by Jurist should possibly point to a different page when browsing by Federal Reporter. And that sounds problematic... I suppose you can create several separate trees within the same vocabulary and only the leaves would be nodes with the actual articles.

Otherwise I have been working on a big site and thus have been quite busy... Otherwise, if you can spare some cash, I'd appreciate and make sure this is a priority. 8-)

Thank you.
Alexis Wilke

Alright, I have just checked in a new version that includes a parent/child navigation system. You need to edit the vocabulary in admin/content/taxonomy and turn on the Parent/Child flag. By default it is off so Taxonomy VTN works as before.

The result is pretty good so far, I think.

Don't forget to reset your Taxonomy VTN cache if you have that feature turned on. admin/settings/taxonomy_vtn

Thank you.
Alexis Wilke

Okay, I'll mark this as fixed. If you want to complain about the location of the Hide/show description, create a new issue, please. Plus, you could just remove the link if it bugs you. Most people are not going to use it anyway.

Thank you.
Alexis Wilke.

Automatically closed -- issue fixed for 2 weeks with no activity.