Hi Periklis, Unfortunately, I don't know of an easy way to change that "score" only for communities/collections.
It's worth noting the "score" in this situation is a concept from Apache Solr -- it is the relevancy that Solr determined, based on your query. So, any attempt to update it may require you to customize the way Communities or Collections are being indexed in Apache Solr. I'll admit, this is not an area of the DSpace codebase that I know well (but others may be able to provide better advice). There are also some general guidelines from Apache Solr on increasing the "score" of individual indexed objects (which Solr calls "documents"): https://wiki.apache.org/solr/SolrRelevancyFAQ#How_can_I_increase_the_score_for_specific_documents - Tim On Tue, Oct 2, 2018 at 2:56 AM Periklis Ntanasis <[email protected]> wrote: > Hi Tim, > > Thank you very much for your detailed suggestions. They seem very > promising and I will try them both. > > Do you know by any chance if it is easy to change the "score" for the > communities and collections? I was thinking, if adding an artificial fixed > score to the communities and collections, maybe it could produce the > desired result. > > Thank you, > Periklis > > On Mon, Oct 1, 2018 at 9:38 PM Tim Donohue <[email protected]> wrote: > >> Hello Periklis, >> >> I suspect this is caused by the fact that all DSpace search results sort >> by "score" by default. The "score" is essentially a way of returning the >> objects that look to best match the query. In this situation, I suspect >> that only the closest "matching" communities/collections are appearing on >> your first page of results, while others appear on later pages. >> >> I don't believe we have a sort option available that says "list all >> Communities/Collections *first*". But, you could either add in a custom >> default sort, or change the configuration to return more than 10 results >> (by default). All the sorting/results options are in the "discovery.xml" >> configuration file, which is described in this area of the documentation: >> https://wiki.duraspace.org/display/DSDOC5x/Discovery >> >> Here's where the 10 results (by default) is configured in discovery.xml: >> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/spring/api/discovery.xml#L146 >> (You >> could consider increasing this to 20) >> >> Here's where you can override the default "sort by" (which is by "score" >> by default): >> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/spring/api/discovery.xml#L117 >> >> >> Keep in mind that any changes you make will require restarting Tomcat. >> >> If you have further questions, please ask them on this list. >> >> Tim >> >> >> On Fri, Sep 28, 2018 at 4:00 AM Periklis Ntanasis <[email protected]> >> wrote: >> >>> Hi, >>> >>> I am using DSpace 5.8 with JSPUI. >>> >>> In the simple-search results page there is a section of "Community hits" >>> and one of "Collection hits" before the Items. The results in those 2 >>> sections (if there is any) do not populate the first pages first. For >>> example the first page may contain 3 communities, the second 2 and the >>> third 4. >>> >>> This question has been mentioned before here: http://dspace.2283337.n4. >>> nabble >>> .com/Re-Communities-and-Collections-in-search-results-td4672768.html >>> >>> However, the person who asked the question was more interested in hiding >>> the community and collection hits. >>> >>> I was wondering if there is a configuration option or an easy way to >>> make the community and collection hits populate the first pages first. >>> >>> Thanks in advance, >>> Periklis >>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> 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 >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> 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 [email protected]. >> To post to this group, send email to [email protected]. >> 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 -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
