Hi David, Have you removed the references to 'searchFilterIssued' in your discovery index? Personally I would leave the searchFilterIssued uncommented, and remove/comment out the reference from the 'sidebarFacets' in discovery.xml (I have never touched spring-dspace-addon-discovery-configuration-services.xml so I don't know about the configuration in there). e.g. homepageConfiguration -> sidebarFacets or defaultConfiguration -> sidebarFacets. From memory the sidebarFacets and list are still required in those, but you can effectlvely have an empty list if desired.
Regards, Genevieve On Friday, 5 May 2017 05:53:41 UTC+10, David A wrote: > > Hi everybody, > > So I gave up on trying to edit the number of years listed on the sidebar, > and have decided to just remove the date-issued bean from the sidebar > altogether. > > However, even this is presenting a challenge. I thought it would be as > simple as commenting-out or deleting the following from *discovery.xml* > and *spring-dspace-addon-discovery-configuration-services.xml* > > <bean id="searchFilterIssued" > class="org.dspace.discovery.configuration.DiscoverySearchFilterFacet"> > <property name="indexFieldName" value="dateIssued"/> > <property name="metadataFields"> > <list> > <value>dc.date.issued</value> > </list> > </property> > <property name="type" value="date"/> > <property name="facetLimit" value="10"/> > <property name="sortOrder" value="VALUE"/> > </bean> > > But when I comment out or delete this code from those two files, it > triggers a 404 error. This happens, even after resetting the server and > update-discovery-index. > > > <https://lh3.googleusercontent.com/-PTkq5CW7E3A/WQuGZpxmwtI/AAAAAAAACFw/0zYc90BKO7om2p7RWqi9E9e-sG4f086EgCLcB/s1600/Screen%2BShot%2B2017-05-04%2Bat%2B3.33.25%2BPM.png> > > > > Any hints? > > Many thanks, > David > > > On Wednesday, February 15, 2017 at 2:28:26 PM UTC-5, David A wrote: >> >> Hi everybody, >> >> An update: I was able to get over the SSH error and am now able to run >> the update-discovery-index. After looking more at the documentation >> <https://wiki.duraspace.org/display/DSDOC3x/Discovery>, here's what I >> have tried to no avail: >> >> 1. I noticed that unlike Author and Subject sidebar facets, the Date >> Issued facet does not offer a "View more" link for what I presume is the >> default maximum of 10 entries >> 2. So I increased the optional <property name="facetLimit" >> value="15"/> to <bean id="searchFilterIssued"> sidebar facet which sorts >> by >> dc.date.issued >> 3. I made this change in two files: >> 1. >> >> config/spring/discovery/spring-dspace-addon-discovery-configuration-services.xml >> 2. config/spring/api/discovery.xml >> 4. Then, I ran [dspace]/bin/dspace *update-discovery-index* and >> didn't seem to receive an error: >> >> INFO [main] (DSpaceKernelInit.java:52) - Created new kernel: >> >> DSpaceKernel:org.dspace:name=18bbb8f5-f9a8-4b1d-8e94-189ebb8347b0,type=DSpaceKernel:lastLoad=null:loadTime=0:running=false:kernel=null >> INFO [main] (ConfigurationManager.java:1224) - Loading from >> classloader: file:/apps/dspace/config/dspace.cfg >> INFO [main] (ConfigurationManager.java:1224) - Using dspace provided >> log configuration (log.init.config) >> INFO [main] (ConfigurationManager.java:1224) - Loading: >> /apps/dspace/config/log4j.properties >> >> 5. Then I restarted the server >> 6. But the problem persists. >> >> >> Has anybody else encounter this? >> >> FYI, it appears I'm using XMLUI for DSpace version 3.0. >> >> Thanks, >> David >> >> On Fri, Feb 3, 2017 at 2:38 PM, David A wrote: >> >>> Greetings! >>> >>> The "Date Issued" list on the Discovery sidebar of our website >>> <https://fcsktp.ryerson.ca/xmlui/> seems to be stuck at 2015, despite >>> the fact that we have entries for 2016 >>> <https://fcsktp.ryerson.ca/xmlui/discover?filtertype=dateIssued&filter_relational_operator=equals&filter=2016> >>> . >>> The *discover.cfg* and >>> *spring-dspace-addon-discovery-configuration-services.xml* have not >>> been modified recently, so I don't believe the issue lies there. >>> I tried to run update-discovery-index through SSH, and appeared to get >>> some errors (see attached "Terminal Saved Output" file). >>> >>> Does anybody have any tips on how I might resolve this? >>> >>> Many thanks, >>> David >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "DSpace Technical Support" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/dspace-tech/dOno8dXeKns/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected] <javascript:>. >>> To post to this group, send email to [email protected] >>> <javascript:>. >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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.
