Another Duplicate File Issue: Stuck in the middle with you.

See RT 295094, Julian mentioned some intermittent issue uploading files where it failed with the dupe files message:

The first time I tried to upload both files at the same time by dragging them both into the window, after the progress bar for both files filled up, I got an error message about a duplicate file name "0V". I thought it would happen again and planned to take a screenshot then, but it didn't happen when I tried uploading the files a second time.

When I hit cancel and tried the second time, I dragged one file in first, waited for it to load, which took a few seconds, and dragged the second file in. And I didn't get an error for either file. So I tried dragging both files in so I could copy the duplicate file name error, but both files uploaded successfully.

I hit cancel again and asked the depositor to try uploading both files again.

There are 68 files with the file name "0V".

The dataset, doi:10.7910/DVN/OJHYZA has 68 duplicate files named 0V. This likely occurred through a loop hole in an earlier version of Dataverse, maybe 5.0.

There are also 2 duplicate files named 0.5V. There may be others. Not sure whether fixing them entails only renaming them in a new draft or in the existing published version since it is an illegal state and may cause other issues at a later date.

The reason this became an issue is that you cannot upload or save any changes to files until these dupes are fixed.

1. Upload 2 new files, save, fails with error: × The files could not be updated. – Duplicate filenames: 0V
2. Rename all 68 0V files in UI, save, fails with error: × The files could not be updated. – Duplicate filenames: 0.5V

No source file or test is named. Reproduce the duplicate-filename failures in the upload and dataset file-editing UI using the steps and dataset in the report, then trace the validation and save workflow. Done should include a decided and tested way to handle existing duplicate files without blocking uploads or changes.