SUNScholar/Browse Indexes/4.X

Back to Browse Indexes

Introduction
Starting with DSpace versions =>3.2, the DAO engine can now be defined to be one of the following:
 * PostgreSQL
 * Oracle
 * SOLR

Refer: https://wiki.duraspace.org/display/DSPACE/Refactoring+the+DSpace+Domain+Model

See step 1 below to determine which engine to use.

Step 1 - Select DAO (Data Access Objects) Engine
Edit the dspace.cfg file and select the DAO engine by typing as follows: nano $HOME//dspace/config/dspace.cfg Select SOLR DAO engine as per example below:

browseDAO.class = org.dspace.browse.SolrBrowseDAO browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO
 * 1) Browse Configuration ######
 * 2) Define the DAO class to use this must meet your storage choice for
 * 3) the browse system (RDBMS: PostgreSQL or Oracle, Solr).
 * 4) By default, since DSpace 4.0, the Solr implementation is used
 * 5) PostgreSQL:
 * 6) browseDAO.class = org.dspace.browse.BrowseDAOPostgres
 * 7) browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres
 * 8) Oracle:
 * 9) browseDAO.class = org.dspace.browse.BrowseDAOOracle
 * 10) browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOOracle
 * 11) Solr:
 * 1) browseDAO.class = org.dspace.browse.BrowseDAOOracle
 * 2) browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOOracle
 * 3) Solr:
 * 1) Solr:

Step 2 - Setup custom indexes
Modify the following sections of the "dspace.cfg" config file.

Simple and Advanced Search Indexes
Replaced by the "Discovery" search indexes.

Browse Indexes
Go to line 1125 approx in the DSpace config file and modify as desired. webui.browse.index.1 = title:item:title:asc webui.browse.index.2 = author:metadata:dc.contributor.author:text webui.browse.index.3 = advisor:metadata:dc.contributor.advisor:text webui.browse.index.4 = dateissued:metadata:dc.date.issued:date:desc webui.browse.index.5 = subject:metadata:dc.subject.*:text webui.browse.index.6 = type:metadata:dc.type:text  = as per "item" definition above. webui.itemlist.sort-option.1 = title:dc.title:title webui.itemlist.sort-option.2 = dateissued:dc.date.issued:date webui.itemlist.sort-option.3 = dateaccessioned:dc.date.accessioned:date
 * 1) webui.browse.index. = : metadata : (dc schema identifier) : (date | title | text) : (asc | desc)
 * 2) webui.browse.index. = : item : : (asc | desc)
 * 3) SUNScholar browse indexes ###
 * 1) webui.itemlist.sort-option. = : (dc schema identifier) :  (date | title | text) : (show | hide)
 * 2) SUNScholar item lists ###

Author Listing Indexes
Using "nano" modify the following section in the DSpace config file to suit your needs. The default as configured below is to list all contributors.
 * 1) Set the options for how authors are displayed in the browse listing

listed in the webui.browse.author-field = dc.contributor.*
 * 1) Define which field is the author/editor etc listing.  This should be
 * 1) field webui.itemlist.columns, otherwise it will have no effect.
 * 2) This cannot be a field already marked out as a title or a date, as this
 * 3) will also have no effect.  This is used in conjunction with the
 * 4) webui.browse.author-limit field below, to truncate author lists.  For
 * 5) configuring links to author publication lists use webui.browse.link below.
 * 6) (This setting is not used by the XMLUI as it is controlled by your theme)
 * 7) webui.browse.author-field = dc.contributor.author
 * 1) webui.browse.author-field = dc.contributor.author

"et al"
 * 1) define how many authors to display before truncating and completing with
 * 1) (or language pack specific alternative)
 * 2) Use -1 for unlimited (which is what will be used if this option
 * 3) is omitted)
 * 4) webui.browse.author-limit = 3
 * 1) webui.browse.author-limit = 3
 * 1) webui.browse.author-limit = 3

clicked on. share If page, theme) that author webui.browse.link.1 = author:dc.contributor.*
 * 1) which fields should link to other browse listings.  This should associated
 * 2) the name of one of the above browse indices with a metadata field listed
 * 3) in  above.  The form is:
 * 4) webui.browse.link. = :
 * 5) Note that cross linking will only work for fields other than title.
 * 6) The effect this has is to create links to browse views for the item
 * 1) Note that cross linking will only work for fields other than title.
 * 2) The effect this has is to create links to browse views for the item
 * 1) The effect this has is to create links to browse views for the item
 * 1) If it is a "single" type, it will link to a view of all the items which
 * 1) that metadata element in common (i.e. all the papers by a single author).
 * 1) it is a "full" type, it will link to a view of the standard full browse
 * 1) starting with the value of the link clicked on.
 * 2) (This setting is not used by the XMLUI, as links are controlled by your
 * 1) The default below defines the authors to link to other publications by
 * 1) The default below defines the authors to link to other publications by
 * 1) webui.browse.link.1 = author:dc.contributor.author
 * 1) webui.browse.link.1 = author:dc.contributor.author

Recent Submissions Sort

 * 1) Additional configuration for Recent Submissions code ####

recent.submissions.sort-option = dateaccessioned
 * 1) the sort option name (from webui.itemlist.sort-option above) to use for
 * 2) displaying recent submissions.  (this
 * 3) is used by the Recent Submissions system and any other time based
 * 4) browse query such as FeedServlet)

Step 3 - Update messages.xml file
Because we introduced new search and browse indexes above, we need to update the language file to present human readable messages for these new indexes.

Edit the following file: nano $HOME//dspace-xmlui/src/main/webapp/i18n/messages.xml

Add the following to the bottom of the file before the closing   tag.

Also see: Language modification

Step 5 - Rebuild Indexes
 Remember:  Clear the XMLUI cache when logged in as an administrator, after rebuilding the discovery indexes..