When one uploads a file, it is first registered and a rawfile entry is made. If the upload script is aborted, and the file name is then changed somehow (i.e. before upload), it will upload using the new name (same MD5, so match) and create a storedfile entry using the new name.
In rawstatus/views there is get_or_create rawfile, which may have to error on this or change rawfile name. It is assumed the user wants to have another rawfile name. Maybe have guards for when a user switches producer or size or something.
Also interesting to look at the upload, should it actually upload the file name or take that from the rawfile (probably use file name in case they want to change it?)
When one uploads a file, it is first registered and a rawfile entry is made. If the upload script is aborted, and the file name is then changed somehow (i.e. before upload), it will upload using the new name (same MD5, so match) and create a storedfile entry using the new name. In rawstatus/views there is get_or_create rawfile, which may have to error on this or change rawfile name. It is assumed the user wants to have another rawfile name. Maybe have guards for when a user switches producer or size or something. Also interesting to look at the upload, should it actually upload the file name or take that from the rawfile (probably use file name in case they want to change it?)