[ad_1]
Hi Kurt,
Really appreciate the ongoing feedback and requests you provide, it’s always welcome!
This is a valid idea, but I do feel it stands a little beyond the scope of the plugin. This plugin is built to support most common use-cases of data import from podcast RSS feeds.
It just feels a little out of scope to start mapping the different fields manually as it does, sort of, change the whole concept of the plugin.
If there’s a need that can be relevant to several users, we’d definitely think about it, and streamline that need into a properly built feature rather than an open-ended option to map any key to any custom field.
I do understand that this could help, but it’s also adding a ton of complexity (both for users and for supporting the dev side). There are several plugins like WP All Import and similar that would let you map each and every field from any source (including RSS feeds) to WP, maybe that could be more relevant.
(although it’s not podcast-specific and probably missing a few options too)
Our plugin is meant to be easy to use while robust enough to support the vast majority of the use-cases, so in this case I’ll probably say that this is beyond what we’re trying to build with this plugin.
For now, I’ll close this ticket, but if at some point in the future we change our minds – you’ll be the first to know!