All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
...
You can independently enable Discovery for XMLUI or JSPUI. Follow the steps below.
...
As with any upgrade procedure, it is highly recommend that you backup your existing data thoroughly. Although upgrades in versions of Solr/Lucene do tend to be forwards forward-compatible for the data stored in the Lucene index, it is always a best practice to backup your [dspace-install-dir]/solr/statistics
cores to assure no data is lost.
config/xmlui.xconf
SearchArtifacts
Uncomment: Discovery
Code Block | ||||
---|---|---|---|---|
| ||||
<xmlui> <aspects> <!-- @deprecated: the Artifact Browser has been devided into ViewArtifacts, BrowseArtifacts, SearchArtifacts <aspect name="Artifact Browser" path="resource://aspects/ArtifactBrowser/" /> --> <aspect name="Displaying Artifacts" path="resource://aspects/ViewArtifacts/" /> <aspect name="Browsing Artifacts" path="resource://aspects/BrowseArtifacts/" /> <!--<aspect name="Searching Artifacts" path="resource://aspects/SearchArtifacts/" />--> <aspect name="Administration" path="resource://aspects/Administrative/" /> <aspect name="E-Person" path="resource://aspects/EPerson/" /> <aspect name="Submission and Workflow" path="resource://aspects/Submission/" /> <aspect name="Statistics" path="resource://aspects/Statistics/" /> <!-- To enable Discovery, uncomment this Aspect that will enable it within your existing XMLUI Also make sure to comment the SearchArtifacts aspect as leaving it on together with discovery will cause UI overlap issues--> <aspect name="Discovery" path="resource://aspects/Discovery/" /> <!-- This aspect tests the various possible DRI features, it helps a theme developer create themes --> <!-- <aspect name="XML Tests" path="resource://aspects/XMLTest/"/> --> </aspects> |
Add discovery to the list of event.dispatcher.default.consumers
Code Block |
---|
# default synchronous dispatcher (same behavior as traditional DSpace) event.dispatcher.default.class = org.dspace.event.BasicDispatcher #event.dispatcher.default.consumers = versioning, search, browse, eperson, harvester event.dispatcher.default.consumers = versioning, search, browse, discovery, eperson, harvester |
Change recent.submissions.count to zero
Code Block |
---|
#Put the recent submissions count to 0 so that discovery can use it's recent submissions, # not doing this when discovery is enabled will cause UI overlap issues #How many recent submissions should be displayed at any one time #recent.submissions.count = 5 recent.submissions.count = 0 |
If all of your traffic runs over port 80, then you need to remove the port from the URL
Code Block |
---|
##### Search Indexing ##### solr.search.server = http://localhost/solr/search |
From the command line, navigate to the [dspace] directory and run the command below to index the content of your DSpace instance into Discovery.
Code Block |
---|
./bin/dspace update-discovery-index |
Panel |
---|
NOTE: This step may take some time if you have a large number of items in your repository. |
...
...
As with any upgrade procedure, it is highly recommend that you backup your existing data thoroughly. Although upgrades in versions of Solr/Lucene do tend to be forwards compatible for the data stored in the Lucene index, it is always a best practice to backup your [dspace-install-dir]/solr/statistics
cores to assure no data is lost.
config/dspace.cfg
org.dspace.app.webui.search.LuceneSearchRequestProcessor
Uncomment: org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor
Code Block | ||||
---|---|---|---|---|
| ||||
plugin.single.org.dspace.app.webui.search.SearchRequestProcessor = \ org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor |
Add discovery to the list of event.dispatcher.default.consumers
Code Block |
---|
# default synchronous dispatcher (same behavior as traditional DSpace) event.dispatcher.default.class = org.dspace.event.BasicDispatcher #event.dispatcher.default.consumers = versioning, search, browse, eperson, harvester event.dispatcher.default.consumers = versioning, search, browse, discovery, eperson, harvester |
Note |
---|
As it is not possible in JSPUI to use both search provider (Lucene and Discovery), it it is generally more appropriate, but not required, to remove the "search" consumer from the list above. The "browse" consumer can be removed as well if you configure the Browse System to use Solr/Discovery as its backend (see Defining the Storage of the Browse Data) |
Enable facet showing in the Repository, Communities and Collections home pages
Code Block |
---|
plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \ org.dspace.app.webui.components.RecentCommunitySubmissions,\ org.dspace.app.webui.discovery.SideBarFacetProcessor plugin.sequence.org.dspace.plugin.CollectionHomeProcessor = \ org.dspace.app.webui.components.RecentCollectionSubmissions,\ org.dspace.app.webui.discovery.SideBarFacetProcessor plugin.sequence.org.dspace.plugin.SiteHomeProcessor = \ org.dspace.app.webui.discovery.SideBarFacetProcessor |
Note |
---|
Please note that JSPUI (in contrast to XMLUI) still relies on the Browse Engine to show "recent submissions". The browse engine can be configured to use Solr/Discovery as its backend (see Defining the Storage of the Browse Data) |
Enable a JSON endpoint to provide the autocompletion feature in the search form
Code Block |
---|
plugin.named.org.dspace.app.webui.json.JSONRequest = \ org.dspace.app.webui.discovery.DiscoveryJSONRequest = discovery |
If all of your traffic runs over port 80, then you need to remove the port from the URL
Code Block |
---|
##### Search Indexing ##### solr.search.server = http://localhost/solr/search |
From the command line, navigate to the [dspace] directory and run the command below to index the content of your DSpace instance into Discovery.
Code Block |
---|
./bin/dspace update-discovery-index |
Panel |
---|
NOTE: This step may take some time if you have a large number of items in your repository. |
...