Hey there,

I have the following problem and wonder if hierarchical select is the right solution for that:

Vocabulary (Students with duration of studies and employees with size of company):
- Student
-- 1 years
-- 2 years
-- ...
- Employee
-- 0-10 employees
-- 10-50 employees
-- ...

Alright ... this is a typical case for hierarchical select I guess... BUT

If people choose "Student" they should also be asked for another Vocabulary "Field of Studies":
-- Computer Science
-- Economics
-- ...
(indipendent from student's "duration of studies" children)

Employees, of course, should not be asked for "Field of Studies".

Is it possible to do that (and even some more complex) logical connection of different Vocabularies with hierarchical Select?
If yes: YEAH ... you rock :)
If not: Please give me a hint to get started with developing a custom module.

Greetings,
Morgenstern

CommentFileSizeAuthor
#9 vocabselect 1.3.zip5.05 KBwim leers

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Yes, it's possible, but it must be done through a custom module. A module that looks an awful lot like hs_taxonomy.module, but that allows you to create hierarchies of vocabularies as well. Essentially it means that if people choose "student", which has no child terms in its own vocabulary, that you *pretend* another vocabulary tree is the child tree of "student". This principle is what you'll have to convert into code. It's fairly easy though :) Just look at API.txt and hs_taxonomy.module's code!

Morgenstern’s picture

Morgenstern commented

Thanks for the hint!! I'll have a look at that!

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Category: support » feature
Status: Active » Postponed

Postponed for now (cleaning up the issue queue). Morgenstern contacted me about sponsoring this custom module.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Postponed » Closed (fixed)

For the record: this new module was never developed in the end, because Morgenstern had opted for an alternative solution.

jvieille’s picture

jvieille commented

Which solution?
I am greatly interested
Thanks

Anonymous’s picture

Anonymous (not verified) commented

I'm also interested...
Which solution please ?

Thank you

bakinbox’s picture

bakinbox commented

I´m very interested too, even if is a paid module.
Thankssss

bakinbox’s picture

bakinbox commented

Any ideasss?????

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
StatusFileSize
new vocabselect 1.3.zip5.05 KB

I've attached a module I wrote for a client some time ago. Since I can't reach her to get her approval, I'm just going to assume she's okay with it. It's definitely in the Drupal spirit, so :)

Note that this is not the solution Morgenstern used as far as I know, he used some other work-around to achieve what he needed.

bakinbox’s picture

bakinbox commented

Thanks so much for the answer, anyway i still can find the solution, to have

Vocabulary1 >> Vocabuary2 (What should i change?? or how i install and configure it)

Thank so much

klikissy’s picture

klikissy commented

GREAT!!! is there a Drupal 7 version?