Assigning feed items to their own node

Is there a way to create another content type which holds a certain feed so I can change the workflow settings for that particular feed?

Do you mean 'certain importer' when you say 'certain feed'?

Are you looking for attaching an importer to more than one content type?

yes!!

http://drupal.org/project/better_formats

It solved my input filter problem too. Also create a different content type. I dont think there is a way y to create a per feed workflow scenereo.

Subscribe, looking for the same.

What I would like is each feed be mapped to its own content type. e.g. If I have a feed called news, I would like it to be mapped to content type news. However if I have feed for movie show time, I would like to appear on a different content type called movie-times.

Currently all the feeds can only be mapped to one content type i.e feed-item

I would like to switch from feed-api but this feature is holding me up.

#2

Did you consider writing a custom module for this problem that modifies a node on hook_nodeapi('insert') or 'submit' ?

#5

What I would like is each feed be mapped to its own content type. e.g. If I have a feed called news, I would like it to be mapped to content type news.

Couldn't you solve this problem by not using different content types for feed items but a flag on a content type? E. g. a CCK text field with the possible values "news", "show times" etc. If you use one importer for these content types they must be very similar in the first place.

HI

Thanks for the Great module

Topic of this issue "Assigning feed items to their own node" is seems which one i am looking for.

while I am importing all of the nodes are assigned to anonymous user instead of the actual feed node uid.

any help?

I am using latest 6.x-1.0-alpha12

#7 - you are looking for #652180: Assign author of imported nodes

Same issue as #5.

I want to import a list of feeds (in OPML format e.g.) and each feed will be mapped on a different content type. For example, the first feed will be imported using RSS into a "story" content type, the second type using XML into a "shop item" content type.

Alex' suggestion in #6 to use a CCK field wouldn't work here as the feeds content of the RSS feed and the XML feed are very different.

I thought about modifying the Feed Node Processor to store feed items into different content types, based on e.g. a value of your feed list (e.g. your OPML specifies that feed 1 should be processed into content type x, or for that matter any other value parsed by your selected parser). Love to get feedback on this!

#5/#9: you could extend the parser class to expose a mapping source "node type" and extend the FeedsNodeProcessor to accept a mapping target "node type". The mapping source "node type" could be populated based on your custom needs.

Read up on the code in the parser and the processor you're using to figure out how to do this.

@alex_b Here is a first implementation of this idea, implemented as a submodule feeds_multifeeds. The module defines a processor 'FeedsMultiFeedNodeProcessor' subclassing from 'FeedsFeedNodeProcessor' that accepts the target node_type. If set, it creates the feed node of the specified type. If the feed type is not found, it uses the default fallback node type specified in the settings.

I've added a simple unit test that takes an OPML with two feeds. Feed 1 is of type=feed1 and feed 2 of type=feed2. Each of the feeds imports their feed items in the specified content type.

Code can be found at http://github.com/pvhee/feeds_multifeeds

If there is interest, I could make a patch for the feeds module.

Perhaps I missed the solution if it was stated in this thread. I used FeedApi before upgrading to feeds. (FeedApi conflicted with certain modules like activitystream.)

In FeedApi I could create a feed and then select a content type (such as Blog) to process the content to. Blog items were created from this particular feed, and I could use open Calais' sementic proxy to assign terms and retreive additional content.

In Feeds I'm completely missing this node processing option. If I create an importer, I can attach it to a content type but I can't specify a url to retreive content from. So I guess that's not where I need to look. If I create a new feed I can't assign a content type to be created at all.

I use specific feeds to import content from. A blog feed should create blogs, news feeds should create news items, video feeds ... etc.

I feel like I'm just missing something but I nonetheless I can't seem to find the answer. I installed the multifeed module but still the desired option is not showing up....

#12 - Have you checked out the screencasts at http://developmentseed.org/blog/2009/dec/15/importing-and-aggregating-st... ?

I think we have slightly overlapping requests here:

A) Decide on an feed node per feed node basis what content type to create (initial report)
B) Programmatically decide which content type to map an imported record to (#9).

For A) I would still recommend going with #6 (don't use different content types) or alternatively, create different importer configurations on admin/build/feeds, attach them to different content types and configure them to creating different content types of feed items.

B) is actually the tougher nut, I'd like to break it out to #731338: Map to content type

Hi Alex,

Thanks for your quick reply. I was actually looking for option A, yet I can't figure out how to manage this. Because if I create a feed importer, how do I specify which feed to attach the importer to?

For example:
A) I create a feed importer attached to the blog content type that processes imported items to blog nodes

B) I create a feed importer attached to the News article content type that processes imported items to News article nodes

Now..

I) I create a feed and input a blog RSS feed url to retreive items from.

II) I create a second feed and input a news RSS feed url to retreive items from.

I) should be attached to the A) importer and II) should be attached to the B) importer. Yet here I get absolutely stuck. I can have more than one importer yet I cannot specify the desired importer when creating a feed. Neither can I submit an RSS url in the importer settings itself (like it sort of worked with FeedApi, which off course didn't feature the importers.)

I'm sure my logic is faulty in some way. I noticed though, that the quality of imports is better with the new Feeds module and I absolutely love both it and its predecessor. With feeds installed I am able to use many modules that conflicted in someway with FeedAPI, which now makes me very happy. So rolling back to FeedApi is not something I'd like to do but the website I'm using this functionality for depends on its different content types.

And one other thing I would like to ask about; when using FeedAPI I mapped the original URL to a CCK field I created for blogs, news articles, etc. I used this for sematic proxy processing through the Open Calais module suite. However, after upgrading to feeds this mapping doesn't work anymore. My own, custom CCK field does not show up in the feed importer configurations and the CCK field 'URL' that is present in the importer settings does not show up in the Calais Node settings tab. So it's not available for semantic processing, returning the infamous 'URL for semantic proxy is invalid' and tags are therefore no longer applied, nor is additional content retreived.

Thanks in advance for your feedback on this!

I create a feed importer attached to the blog content type that processes imported items to blog nodes

This sounds wrong... usually you would attach an importer to one content type that you then use for creating feed subscriptions, but the subscriptions would actually create another content type configured in the _processor_ settings of the importer - is this the source of confusion?

Open a different issue for OpenCalais/mapping please (here is documentation on building your own mappers: Feeds Mapping API documentation).

Could very well be.... Thanks, I'll go and explore that.

I second that. I eventually rolled back to FeedApi. I also see some trouble with this specific issue for the opencalais and openpublish distributions. But also, I understand there's probably a good reason for the current structure and I acknowledge and appreciate the vast amount of good solid work going into both versions of this module.

@lagerassassin

I can understand (and certainly recognize) your frustration, I have wrestled through the issues associated with this too. Can't even tell you how many times I broke something and had to start over. However, I'm not necessarily convinced the modules are of poor quality. It is just a complex thing to pull off. I guess sometimes it's tempting to forget how much logical depth is required in the technologies we see all around us every day :)

Could you specify what the entry says in your recent log entry report about the cron thing? I have had a problem with that where there was an error that sounded something like attemted to re-run cron when it was already running or something like that. I know how to solve that.

I'd be happy to take a look at other difficulties as well, I've been at this a while now and I managed to get it to work very well with feedAPI. I've dropped Feeds for now, I guess it needs a better adoption of the popular features from FeedAPI.

@lagerassassin

You're welcome and happy to learn you got it all to work out in the end :)

I've added my reply on the youtube issue to its original thread, I had the same issue but found a handy tool for solving it. See this website that allows you to compile your desired youtube feed: http://referd.info/. It outputs a feed that solved the issue for me.

Haha, thanks!

Closing after prolonged period of inactivity.

Ok, sorry for commenting on a closed issue, but I think I've found the answer to the important question one runs into if you are used to feed_api, as I was and is discussed in this thread. In my first attempt (http://drupal.org/node/721270#comment-2702114) I couldn't figure it out and rolled back to feed api. But now, I've seen the light. This info is probably a no brainer for many who are used to feeds. It is intended for those who were used to feed_api, for I believe that's when feeds becomes complicated to setup. At least it was in my case.

The main confusing element is that in feed api you could have multiple feeds and provide feed specific settings on how to handle the items retreived from them. Such as which elements to map to, and what types of nodes to create from said feeds (blog, page, story, etc.). The equivalent of this functionality in feeds, seems to be missing but is actually found through the /import page.

For this use case, as I and lagerassasin wrestled with in this thread, you can basically ignore the feed-item and feed content type. Instead, first you build an importer for your feeds. Say, I have 2 feeds (AA & BB). I have a content type called article and blog. I want items in the AA feed to become articles and BB to become blog items. Also, mapping elements will vary between the two.

So, I create my first importer. I call it AA importer and describe it as "This creates articles from the AA feed"
Then:

• Basic settings: attached to: Use standalone form(this is important!) - Refresh: every 30 minutes - Import: on submission
• Fetcher: http fetcher
• Parcer: Common syndication parser
• Processor: Node processor
• Processor (settings): content type: article - input format: full html - author: anonymous, etc (tune to to your liking)
• Processor (mapping): map at least your title, description. Mapping options can be supplemented with several contrib modules

Now, go to yoursite.com/import. You will find your importer there. Click it and supply your RSS link that you want to retreive content from. Click import, and the magic starts. You have now properly submitted your feed. It will be updated on cron runs from now on, periodically fetching you new nodes. (The latter was unclear to me at first.)

You can repeat this for all the other feeds you desire. My BB feed would be the same as the above, but I would set the processor settings to the blog-item content type. It is basically the same as what happened in feed_api, but very different at the same time.

For the above I used the latest 6.x dev of the feeds module and a D6 stack (off course).

@AlfTheCat
A quick note to say thanks, for coming back 8 months later and updating this thread with your findings. It is this kind of attention to detail and attitude of giving that makes the Drupal community shine for me.
Thank you, you probably cut days off of my project.

(not to mention a great module, many thanks to the Maintainers.)

Hi mrvinch,

Thank you so much for your kind words! It's these kind of nice comments that shape the unique Drupal culture :)
And my sincere appreciation for the Feeds maintainers too, doing wonderful things with this framework.

Good luck!