Closed (fixed)
Project:
Recruiter
Version:
7.x-1.0-beta4
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
31 Aug 2011 at 03:32 UTC
Updated:
17 Sep 2012 at 14:51 UTC
I would like to give the option to list many different skills. However, I have put them into several different vocabularies. There is one field-collection with eight different term-level fields each with a single vocabulary and each vocabulary has about 10 to 20 terms. It looks fine. However, I'm starting to build the database search index with the Search API and the references needed to get to that level are making a huge options page when configuring the Search API index.
Is this too much and will it be inefficient?
Comments
Comment #1
dasjohave you had your issue solved?
Comment #2
mh86 commentedRegarding the performance considerations, this shouldn't be a big problem. The data is only fetched while indexing, which happens on cron runs.
One possible solution to that is having an additional taxonomy field with multiple vocabularies, hide it from the end user, and sync the data from the different term level fields with Rules.