I have noticed that when sorting files, Newest and Oldest seems to be backwards (at least from my understanding).
I assumed IF I choose "Newest" I should see the most recent file uploaded at the top, BUT I see the oldest at the top. When I then choose "Oldest" sort order, I see the newest at the top.
I see it in my own instance as well as Harvard's:
https://doi.org/10.7910/DVN/KFVIIH
Hmm, that's unfortunate. Steve K. just looked over my shoulder and we agree it seems like a bug. Would you mind opening an issue?
Also, if it's not too much to ask, would you be able to check the SPA to see if the bug is there too? https://beta.dataverse.org/spa/
I think the bug is there too. I just created a dataset in SPA and don't have different file dates BUT, looking at the URL.... it puts
fileSortOrder=desc
in the URL when "Oldest" is selected. That parameter (fileSortOrder) is not in the URL when "Newest" is selected.
Just like V6.2.
What if you add an extra file to this dataset? https://beta.dataverse.org/spa/datasets?persistentId=doi:10.5072/FK2/VFZSSB
I need permission - I am "shlakeuva" on SPA
Aw... let me create a different account to match that one that created that.
Go go go!
Actually, I added a second file here: https://beta.dataverse.org/spa/datasets?persistentId=doi:10.5072/FK2/KCEUO7
I dunno, I think the SPA is fine. What do you think?
Thanks, because I got all my "demo" accounts mixed up.
sorting on SPA is working. Thanks. There is no URL string on SPA when sorting changes. I assume that's as designed?
Issue created: https://github.com/IQSS/dataverse/issues/10742
The issue looks great. Thanks.
I suppose no URL string on SPA is by design. Not sure.
Sherry Lake has marked this topic as resolved.
Last updated: Oct 30 2025 at 06:21 UTC