Versions Compared

Old Version 15

changes.mady.by.user Robin Taylor

Saved on

compared with

New Version 16

changes.mady.by.user Andrea Bollini (4Science)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: browse configuration to include DAO settings (related to the SOLR Browse work) and show frequencies

...

Property:

webui.browse.index.<n >

Example Value:

{{webui.browse.index.1 = dateissued:metadata:dc.date.issued:date:full }}

Informational Note:

This is an example of how one "Defines the Indexes". See Defining the Indexes in the next sub-section.

Property:

webui.itemlist.sort-option.<n >

Example Value:

webui.itemlist.sort-option.1 = title:dc.title:title

Informational Note:

This is an example of how one "Defines the Sort Options". See Defining Sort Options in the following sub-section.

Defining the storage of the Browse Data.

Info
Starting from DSpace 3.0 you can configure which implementation use for the Browse DAOs both for create/update operations than for read operations.

Property:

browseDAO.class

Example Value:

browseDAO.class = org.dspace.browse.SolrBrowseDAO

Informational Note:

This property configures the java class that is used for READ operations by the Browse System. You need to have Discovery enabled to use the SOLR Browse DAOs

Property:

browseCreateDAO.class

Example Value:

browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO

Informational Note:

This property configures the java class that is used for WRITE operations by the Browse System. You need to have Discovery enabled to use the SOLR Browse DAOs

Note

If DAOs configuration is not provided the system will use the out-of-box implementation available for your DMBS (PostgreSQL or Oracle)

Configure the browse system to use SOLR DAOs
Warning

Use of SOLR DAOs for the Browse System requires that you have Discovery enabled. Please check the Discovery configuration section

the configuration is as follow

Code Block
browseDAO.class = org.dspace.browse.SolrBrowseDAO
browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO
Configure the browse system to use PostgreSQL DAOs

the configuration is as follow

Code Block
browseDAO.class = org.dspace.browse.BrowseDAOPostgres
browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres
Configure the browse system to use Oracle DAOs

the configuration is as follow

Code Block
browseDAO.class = org.dspace.browse.BrowseDAOOracle
browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOOracle

Defining the Indexes.

DSpace arrives with four default indexes already defined: author, title, date issued, and subjects. Users may also define additional indexes or re-configure the current indexes for different levels of specificity. For example, the default entries that appear in the dspace.cfg as default installation:

...

We set other browse values in the following section.

Property:webui.browse.metadata.show-freq.< n >
Example Value:webui.browse.metadata.show-freq.1 = false
Informational Note:This enable/disable the show of frequencies (count) in metadata browse < n > refers to the browse configuration. As default frequencies are shown for all metadata browse

Property:

webui.browse.value_columns.max

Example Value:

webui.browse.value_columns.max = 500

Informational Note:

This sets the options for the size (number of characters) of the fields stored in the database. The default is 0, which is unlimited size for fields holding indexed data. Some database implementations (e.g. Oracle) will enforce their own limit on this field size. Reducing the field size will decrease the potential size of your database and increase the speed of the browse, but it will also increase the chance of mis-ordering of similar fields. The values are commented out, but proposed values for reasonably performance versus result quality. This affects the size of field for the browse value (this will affect display, and value sorting )

Property:

webui.browse.sort_columns.max

Example Value:

webui.browse.sort_columns.max = 200

Informational Note:

Size of field for hidden sort columns (this will affect only sorting, not display). Commented out as default.

Property:

webui.browse.value_columns.omission_mark

Example Value:

webui.browse.value_columns.omission_mark = ...

Informational Note:

Omission mark to be placed after truncated strings in display. The default is "...".

Property:

plugin.named.org.dspace.sort.OrderFormatDelegate

Example Value:

Code Block
plugin.named.org.dspace.sort.OrderFormatDelegate = \
org.dspace.sort.OrderFormatTitleMarc21=title

Informational Note:

This sets the option for how the indexes are sorted. All sort normalizations are carried out by the OrderFormatDelegate. The plugin manager can be used to specify your own delegates for each datatype. The default datatypes (and delegates) are:

Code Block
author = org.dspace.sort.OrderFormatAuthor
title  = org.dspace.sort.OrderFormatTitle
text   = org.dspace.sort.OrderFormatText

If you redefine a default datatype here, the configuration will be used in preferences to the default. However, if you do not explicitly redefine a datatype, then the default will still be used in addition to the datatypes you do specify. As of DSpace release 1.5.2, the multi-lingual MARC21 title ordering is configured as default, as shown in the example above. To use the previous title ordering (before release 1.5.2), comment out the configuration in your dspace.cfg file.

...

The XML Logger plugin is provided as the class org.dspace.app.statistics.UsageEventXMLLogger. It writes event records to a file in a simple XML-like format. If left unconfigured, an error will be noted in the DSpace log and no file will be produced. To specify the file path, provide an absolute path as the value for usageEvent.xmlLogger.file in dspace.cfg.

 webui.browse.metadata.show-freq.1 = false
# webui.browse.metadata.show-freq.2 = false