Some way to relate parent and child taxonomy terms

Events happening in the community are now at Drupal community events on www.drupal.org.
colincalnan's picture

Hi,

I'm trying to build a site that keeps track of all Drupal modules and their versions across a lot of sites I'm running, kind of a bookkeeping/housekeeping site, rather than a spreadsheet. So far I've created a content type called "Site" that has a "Modules" taxonomy.

However I'm stuck on how to create the "Module Version" taxonomy.

When I add a content type "Site" I can choose multiple modules but not the version of those modules. I can choose multiple modules from the module taxonomy dropdown but not apply a version to that.

I tried making a hierarchical taxonomy with the module version as a child term of the module term; but views can't do what I want with that, and you can select just the version from the taxonomy dropdown and not select a module, which is pretty dumb.

Basically what I need is that when you choose to add a site to your list of sites, you simply choose your module from a dropdown and then choose it's version, then choose another module and it's version, and so on and so on, down the module list.

I guess I could try to build my own module to do this, but I really want to get it done fast and easy.

Is there any taxonomy modules out there that can allow me to do that, choose a term and then choose one of it's children, and then be able to filter by that later in views or in the taxonomy views?

Any help appreciated.

Col.

Comments

Hi Cal, If I understand your

jfall's picture

Hi Cal,
If I understand your problem correctly, then I think a model that uses 2 taxonomies (module & version) won't really work, because you won't be able to link together which version term belongs to which module term. (e.g., in a node tagged with "ModuleA, ModuleB" and "version.0.8, version.1.2", which version belongs to which module?)

A hierarchical model could work, but a version number is not a child of a module name. Try:
- Module A
-- Module A v.0.8
-- Module A v.1.3
- Module B
-- Module B v.1.2
-- Module B v.2.0
- etc.

In fact, perhaps you don't need a hierarchy at all (especially if Views doesn't like it)... try:
- Module A v.0.8
- Module A v.1.3
- Module B v.1.2
- Module B v.2.0
- etc.

Now you can multi-select the module and version in one step.
I see the issue here - you want to know all sites with Module B installed (regardless of version) - this model can do that, although it is cumbersome since you'd need a query or view that pulled in all the Module B versions, which of course would have to be updated whenever a new term was added - yuck.
The hierarchical model above resolves that by using a depth of 2 in the query. I use Views with a hierarchical taxonomy, and it works fine - perhaps I don't clearly understand the issue.

One final thought - there are some nifty contrib modules out there that grab all the info. about installed modules on a site (usually to check if updates are required, or whatever) - perhaps you could make use of some of the ideas there?

good luck & best wishes.

"One final thought - there

mundowen's picture

"One final thought - there are some nifty contrib modules out there that grab all the info. about installed modules on a site (usually to check if updates are required, or whatever) - perhaps you could make use of some of the ideas there?"

That sounds like the best idea, if you could run some sort of service on your sites to expose modules + versions, and then pick them all up on the main site. (Perhaps some sort of JSON layer on slave sites). If you can't find anything specific let me know, I could probably help out.

What I would do is instead

dwees's picture

What I would do is instead of creating sites, create modules and have a versions vocabulary and a sites taxonomy. You can then use Views to display a list by site of all modules (or even a default taxonomy display).

Alternatively, you could create a site as a node with a description, and a module as a node with a version taxonomy, and a node reference to the sites previously created.

If you want to do it all in one form, examine the nodefamily module which I think allows you to create multiple nodes together.

Dave

you may try module 'Web

TechSteve's picture

you may try module 'Web Services' or 'Services'. they claim that you could check module exists remotely.

good luck,
steve

A Drupal Developer

taxonomy

meryd's picture

i have categories like
Real Estate
-Apartments
--rent
--sale
-land
Vehicle
-bikes
-cars

i want to create taxonomy list in different columns like gumtree( http://www.gumtree.com/).
Any module is in drupal to list vocabulary parent term and its childs in different column???
how to list using views???

Vancouver

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: