Hi
feeds are "static" functions that accept a given number of properties and can be optionally be cloned. In a system where for example each user can have its own feed item pulling content into the site, we can just have a feed template and add a new feed for each new user, where the only difference will be the URL where the feed is pulling data from.
This is not scalable at all, and in case we need to change a field mapping, this change has to be propagated to each feed.
Now, a way to ease the setup of such a system would be the possiblity to create some "variables" in the feeds setup.
For example the URL of the feed origin may be just a list of URLs.
Feeds may be updated to full fieldable entities.

Simone

Comments

cimo75 created an issue. See original summary.

MegaChriz’s picture

MegaChriz CreditAttribution: MegaChriz at WebCoo commented
Status: Active » Postponed (maintainer needs more info)

I do not quite understand what you are requesting here, but it sounds like you are requesting big changes. If so, such ideas would fit better in the 8.x-3.x version, which is still in the process of being formed.

the URL of the feed origin may be just a list of URLs

If the source consists of multiple URL's, then perhaps the Feeds Crawler or Feeds Spider module may do the job.

Feeds may be updated to full fieldable entities.

This is the case in the 8.x-3.x version. It is unlikely to happen for the 7.x-2.x version.
Some related issues to this:
#1257314: Ability to attach a feeds source to any entity, not only nodes
#1127696: Attach multiple importers to one content type (in D7)
#856316: Add option to make source URL/file not required for importers attached to nodes

Can you explain your request further? Maybe with steps to take and mockups?