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

Crell’s picture

That'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.

berdir’s picture

Aggregator 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 ;)

dawehner’s picture

Version: 8.0.x-dev » 8.1.x-dev
Issue summary: View changes

Moving to 8.1.x

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

wim leers’s picture

Status: Active » Closed (works as designed)
Issue tags: +API-First Initiative

This 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.