Feature #22076
Updated by Peter Amstutz 3 months ago
Accessed by making a POST request to the root of the (WebDAV endpoint) for the collection on keep-web. Works by PDH or UUID.
Should work the same whether using the "inline" or "download only" endpoint. Must be the collection root, not a subdirectory.
Indicate that it should be a zipfile by providing the header @Accept: application/zip@ (confirm that is the right MIME type).
The POST body is either empty (get the whole collection), or a JSON array of strings which are paths within the collection to be included in the zip.
These are files or directories, if a path goes to a directory then it gets the entire contents of that directory. If there is both a reference to a subdirectory and to a specific file within that subdirectory, it gets the whole subdirectory (the file reference is redundant).
The list of files/directories should be sorted so they always download in the same order.
The zip file should be streamed to avoid excessive copying or use of staging storage.
If any of the file paths requested do not exist in the collection, return an error.
h2. Check with customer
We probably do not need to support Range requests, this will be confirmed with customer.
We probably don't need to compress the files, but need to check.
Consider including the ".arvados#collection" file in the zip with the collection metadata.