When first installing the module many users will expect it to provide tagging out of the box.

Suggested implementation:

* On node type configuration page, if node type is assigned to an extractor vocabulary and has body field enabled, provide checkbox. Title: "Apply tag extraction" Description: "Enable this option to have tags automatically applied on node update."
* Add configuration option per CCK text field to use in extractor.
* In nodeapi insert and update, call $extractor->extract(); and merge results with existing $node->taxonomy data.

Could model the nodeapi bit on http://api.drupal.org/api/function/_node_index_node/.

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Some potentially relevant code in #795876: Example: Using Extractor to add terms to Content Taxonomy field.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Title: Nodeapi integration » Nodeapi integration: automatic extraction for specific node types
nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Thinking about this more, I'm not sure this is a good idea. It may be better to allow other modules to use extractor as an API. E.g., terms may be better offered as suggestions, a task that's beyond the scope of extractor's core focus.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Included draft Extractor support in this issue on Suggested Terms: #942826: Make pluggable, offer an API.

alex_b’s picture

alex_b commented
Status: Active » Postponed

#3 - yeah, I am a little torn here. Basically, extractor never left the Custom Managing News Module stage and I am not sure it shouldn't. I was put it on d. o. with the plan to eventually merge efforts with auto tagging module. Now there is also the Tagging module which I haven't reviewed so far. Given my very limited bandwidth at the moment, I won't be able to put much work into Extractor and likely leave it as-is. If you have vision and motivation to do more than that, I'd love to talk.

Postponed for now?

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Drafted a spec to try to address the need for common APIs and a separation between front end (UI + data handling) and backend (tag suggestion) solutions: http://groups.drupal.org/node/100179.