Re-download deleted submission files during next pull from aggregate about briefcase HOT 6 CLOSED

Oh, but if someone wants to do the same for media (just handling the delete case), I think that would be good as well.

from briefcase.

@shivam-tripathi regarding this issue i think this solves the problem and i can confirm that the re-downloaded files are exported successfully.
Regarding the file tampering issue that you described above a new issue could be filled so that we could get a detail discussion regarding how to solve that. @yanokwa @rclakmal @lognaturel what do you think?

from briefcase.

@yanokwa i would like to work on this

from briefcase.

@icemc Thank you for finding and documenting this bug. Please send in a PR!

from briefcase.

@yanokwa @icemc This is much more complicated. As I mentioned here, if some one deletes/renames the media file, then upon exporting - the file would be skipped, same thing as with submission xml file.
If we are considering tampering - we should in my opinion consider not just submission xml, but also media files. :)
Also, @icemc you are just considering deletion - what if the file has been renamed? Maybe delete such a file. :)
All this is a big hassle. How to ensure data integrity when the entire storage is being compromised? I think this needs some discussion to prevent tampering - and give warning about the risks involved with the tampering if done intentionally. :)

from briefcase.

I think there's only so much we can really do to save users from themselves. Dragging a submission out actually seems like it'd be an easy thing to do accidentally and I do think it makes sense to try to keep the local briefcase consistent on the next pull in case that does happen. Once a user starts renaming files, I kind of feel like they're on their own! But I can be convinced otherwise if someone wants to create an issue and make an argument for doing deeper integrity checks.

from briefcase.