Alan Orth
Alan Orth
Your proposal sounds good, though it seems the opposite was done in https://github.com/DSpace/DSpace/pull/8924 a few years ago?
Thanks @mwoodiupui. I ported this patch to DSpace 7.6 and tested resolving a handle using the built-in HTTP resolver. [9864-dspace-7_x.patch.txt](https://github.com/user-attachments/files/17227594/9864-dspace-7_x.patch.txt) (only contains the functional changes in `dspace-api`, not the tests...
Another data point for this: we've been having problems with Altmetric not tracking our content since we upgraded to DSpace 7. After discussing with them we realized their bot does...
> A version for DSpace 7.6 is in production here. Running in production on DSpace 7.6 for a week now here as well.
Hey @misilot. Which patch did you use? I manually ported it in my branch of 7.6.3-SNAPSHOT as of a week or two ago and it's working: https://github.com/ilri/DSpace/commit/374069565a9a963c00d21e0de1437eb0dc91b8a4
The patch in this PR is against `main` so there has been some divergence from 7.6 I guess.
I've found a side effect of this patch: collection subscriptions now display the object paths instead of legacy handle paths. Email from before I applied the patch: ``` This email...
Another side effect of this patch is that it breaks the DSONameService, used to find the names of DSpace objects, for example here on the site statistics page: ![Screenshot 2025-02-12...
> @alanorth Regarding the subscription emails: is there a problem or only a surprise? What should we be showing there? Hey @mwoodiupui, historically we showed the Handles here and this...
Hi @mwoodiupui, according to my notes from #9994 the DSpace 6 behavior was to show the canonical hdl.handle.net form: ``` New items are available in the collections you have subscribed...