Re: [Dspace-tech] Modifying the navigation sidebar item display in XMLUI
Hello Satya, I haven't looked into your question #1 below, but regarding question #2, I was thinking of doing the same thing. I'm new to DSpace customization, but I am getting the desired result by going into my theme's directory and editing lib/xsl/aspect/artifactbrowser/item-list.xsl -- and in place of the xsl:if element that starts like this: xsl:if test=dim:field[@element='date' and @qualifier='issued'] or dim:field[@element='publisher'] I am substituting this: xsl:if test=dim:field[@qualifier='citation'] xsl:text(/xsl:text xsl:value-of select=dim:field[@qualifier='citation']/ xsl:text)/xsl:text /xsl:if I hope this helps, Greg On Jun 25, 2015, at 7:32 AM, Satya wrote: Dear members, 1. I want to change the default browse list in the navigation sidebar of XMLUI. Default Browse list has a link to Communities Collections page. We want to change the link to [baseURL]/handle/2264/1 as we have only one community. Kindly guide where to change to reflect in whole site. 2. Recently additions or browse of records (Title/Author/Date Issues) shows the item in the following way: Title Authors (Publisher) Snippet of Abstract I want to replace the PUBLISHER in bracket to CITATION. Which are the placse to do these customization? -- Regards Satya Ranjan Sahu CSIR-National Institute of Oceanography Goa, India - 403004 -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ 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] New submissions are not searchable
Andrea, Thank you for the clarification about the default behavior, and for the chown advice. Thanks, Greg On Jun 23, 2015, at 12:02 AM, Andrea Schweer wrote: Hi, On 23/06/15 03:58, Murray, Gregory wrote: Thank you very much for this information. It's extremely helpful. I must say I'm very surprised that DSpace doesn't provide full-text searching by default -- only by setting up a cron job or by running the indexing manually. Searching the full text of text-based file formats should be the default behavior out of the box, not a specialized or atypical use case. The short answer is, I'm sure there were good reasons for this behaviour back when it was first implemented, and it has never been enough of a problem for someone to submit a pull request or file a bug report. For the record, I do agree with you that it would be great not to have to set up additional things to support fulltext search. On the other hand, the cron job gives you the flexibility to schedule the fulltext extraction whenever it suits you, since this may be a resource intense task (probably more of a problem 10 years ago than it is now -- hence our drive to look at the use cases for the modern repository). As regards running the dspace script with sudo, now that I've done it once, is there a way for me to determine whether I've messed up the file system permissions? You could run a recursive chown (chown -R tomcat:tomcat or whatever your user/group are) on the dspace directory to fix its permissions. If you also throw in a -c, chown will tell you about all changes it makes. Note though that chown won't follow symbolic links. So if your dspace directory contains symbolic links, you'll have to run chown on the targets of these links too. cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ 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] New submissions are not searchable
Hello Andrea, Thank you very much for this information. It's extremely helpful. I must say I'm very surprised that DSpace doesn't provide full-text searching by default -- only by setting up a cron job or by running the indexing manually. Searching the full text of text-based file formats should be the default behavior out of the box, not a specialized or atypical use case. As regards running the dspace script with sudo, now that I've done it once, is there a way for me to determine whether I've messed up the file system permissions? Many thanks, Greg On Jun 22, 2015, at 12:57 AM, Andrea Schweer wrote: Hi, On 20/06/15 06:03, Murray, Gregory wrote: From the DSpace bin directory I ran sudo ./dspace index-discovery but it had no effect on the problem. I don't see anything in the documentation to indicate that full-text indexing has to be enabled with a config change. Surely it's enabled by default, right? Fulltext extraction needs to be scheduled via cron, see https://wiki.duraspace.org/display/DSDOC5x/Scheduled+Tasks+via+Cron -- you need the media filter task. This task extracts the full text and it also generates thumbnails. That's what Hilton was referring to. Unfortunately, full-text extraction doesn't happen automatically, you do need to run the media filter. The media filter will trigger a re-index of the item once the .pdf.txt file has been generated, and from then on you can do fulltext searches on that item. You may be aware that we're currently collecting use cases for DSpace. Automatically running the media filter when an item is ingested is mentioned in the Tim's comment on this use case: https://wiki.duraspace.org/display/DSPACE/Admin+UI+-+Run+media+filters -- if you think this would be useful, you may wish to like Tim's comment and/or leave a comment of your own on the use case. Finally, unless you're running DSpace as root, you should never ever run a dspace command with just sudo. This can thoroughly mess up the file system permissions. All dspace commands need to be run as the same user that Tomcat runs under (the user is dspace if you followed the DSpace installation instructions, but it could be tomcat or something else depending on your OS/distribution). cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o___ 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] New submissions are not searchable
Hello, I'm using DSpace 5.1 and XMLUI. After submitting an item (fully, successfully) the full text of the item is not searchable. Only the metadata is searchable. In other words, searching for a word that I know occurs in the text returns search results where that item is not included. This is true even if I take a PDF that I submitted a few weeks ago that is currently full-text searchable, and then submit that same PDF today, only to find that it is not full-text searchable. I realize that some PDFs do not contain embedded text, only images, but that is not the situation here. The PDF is searchable in a standard PDF viewer. In those cases where I do need to submit a non-textual PDF, I also submit a .txt file containing the full text, and I would have expected that textual data to be searchable within DSpace, but it's not. I don't know where to begin to diagnose this problem. Any help would be greatly appreciated. Thanks, Greg -- ___ 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] New submissions are not searchable
Hi Hilton, No, I have not specifically set up a cron job. I was assuming that DSpace would simply index the full text as well as the metadata at the point of submission. Is there a default setting in DSpace for the frequency that the full-text content gets indexed? Is there a script that comes with DSpace that I could run to perform such a full-text indexing on demand? Many thanks, Greg On Jun 19, 2015, at 11:48 AM, Hilton Gibson wrote: HI Greg, Have you arranged for full-text extraction to happen? See: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Daily_Admin/5.X We do ours nightly so as not to overload our server during the day. Cheers hg Hilton Gibson Ubuntu Linux Systems Administrator Stellenbosch University Library http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html On 19 June 2015 at 16:39, Murray, Gregory gregory.mur...@ptsem.edumailto:gregory.mur...@ptsem.edu wrote: Hello, I'm using DSpace 5.1 and XMLUI. After submitting an item (fully, successfully) the full text of the item is not searchable. Only the metadata is searchable. In other words, searching for a word that I know occurs in the text returns search results where that item is not included. This is true even if I take a PDF that I submitted a few weeks ago that is currently full-text searchable, and then submit that same PDF today, only to find that it is not full-text searchable. I realize that some PDFs do not contain embedded text, only images, but that is not the situation here. The PDF is searchable in a standard PDF viewer. In those cases where I do need to submit a non-textual PDF, I also submit a .txt file containing the full text, and I would have expected that textual data to be searchable within DSpace, but it's not. I don't know where to begin to diagnose this problem. Any help would be greatly appreciated. Thanks, Greg -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto: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 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] New submissions are not searchable
From the DSpace bin directory I ran sudo ./dspace index-discovery but it had no effect on the problem. I don't see anything in the documentation to indicate that full-text indexing has to be enabled with a config change. Surely it's enabled by default, right? On Jun 19, 2015, at 12:03 PM, Murray, Gregory wrote: Hi Hilton, No, I have not specifically set up a cron job. I was assuming that DSpace would simply index the full text as well as the metadata at the point of submission. Is there a default setting in DSpace for the frequency that the full-text content gets indexed? Is there a script that comes with DSpace that I could run to perform such a full-text indexing on demand? Many thanks, Greg On Jun 19, 2015, at 11:48 AM, Hilton Gibson wrote: HI Greg, Have you arranged for full-text extraction to happen? See: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Daily_Admin/5.X We do ours nightly so as not to overload our server during the day. Cheers hg Hilton Gibson Ubuntu Linux Systems Administrator Stellenbosch University Library http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html On 19 June 2015 at 16:39, Murray, Gregory gregory.mur...@ptsem.edumailto:gregory.mur...@ptsem.edu wrote: Hello, I'm using DSpace 5.1 and XMLUI. After submitting an item (fully, successfully) the full text of the item is not searchable. Only the metadata is searchable. In other words, searching for a word that I know occurs in the text returns search results where that item is not included. This is true even if I take a PDF that I submitted a few weeks ago that is currently full-text searchable, and then submit that same PDF today, only to find that it is not full-text searchable. I realize that some PDFs do not contain embedded text, only images, but that is not the situation here. The PDF is searchable in a standard PDF viewer. In those cases where I do need to submit a non-textual PDF, I also submit a .txt file containing the full text, and I would have expected that textual data to be searchable within DSpace, but it's not. I don't know where to begin to diagnose this problem. Any help would be greatly appreciated. Thanks, Greg -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto: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 mailing list DSpace-tech@lists.sourceforge.netmailto: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 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] Getting started with UI customization: sitemap file not found
You must remember you are working with source. I get that, but I was thinking that the source files are wherever you unzipped the download (on my system, ~/dspace-5.1-src-release) and that the live directory where theme files are actually read from disk at runtime would be this: /dspace/webapps/xmlui/themes (for example, on my system). But when you say live are you referring to /var/lib/tomcat7/webapps/xmlui/themes? If so, does that mean that /dspace/webapps/xmlui/themes is actually the source directory? Related question: If you're doing UI customization, all that seems to matter is the theme directory. So why do you have to rebuild -- why not just copy the theme directory from /dspace/webapps/xmlui/themes/MyTheme to /var/lib/tomcat7/webapps/xmlui/themes/MyTheme ? Thanks! On May 28, 2015, at 6:44 PM, Hilton Gibson wrote: Short answer = yes, but it depends. Rebuild is the safest. You must remember you are working with source. The production (live) webapp is served by Tomcat in a totally different folder location. Hard to explain via email. Hilton Gibson Ubuntu Linux Systems Administrator Stellenbosch University Library http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html On 29 May 2015 at 00:38, Murray, Gregory gregory.mur...@ptsem.edu wrote: Thanks for the link to your detailed guide. The Manakin Theme Tutorial says to restart Tomcat to install a new theme, whereas your wiki says to rebuild DSpace, which judging by the example rebuild script involves not only restarting Tomcat but also running Maven and Ant. So when you have a source installation do you have to rebuild to get DSpace to see the new theme directory? On May 28, 2015, at 6:04 PM, Hilton Gibson hilton.gib...@gmail.com wrote: Hi Greg Perhaps this will help: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Theme It's a more holistic guide. Cheers hg Hilton Gibson Ubuntu Linux Systems Administrator Stellenbosch University Library http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html On 28 May 2015 at 23:29, Murray, Gregory gregory.mur...@ptsem.edu wrote: Hello, I am new to DSpace and trying to get started with UI customization. I'm comfortable at the Unix/Linux command line, but I'm not a system administrator. I'm working with a source (not binary) installation of DSpace 5.1 on Ubuntu. I'm following the Manakin theme tutorial here: https://wiki.duraspace.org/display/DSPACE/Manakin+theme+tutorial I'm finding that I can edit /dspace/config/xmlui.xconf to indicate any of the pre-installed themes (Mirage, Reference, Classic, Kubrick, template), restart Tomcat, and the new theme gets applied successfully. But if I indicate a theme in a directory I've made, Tomcat returns an error message (details below). For example, if I copy the template directory and call it test like so: cd /dspace/webapps/xmlui/themes cp -r template test and then edit /dspace/config/xmlui.xconf to indicate the test theme like so: theme name=test regex=.* path=test/ / then when I restart Tomcat it returns this error: java.io.FileNotFoundException: jndi:/localhost/xmlui/themes/test/sitemap.xmap I don't see how it can be a permissions problem, because both the template and test directories have the same owner and permissions, and the files in those directories have the same owner and permissions. That is, the directories appear to be identical except for the name. Any ideas as to why setting the config to this: theme name=template regex=.* path=template/ / works just fine, whereas this: theme name=test regex=.* path=test/ / fails? Thanks, Greg PS. For the newbie, it's not clear whether the changes described in the tutorial should happen in the source directory at ~/dspace-5.1-src-release/dspace-xmlui/src/main/webapp/themes -- or in /dspace/webapps/xmlui/themes -- or both. The tutorial indicates the source directory, but it refers to DSpace 1.5, so that's not necessarily accurate. Based on the error message described above -- which says .../xmlui/themes/... -- apparently UI customizations are supposed to be made in /dspace/webapps/xmlui/themes. So the tutorial needs to be updated, right? -- ___ 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 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] Getting started with UI customization: sitemap file not found
Thanks for the link to your detailed guide. The Manakin Theme Tutorial says to restart Tomcat to install a new theme, whereas your wiki says to rebuild DSpace, which judging by the example rebuild script involves not only restarting Tomcat but also running Maven and Ant. So when you have a source installation do you have to rebuild to get DSpace to see the new theme directory? On May 28, 2015, at 6:04 PM, Hilton Gibson hilton.gib...@gmail.commailto:hilton.gib...@gmail.com wrote: Hi Greg Perhaps this will help: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Theme It's a more holistic guide. Cheers hg Hilton Gibson Ubuntu Linux Systems Administrator Stellenbosch University Library http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html On 28 May 2015 at 23:29, Murray, Gregory gregory.mur...@ptsem.edumailto:gregory.mur...@ptsem.edu wrote: Hello, I am new to DSpace and trying to get started with UI customization. I'm comfortable at the Unix/Linux command line, but I'm not a system administrator. I'm working with a source (not binary) installation of DSpace 5.1 on Ubuntu. I'm following the Manakin theme tutorial here: https://wiki.duraspace.org/display/DSPACE/Manakin+theme+tutorial I'm finding that I can edit /dspace/config/xmlui.xconf to indicate any of the pre-installed themes (Mirage, Reference, Classic, Kubrick, template), restart Tomcat, and the new theme gets applied successfully. But if I indicate a theme in a directory I've made, Tomcat returns an error message (details below). For example, if I copy the template directory and call it test like so: cd /dspace/webapps/xmlui/themes cp -r template test and then edit /dspace/config/xmlui.xconf to indicate the test theme like so: theme name=test regex=.* path=test/ / then when I restart Tomcat it returns this error: java.io.FileNotFoundException: jndi:/localhost/xmlui/themes/test/sitemap.xmap I don't see how it can be a permissions problem, because both the template and test directories have the same owner and permissions, and the files in those directories have the same owner and permissions. That is, the directories appear to be identical except for the name. Any ideas as to why setting the config to this: theme name=template regex=.* path=template/ / works just fine, whereas this: theme name=test regex=.* path=test/ / fails? Thanks, Greg PS. For the newbie, it's not clear whether the changes described in the tutorial should happen in the source directory at ~/dspace-5.1-src-release/dspace-xmlui/src/main/webapp/themes -- or in /dspace/webapps/xmlui/themes -- or both. The tutorial indicates the source directory, but it refers to DSpace 1.5, so that's not necessarily accurate. Based on the error message described above -- which says .../xmlui/themes/... -- apparently UI customizations are supposed to be made in /dspace/webapps/xmlui/themes. So the tutorial needs to be updated, right? -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto: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 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] Getting started with UI customization: sitemap file not found
Hello, I am new to DSpace and trying to get started with UI customization. I'm comfortable at the Unix/Linux command line, but I'm not a system administrator. I'm working with a source (not binary) installation of DSpace 5.1 on Ubuntu. I'm following the Manakin theme tutorial here: https://wiki.duraspace.org/display/DSPACE/Manakin+theme+tutorial I'm finding that I can edit /dspace/config/xmlui.xconf to indicate any of the pre-installed themes (Mirage, Reference, Classic, Kubrick, template), restart Tomcat, and the new theme gets applied successfully. But if I indicate a theme in a directory I've made, Tomcat returns an error message (details below). For example, if I copy the template directory and call it test like so: cd /dspace/webapps/xmlui/themes cp -r template test and then edit /dspace/config/xmlui.xconf to indicate the test theme like so: theme name=test regex=.* path=test/ / then when I restart Tomcat it returns this error: java.io.FileNotFoundException: jndi:/localhost/xmlui/themes/test/sitemap.xmap I don't see how it can be a permissions problem, because both the template and test directories have the same owner and permissions, and the files in those directories have the same owner and permissions. That is, the directories appear to be identical except for the name. Any ideas as to why setting the config to this: theme name=template regex=.* path=template/ / works just fine, whereas this: theme name=test regex=.* path=test/ / fails? Thanks, Greg PS. For the newbie, it's not clear whether the changes described in the tutorial should happen in the source directory at ~/dspace-5.1-src-release/dspace-xmlui/src/main/webapp/themes -- or in /dspace/webapps/xmlui/themes -- or both. The tutorial indicates the source directory, but it refers to DSpace 1.5, so that's not necessarily accurate. Based on the error message described above -- which says .../xmlui/themes/... -- apparently UI customizations are supposed to be made in /dspace/webapps/xmlui/themes. So the tutorial needs to be updated, right? -- ___ 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
