Difference between revisions of "SUNScholar/Browse Indexes"
| Line 10: | Line 10: | ||
===[[SUNScholar/Browse Indexes/3.X|For DSpace 3.X]]=== | ===[[SUNScholar/Browse Indexes/3.X|For DSpace 3.X]]=== | ||
==<font color="red">'''OLD INDEX PURGE'''</font>== | ==<font color="red">'''OLD INDEX PURGE'''</font>== | ||
| − | |||
===For DSpace =>5.X=== | ===For DSpace =>5.X=== | ||
A new command has been introduced with DSpace =>5.X. See below for an example. | A new command has been introduced with DSpace =>5.X. See below for an example. | ||
Revision as of 12:03, 19 June 2016
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. With DSpace versions =>3.X, the browse indexes can now be delivered via the SOLR service, if so desired. The browse indexes were previously only delivered via the PostgreSQL/Oracle database service.
Instructions
For DSpace 5.X
For DSpace 4.X
For DSpace 3.X
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
For DSpace <=4.X
Check that you have a backup of the database before doing any purging. You have been warned.
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.
Bug Reports
- https://jira.duraspace.org/browse/DS-2602
- https://jira.duraspace.org/browse/DS-2578
- https://jira.duraspace.org/browse/DS-2188
- https://jira.duraspace.org/browse/DS-2145
- https://jira.duraspace.org/browse/DS-1920
- https://jira.duraspace.org/browse/DS-1619
Check SOLR webapp operation
If you have problems with the SOLR webapp, then complete the following to check its operation.
Install the "lynx" application.
sudo apt-get install lynx
Then type the following in the console:
lynx http://localhost/solr
You should get the following:
If not debug the solr webapp until you can.
Remember to restart the Tomcat server for each change you make to a webapp configuration.
SOLR Help
General
- https://wiki.duraspace.org/display/DSPACE/Solr
- http://lucene.apache.org/solr
- http://wiki.apache.org/solr
Maintaining SOLR
- https://wiki.duraspace.org/display/DSDOC6x/SOLR+Statistics+Maintenance
- https://wiki.duraspace.org/display/DSDOC5x/SOLR+Statistics+Maintenance
DSpace Settings
Querying the SOLR DB
- https://wiki.duraspace.org/display/DSDOC5x/SOLR+Statistics#SOLRStatistics-CustomReporting-QueryingSOLRDirectly
- https://wiki.duraspace.org/display/DSDOC4x/DSpace+Statistics#DSpaceStatistics-CustomReporting-QueryingSOLRDirectly
- https://wiki.duraspace.org/display/DSDOC3x/DSpace+Statistics#DSpaceStatistics-CustomReporting-QueryingSOLRDirectly
Tips
- http://kim-shepherd.blogspot.com/2010/11/discovering-discovery-dspace-solr-tips.html
- http://www.scottphillips.com/2011/10/merging-two-dspace-solr-based-data-sets-together
References
- https://wiki.duraspace.org/display/DSDOC5x/Configuration+Reference#ConfigurationReference-BrowseIndexConfiguration
- https://wiki.duraspace.org/display/DSDOC4x/Configuration+Reference#ConfigurationReference-BrowseIndexConfiguration
- http://wiki.duraspace.org/display/DSDOC3X/Configuration#Configuration-BrowseIndexConfiguration
