Update formatscaper according to identified requirements
During test runs, we saw that a "flat" assessment of endangerment status per file format ("endangered" vs. "safe") isn't enough. Even if a file format is at risk of becoming obsolete (or is already dead), this doesn't necessarily mean that a dataset containing such files is necessarily at risk (e.g. vim swap files likely just end up in the dataset accidentally and could be removed).
As such, we started following more of a risk management approach by evaluating the risk for each file, based on the probability of its format becoming obsolete, and the impact severity in case this file becomes uninterpretable.
Merge request reports
Activity
Filter activity
added 1 commit
- f839cffc - Add a unique constraint for filenames per record
mentioned in commit 101b6422
Please register or sign in to reply