Unite Harvest- and Post-Process-Plugins #443
Description
While developing the structure of the provenance data in #442 (see here) I thought about the post-process step.
Its purpose is to update the metadata sources with the new data from the deposit step. But it could also be used to update the sources with the data from the other sources which is merged and curated at this point.
For example a new member has commited to the project on GitHub but is not mentioned in the pyproject.toml. The git plugin would harvest the information about the new user, a human would approve the changes and than the new name is written into the pyproject.toml by the pyproject plugin.
Therefor I suggest to unite the harvest- and post-process-plugins. Each harvest-plugin could implement the option to update their source or don't do so. This would require the deposit plugins to update the metadata e.g. with the new id on Zenodo. As plugins are enabled for each step separatly the user can toggle the harvesting and the post-processing function of each united plugin separatly.