When collecting records, Cutback should be able to optionally gather metadata about each record item including file size, *nix permissions/times, exif/filetype specific metadata.
Show a warning when this gathered metadata exceeds size of the actual data, causing the act of gathering the record of that file useless (probably a rare instance but totally possible).
If this process is also applied to manifest items, the FileListCalculator class becomes near-obsolete as we would already have that data in most cases. The only time it would be used is when a user chooses both to view progress and not generate the manifest item attributes. In this case, the user should be warned that "hey, we're already generating this data, you might as well save it)
When collecting records, Cutback should be able to optionally gather metadata about each record item including file size, *nix permissions/times, exif/filetype specific metadata.
Show a warning when this gathered metadata exceeds size of the actual data, causing the act of gathering the record of that file useless (probably a rare instance but totally possible).
If this process is also applied to manifest items, the
FileListCalculatorclass becomes near-obsolete as we would already have that data in most cases. The only time it would be used is when a user chooses both to view progress and not generate the manifest item attributes. In this case, the user should be warned that "hey, we're already generating this data, you might as well save it)