Is it possible to automatically assign a taxonomy term based on feed source? I have over 30 different feeds and would like to use views to slice up the data based on the taxonomy term that I provided. Note, I don't mean the category defined in the feed itself.
Example:
Feed A -> tags term A in feed-item (Terms A&B would be part of the same Vocabulary)
Feed B -> tags term B in feed-item
Otherwise, I think I would have to setup multiple cck definitions per feed source and this seems pretty cumbersome. I think that would be 60 CCK definitions and 30 feed importer definitions as opposed to just 2 cck definitions and 1 feed importer definition.
Thoughts?
Comments
Comment #1
arcane commentedOk I think I found the answer at http://drupal.org/node/1074662
Comment #2
chadwyck commentedHey, did you ever get this to work? I'm having trouble assigning taxonomy by source. I can do it by author, but it just doesn't seem to "take" for the source.
Comment #3
kingandyAssuming you have a separate import per feed, you could set up a dummy field (one not expected in the source feed) and use Feeds Tamper to set it to a different value in each import.
For example: if you had three imports, scraping from BBC News, Yahoo and MSN, you could set up a field in each one called "Source feed" mapped to your "source" taxonomy field. In the BBC import rewrite this to "BBC", in Yahoo's import rewrite it to "Yahoo", etc.
I think if you're scraping from a remote field or URL, Feeds Tamper will provide you with a specific dummy field, "Blank Source" or something?
Comment #4
bluegeek9 commentedDrupal 7 reached end of life and the D7 version of Feeds is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues.
If you still have questions about using Feeds on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #feeds channel on Drupal Slack.
If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome!