- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
|Table of Contents
DSpace offers two options to index content for Browsing & Searching:
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.
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.
Arguments short and long forms):
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.
Because this command actually deletes existing Browse Index tables, you must stop Tomcat (or your Servlet Container of choice) before executing
[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-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.
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
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:
Examples of new browse indexes that are possible. (The system administrator is reminded to read the section on Browse Index Configuration)
webui.browse.index.6 = series:metadata:dc.relation.ispartofseries:text:single
webui.browse.index.3 = title:metadata:dc.title,dc:title.uniform,dc:relation.ispartofseries:title:full
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.
For information about configuring new Search Indexes, please refer to Configuring Lucene Search Indexes.