Page History
...
For example, the following entries appear in the default DSpace installation:
search.index.1 = author:dc.contributor.*
search.index.2 = author:dc.creator.*
search.index.3 = title:dc.title.*
search.index.4 = keyword:dc.subject.*
search.index.5 = abstract:dc.description.abstract
search.index.6 = author:dc.description.statementofresponsibility
search.index.7 = series:dc.relation.ispartofseries
search.index.8 = abstract:dc.description.tableofcontents
search.index.9 = mime:dc.format.mimetype
search.index.10 = sponsor:dc.description.sponsorship
search.index.11 = id:dc.identifier.*
search.index.11 12 = language:dc.language.iso
The format of each entry is search.index.<id> = <search label> index name> : <schema> . <metadata field>[:index type] where:
| is an incremental number to distinguish each search index entry |
| is the identifier for the search field this index will correspond to |
| is the schema used. Dublin Core (DC) is the default. Others are possible. |
| is the DSpace metadata field to be indexed. |
<index type> | can be used to specify how manipulate the values before indexing. Example: search.index.12 = language:dc.language.iso:inputform Possible values are: text - default, no special treatment. Metadata value are passed to lucene as text timestamp - the values are interpreted as date with second granularity. An additional index postfixed with .year is created with year granularity date - the values are interpreted as date with day granularity. An additional index postfixed with .year is created with year granularity inputform - in addition to the values stored in the metadata the displayed form of this value as derivable from the input-form (in any of the available languages) are stored |
In the example above, search.index.1 and search.index.2 and search.index.3 are configured as the author search field. The author index is created by Lucene indexing all dc.contributor.*,dc.creator.* and description.statementofresponsibility metadata fields.
...
Overview
Content Tools