This is an attempt to link up some related issues (http://drupal.org/node/784928, http://drupal.org/node/624664) in the Managing News project queue with the great work that's been done on allowing node imports to inherit terms that are assigned to the "parent" feed. (Inherit settings from parent feed node (like taxonomy))

Managing News, for good reason, does not create nodes for every item that's imported, instead using the Data module and the Feeds module's Data Processor. Unfortunately, that means you can't use the patched FeedsNodeProcessor.inc to set up taxonomy inheritance for Managing News feeds -- that functionality would have to live in FeedsDataProcessor.inc instead.

For me, that's a problem, as we'd like to map news items to their source as well as to whatever location terms happen to pop up in the text of an individual item. And obviously there are others who want to do the same thing.

alex_b has posted in the Managing News queue that it's still TBD whether taxonomy inheritance will be part of a future release. I'm posting here to cast my vote for it -- and to link together the different issue threads for others who might be interested, or who have the chops to think about patching FeedsDataProcessor.inc!

(Note: The version is set for 6.x-1.0-alpha14, as that's what is packaged in the latest release -- 1.0-beta9 -- of Managing News)

Comments

cglusky’s picture

cglusky commented

Thanks for starting this @TKS. As I mentioned over at #784928: Taxonomy inheritance my gut is telling me it's not worth trying to support inheritance via Data. You can see from all the node properties that people want to possibly inherit you may as well use the Node processor. I agree that Data gives you more efficiency when you do not want the overhead of a full node to save simple items, but where is the point that is no longer true? I do not really know but I will stick with my gut and say that if you want to inherent stuff from the Feed node then stick with a node processor.

alex_b’s picture

alex_b commented
Version: 6.x-1.0-alpha14 » 6.x-1.x-dev

I think this is a reasonable feature request.

but where is the point that is no longer true?

If you can take the performance hit of saving (and more expensively in comparison to data) deleting nodes at a very high rate. I.e. if you don't aggregate a lot of stuff.

cglusky’s picture

cglusky commented

@alex_b are you going to allow the same kind/number of properties to be inherited as is being worked on for #632920: Inherit properties from parent feed node (taxonomy, author, OG, language) ? Seems like if you do then you end up potentially recreating a node and it's schema using Data. It's been a few years since I studied SQL but it seems like you could end up with a Data table full of foreign keys in order to pull this off, so is it any more efficient than using a node? The request is for taxonomy and that would be nice but where do you stop? Or does it not matter if you do inherit everything from a parent node and stuff it in a Data table? And those are not meant to be rhetorical - I am very much in student mode here.

alex_b’s picture

alex_b commented

it seems like you could end up with a Data table full of foreign keys in order to pull this off, so is it any more efficient than using a node?

Hehe. You're touching on an interesting point :-) The main differences remain:

- data has a delete API which allows for deleting in one swoop instead of many different delete queries.
- optimization for one dimensional data (key, value).

But indeed, there is more concepting work to be done around Data. Drupal 7 with an entity and field API is going to be very interesting.

cglusky’s picture

cglusky commented

@alex_b - thanks very much for taking the time to educate. it is appreciated.

alex_b’s picture

alex_b commented

Sure - also have a look at #827000-3: Port Data Module to Drupal 7 for a discussion on Data in D7.

David Goode’s picture

David Goode commented

See my comment and patch in the previously mentioned issue for nodes: http://drupal.org/node/632920#comment-3363006

This patch adds the inheritance support to the parser and exposes them as sources, so data works just as well as nodes so long as a mapper exists for that type of information. It was tested with the data processor on MN to associate tags on the feed with tags for the data entries in data_taxonomy.

alex_b’s picture

alex_b commented
Status: Active » Fixed

#632920: Inherit properties from parent feed node (taxonomy, author, OG, language)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.