Howdy, I'm in the process of vacuuming-up some extraneous and redundant metadata on a slew of legacy collections while also been trying to resolve a very odd and vexing issue with Discovery results.
The first, and most obvious issue is a facet "*|||*" which does not actually connect to any collections' items: https://imgur.com/KzJPrNE Clicking on the slug results in ZERO results: https://imgur.com/p60c66e Further, under some of the facets, these added results...um...result: https://imgur.com/VLclHoI ...additional facets are created as a progressive concatenation of each the main facet's lowercased characters (except the first), delineated with that "*|||*". https://imgur.com/ZC14vwc I've rebuilt DS and completely flushed and reindexed the Solr-data after fiddling with the Discovery configurations, and out of desperation (since that "*|||*" delimiter was no where to be found in the data or elsewhere in the code besides the *discovery.** files) went as far as converting the *searchFilterSubject *bean settings from a *HierarchicalSidebarFacetConfiguration *to a *DiscoverySearchFilterFacet* in *discovery.xml*...no dice: * <!--FITZ - 20220307 - converted from HierarchicalSidebarFacetConfiguration -> DiscoverySearchFilterFacet -->* * <!--<bean id="searchFilterSubject" class="org.dspace.discovery.configuration.HierarchicalSidebarFacetConfiguration">-->* * <bean id="searchFilterSubject" class="org.dspace.discovery.configuration.DiscoverySearchFilterFacet">* * <property name="indexFieldName" value="subject" />* * <property name="metadataFields">* * <list>* * <value>dc.subject.*</value>* * <value>dcterms.subject</value>* * </list>* * </property>* * <property name="facetLimit" value="10" />* * <property name="sortOrderSidebar" value="COUNT" />* * <property name="sortOrderFilterPage" value="COUNT" />* * <!--<property name="splitter" value="|||" />-->* * </bean>* Furthermore, I even removed references to this delimiter in *discovery.cfg*: *# Value used for the namedresourcetype facet used by the mydspace* *# <sort-value>\n|||\n<display-value>###<authority-value>* *# the separator between the sort-value and the display-value \n|||\n must* *# match the value of the discovery.solr.facets.split.char defined above* *# the sort-value can be used to force a fixed order for the facet if it is* *# configured in the discovery.xml to be sorted by value* *#FITZ - 20220307 - Not sure where the following got dropped in v6.4* *#discovery.facet.namedtype.item = 000item\n|||\nArchived###item* *#discovery.facet.namedtype.workspace = 001workspace\n|||\nWorkspace###workspace* *#discovery.facet.namedtype.workflow.item = 002workflow\n|||\nWorkflow###workflow* *#discovery.facet.namedtype.workflow.claimed = 003workflow\n|||\nValidation###validation* *#discovery.facet.namedtype.workflow.pooled = 004workflow\n|||\nWaiting for Controller###waitingforcontroller* As you might notice in my code-notes, I was surprised to find that the REM'ed code appears to not actually be part of DS 6.4, but is in DS 7.2 . I'm a bit embarrassed since I've been actively testing a DS 7.2 instance in conjunction with the DS 6.4 metadata cleanup, so it's likely I'd inadvertently included those removed-lines in my troubleshooing. In any case, if someone could shed some much needed light on this, I'd be truly grateful; I've been pulling out my long-overdue-for-a-cut COVID-hair for far too long. -John -- 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/486b902e-42c8-4b97-bf30-eaa851f8c50dn%40googlegroups.com.
