Re: [Dspace-tech] how to remove jspui in url to access jspui interface
Thanks Mark, It works by changing /jspui to /ROOT Actually we just created a symlink from 'ROOT' to jspui in [tomcat]/webapps/ Thanks very much for your help! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - - Original Message - From: Mark H. Wood mw...@iupui.edu To: dspace-tech@lists.sourceforge.net Sent: Tuesday, August 18, 2015 9:00:52 AM Subject: Re: [Dspace-tech] how to remove jspui in url to access jspui interface On Mon, Aug 17, 2015 at 11:51:31AM -0400, Yongming Wang wrote: We just implemented DSpace 5.2 and use jspui interface. In order to access the application, we use the url http://.tcnj.edu/jspui; (we have already changed the default port 8080 to 80). Is it possible to remove the jspui part? So that when people enter http://.tcnj.edu;, it will access the jspui application. If you are using Tomcat as your servlet container, the webapp. at the root path (/) is named ROOT. So find the place where JSPUI was deployed to Tomcat and rename it: o If you are using an unpacked webapp, it will be a directory named jspui. Rename it to ROOT. o If you are using a WAR, it will be named jspui.war, and should be renamed to ROOT.war. o If you are using separate Context descriptor files, the file will be named jspui.xml, and should be renamed ROOT.xml. The directory or WAR which is named as the docbase in that file need not be renamed, and it is probably most convenient not to. http://tomcat.apache.org/tomcat-8.0-doc/config/context.html#Naming If you're using some other container, I can't give specific advice. I'm sure there is a way to do this, but it will be different. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- ___ 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
[Dspace-tech] how to remove jspui in url to access jspui interface
Hi, We just implemented DSpace 5.2 and use jspui interface. In order to access the application, we use the url http://.tcnj.edu/jspui; (we have already changed the default port 8080 to 80). Is it possible to remove the jspui part? So that when people enter http://.tcnj.edu;, it will access the jspui application. Is this something called http redirect which can do the job? Thanks in advance for your help! (Our server is RH Linux 7.) Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - -- ___ 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] tomcat bound to port 80
Hi Graham, Thanks very much for your advice, especially on the security front. I don't have any experience with the Apache HTTPd with mod_proxy / mod_jk. I don't want to bother the college IT department again. So I'll stay with the current solution they provide, the jsvc. Thanks again. Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - - Original Message - From: Graham Triggs grahamtri...@gmail.com To: Yongming Wang wan...@tcnj.edu Cc: dspace-tech@lists.sourceforge.net Sent: Monday, August 3, 2015 4:53:35 PM Subject: Re: [Dspace-tech] tomcat bound to port 80 Hi, The error that you have received is because the main DSpace application can't communicate with the secondary Solr application - which by default it expects to be in the same Tomcat, and on the default port of 8080. Note that the circumstances of this error point to a very good reason why you should NOT relocate the Tomcat port. By putting the main Tomcat connector on port 80, you are - by default - exposing(*) all of the applications hosted in that Tomcat to the internet. This includes the internal support applications like Solr, which may be a security risk. (* this may very depending on other firewalls that you may be running). If you instead use something like Apache HTTPd with mod_proxy / mod_jk, you can be more explicit about what applications you mount through HTTPd, limiting what is exposed to potential attacks. Also, it gives you a place to more easily add other security modules / features. Plus, if it is ever necessary, it gives you a means to disable general access to the underlying application, whilst you still have direct access to the Tomcat application. Regards, Graham On 3 August 2015 at 16:09, Yongming Wang wan...@tcnj.edu wrote: Hi, I'm new to DSpace. My situation is: DSpace 5.2 on RH Enterprise Linux 7, using jspui. I'm trying to change the default tomcat port 8080 to 80. I searched the Internet and dspace mailing-list and decided to use the following method: Step one: modify [tomcat]/conf/server.xml, change connector port from 8080 to 80 Step two: install the AUTOBIND package. But instead my school IT department installed something called jsvc which they told me is newer and better than AUTHBIND. Now I got some internal error message when trying to access the application homepage at port 80. I'll paste it below. Does anyone have any suggestions and insight to this issue? Or in general, how do you change the 8080 port to 80 so user won't need to type 8080 to access the application? What is the simplest way? Thanks very much in advance! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - exception stack: -- URL Was: http://xx.tcnj.edu/jspui/internal-error -- Method: GET -- Parameters were: Exception: org.apache.jasper.JasperException: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:549) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:455) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501
Re: [Dspace-tech] tomcat bound to port 80
Hi Mark, You are right. I searched through the system and changed all 8080 to 80. It's working now! Thank you so much for your help! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - - Original Message - From: Mark H. Wood mw...@iupui.edu To: dspace-tech@lists.sourceforge.net Sent: Monday, August 3, 2015 4:23:24 PM Subject: Re: [Dspace-tech] tomcat bound to port 80 On Mon, Aug 03, 2015 at 11:09:49AM -0400, Yongming Wang wrote: I'm new to DSpace. My situation is: DSpace 5.2 on RH Enterprise Linux 7, using jspui. I'm trying to change the default tomcat port 8080 to 80. I searched the Internet and dspace mailing-list and decided to use the following method: Step one: modify [tomcat]/conf/server.xml, change connector port from 8080 to 80 Step two: install the AUTOBIND package. But instead my school IT department installed something called jsvc which they told me is newer and better than AUTHBIND. jsvc is what I would choose. It is used to start Java-based processes in a similar fashion to traditional Unix daemons: begin as root, open access to privileged resources (such as low-numbered ports), then setuid() to a nonprivileged user and begin service. Tomcat is one Java application which is designed to be used this way. Now I got some internal error message when trying to access the application homepage at port 80. I'll paste it below. Does anyone have any suggestions and insight to this issue? See below. Your DSpace configuration still contains some references to port 8080. I would check: o search.server in config/modules/discovery.cfg o server in config/modules/solr-statistics.cfg o solr.url in config/modules/oai.cfg Or in general, how do you change the 8080 port to 80 so user won't need to type 8080 to access the application? What is the simplest way? Probably the way you are doing it. It is made less simple because there are three URLs in build.properties which, as delivered, select port 8080 and these are copied into various other configuration files as part of the installation process. If you start with dspace.url, dspace.baseUrl, and solr.server all set to port 80 and then build DSpace (mvn clean install) then you should wind up with an installation package that will use port 80 throughout. If you built your DSpace for port 8080 and then changed the built configuration, you have to find all of the places where these build.properties values are used and change them accordingly. Thanks very much in advance! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - exception stack: -- URL Was: http://xx.tcnj.edu/jspui/internal-error -- Method: GET -- Parameters were: Exception: org.apache.jasper.JasperException: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search DSpace made an internal reference to port 8080 here. at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:549) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:455) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java
[Dspace-tech] tomcat bound to port 80
Hi, I'm new to DSpace. My situation is: DSpace 5.2 on RH Enterprise Linux 7, using jspui. I'm trying to change the default tomcat port 8080 to 80. I searched the Internet and dspace mailing-list and decided to use the following method: Step one: modify [tomcat]/conf/server.xml, change connector port from 8080 to 80 Step two: install the AUTOBIND package. But instead my school IT department installed something called jsvc which they told me is newer and better than AUTHBIND. Now I got some internal error message when trying to access the application homepage at port 80. I'll paste it below. Does anyone have any suggestions and insight to this issue? Or in general, how do you change the 8080 port to 80 so user won't need to type 8080 to access the application? What is the simplest way? Thanks very much in advance! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - exception stack: -- URL Was: http://xx.tcnj.edu/jspui/internal-error -- Method: GET -- Parameters were: Exception: org.apache.jasper.JasperException: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search at org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:549) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:455) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: javax.servlet.ServletException: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search at org.apache.jsp.index_jsp._jspService(index_jsp.java:128) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) ... 26 more Caused by: org.dspace.plugin.PluginException: org.dspace.app.webui.components.RecentSubmissionsException: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search
Re: [Dspace-tech] HELP: Updating JSPUI Front End Files DSpace 5.2
That's exactly what I'm trying to learn right now! I just wish that there is some kind of DSpace training class or workshop available, either online or offline. Better, a training class towards a certificate of DSpace administrator. I think it would be a good business. Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - - Original Message - From: Rwakimari Arnold Babasa realns...@gmail.com To: dspace-tech@lists.sourceforge.net Sent: Thursday, June 18, 2015 2:52:15 AM Subject: [Dspace-tech] HELP: Updating JSPUI Front End Files DSpace 5.2 Hi There, I hope everyone is in good health. I am new to DSpace and as an IT administrator in a University I work for I was tasked on setting up DSpace. I have gotten a bit of experience especially when it came to Installing and setting up DSpace. I have gotten some knowledge on how Maven and Ant work, as well as Tomcat and so on. I have also become fairly familiar with how to build DSpace after making small or major configuration changes. I am stuck however, with when it comes to making interface changes, style and layout and adding new images. Whenever I make changes and for some reason I have to rebuild, everything gets lost and I have to re-do my stylesheet and say for example header layout changes. Is there a way to make these changes so that when I perform an ant update the changes I make in my [dspace]/webapps folder do not change? Thank you for your assistance. -- ___ 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] missing Messages.properties file - re-post
thanks, Mark, I have forgot to mention that the problem has been solved. Two people helped me offline. Basically I need to go to github to download the Messages.properties manually and put it in [resources] directory (I created [resources] directory because it's not there), and rebuild it. I never suspected that the rebuild is so simple and easy. Thank you very much for your input. Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - - Original Message - From: Mark H. Wood mw...@iupui.edu To: dspace-tech@lists.sourceforge.net Sent: Friday, June 12, 2015 12:24:45 PM Subject: Re: [Dspace-tech] missing Messages.properties file - re-post On Mon, Jun 08, 2015 at 10:30:37AM -0400, Yongming Wang wrote: I don't get any response for my previous posting a week ago. So try again. (please see the description below for the problem I encountered.) My installation is definitely missing the critical Messages.properties file. The reason, I guess, may be that I downloaded dspace-5.1-release.tar.gz, which probably doesn't contain Messages.properties. Can anyone tell me if that is why I don't have Messages.properties. Thanks so much. You are correct. 'dspace-5.1-release.tar.gz' is the precompiled version, and Messages.properties is packed inside one of the .jar files that it downloads. If that's really the reason, what is the remedy? If you unpack a copy of the file, edit it, and place it in [DSpace]/webapps/jspui/WEB-INF/classes, I think that copy will be found before the one in the JAR, but I have not tested this. You can unpack it this way: cd [DSpace] jar xf webapps/jspui/WEB-INF/lib/dspace-api-5.1.jar Messages.properties That should result in a copy of the file being placed in [DSpace]. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- ___ 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] missing Messages.properties file - re-post
I don't get any response for my previous posting a week ago. So try again. (please see the description below for the problem I encountered.) My installation is definitely missing the critical Messages.properties file. The reason, I guess, may be that I downloaded dspace-5.1-release.tar.gz, which probably doesn't contain Messages.properties. Can anyone tell me if that is why I don't have Messages.properties. Thanks so much. If that's really the reason, what is the remedy? Here is my directory listing under /local/home/dspace/dspace-5.1-release which is [dspace-source] README NOTICE LICENSE_HEADER LICENSE pom.xml LICENSES_THIRD_PARTY build.properties.orig target dspace build.properties Thank you in advance. Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - - Original Message - From: Yongming Wang wan...@tcnj.edu To: dspace-tech@lists.sourceforge.net Sent: Thursday, June 4, 2015 1:39:57 PM Subject: missing Messages.properties file Hi, I'm a newbie on DSpace. I just installed DSpace 5.x for my library. We use jspui. I added a new field (advisor) on the Submission form by editing the /dspace/config/input-forms.xml file, which works fine. In order to display it on the default simple item record page, I modified the /dspace/config/dspace.cfg file by adding dc.contributor.advisor to webui.itemdisplay.default = section, like the following: webui.itemdisplay.default = dc.title, dc.title.alternative, dc.contributor.author, dc.contributor.advisor, \ dc.subject(nobreakline), dc.date.issued(date), dc.publisher, \ dc.identifier.citation, dc.relation.ispartofseries, \ dc.description.abstract, dc.description, \ dc.identifier.govdoc, dc.identifier.uri(link), \ dc.identifier.isbn, dc.identifier.issn, \ dc.identifier.ismn, dc.identifier The interesting thing is that originally this part is all commented out and I had to uncomment it to make my new field to work. Now the real challenge comes, the label for the advisor field on the simple item record page is: metadata.dc.contributor.advisor, not simply advisor as I expected! After more research, I came to know that I need to change the Messages.properties file inside my source directory, like the documentation told me: Location of the JSPUI message catalog in the DSpace source tree [dspace-source]/dspace-api/src/main/resources/Messages.properties The problem is, I can't find Messages.properties anywhere. It simply doesn't exist! My question: Where is this file hided? My another question is: Is this the only way to change my label from metadata.dc.contributor.advisor to advisor? Because I don't want to rebuild dspace just for such a small change. Thanks in advance for your help! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - -- ___ 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] missing Messages.properties file
Hi, I'm a newbie on DSpace. I just installed DSpace 5.x for my library. We use jspui. I added a new field (advisor) on the Submission form by editing the /dspace/config/input-forms.xml file, which works fine. In order to display it on the default simple item record page, I modified the /dspace/config/dspace.cfg file by adding dc.contributor.advisor to webui.itemdisplay.default = section, like the following: webui.itemdisplay.default = dc.title, dc.title.alternative, dc.contributor.author, dc.contributor.advisor, \ dc.subject(nobreakline), dc.date.issued(date), dc.publisher, \ dc.identifier.citation, dc.relation.ispartofseries, \ dc.description.abstract, dc.description, \ dc.identifier.govdoc, dc.identifier.uri(link), \ dc.identifier.isbn, dc.identifier.issn, \ dc.identifier.ismn, dc.identifier The interesting thing is that originally this part is all commented out and I had to uncomment it to make my new field to work. Now the real challenge comes, the label for the advisor field on the simple item record page is: metadata.dc.contributor.advisor, not simply advisor as I expected! After more research, I came to know that I need to change the Messages.properties file inside my source directory, like the documentation told me: Location of the JSPUI message catalog in the DSpace source tree [dspace-source]/dspace-api/src/main/resources/Messages.properties The problem is, I can't find Messages.properties anywhere. It simply doesn't exist! My question: Where is this file hided? My another question is: Is this the only way to change my label from metadata.dc.contributor.advisor to advisor? Because I don't want to rebuild dspace just for such a small change. Thanks in advance for your help! Yongming - Yongming Wang Systems Librarian The College of New Jersey Library phone: 609-771-3337 email: wan...@tcnj.edu - -- ___ 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
