I have installed the field indexer module to view an advances openlinst search option. the module let me choose what fields to include in this openlist choise.
the thing is it showin only 4 fields I have use in one faceted environment(the first one I have created).
now I want more fields from different CCK to display new environment in new site categoty.

Comments

david lesieur’s picture

david lesieur commented

Sorry, I don't really understand what you are trying to express here. If this is a bug report, could you provide screenshots?

amirtaiar’s picture

amirtaiar commented

Hey David,
I have got it. I ment the fields you can choose in the faceted admin. I have found they can be figure at the field_indexer admin. what I didnt understand i how to allow taxonomy fields to be as index.

david lesieur’s picture

david lesieur commented
Title: field indexer issues. » Allow indexing of taxonomy terms
Project: Faceted Search » Field Indexer
Component: Field Search » Code
Assigned: amirtaiar » Unassigned
Category: task » feature
Priority: Critical » Normal

Glad that you found out for the Field Indexer admin settings.

Currently, Field Indexer does not implement indexing for taxonomy terms. It would be a valuable feature, so I'm adding it as a feature request!

amirtaiar’s picture

amirtaiar commented

That will be excellent!
Thank you for this work...

sidharth_k’s picture

sidharth_k commented

Yes it would be a wonderful idea to allow taxonomy items to be indexed by field indexer. Actually I need this for one of my projects!!

Sample usage scenario:

Lets say there is a taxonomy field "City" and there are about 1,000 cities. You may want to search for all cities that start with "San" e.g. San Diego, San Francisco, San Jose ... currently this would not be possible because you would get results from all content types if they have "San" anywhere in the body.

A way to get around the above would be to use CCK taxonomy: CCK facets would allow the cities to be exposed as facets and field_indexer would allow them to be searched.

@David: Is my understanding correct? I haven't tried my suggested workaround -- do you think it will work?

sidharth_k’s picture

sidharth_k commented

Wait ... this gets confusing:

OPTION A

CCK Facets is a bundle of modules that integrate with Faceted Search to expose Content Construction Kit (CCK) fields as facets. This allows users to browse field values and to filter search results with those values.

The supported CCK field types are:

* Text
* Number
* Node Reference
* User Reference
* Date
* Datestamp

From http://drupal.org/project/cck_facets

OPTION B

CCK Field Indexer: Implements indexing for CCK fields.

From http://drupal.org/project/field_indexer

If Option A is what the field indexer uses... its pretty clear that CCK Taxonomy Fields will not be picked up by the field Indexer.

If Option B is what the field indexer user: Its not clear to me whether or not the CCK Taxonomy fields will be picked up by the field indexer.

Someone please clarify :-) !

david lesieur’s picture

david lesieur commented

There are not really any relationships between the CCK Facets module and the CCK support in Field Indexer. The facets are just for browsing field content.

Normally, Field Indexer should pick up any CCK field, including your CCK Taxonomy Fields (or Content Taxonomy, if you're using Drupal 6). I have never tried that option, but it seems worth trying!

However, even if that works as it should, I would still consider implementing a Field Indexer sub-module for taxonomy a good idea, as that would still be simpler to use and maintain.

Ela’s picture

Ela commented

just curious.. did you try this out and did it work for you?

david lesieur’s picture

david lesieur commented

Unfortunately, I never got to implement this. Still an interesting idea though.

zacho’s picture

zacho commented

I accomplished this with a Computed Field (http://drupal.org/project/computed_field) and and a little bit of code inspired by this post: http://www.agileapproach.com/blog-entry/computed-field-module-and-how-it...

chris_car’s picture

chris_car commented

@zacho So you created a computed field which fetches the taxonomy term id from your content taxonomy field, gets the string term for it and stores it in a text field, so it can be indexed?