The module already supports aggregating images with every item, but both RSS & ATOM do not have this information in their feeds. So this feature won't be useful unless you have a custom feed that contains an image per item.
The aggregation module is extensible to support such custom feeds, please check the readme file.
As to MP3, I really don't understand what you mean. Could you explain this in detail? And if available, provide me or point me to an XML feed you have in mind?
I think the request here is to just support the generic RSS enclosure tag so that when the feed item node is made there is a field populated with the remote enclosure URL.
Well, if the enclosure is an image, then my module is capable of extracting the image as an image node locally on the server, and linking it to the main article. Not just linking to it like the link to the original URL.
However, if the enclosure is audio/video, then my module is unable to currently handle it. I might add the support to link to it in this case, but I always rather extracting everything rather than just linking to them. I'm looking for a generic way to handle this. Would welcome any suggestions here.
My feeling is that having a generic link for enclosure urls (with just a simple link to the file) would still be useful in addition to extraction handlers. Probably having this as a default method to deal with enclosures would satisfy a wide variety of uses, and then as time goes on various extraction handlers for each file type could be added. And in certain cases, you wouldn't want to import/extract the enclosure because of file size, copyright issues, or strange file types (PDF, .doc).
Comments
Comment #1
Ashraf Amayreh commentedThe module already supports aggregating images with every item, but both RSS & ATOM do not have this information in their feeds. So this feature won't be useful unless you have a custom feed that contains an image per item.
The aggregation module is extensible to support such custom feeds, please check the readme file.
As to MP3, I really don't understand what you mean. Could you explain this in detail? And if available, provide me or point me to an XML feed you have in mind?
Comment #2
zirafa commentedI think the request here is to just support the generic RSS enclosure tag so that when the feed item node is made there is a field populated with the remote enclosure URL.
Comment #3
Ashraf Amayreh commentedWell, if the enclosure is an image, then my module is capable of extracting the image as an image node locally on the server, and linking it to the main article. Not just linking to it like the link to the original URL.
However, if the enclosure is audio/video, then my module is unable to currently handle it. I might add the support to link to it in this case, but I always rather extracting everything rather than just linking to them. I'm looking for a generic way to handle this. Would welcome any suggestions here.
Comment #4
zirafa commentedMy feeling is that having a generic link for enclosure urls (with just a simple link to the file) would still be useful in addition to extraction handlers. Probably having this as a default method to deal with enclosures would satisfy a wide variety of uses, and then as time goes on various extraction handlers for each file type could be added. And in certain cases, you wouldn't want to import/extract the enclosure because of file size, copyright issues, or strange file types (PDF, .doc).
Comment #5
Ashraf Amayreh commentedYes, very interesting. Now the time to implement it is another issue.
It can also be a checkbox inside the feed form, something along the lines of "check this to extract content (if supported) rather than linking to it".
Comment #6
zirafa commentedA checkbox per feed sounds like a good idea.
Comment #7
Ashraf Amayreh commentedI'm getting ready to work on the new wave of features. So I'm moving this to postponed.
Comment #8
Ashraf Amayreh commentedunassigning until I start working on this...