Re: [Dspace-tech] Hit-highlighting disappeared
Hi helix84, Hat off to you! My many reckless efforts with updating mirage had resulted in overwriting the discovery settings... A careful rebuilding solved everything and now discovery works and so does hit highlighting... All the best /Yannis -Original Message- From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84 Sent: Monday, December 09, 2013 3:43 PM To: Ioannis Damastianos Panagis Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Hit-highlighting disappeared On Mon, Dec 9, 2013 at 2:55 PM, Ioannis Damastianos Panagis ioannis.pana...@jur.ku.dk wrote: Take a look at this URL [1] The url: http://localhost:8080/xmlui/DRI/discover?query=test is giving me a resource not found. If your DSpace XMLUI is accessible at http://localhost:8080/xmlui/ and you have Discovery enabled, then that URL should be correct. Maybe the problem is that you don't have Discovery enabled, which would be consistent with /discover throwing a 404. Check that you went through all the steps to enable Discovery [1] and that the /discover URL works. Any search should take you to the /discover url if you have Discovery enabled. [dspace]/bin/dspace update-discovery-index -b I'd think that would work, but better try update-discovery-index -f just because that's what the upgrading docs recommend [2]. The difference is described here [3]. [1] https://wiki.duraspace.org/display/DSDOC3x/Discovery#Discovery-StepsrequiredforXMLUI [2] https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+1.8.x+to+3.x [3] https://wiki.duraspace.org/display/DSDOC3x/Discovery#Discovery-DiscoverySolrIndexMaintenance Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Hit-highlighting disappeared
Hi everyone, Although I got hit-highlighting initially working, it has now disappeared after some changes I made to the original Mirage theme, while the settings in discovery.xml seem ok. What I get now in the search results is the attached screenshot. Does anyone have a clue on why is this happening? I am using DSpace 3.2 Cheers, Yannis attachment: search.png-- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Hit-highlighting disappeared
Hi helix84, Thank you for your quick reply. Take a look at this URL [1] The url: http://localhost:8080/xmlui/DRI/discover?query=test is giving me a resource not found. If they do, it's your theme that ignores them. Make sure that you didn't simply copy your modified 1.8 theme to DSpace 3.x, because the 1.8 theme doesn't recognize highlighting. For sure I didn't do that ;) If they don't, the problem is either with configuration or with your indexing (e.g. if you didn't reindex, the highlighting fields wouldn't be created). I reindexed by running: [dspace]/bin/dspace index-init [dspace]/bin/dspace update-discovery-index -b Removing cocoon cache and restarting Tomcat I also ran a query in solr and the element lst name=highlighting is empty. Might it be then that solr needs reindexing? Best Yannis -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Hit-highlighting disappeared
A correction: the element lst name=highlighting is not totally empty but contains elements of the form lst name=2-4/ /Y. -Original Message- From: Ioannis Damastianos Panagis [mailto:ioannis.pana...@jur.ku.dk] Sent: 9. december 2013 14:55 To: heli...@centrum.sk Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Hit-highlighting disappeared Hi helix84, Thank you for your quick reply. Take a look at this URL [1] The url: http://localhost:8080/xmlui/DRI/discover?query=test is giving me a resource not found. If they do, it's your theme that ignores them. Make sure that you didn't simply copy your modified 1.8 theme to DSpace 3.x, because the 1.8 theme doesn't recognize highlighting. For sure I didn't do that ;) If they don't, the problem is either with configuration or with your indexing (e.g. if you didn't reindex, the highlighting fields wouldn't be created). I reindexed by running: [dspace]/bin/dspace index-init [dspace]/bin/dspace update-discovery-index -b Removing cocoon cache and restarting Tomcat I also ran a query in solr and the element lst name=highlighting is empty. Might it be then that solr needs reindexing? Best Yannis -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Cannot change the default browse index fields in Discovery
Hi Emilio, Thanks for your reply. As you said, the browse index in the 3.2 version is taken from Lucene instead of SOLR (because you modify the dspace.cfg instead of /solr/schema.xml). you´d better try to do a dspace index-update (tomcat stopped) (lucene index) instead of dspace update-discovey-index (update the solr index) However, I am using Solr Browse DAO and as it is mentioned here: https://wiki.duraspace.org/pages/viewpage.action?pageId=32474035#ReIndexingContent%28forBrowseorSearch%29-UpdatingtheIndexes and here: https://wiki.duraspace.org/display/DSDOC3x/Discovery#Discovery-DiscoverySolrIndexMaintenance I have to use update-discovery-index. Since it is failing I might return to the conventional Lucene index for the browse :), however it just occurred to me that I 'll have to change /solr/schema.xml although it is not mentioned in the documentation. It is wrong to use extra '.*' for the language you are right. Do you know by any chance why when defining the metadata field for the title, it originally uses only title:item:title. How does it know which metadata field to index? Best Yannis From: emilio lorenzo [mailto:elore...@arvo.es] Sent: Wednesday, December 04, 2013 7:18 PM To: Ioannis Damastianos Panagis; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Cannot change the default browse index fields in Discovery Hi Ioannis El 04/12/2013 17:45, Ioannis Damastianos Panagis escribió: Hello everyone, First of all I am pretty new to DSpace so please show tolerance ;). I 'm using version 3.2 and I am trying to customize the Browse index to use Solr and my own custom metadata. Following the manual I am setting in dspace.cfg something like: webui.browse.index.2 = author:metadata:dc.contributor.*,myschema.mycontributor.author.*:text The reason why I put '.*' after mycontributor.author is because the metadata for some of the files I uploaded have a language qualifier which is en-US That is strange and probably wrong. The language qualifier does not belong to the schema hierachy, so the codification is just schema.field.qualifierI Think it does not support another *. You probably do not need the .* (and probably is wrong) I am updating the Solr index and restarting Tomcat but browsing displays no results, even though I have 3 files. Do I need perhaps to *rebuild* Dspace as required when customizing the Lucene index? As you said, the browse index in the 3.2 version is taken from Lucene instead of SOLR (because you modify the dspace.cfg instead of /solr/schema.xml). you´d better try to do a dspace index-update (tomcat stopped) (lucene index) instead of dspace update-discovey-index (update the solr index) Best luck Emilio -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Cannot change the default browse index fields in Discovery
Update: I got it working and updating correctly. The reason for the initial failure was that I hadn't structures the metadata schema properly, i.e. I had something like test.panagis.author test.panagis.title test.panagis.date which means that all the metadata elements were qualifiers (argh!)... I also followed the update procedure here: http://sourceforge.net/mailarchive/message.php?msg_id=30784046 instead of only running [dspace]/bin/dspace update-discovery-index Best Yannis From: Ioannis Damastianos Panagis [mailto:ioannis.pana...@jur.ku.dk] Sent: Thursday, December 05, 2013 11:17 AM To: emilio lorenzo; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Cannot change the default browse index fields in Discovery Hi Emilio, Thanks for your reply. As you said, the browse index in the 3.2 version is taken from Lucene instead of SOLR (because you modify the dspace.cfg instead of /solr/schema.xml). you´d better try to do a dspace index-update (tomcat stopped) (lucene index) instead of dspace update-discovey-index (update the solr index) However, I am using Solr Browse DAO and as it is mentioned here: https://wiki.duraspace.org/pages/viewpage.action?pageId=32474035#ReIndexingContent%28forBrowseorSearch%29-UpdatingtheIndexes and here: https://wiki.duraspace.org/display/DSDOC3x/Discovery#Discovery-DiscoverySolrIndexMaintenance I have to use update-discovery-index. Since it is failing I might return to the conventional Lucene index for the browse :), however it just occurred to me that I 'll have to change /solr/schema.xml although it is not mentioned in the documentation. It is wrong to use extra '.*' for the language you are right. Do you know by any chance why when defining the metadata field for the title, it originally uses only title:item:title. How does it know which metadata field to index? Best Yannis From: emilio lorenzo [mailto:elore...@arvo.es] Sent: Wednesday, December 04, 2013 7:18 PM To: Ioannis Damastianos Panagis; dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Cannot change the default browse index fields in Discovery Hi Ioannis El 04/12/2013 17:45, Ioannis Damastianos Panagis escribió: Hello everyone, First of all I am pretty new to DSpace so please show tolerance ;). I 'm using version 3.2 and I am trying to customize the Browse index to use Solr and my own custom metadata. Following the manual I am setting in dspace.cfg something like: webui.browse.index.2 = author:metadata:dc.contributor.*,myschema.mycontributor.author.*:text The reason why I put '.*' after mycontributor.author is because the metadata for some of the files I uploaded have a language qualifier which is en-US That is strange and probably wrong. The language qualifier does not belong to the schema hierachy, so the codification is just schema.field.qualifierI Think it does not support another *. You probably do not need the .* (and probably is wrong) I am updating the Solr index and restarting Tomcat but browsing displays no results, even though I have 3 files. Do I need perhaps to *rebuild* Dspace as required when customizing the Lucene index? As you said, the browse index in the 3.2 version is taken from Lucene instead of SOLR (because you modify the dspace.cfg instead of /solr/schema.xml). you´d better try to do a dspace index-update (tomcat stopped) (lucene index) instead of dspace update-discovey-index (update the solr index) Best luck Emilio -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Help on basic editing of Mirage theme
Hello everyone, I am running Dspace 3.2 with XMLUI. I am trying to change inplace the Mirage theme and just for a test to modify the header. So I have tried everything from changing [dspace-src]\dspace-xmlui\src\main\webapp\themes\Mirage\lib\xsl\core\page-structure.xsl, rebuilding dspace, substituting webapps, restarting Tomcat, to directly editing [tomcat]\webapps\xmlui\themes\Mirage\lib\xsl\core\page-structure.xsl , cleaning Cocoon cache and restarting Tomcat. Everytime I am editing xsl:template name=buildHeader ... span id=ds-header-logo-textmirage/span and changing the text between the span to something custom. Do you think there is something wrong with this approach? Should I just copy Mirage to a new template in [dspace-source] and modify the new one? Thank you all in advance Yannis -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Cannot change the default browse index fields in Discovery
Hello everyone, First of all I am pretty new to DSpace so please show tolerance ;). I 'm using version 3.2 and I am trying to customize the Browse index to use Solr and my own custom metadata. Following the manual I am setting in dspace.cfg something like: webui.browse.index.2 = author:metadata:dc.contributor.*,myschema.mycontributor.author.*:text The reason why I put '.*' after mycontributor.author is because the metadata for some of the files I uploaded have a language qualifier which is en-US I am updating the Solr index and restarting Tomcat but browsing displays no results, even though I have 3 files. Do I need perhaps to *rebuild* Dspace as required when customizing the Lucene index? Best, Yannis Ioannis (Yannis) Panagis, PhD Data Specialist Faculty of Law University of Copenhagen iCourts Centre of Excellence for International Courts Studiestraede 6 DK-1455 Copenhagen K ioannis.pana...@jur.ku.dkmailto:ioannis.pana...@jur.ku.dk http://jura.ku.dk/icourts [JUR_bomaerke_UK] inline: image001.gif-- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
