Difference between revisions of "SUNScholar/Browse Indexes"
m (→WARNING) |
m (→WARNING) |
||
| Line 11: | Line 11: | ||
==<font color="red">'''WARNING'''</font>== | ==<font color="red">'''WARNING'''</font>== | ||
| − | |||
| − | |||
''Instructions to remove old browse index tables, if using SOLR as DAO after an [[SUNScholar/Upgrading/DSpace/Release_Notes/3.2|upgrade from 1.8.2 to 3.2]]'' | ''Instructions to remove old browse index tables, if using SOLR as DAO after an [[SUNScholar/Upgrading/DSpace/Release_Notes/3.2|upgrade from 1.8.2 to 3.2]]'' | ||
These actions are needed to be able to permanently delete items after the upgrade from 1.8.2 to 3.2. | These actions are needed to be able to permanently delete items after the upgrade from 1.8.2 to 3.2. | ||
| − | + | ---- | |
| + | '''A fix has been committed for DSpace =>5.X, see: 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=== | ===Remove "communities2item" table=== | ||
Login into the server as the '''dspace''' user and then type the following; | Login into the server as the '''dspace''' user and then type the following; | ||
Revision as of 23:37, 19 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 version 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
Instructions to remove old browse index tables, if using SOLR as DAO after an upgrade from 1.8.2 to 3.2
These actions are needed to be able to permanently delete items after the upgrade from 1.8.2 to 3.2.
A fix has been committed for DSpace =>5.X, see: 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.
