There is the library BatchuPloadTools for batchuploads, which in a way passes on knowledge from prior batchupload work. There is also example batchupload folders here which is also helpful. There is no standardized project structure.

A well-defined standard project structure could mean that a newcomer can begin to understand a previous or create a new batchupload without digging in to all code and all documentation (most often in the code aswell as on several places on wikis).

The main advantage would be to not have to read through 100% of the tools library code plus 100 % of example batchupload libraries to know where to look for a specific thing e.g. a pre-existing function for a common task in preprocessing of metadata.

This example from the data science domain might be a good structure and presentation to guide this task.

In theory it would be possible to automatically create and guide the user to input the general parameters such as "batch name", "metadata file location", "metadata file type" and "media files directory" when starting a new batchupload project with e.g.

batchupload new_project from command line just like when starting a Django app etc