Automate the creating (and checking?) of archives for data applicants

Prospectively, it seems both doable and feasible to automate the process of creating and checking data archives that are being delivered to data applicants after the contract has been concluded, at least for the standard cases. The following steps seem "automatable" enough to me, but they have quite some differential in difficulty, so they should probably be implemented in multiple steps:

- [ ] creating the necessary subdirectory
- [ ] copying the data to the archive, preserving the folder structure of each study
- [ ] renaming all data files with the application ID
- [ ] changing the data file format, if necessary/requested
- [ ] creating grouping variables (for federal states)
- [x] compiling the ReadMe file and naming it in a reasonable way (might become weird when someone applies for many studies)
- [ ] creating a checksum (if possible with R)
- [ ] packing the archive into a zip file (if possible with R)

What are your thoughts on this? This suggestion is not urgent but some steps seem easy enough. (Actually, the first two steps I had kind of implemented in that ´checks-and-fixes´ syntax over on Gitlab.)