JSON API for moving of dependent assets between repositories and backups

[alliomeria]

What is this about?

Per @DiegoPino on the Archipelago Slack #feature-request channel, it would be great to...

• "Use the powerful JSON API to allow seamless moving of dependent assets between repositories and also backups.
  • Right now this is possible out of the box but with a lot of JSON mangling. The reason for that is that JSON API is 1.- mostly atomic (with a few exceptions) but also on query (GET) exposes keys that can not be used directly to POST or PATCH into another instance. These fields include drupal ids, revision ids, uids and a lot of links (internal between resources)."
• What is wanted: "a set of scripts, either directly command line (bash) or Drush that are able to clean up the gets from one repo, restructure (and order) the second repo needs and push them back so we can replicate:
  • Twig templates, Blocks with Content, menus and of Course Digital Objects with all their attached files.
• This is not needed for Configs, only for actual fieldable content.
• This will also allow Admin option of “rebuild your whole repo” based on the existing dostorage folder. ✨
• Another cool feature 😎 of the JSON API is that it allows huge File uploads without PHP file limit restrictions by streaming octets up. We want to replicate that functionality also for webform uploads."