Deirdre Kirmis (Feb 09 2026 at 23:14): Deirdre Kirmis (Feb 09 2026 at 23:14):Hi there .. we have a dataset where the user uploaded a file in v1, then posted several new revisions, then needed to change that original uploaded file. This person uploaded a new file with the changes, but then realized the old file could just be replaced, so we deleted the new file, made changes to the original file, and replaced it. However, none of these changes appear in the version history for the file or for the dataset. Usually these type of changes do appear in the history. Any ideas?
df-file-changes.jpg
Philip Durbin 🚀 (Feb 10 2026 at 14:46):Hmm, want to try replicating this on https://demo.dataverse.org ?
Deirdre Kirmis (Feb 10 2026 at 16:04):okay I did test on the demo DV .. I uploaded a file > published > uploaded second copy of file > published > deleted second copy > published > made a change to original file and replaced > published .. all of those changes showed in the version history except for the file replacement .. so likely a publish was not done after each step on our side .. makes sense that if not, the version info wouldn't show as the diff is just between published versions ..
.. but there was definitely a publish after the final replacement of the original file .. would that not show a change in version history? (ie: do file changes done via "Replace" show in the version history?)
test 2.jpg
Philip Durbin 🚀 (Feb 10 2026 at 16:32):I'm confused. Are you saying you replaced a file between these two versions?
I'm asking because I see the same file with the same md5.
Deirdre Kirmis (Feb 10 2026 at 21:35):Yea the plot is thickening on this .. @Rachel Fernandez did some detective work here on our repo and noticed that any file that is uploaded via "Replace" is not actually registering the uploaded file. The same thing has happened here, which is why those 2 files are the same. I did a "replace" and publish but the second publish did not capture the changed file. Both files exist on S3 though, so I know it is making it that far. The step to register the changed file to dataverse just does not seem to be happening.
Deirdre Kirmis (Feb 10 2026 at 21:36):We didn't notice originally that the changed file was not showing the changes in the dataset itself.
Philip Durbin 🚀 (Feb 10 2026 at 21:44):smells like a bug :lady_beetle:
Deirdre Kirmis (Feb 10 2026 at 22:02):i will submit a ticket .. i think this could be related to https://github.com/IQSS/dataverse/issues/11976 as we are having that issue as well
Philip Durbin 🚀 (Feb 12 2026 at 16:20):@Deirdre Kirmis thanks for opening this issue!
Replace feature does not replace the file #12157
Philip Durbin 🚀 (Feb 12 2026 at 16:25):I hope you don't mind but I edited the issue to link to this topic on Zulip.
Deirdre Kirmis (Feb 12 2026 at 16:45):oh sure, no problem .. thanks for doing that :slight_smile:
Philip Durbin 🚀 (Feb 12 2026 at 16:47):Sure. Can you also mention in the issue that you were able to reproduce it on demo?
Philip Durbin 🚀 (Feb 12 2026 at 16:47):Also, I'm wondering if you happen to know if replacing file via API is a good workaround.
Deirdre Kirmis (Feb 12 2026 at 19:27):yes will do .. good point on the API .. I tried it and it does seem that the API replaced the file with the changed one correctly (it created a new draft, and the draft file is the new one, and then the published dataset has the correct file
Philip Durbin 🚀 (Feb 12 2026 at 19:52):phew!
Last updated: Apr 03 2026 at 06:08 UTC