First, my respect and appreciation to the folks who have weighed into this area and try to make sense out of deeply non-linear, non-conformant info structures.

I'm learning as fast as I can about what can be done with Feeds importers for the various RSS sources out in the wild and hit a problem with an ATOM source.

The feed sample is: https://theconversation.edu.au/profiles/andrew-campbell-3060.atom

Under the <entry> ... <entry> element the feed has tags such as:

<title>...</title>
<content type="html"> ... </content>
<author>
      <name>Andrew Campbell, Director, Research Institute</name>
      <foaf:homepage rdf:resource="http://theconversation.edu.au/profiles/3060"/>
</author>

On import, only the Title field is successfully written to my new feed-item nodes.
Looking at the mapping, I can see that source:title maps cleanly to import:title

However not a single one of the other fields (eg, Body, Date, Author, Source URL) are imported...all for various reasons of mapping incompatibility I suspect.

Let's look at the simplest case, the body text.

Feeds Importer does not seem to gracefully read the source tag content type="html" and translate that to the well-understood field Body.

I cannot see how to create a new source field that will reflect my ATOM source better.

In common_syndication_parser.inc we see this line:

'description' => array('rss:description', 'dc:description', 'content:encoded'),

But it is apparently not flexible enough to pick up content type="html"?

It seemed like Feeds Tamper might be a good tool to use (thanks @twistor!) but actually I could not see an option to "map source field to import field".

Like others, I've already spent several hours prowling through the issue queue and getting a feeling for how complex this can be...but I still haven't actually found an answer to this mapping issue.

Any guidance or assistance much appreciated.

Comments

boabjohn’s picture

Issue summary: View changes

Minor typos cleaned up.

boabjohn’s picture

G'Day all,
Just wondering if there are other ways to investigate this issue? Are there any bright suggestions out there? Seems odd that ATOM is not handled gracefully...
Is Fields Tamper an option in this case? How would I use it?

boabjohn’s picture

G'Day all,
Just a note to say we're still stuck. I have no idea what to describe about this situation other than what's already above.
Any notes of sympathy or actual solutions would be most welcome.
Kind regards, JB

boabjohn’s picture

Issue summary: View changes

Code tags around 'entry'

twistor’s picture

Status: Active » Closed (cannot reproduce)

Sorry for the long delay, I just tested this and things worked as expected.

I couldn't find that exact feed, but I was able to find another one on that site.

Feel free to re-open if you're still having this trouble.