Scripts for summarizing and validating content on the Digital Production Hub, the UGA Libraries' centralized storage for digital objects that are not suitable for our digital preservation system.
Creative Commons Attribution Share Alike 4.0 International
It would be nice if the risk_update.py could continue where it left off if it breaks, rather than starting again from the beginning. The script is slower and (more importantly) makes changes to documents in the accession folders, meaning we either get duplicate information or have to find and reset these edited files.
It already generates update_risk_log.csv with a list of every updated risk, so it could skip anything in that file when restarting.
Only worth it if the scripts breaking continue to come up after this initial development phase. This will depend on how much unanticipated data variation there is.
It would be nice if the risk_update.py could continue where it left off if it breaks, rather than starting again from the beginning. The script is slower and (more importantly) makes changes to documents in the accession folders, meaning we either get duplicate information or have to find and reset these edited files.
It already generates update_risk_log.csv with a list of every updated risk, so it could skip anything in that file when restarting.
Only worth it if the scripts breaking continue to come up after this initial development phase. This will depend on how much unanticipated data variation there is.