Difference between revisions of "SUNScholar/Browse Indexes"
m (→PLEASE NOTE:) |
m (→WARNING:) |
||
| Line 45: | Line 45: | ||
====Step 2 - Remove all "bi_" tables==== | ====Step 2 - Remove all "bi_" tables==== | ||
I used [http://www.pgadmin.org pgadmin] to do a "cascade drop" of all the bi_* tables, where bi = browse index. | I used [http://www.pgadmin.org pgadmin] to do a "cascade drop" of all the bi_* tables, where bi = browse index. | ||
| + | |||
| + | ==References== | ||
| + | *https://wiki.duraspace.org/display/DSDOC4x/Configuration+Reference#ConfigurationReference-BrowseIndexConfiguration | ||
| + | *https://jira.duraspace.org/browse/DS-1920 | ||
| + | *https://jira.duraspace.org/browse/DS-1619 | ||
Revision as of 14:57, 30 May 2015
Back to Indexes
Contents
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, 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.
For DSpace 5.X
For DSpace 4.X
WARNING:
If during your upgrade to DSpace =>3.X, you decide to use the SOLR service to deliver indexes, then you need to purge the old PostgreSQL/Oracle database indexes.
Old Index Purge for DSpace =>5.X
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
Old Index Purge for DSpace <=4.X
Check that you have a backup of the database before doing any purging. You have been warned.
Bug reports: https://jira.duraspace.org/browse/DS-2145 and https://jira.duraspace.org/browse/DS-2188 and https://jira.duraspace.org/browse/DS-2578
Step 1 - 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
Step 2 - Remove all "bi_" tables
I used pgadmin to do a "cascade drop" of all the bi_* tables, where bi = browse index.