Page History
...
- Faceted/Filtered Search & Browse (via Solr & DSpace Discovery) - enabled by default since DSpace 4.0
- Traditional Browse & Search (via Lucene & Database tables) - this is disabled by default, it was used in older versions of dspace and is being phased out
This particular page only describes the "Traditional Browse & Search" indexing processes. For more information on Faceted/Filtered Browse & Search, please see DSpace Discovery, in particular Discovery Solr Index Maintenance .
Re-Enabling the legacy Lucene Search and/or DBMS Browse providers
| Warning |
|---|
TO BE COMPLETED TODO: also add the DB-backed itemcounter here (?) |
DBMS Browse ProvidersThe old Lucene/DB search and browse will still work, but will need to be configured to work. The three options are SOLR (default), or Postgres/Lucene, or OracleDB/Lucene. When you set the value to these configs, ensure that at most only one provider is chosen.
| Note |
|---|
If a DAOs configuration is not provided the system will use default to using the SOLR Browse Engine |
Configure
...
search and browse
...
to use PostgreSQL
This option enables the browse engine to store its indexes in PostgreSQL database tables. All browsing is then performed via queries to those database tables. This is the traditional browsing option for users of PostgreSQL. The configuration is as follows:.
Alter dspace.cfg to set the browseDAO to postgres.
| Code Block | ||
|---|---|---|
| ||
browseDAO | ||
| Code Block | ||
browseDAO.class = org.dspace.browse.BrowseDAOPostgres
browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres |
...
Alter dspace.cfg to have ItemCount use Postgres
| Code Block | ||
|---|---|---|
| ||
ItemCountDAO.class = org.dspace.browse.ItemCountDAOPostgres |
Configure search and browse to use Oracle
This option enables the browse engine to store its indexes in Oracle database tables. All browsing is then performed via queries to those database tables. This is the traditional browsing option for users of Oracle. The configuration is as follows:.
Alter dspace.cfg to set the browseDAO to Oracle
| Code Block | ||
|---|---|---|
| ||
browseDAO | ||
| Code Block | ||
browseDAO.class = org.dspace.browse.BrowseDAOOracle browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOOracle |
Alter dspace.cfg to have ItemCount use Oracle
| Code Block | ||
|---|---|---|
| ||
ItemCountDAO.class = org.dspace.browse.BrowseCreateDAOOracleItemCountDAOOracle |
Creating the Browse & Search Indexes
It is possible that the database tables to hold the search and browse data do not exist, so they must be created:
| Code Block | ||
|---|---|---|
| ||
[dspace]/bin/dspace index-db-browse |
To create (or recreate) all the various browse/search indexes that you define as described in this page there are a variety of options available to you. You can see these options below in the command table.
Command used: |
|
Java class: | org.dspace.browse.IndexBrowse |
Arguments short and long forms): | Description |
| Should we rebuild all the indexes, which removes old tables and creates new ones. For use with |
|
|
| Execute all the remove and create SQL against the database. For use with |
| Actually do the indexing. Mutually exclusive with |
|
|
| Write the remove and create SQL to the stdout. For use with |
| Create the tables only, do no attempt to index. Mutually exclusive with |
| Make the tables, and do the indexing. This forces |
| Print extra information to the stdout. If used in conjunction with |
| Delete all the indexes, but do not create new ones. For use with |
| Show this help documentation. Overrides all other arguments. |
...
Overview
Content Tools