God morning!
I'm currently stuck on a problem with my dspace 7.6 instance. After a
migration to a new server, I discovered the following problem. If I
tried to access a collection with 100 or more items, the loading process
became quite long and my backend logs (dspace.log) started to fire a
Running "bin/dspace index-discovery -b" command fixed it.
On Monday, September 11, 2023 at 10:26:43 AM UTC+12 Snickers wrote:
> So, I found below configuration from the dspace.cfg file:
>
> webui.browse.index.1 = dateissued:item:dateissued
> webui.browse.index.2 = author:metadata:dc.contributor.*\
So, I found below configuration from the dspace.cfg file:
webui.browse.index.1 = dateissued:item:dateissued
webui.browse.index.2 = author:metadata:dc.contributor.*\,dc.creator:text
webui.browse.index.3 = title:item:title
webui.browse.index.4 = subject:metadata:dc.subject.*:text
Then, I have added
Thanks to everyone for your help on this issue and the issue with the url
showing incorrectly in the BE. The issue seems to been caused by the BE server
not reading the local.cfg file but only the dspace.cfg file. I am not sure
what caused the issue, but once I recreated the local.cfg file fro
