Hi, I believe this older email was turned into this ticket: https://github.com/DSpace/DSpace/issues/9419
There's a recent PR that may end up solving that ticket: https://github.com/DSpace/DSpace/pull/9690 It is still being tested/reviewed. That said, we welcome testers from anywhere -- if others find this solution works well, then that will help us to get it added to the DSpace codebase more rapidly. Tim On Tuesday, December 17, 2024 at 8:29:17 PM UTC-6 Diego Brice wrote: > Hi Aroldo. Did you solve this problem? > > El sábado, 21 de octubre de 2023 a la(s) 5:36:22 a.m. UTC+8, Aroldo Rique > Júnior escribió: > >> Hello everybody. >> >> My searches in Dspace 7.5 are searching in metadata that should not be >> indexed. For example: the dc.description.provenance metadata. Some searches >> I do are returning items because the search parameter is within the item's >> dc.description.provenance metadata. >> >> I am following the documentation described in this link: >> https://wiki.lyrasis.org/display/DSDOC7x/Discovery#Discovery-Nonindexedmetadatafields >> >> and I have included the dc.description.provenance metadata in the list of >> those that should not be indexed. >> >> Below I am placing my >> org.dspace.discovery.configuration.DiscoveryConfigurationService bean from >> discovery.xml. Something's missing? Am I doing something wrong? How do I >> stop the dc.description.provenance metadata from being indexed? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *<bean >> id="org.dspace.discovery.configuration.DiscoveryConfigurationService" >> class="org.dspace.discovery.configuration.DiscoveryConfigurationService"> >> <property name="map"> <map> <!--The map >> containing all the settings, the key is used to refer to >> the page (the "site" or a community/collection handle) >> the value-ref is a reference to an identifier of the DiscoveryConfiguration >> format --> <!-- The default entry, DO NOT >> REMOVE the system requires this --> <entry key="default" >> value-ref="defaultConfiguration" /> <!-- Same as the >> "default" configuration, but does NOT filter out older versions of items >> --> <!-- Used to display related items on single-item pages, >> because a relationship does not always point to the latest version of the >> related item --> <entry key="default-relationships" >> value-ref="defaultRelationshipsConfiguration" /> <!--Use >> site to override the default configuration for the home page & default >> discovery page--> <entry key="site" >> value-ref="homepageConfiguration" /> <!--<entry >> key="123456789/7621" value-ref="defaultConfiguration"/>--> >> <!-- Used to show filters and results on MyDSpace --> <!-- >> Do not change the id of special entries or else they won't work --> >> <!-- "workspace" is a special entry to search for your own >> workspace items --> <entry key="workspace" >> value-ref="workspaceConfiguration" /> <entry >> key="supervisedWorkspace" value-ref="supervisedWorkspaceConfiguration" /> >> <!-- "workflow" is a special entry to search for your own >> workflow tasks --> <entry key="workflow" >> value-ref="workflowConfiguration" /> <!-- "workflowAdmin" is >> a special entry to search for all workflow items if you are an >> administrator --> <entry key="workflowAdmin" >> value-ref="workflowAdminConfiguration" /> <!-- "supervision" >> is a special entry to search for all workspace and workflow items if you >> are an administrator --> <entry key="supervision" >> value-ref="supervisionConfiguration" /> <entry >> key="undiscoverable" value-ref="unDiscoverableItems" /> >> <entry key="administrativeView" value-ref="administrativeView" /> >> <entry key="publication" value-ref="publication"/> >> <!-- Same as the "publication" configuration, but does NOT filter out older >> versions of items --> <!-- Used to display related items on >> single-item pages, because a relationship does not always point to the >> latest version of the related item --> <entry >> key="publication-relationships" value-ref="publicationRelationships"/> >> <entry key="person" value-ref="person"/> <!-- Same >> as the "person" configuration, but does NOT filter out older versions of >> items --> <!-- Used to display related items on single-item >> pages, because a relationship does not always point to the latest version >> of the related item --> <entry key="person-relationships" >> value-ref="personRelationships"/> <entry key="orgunit" >> value-ref="orgUnit"/> <!-- Same as the "orgunit" >> configuration, but does NOT filter out older versions of items --> >> <!-- Used to display related items on single-item pages, because a >> relationship does not always point to the latest version of the related >> item --> <entry key="orgunit-relationships" >> value-ref="orgUnitRelationships"/> <entry key="journalissue" >> value-ref="journalIssue"/> <!-- Same as the "journalissue" >> configuration, but does NOT filter out older versions of items --> >> <!-- Used to display related items on single-item pages, because a >> relationship does not always point to the latest version of the related >> item --> <entry key="journalissue-relationships" >> value-ref="journalIssueRelationships"/> <entry >> key="journalvolume" value-ref="journalVolume"/> <!-- Same as >> the "journalvolume" configuration, but does NOT filter out older versions >> of items --> <!-- Used to display related items on >> single-item pages, because a relationship does not always point to the >> latest version of the related item --> <entry >> key="journalvolume-relationships" value-ref="journalVolumeRelationships"/> >> <entry key="journal" value-ref="journal"/> >> <!-- Same as the "journal" configuration, but does NOT filter out older >> versions of items --> <!-- Used to display related items on >> single-item pages, because a relationship does not always point to the >> latest version of the related item --> <entry >> key="journal-relationships" value-ref="journalRelationships"/> >> <entry key="project" value-ref="project"/> <!-- Same as >> the "project" configuration, but does NOT filter out older versions of >> items --> <!-- Used to display related items on single-item >> pages, because a relationship does not always point to the latest version >> of the related item --> <entry key="project-relationships" >> value-ref="projectRelationships"/> <!-- search for an entity >> that can be a Person or an OrgUnit --> <entry >> key="personOrOrgunit" value-ref="personOrOrgunit"/> <!-- >> OpenAIRE4 guidelines - search for an OrgUnit that have a specific >> dc.type=FundingOrganization --> <entry >> key="openAIREFundingAgency" value-ref="openAIREFundingAgency"/> >> <entry key="eperson_claims" value-ref="eperson_claims"/> >> </map> </property> <property name="toIgnoreMetadataFields"> >> <map> <entry> >> <key><util:constant >> static-field="org.dspace.core.Constants.COMMUNITY"/></key> >> <list> <value>dc.rights</value> >> </list> </entry> >> <entry> <key><util:constant >> static-field="org.dspace.core.Constants.COLLECTION"/></key> >> <list> >> <value>dc.rights</value> >> </list> </entry> <entry> >> <key><util:constant static-field="org.dspace.core.Constants.ITEM"/></key> >> <list> >> <value>dc.description.provenance</value> </list> >> </entry> </map> </property> </bean>* >> >> Aroldo >> > -- 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 visit https://groups.google.com/d/msgid/dspace-tech/fe6f4914-99b8-4796-b158-89e295a1e000n%40googlegroups.com.
