Versions Compared

Old Version 1

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 2

changes.mady.by.user Ivan Masár

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Class
Note
tagcloudGeneral class for the whole tagcloud
tagcloud_1Specific tag class for tag of type 1 (baed based on score)
tagcloud_2Specific tag class for tag of type 2 (baed based on score)
tagcloud_3Specific tag class for tag of type 3 (baed based on score)

Discovery Solr Index Maintenance

Command used:

[dspace]/bin/dspace index-discovery [-cbhf[r <item handle>]]

Java class:

org.dspace.discovery.IndexClient

Arguments (short and long forms):

Description

 

called without any options, will update/clean an existing index

-b

(re)build index, wiping out current one if it exists

-c

clean existing index removing any documents that no longer exist in the db

-f

if updating existing index, force each handle to be reindexed even if uptodate

-h

print this help message

-o

optimize search core

-r <item handle>

remove an Item, Collection or Community from index based on its handle

...

It is strongly recommended to run maintenance on the Discovery Solr index daily occasionally (from crontab or your system's scheduler), to prevent your servlet container from running out of memory:

[dspace]/bin/dspace index-discovery -o

(Since Solr 4, the underlying optimize operation has been discouraged as mostly unnecessary and renamed. See https://issues.apache.org/jira/browse/SOLR-3141).

Advanced Solr Configuration

Discovery is built as an application layer on top of the Solr open source enterprise search server. Therefore, Solr configuration can be applied to the Solr cores that are shipped with DSpace.
The DSpace Solr instance itself now currently runs two cores. One for collection DSpace Solr based "statistics", the other for Discovery Solr based "search".several cores (which means indexes in Solr parlance). The "statistics" core is for collection of DSpace usage events for statistical purposes (if you have been collecting statistics for multiple years, you may have chosen to use sharding and you will see one core per each year collected). The "search" core is used by Discovery for for search and  faceting, for displaying the collection/community hierarchy and item counts. The "authority" core is used by SolrAuthority to store information about authors, including their data imported from the ORCID registry.

Code Block
solr
├── solr.xml
Code Block
solr
├── search
│   ├──└── conf
│    │   ├── admin-extra.html
│   │    ├── elevate.xml
│   │    ├── protwords.txt
│   │    ├── schema.xml
│    │   ├── scripts.conf
│    │   ├── solrconfig.xml
│    │   ├── spellings.txt
│   │    ├── stopwords.txt
│   │    ├── synonyms.txt
│   │    └── xslt
│    │       ├── DRI.xsl
│   │        ├── example.xsl
│    │       ├── example_atom.xsl
│    │       ├── example_rss.xsl
│   │        └── luke.xsl
│   └── conf2
├── solr...xml
└── statistics
    └── conf
        ├── admin-extra.html
        ├── elevate.xml
        ├── protwords.txt
        ├── schema.xml
        ├── scripts.conf
        ├── solrconfig.xml
        ├── spellings.txt
        ├── stopwords.txt
        ├── synonyms.txt
        └── xslt
            ├── example.xsl
            ├── example_atom.xsl
            ├── example_rss.xsl
            └── luke.xsl

Internationalization

Discovery currently has its own messages.xml file, located at dspace/modules/xmlui/src/main/resources/aspects/Discovery/i18n/messages.xml. Should you want to add your own labels for new fields and facets, you may add them either to this file or to the main messages.xml file. Same goes for translations - it's encouraged to submit a single messages_XX.xml file including messages from all the separate messages.xml files in DSpace.