Posted by dww on May 19, 2010 at 9:25pm
3 followers
Jump to:
| Project: | iTunes |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
On the site where I'm trying to use this module, my media nodes use a node reference to point to person nodes. That way, I can have landing pages for each person, their own bio fields, embedded view of all media by that person, blah blah blah. So, it'd be nice to configure the podcast to slurp in the node title of the person node from the node reference in the media node, instead of assuming that the author is a text field that's native on the media nodes.
Might be nice to coordinate with drewish on how he'd like this to work before I start hacking a patch. ;)
Comments
#1
humm... this starts to make the case for a pluggable system for converting content into elements. though at this point for pluggins i'm tempted to just add ctools as a dependency.
#2
I'd certainly be in favor of a ctools dependency in general. You're already assuming views, and views is probably going to move towards a ctools dependency in the future, anyway...
However, I'm not exactly sure what level of granularity you're talking about having plugins for, perhaps you could elaborate on that? ;) You mean some kind of plugin system for each field? Or in general a plugin for how to pull the data out of a node to stuff into the feed? If the later, I don't see how that would solve the problem here other than each site having to write its own plugins for their own specific audio node type configuration. So, I'm hoping you mean some kind of plugin for each field, although that could get really unwieldy. Anyway, I haven't thought about this very much, so if you've already figured it out in some detail, I'd love to see a description. Might make more sense in a separate "create plugin system" task, in which case, just link it here and I'll see it. ;)
Thanks,
-Derek
p.s. This seems very similar to #481076: Add choices for the item <itunes:summary> source
#3
Random other thought -- what about using fields in the view itself to define this stuff? E.g. you put all the fields you want in the feed in your view. You can use all the power of views (and relationships) to get exactly what you want, use the field rewriting magic, tokens, etc. And then in the itunes feed style settings there's a UI to map fields from the view to the metadata fields in the feed. Then maybe you don't need an elaborate plugin system, the itunes.module itself doesn't have to manually care about which field holds/points to the audio file, etc.
Is this crazy talk, or am I onto something cool here? ;)
Thanks,
-Derek
#4
I am trying to get this module running and am coming up against a few teething problems which I think are related to this post, sorry if I am off-topic?
Query - how do you map your nodes fields against the elements required by the iTunes feed?
Scenario - i have a node 'itunes media' which has all of the attributes I need, but called user friendly things like 'author' I then need my feed to create the apple spec feed.
Problem - the module seems to map the fields directly to XML feed, therefore in default view I cant change the label or anything similar to map my node fields to the apple fields?
Another problem - I need to create the enclosure tag with attributes inside the tag, how do I do this in the views panel?
I can figure out the basics, and realise that others are using this module so I know I'm missing something but I feel really stuck and puzzled? I saw above ctools - how does that work with this? Can anyone offer any more information?
Thanks for the help - I'm happy to write up a simple userguide for this if I can get from A-Z as there isnt much documentation on this and there is a bit of a learning curve...
Chris