Inconsistent link generation for items with `dspace.customurl` in search results

[saschaszott]

Description

We have noticed that in the search results, items that have the metadata field dspace.customurl sometimes generate links to the item detail page using the item UUID, and sometimes using the actual value of dspace.customurl. Links should consistently use the same scheme. If dspace.customurl is present, it should be consistently preferred (or documented otherwise).

(Side note: there has been prior discussion about whether we should really use the cris metadata schema for this purpose in DSpace 10.)

A video demonstrating the problem is attached.

• First part: the UUID is used in the link
• Second part: the cris.customurl value is used

Bildschirmaufnahme.2026-03-13.um.15.50.55.mov

The two sections have been clipped from the original video to highlight the effect more clearly.

First Part: item's UUID is used in the link

Second part: value of metadata field dspace.customurl is used

[tdonohue]

@saschaszott : Please make sure to verify that there's nothing that has been cached in your user interface display.

The behavior you describe looks like the behavior that would occur if the first page of results (with the UUID) is cached data, while the later page has reloaded the object and found the custom URL.

To avoid using a cache you can do a hard refresh in your browser or try it in a different browser.