SUNScholar/Browse Indexes

Back to Indexes

Introduction

The browse indexes for DSpace can be extensively configured. The configuration allows you to take control of the indexes you wish to browse, and how you wish to present the results.

PLEASE NOTE:

• With DSpace versions 3.X and greater, the browse indexes can be configured to be delivered via the SOLR service, if so desired.
• The browse indexes were previously only delivered via the PostgreSQL/Oracle database service.

WARNING:

Update - 2015/05/26

A new command has been introduced with DSpace =>5.X. See below for an example.

$HOME/bin/dspace index-db-browse -f -d

See step 11 of: https://wiki.duraspace.org/display/DSDOC5x/Upgrading+DSpace

---

---

Instructions to remove old browse index tables, if using SOLR as DAO after an upgrade of DSpace from versions <=1.8.2

These actions are needed to be able to permanently delete items or collections after an upgrade of DSpace from versions <=1.8.2.

---

Fixes committed: https://jira.duraspace.org/browse/DS-2145 and https://jira.duraspace.org/browse/DS-2188 and https://jira.duraspace.org/browse/DS-2578

---

Remove "communities2item" table

Login into the server as the dspace user and then type the following;

sudo -i

su - postgres

psql dspace

DELETE from communities2item;

\q

exit

exit

exit

Remove all "bi_" tables

I used pgadmin to do a "cascade drop" of all the bi_* tables, where bi = browse index.

See the notes link above to view the bug report.

Check that you have a backup of the database before doing this. You have been warned.