Package(d) ADO download

[DiegoPino]

What?

This has been in the roadmap as an idea for a while and woke up thanks to @alliomeria today. We have already Frictionless package processing but no formatter for their content yet. But also people have asked/commented in the wild it could be nice to have a way to download a whole Object (ADO) with files, etc.

If we extend the idea, and think about a roundtrip, this concept of allowing a whole ADO to be downloaded as a ZIP file with a manifest, individual streams, etc (a Frictionless data package) could also allow seamless moving of ADOs as a whole (and ingest-able via AMI and/or JSON API) between systems.

This would also (if thought properly) allow users to have different modes (one for admins with the whole knit and caboodle 🧶 ) and one defined at a finer level for end users to download, maybe using a selective ap:tasks key, partial/admin defined subsets? Or maybe driven also by a template? or a global configuration? Or all of them? This might even allow us to package "multiple revisions" and re ingest, if someone wants to keep the whole history of changes, a thing Drupal also by default does not allow via the JSON-API or REST.

I personally like the idea of this being a data package. Very re-usable, consistent even between other platforms and reuses tooling we have.
(e.g we have a post processor that can list/read contents of such already).

The implementation could start with an on-the-fly 🪰 zipper 🤐 of attached files and JSON content protected via permissions/controller) for certain roles. And then extend to configuration and rountrip/re-ingest?

@alliomeria please feel free to comment/add/remove (or use say no/"níl" 🇮🇪 if this makes or not sense) and thanks for bringing back this idea through your pro interaction with our partners.

[DiegoPino]

Connects with
#441

[DiegoPino]

and with esmero/strawberry_runners#39