Feature Request: API endpoint to extract ZIP files

Overview of the Feature Request

UC Berkeley would like an endpoint that would superusers to process uploaded ZIP files that were not extracted on their initial upload.

What kind of user is the feature intended for?

Superuser, Sysadmin

What inspired the request?

• At Berkeley, we're still using file-backed storage and the Native API to upload files using DVUploader.
  • For some large files, we need to use a workaround to send a temporary "placeholder" ZIP file which is then replaced by moving a the correct file in the storage location and updating the corresponding row in the database.
• ZIP files added to Dataverse in this way won't be extracted. This is also true for ZIP files uploaded using the Direct Upload method (see Zulip thread).
• However, some other file types, e.g. tabular data, can be reprocessed/reingested by calling an API endpoint.

What existing behavior do you want changed?

n/a

Any brand new behavior do you want to add to Dataverse?

• Add an API endpoint similar to the Reingest a File, Redetect File Type, or Extract NcML endpoints that will start a process to unzip the file.

Any open or closed issues related to this feature request?

#10148

Are you thinking about creating a pull request for this feature?

Not at this point.

Start by comparing the existing Reingest a File, Redetect File Type, and Extract NcML Native API endpoints described in the API guide, then review related issue #10148. Done means a documented endpoint lets an authorized superuser or sysadmin start extraction for an uploaded ZIP file that was not extracted initially.