The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Hand-waving quite a bit here, but...
It seems like we have a lot of stuff in REST.module and such for getting data *out* of Drupal, but we don't have anything for getting it back *in* to Drupal. But we have a module in core that can already suck in data from external stuff and turn it into native content: aggregator module.
So it seems like what would really round out the Web Services initiative is the ability to take content from Drupal site A and pull it into Drupal site B in this manner.
If there's already a duplicate of this, I apologize.
Comments
Comment #1
Crell commentedThat's the "deserializer" that we've been talking about in various places. The caveat is that the REST approach is more of a push model, where you'd message a site and say "here, have this node" rather than aggregator's pull-based model.
I don't know what it would take to make aggregator parse arbitrary feeds, or in this case to route a specific feed to the existing Serializer/Deserializer support. Aggregator already needs love to eliminate Drupal 3-era code: #1839468: [Followup] Replace aggregator rss parsing with Zend Feed
If someone is interested in working on this I can certainly try to point them in the right direction, although I think Lin Clark would be an even better resource.
Comment #2
berdirAggregator isn't that bad anymore, and we're working on making it better, see for example #1930274: Convert aggregator processors and parsers to plugins.
Zend Feed is a nice idea but not an option until the zend framework guys fix their dependencies (and possibly composer guys their dependency management) so that depending on zend feed doesn't include the complete zend framework, see the issue for details ;)
Comment #3
dawehnerMoving to 8.1.x
Comment #7
wim leersThis would require setting up a matching entity type (with a matching data model). Feeds have a very limited, predefined set of fields. That's a *huge* difference.