Unsupported Release
This documentation relates to DSpace 1.8.x, an old, unsupported version. Looking for another version? See all documentation.
As of January 2015, DSpace 1.8.x is no longer supported. We recommend upgrading to a more recent version of DSpace. See DSpace Software Support Policy.
ReIndexing Content (for Browse or Search)
Overview
DSpace offers two options to index content for Browsing & Searching:
- Traditional Browse & Search (via Lucene & Database indexes) - this is enabled by default
- Faceted/Filtered Browse & Search (via Solr & DSpace Discovery) - available for XMLUI only and disabled by default
This particular page only describes the "Traditional Browse & Search" indexing processes. For more information on Faceted/Filtered Browse & Search, please see DSpace Discovery.
Creating the Browse & Search Indexes
To create (or recreate) all the various browse/search indexes that you define in the Configuration Section there are a variety of options available to you. You can see these options below in the command table.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e7fc5da7-3c2a-4d53-9c4a-3c0f0c062dd1"><ac:plain-text-body><![CDATA[ |
Command used: |
|
]]></ac:plain-text-body></ac:structured-macro> |
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. |
Running the Indexing Programs
Complete Index Regeneration
Requires that you stop Tomcat first
Because this command actually deletes existing Browse Index tables, you must stop Tomcat (or your Servlet Container of choice) before executing index-init
. After the indexing command completes, you can restart Tomcat.
By running [DSDOCDEV:dspace]/bin/dspace index-init
you will completely regenerate your indexes, tearing down all existing tables and reconstructing with the new configuration.
[dspace]/bin/dspace index-init
Updating the Indexes
By running [DSDOCDEV:dspace]/bin/dspace index-update
you will reindex your full browse & search indexes without modifying the DSpace table structure. (This should be your default approach if indexing, for example, via a cron job periodically). Because it does not "tear down" the existing tables, this command can be run while DSpace (and Tomcat or similar) is still running.
[dspace]/bin/dspace index-update
Destroy and Rebuild Browse Tables
You can destroy and rebuild the database, but do not do the indexing. Output the SQL to do this to the screen and a file, as well as executing it against the database, while being verbose. WARNING: This is not really recommended unless you know what you are doing.
At the CLI screen:
[dspace]/bin/dspace index \-r \-t \-p \-v \-x \-o myfile.sql
Indexing Customization
Browse Index Customization
DSpace provides robust browse indexing. It is possible to expand upon the default indexes delivered at the time of the installation. The System Administrator should review Browse Index Configuration to become familiar with the property keys and the definitions used therein before attempting heavy customizations.
Through customization is is possible to:
- Add new browse indexes besides the four that are delivered upon installation. Examples:
- Series
- Specific subject fields (Library of Congress Subject Headings). (It is possible to create a browse index based on a controlled vocabulary or thesaurus.)
- Other metadata schema fields
- Combine metadata fields into one browse
- Combine different metadata schemas in one browse
Examples of new browse indexes that are possible. (The system administrator is reminded to read the section on Browse Index Configuration)
- Add a Series Browse. You want to add a new browse using a previously unused metadata element.
webui.browse.index.6 = series:metadata:dc.relation.ispartofseries:text:single
- Note: the index # need to be adjusted to your browse stanza in the _dspace.cfg_ file. Also, you will need to update your Messages.properties file.
- Combine more than one metadata field into a browse. You may have other title fields used in your repository. You may only want one or two of them added, not all title fields. And/or you may want your series to file in there.
webui.browse.index.3 = title:metadata:dc.title,dc:title.uniform,dc:relation.ispartofseries:title:full
- Separate subject browse. You may want to have a separate subject browse limited to only one type of subject.
webui.browse.index.7 = lcsubject.metdata:dc.subject.lcsh.text:single
As one can see, the choices are limited only by your metadata schema, the metadata, and your imagination.
Because Browse Indexes are stored in database tables, remember to run index-init
after adding any new definitions in the dspace.cfg
to have the indexes created and the data indexed.
Search Index Customization
For information about configuring new Search Indexes, please refer to Configuring Lucene Search Indexes.