Hi!

I found the issue. To filter only items in the default discovery filter 
that appears when we perform an empty search in DSpace 7.6, I modified the 
defaultFilterQueries property in the defaultConfiguration in the file 
<dspace>/config/spring/api/discovery.xml, as shown below:

Before:
<!--The default configuration settings for discovery-->
    <bean id="defaultConfiguration" 
class="org.dspace.discovery.configuration.DiscoveryConfiguration" 
scope="prototype">
...
       <property name="defaultFilterQueries">
            <list>
                <!--Only find items, communities and collections-->
                *<value>(search.resourcetype:Item AND latestVersion:true) 
OR search.resourcetype:Collection OR search.resourcetype:Community</value>*
                <value>-withdrawn:true AND -discoverable:false</value>
            </list>
        </property>
...

After
<!--The default configuration settings for discovery-->
    <bean id="defaultConfiguration" 
class="org.dspace.discovery.configuration.DiscoveryConfiguration" 
scope="prototype">
...
       <property name="defaultFilterQueries">
            <list>
                <!--Only find items, communities and collections-->
*<value>(search.resourcetype:Item AND latestVersion:true)</value>*
                <value>-withdrawn:true AND -discoverable:false</value>
            </list>
        </property>
...


This affected the search for communities and collections when creating new 
subcommunity/collection or item, respectively.

I reverted the modification, and the 'No community found' issue was 
resolved. 

However, now I'm trying to find a way to return only items when performing 
an empty search in the search box of DSpace 7.6, meaning I don't want 
communities and collections to be returned in this search. 

Does anyone know how to achieve this?

Thank you
Manuela Klanovicz Ferreira
On Wednesday, March 6, 2024 at 12:33:37 PM UTC-3 DSpace Technical Support 
wrote:

> Hi,
>
> More than likely either you have a frontend/backend error occurring, or 
> you need to reindex (as your Solr index is outdated).
>
> To look for errors, see the troubleshooting guide: 
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> To reindex, you can run `./dspace index-discovery -b`
>
> Tim
>
> On Tuesday, February 20, 2024 at 5:56:34 AM UTC-6 kla....@gmail.com wrote:
>
>> Hello! 
>>
>> I'm running DSpace 7.6 with a migrated database, apparently successfully, 
>> from DSpace 6.3. 
>>
>> However, when trying to create a new community or a new collection, the 
>> list of communities that could be parent appears empty with the message "No 
>> community found", as can be seen in the attachment, even though there 
>> are several communities in the database. 
>>
>> In the logs, there is only an informational message "2024-02-20 
>> 11:42:07,754 INFO 4843d4f6-7f1c-4ace-977f-a0293e88cab9 
>> 58ea537e-620e-4c52-a1b8-4d22e9fc82a6 
>> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
>> [GET /server/api/discover/search/objects] originated from /home". 
>>
>> I would like to know how to fix this issue. 
>>
>> Thank you for your attention to this matter.
>>
>> Sincerely,
>> Manuela Klanovicz Ferreira
>>
>>
>>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/39045f5a-45b6-4e0d-a52c-ee47ec3586c8n%40googlegroups.com.

Reply via email to