Thanks for the heads up, Tim. This is a trivial change but makes a big difference to users. I'm happy to see DSpace adopt this change. I've applied it to my DSpace 5.x branch and I'm waiting to be lifted up and carried on the shoulders of my editors and users in celebration.
On Wed, May 18, 2016 at 9:01 PM, Tim Donohue <tdono...@duraspace.org> wrote: > Hi Jeff, > > This change to boolean AND searching was made in the upcoming 6.0 release. > See > > https://jira.duraspace.org/browse/DS-2809 > > The actual code changes are here (and they are tiny): > > https://github.com/DSpace/DSpace/pull/1106 > > - Tim > > > On 5/18/2016 11:47 AM, Jeffrey Sheldon wrote: > > This might answer my question: > > https://wiki.apache.org/solr/SchemaXml#Default_query_parser_operator > > Is this the "correct" way to specify this change? > > > -Jeff > > ________________________________________ > From: dspace-tech@googlegroups.com <dspace-tech@googlegroups.com> on behalf > of Jeffrey Sheldon <jshel...@ksu.edu> > Sent: Wednesday, May 18, 2016 11:43 AM > To: dspace-tech@googlegroups.com > Subject: [dspace-tech] Boolean default in Discovery search > > Folks, > > I noticed that the search.operator attribute in dspace.cfg became > depreciated with Discovery. However, I don't see a provision to define > default search boolean logic. Perhaps I'm missing something obvious? > > Example searches (showing that SOLR honors capital boolean arguments > included in the search keywords): > > cow beef: 9924 results > cow OR beef: 9924 results > cow AND beef: 5375 results > > My institution prefers that all searches to be based on AND and not OR as > default. > > The working theory is to enable the defaultFilterQueries area of > config/spring/api/discovery.xml and include some sort of argument there, but > I can't find any examples which support this theory. > > Thoughts? > > > -Jeff > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > > > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspace-tech+unsubscr...@googlegroups.com. > To post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. -- Alan Orth alan.o...@gmail.com https://englishbulgaria.net https://alaninkenya.org https://mjanja.ch "In heaven all the interesting people are missing." ―Friedrich Nietzsche GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0 -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
