That's good to hear, Tim. I was mistaken about Browse by still using
Lucene. Recently I found some metadata out of date on our DSpace instance,
and it turns out I had to re-activate the Lucene indexing cron jobs which I
had disabled after upgrading to DSpace 4.x last year. But actually this was
After upgrade from DSpace 3.3 to 5.2 I run dspace -f -d -v and get this
output:
Using DSpace installation in: C:\DSPACE
Creating browse indexes for DSpace
init complete (15 ms)
Deleting browse tables
Deleting old indices
Checking for bi_1
Checking for bi_1_dis
... doesn't exist; but
2 matches
Mail list logo
