DSIndexer dependency (outside org.dspace.search) removal: (complete)
====
Removed (unused) java class import from MediaFilter
Removed ItemImport DSIndexer.setBatchProcessingMode references, removed java class import
Removed FlyWay allback to DatabaseLegacyReindexer, removed DatabaseLegacyReindexer class
DSQuery dependency (outside org.dspace.search) removal: (WIP)
====
Removed org.dspace.app.webui.search.LuceneRequestProcessor and dependencies/imports in:
- its reference in dspace.cfg, JSPUI Discovery section, updated comments to reflect removal
- (unused) class import in org.dspace.app.webui.servlet.AdvancedSearchServlet
- (unused) class import in org.dspace.app.webui.servlet.OpenSearchServlet
- (unused) class import in org.dspace.app.webui.servlet.SimpleSearchServlet
- (unused) class import in org.dspace.app.webui.servlet.admin.ItemMapServlet
Removed org.dspace.xmlui.aspect.adminstrative.mapper.LuceneSearchRequestProcessor and its reference in dspace.cfg, XMLUI Discovery section, updated comments to reflect removal.
Notes: org.dspace.app.webui.search now only contains SearchRequestProcessor and
SearchProcessorException. SearchReqeuestProcessor is now only implemented by
org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor. Would it make sense to move
these classes into org.dspace.app.webui.discovery and refactor references to
SearchProcessorException accordingly? Or is it safer for unknown customisations to leave as
is?
org.dspace.app.xmlui.opensearch.DiscoveryOpenSearchGenerator and
org.dspace.app.xmlui.opensearch.StandardOpenSearchGenerator had their summary comments mixed
up - I swapped these back around. No removal of StandardOpenSearchGenerator yet, needs closer
inspection of usage in sitemap, pattern mapping etc.
This PR adds the posibility to define in input-forms.xml that language
tags should be added to selected metadata fields. This possibility is
limited to fields of the following input types: onebox, twobox and
textarea.
Setting Solr's default search operator to AND for the Discovery index leads to
search behaviour that's closer to what our users expect -- "do what Google
does". There is a configuration option for the search operator in dspace.cfg.
However, that setting is used only by the legacy DSQuery class for the now
deprecated Lucene-based search.
