Re: [dspace-tech] Search based on workflow criteria
Hi Andrea! Let me put things straight: *it worked*, thank you very much! However, I had to comment out only the tag and re-run index-discovery. The way comments were done before, the indexing wasn't working. ** Em quinta-feira, 2 de junho de 2016 13:40:46 UTC-3, Tiago Delboni escreveu: > > Hi Andrea, thanks for helping! > > I commented out the following lines in " > [dspace]/config/spring/api/discovery.xml" and then ran "dspace > index-discovery -b". It is still not working, ie, querying for "Submitted > by Valquiria Rosa" returns no item. > > Do I need to configure "dc.description.provenance" as a search filter to > make it searchable? > > > static-field="org.dspace.core.Constants.ITEM"/> > > dc.description.provenance > > > > Em quarta-feira, 1 de junho de 2016 22:38:30 UTC-3, Andrea Schweer > escreveu: >> >> Hi Tiago, >> >> On 02/06/16 04:51, Tiago Delboni wrote: >> >> I'm having a hard time understanding and configuring DSpace's search. I >> have a lot of questions, please help me out. We're on DSpace 5.x using >> default Solr/Discovery search. >> >> >> In case you haven't found it, the appropriate documentation is at >> https://wiki.duraspace.org/display/DSDOC5x/Discovery#Discovery-ModifyingtheDiscoveryUserInterface%28config/spring/api/discovery.xml%29 >> >> >> When you say to "make dc.description.provenance searchable", it means to >> create a "search.index.n" config? We already have this one: >> >> search.index.17 = descriptions:dc.description.* >> >> However, I can't search on "dc.description.provenance" using the >> searchbox with queries like "Submitted by Valquiria Rosa" or "Approved >> for entry into archive by Eliana Cunha". >> >> Is this configuration effective only for Legacy Lucene/DB search or >> "search.index.n" also defines searchable metadata for Solr/Discovery? >> >> >> The search.index settings are not used by Discovery. >> >> We also have this settings regarding provenance: >> >> *dspace.cfg* >> metadata.hide.dc.description.provenance = true >> >> >> I believe this setting now only controls the item page behaviour, though >> it may also be used elsewhere (eg OAI). >> >> *discovery.xml* >> > id="org.dspace.discovery.configuration.DiscoveryConfigurationService" >> class="org.dspace.discovery.configuration.DiscoveryConfigurationService"> >> >> >> >> > static-field="org.dspace.core.Constants.ITEM"/> >> >> dc.description.provenance >> >> >> >> >> >> >> >> This setting causes the search behaviour you're seeing -- it makes >> dc.description.provenance not indexed in solr and hence not searchable via >> Discovery. >> >> To make a custom field searchable, you don't have to do anything -- it >> will be searchable by default. You only need to add a new search filter (as >> described in the documentation linked above) if you want to be able to >> search specifically in that field via the "advanced filters" functionality. >> >> cheers, >> Andrea >> >> -- >> Dr Andrea Schweer >> Lead Software Developer, ITS Information Systems >> The University of Waikato, Hamilton, New Zealand >> +64-7-837 9120 >> >> -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Search based on workflow criteria
Hi Andrea, thanks for helping! I commented out the following lines in " [dspace]/config/spring/api/discovery.xml" and then ran "dspace index-discovery -b". It is still not working, ie, querying for "Submitted by Valquiria Rosa" returns no item. Do I need to configure "dc.description.provenance" as a search filter to make it searchable? dc.description.provenance Em quarta-feira, 1 de junho de 2016 22:38:30 UTC-3, Andrea Schweer escreveu: > > Hi Tiago, > > On 02/06/16 04:51, Tiago Delboni wrote: > > I'm having a hard time understanding and configuring DSpace's search. I > have a lot of questions, please help me out. We're on DSpace 5.x using > default Solr/Discovery search. > > > In case you haven't found it, the appropriate documentation is at > https://wiki.duraspace.org/display/DSDOC5x/Discovery#Discovery-ModifyingtheDiscoveryUserInterface%28config/spring/api/discovery.xml%29 > > > When you say to "make dc.description.provenance searchable", it means to > create a "search.index.n" config? We already have this one: > > search.index.17 = descriptions:dc.description.* > > However, I can't search on "dc.description.provenance" using the > searchbox with queries like "Submitted by Valquiria Rosa" or "Approved > for entry into archive by Eliana Cunha". > > Is this configuration effective only for Legacy Lucene/DB search or > "search.index.n" also defines searchable metadata for Solr/Discovery? > > > The search.index settings are not used by Discovery. > > We also have this settings regarding provenance: > > *dspace.cfg* > metadata.hide.dc.description.provenance = true > > > I believe this setting now only controls the item page behaviour, though > it may also be used elsewhere (eg OAI). > > *discovery.xml* > id="org.dspace.discovery.configuration.DiscoveryConfigurationService" > class="org.dspace.discovery.configuration.DiscoveryConfigurationService"> > > > > static-field="org.dspace.core.Constants.ITEM"/> > > dc.description.provenance > > > > > > > > This setting causes the search behaviour you're seeing -- it makes > dc.description.provenance not indexed in solr and hence not searchable via > Discovery. > > To make a custom field searchable, you don't have to do anything -- it > will be searchable by default. You only need to add a new search filter (as > described in the documentation linked above) if you want to be able to > search specifically in that field via the "advanced filters" functionality. > > cheers, > Andrea > > -- > Dr Andrea Schweer > Lead Software Developer, ITS Information Systems > The University of Waikato, Hamilton, New Zealand > +64-7-837 9120 > > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Search based on workflow criteria
Hi Andrea! I'm having a hard time understanding and configuring DSpace's search. I have a lot of questions, please help me out. We're on DSpace 5.x using default Solr/Discovery search. When you say to "make dc.description.provenance searchable", it means to create a "search.index.n" config? We already have this one: search.index.17 = descriptions:dc.description.* However, I can't search on "dc.description.provenance" using the searchbox with queries like "Submitted by Valquiria Rosa" or "Approved for entry into archive by Eliana Cunha". Is this configuration effective only for Legacy Lucene/DB search or "search.index.n" also defines searchable metadata for Solr/Discovery? We also have this settings regarding provenance: *dspace.cfg* metadata.hide.dc.description.provenance = true *discovery.xml* dc.description.provenance Tiago Em segunda-feira, 30 de maio de 2016 18:26:00 UTC-3, Andrea Schweer escreveu: > > Hi Tiago, > > On 11/05/16 22:50, Tiago Delboni wrote: > > I would like to perform searchs on DSpace 5.x based on workflow criteria > such as "submitted by" and "approved by". > > > I see two options: > >- make dc.description.provenance searchable -- it may not be desirable >to expose all information in that field to the general public, but it's >certainly the easiest way >- write a custom submission step and/or workflow processing action (if >you're using the customisable workflow; otherwise customise the >InstallItem#populateMetadata > > <https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/content/InstallItem.java#L153> > >method) that puts the submitter/approver information into a separate >metadata field in addition to dc.description.provenance, then make that >field searchable > > cheers, > Andrea > > -- > Dr Andrea Schweer > Lead Software Developer, ITS Information Systems > The University of Waikato, Hamilton, New Zealand > +64-7-837 9120 > > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] One item many collections on 5.x
Thank you Claudia, it worked! Em segunda-feira, 30 de maio de 2016 11:40:49 UTC-3, Claudia Jürgen escreveu: > > Hi Tiago, > > yes you can map items see: > https://wiki.duraspace.org/display/DSDOC5x/Mapping+Items > > Hope this helps > > Claudia Jürgen > > Am 30.05.2016 um 16:15 schrieb Tiago Delboni: > > Hi! > > Is it possible to assign one item to more than one collection? I couldn't > find a way to do it using the JSPUI of DSpace 5.x. > > Tiago Delboni > > > > -- > Claudia Juergen > Eldorado > > Technische Universität Dortmund > Universitätsbibliothek > Vogelpothsweg 76 > 44227 Dortmund > > Tel.: +49 231-755 40 43 > Fax: +49 231-755 40 32claudia...@tu-dortmund.de > www.ub.tu-dortmund.de > > > > > *Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie > ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für > diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender > und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz > per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, > wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder > durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. > Important note: The information included in this e-mail is confidential. It > is solely intended for the recipient. If you are not the intended recipient > of this e-mail please contact the sender and delete this message. Thank > you. Without prejudice of e-mail correspondence, our statements are only > legally binding when they are made in the conventional written form (with > personal signature) or when such documents are sent by fax. * > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Re: Search based on workflow criteria
Hi Luiz, Thanks for answering but what I want is to find out how many items were submitted or approved by a given USER in a certain time frame. Em segunda-feira, 30 de maio de 2016 13:01:33 UTC-3, Luiz dos Santos escreveu: > > I guess you can use the dc.date.accessioned or dc.date.available to know > when the item was launched. > > dc.date.accessioned = the date/time that DSpace received this document > (i.e. date/time the item was created in DSpace) > dc.date.available = the date/time that the item was made *available* > through the DSpace web interface. > > On Mon, May 30, 2016 at 9:08 AM, Tiago Delboni <del...@gmail.com > > wrote: > >> I guess that I'll have to index the field "dc.description.provenance" to >> make this work. Sounds good? >> >> >> Em quarta-feira, 11 de maio de 2016 07:50:12 UTC-3, Tiago Delboni >> escreveu: >>> >>> Hi! >>> >>> I would like to perform searchs on DSpace 5.x based on workflow criteria >>> such as "submitted by" and "approved by". >>> >>> Is it possible? Thank you in advance! >>> >>> Tiago M Delboni >>> >> -- >> 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 dspace-tech...@googlegroups.com . >> To post to this group, send email to dspac...@googlegroups.com >> . >> 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Re: Search based on workflow criteria
I guess that I'll have to index the field "dc.description.provenance" to make this work. Sounds good? Em quarta-feira, 11 de maio de 2016 07:50:12 UTC-3, Tiago Delboni escreveu: > > Hi! > > I would like to perform searchs on DSpace 5.x based on workflow criteria > such as "submitted by" and "approved by". > > Is it possible? Thank you in advance! > > Tiago M Delboni > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Search based on workflow criteria
Hi! I would like to perform searchs on DSpace 5.x based on workflow criteria such as "submitted by" and "approved by". Is it possible? Thank you in advance! Tiago M Delboni -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Statistics for items published in a certain month for a given community
Wow, awesome! The query works like a charm. What about that chart? I want that for my DSpace! Is it a customization you made? Em terça-feira, 12 de abril de 2016 11:26:45 UTC-3, Andrea Bollini escreveu: > > Hi Tiago, > you can use this query (Jan 2016): > bi_sort_3_sort:[2016-01-01T00:00.000Z TO 2016-01-31T23:59.999Z] > > the number 3 in bi_sort_3_sort is the index assigned to the > date.accessioned sort option here > > https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/dspace.cfg#L1187 > > BTW, we have included such functionality out of box in the latest > dspace-cris release > see an example here > > http://demo-dspace-cris.cineca.it/cris/stats/community.html?handle=123456789/1_from_date=_to_date==upload > > the functionality can be restricted to administrators. > Andrea > > > Il 11/04/2016 20:18, Tiago Delboni ha scritto: > > Hi! > > How can I find out the number of new items published in a certain month > for a given community? > > I guess that I can do this using "Advanced Search" over > *dc.date.accessioned* ou *dc.date.available* but I either don't know the > right syntax for dates or the default date search is for *dc.date.issued* > only (it seems to be the only date being indexed). > > Thank you in advanced! > -- > 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 dspace-tech...@googlegroups.com . > To post to this group, send email to dspac...@googlegroups.com > . > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > > > > -- > Andrea Bollini > International Business Development, Deputy Leader > Open Source & Open Standards Strategy, Head > Cineca > > Via dei Tizii, 6 > 00185 Roma, Italy > tel. +39 06 44 486 087 - mob. +39 348 82 77 525http://www.cineca.it > > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Statistics for items published in a certain month for a given community
Hi! How can I find out the number of new items published in a certain month for a given community? I guess that I can do this using "Advanced Search" over *dc.date.accessioned* ou *dc.date.available* but I either don't know the right syntax for dates or the default date search is for *dc.date.issued* only (it seems to be the only date being indexed). Thank you in advanced! -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Can't get statistics to work after upgrading from 1.8.x to 5.x
Hi! I'm working on upgrading DSpace from 1.8.2 to 5.4. I guess was able to put everything working but the statistics. Everytime I click the Statistics menu, in JSPUI, DSpace come out with a Internal Server Error. Bellow is the relevant part gattered from dspace.log. Any ideas how to fix it? Also, I would like to know if I can keep the historical statistics I have on 1.8.x. What I did, trying to achieve this, was to copy the contents from [dspace1.8]/log and [dspace1.8]/solr/statistics/data to [dspace5.4] and ran [dspace5.4]/bin/dspace solr-reindex-statistics. 2015-12-17 13:15:12,864 WARN org.dspace.app.webui.servlet.InternalErrorServlet @ :session_id=0CFF63BC0604F2B56DD0EE375E575ED9:internal_error:-- URL Was: https://dspace-novo.almg.gov.br/jspui/statistics -- Method: GET -- Parameters were: java.lang.NullPointerException at org.dspace.app.webui.servlet.StatisticsServlet.showStatistics(StatisticsServlet.java:121) at org.dspace.app.webui.servlet.StatisticsServlet.doDSPost(StatisticsServlet.java:68) at org.dspace.app.webui.servlet.StatisticsServlet.doDSGet(StatisticsServlet.java:49) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:119) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518) at org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:844) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1526) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1482) 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) 2015-12-17 13:15:12,865 WARN org.dspace.app.webui.util.UIUtil @ Unable to send email alert java.lang.NullPointerException at org.dspace.storage.rdbms.DatabaseManager.queryTable(DatabaseManager.java:230) at org.dspace.content.DSpaceObject$MetadataCache.retrieveMetadata(DSpaceObject.java:1330) at org.dspace.content.DSpaceObject$MetadataCache.get(DSpaceObject.java:1265) at org.dspace.content.DSpaceObject.getMetadata(DSpaceObject.java:676) at org.dspace.content.DSpaceObject.getMetadata(DSpaceObject.java:585) at org.dspace.content.DSpaceObject.getMetadataFirstValue(DSpaceObject.java:653) at org.dspace.eperson.EPerson.getFirstName(EPerson.java:772) at org.dspace.eperson.EPerson.getFullName(EPerson.java:748) at org.dspace.app.webui.util.UIUtil.sendAlert(UIUtil.java:419) at org.dspace.app.webui.servlet.InternalErrorServlet.doGet(InternalErrorServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at
Re: [dspace-tech] Can't get statistics to work after upgrading from 1.8.x to 5.x
Hi Monika! Index version looks good: dspace@dspace-novo:/opt/dspace/deploy/bin> ./dspace dsrun org.dspace.app.util.IndexVersion /opt/dspace/deploy/solr/statistics/data/index 4.10.2 2015-12-17 13:53 GMT-02:00 Monika C. Mevenkamp <moni...@princeton.edu>: > You need to upgrade your statistics and solr index ? > > I am getting ready to do the same uproar - and I pieced together some > notes based on > wiki-doc: https://wiki.duraspace.org/display/DSDOC5x/Upgrading+DSpace > <https://wiki.duraspace.org/display/DSDOC5x/Upgrading+DSpace> > > > you can test whether your solr version is outdated (probably you are ok > there since you say everything but stats works) > > # test that index is outdated anything smaller than 3.5 > /dspace/bin/dspace dsrun org.dspace.app.util.IndexVersion > /dspace/solr/statistics/data/index > > but if your versions are off do the following - get yourself an uptodate > lucene-core-3.5.0.jar > > # upgrade statistics index > # in home directory we have the jar parked > java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader > /dspace/solr/statistics/data/index/ > > # expect to see 3.5 > /dspace/bin/dspace dsrun org.dspace.app.util.IndexVersion > /dspace/solr/statistics/data/index > > #update index > ant update_solr_indexes > /dspace/bin/dspace dsrun org.dspace.app.util.IndexVersion > /dspace/solr/statistics/data/index > > > > — > Monika Mevenkamp > Digital Repository Infrastructure Developer > Princeton University > Phone: 609-258-4161 > Skype: mo-meven > > On Dec 17, 2015, at 10:39 AM, Tiago Delboni <delb...@gmail.com> wrote: > > Hi! > > I'm working on upgrading DSpace from 1.8.2 to 5.4. I guess was able to put > everything working but the statistics. Everytime I click the Statistics > menu, in JSPUI, DSpace come out with a Internal Server Error. > Bellow is the relevant part gattered from dspace.log. Any ideas how to > fix it? > > Also, I would like to know if I can keep the historical statistics I have > on 1.8.x. What I did, trying to achieve this, was to copy the contents from > [dspace1.8]/log and [dspace1.8]/solr/statistics/data to [dspace5.4] and > ran [dspace5.4]/bin/dspace solr-reindex-statistics. > > 2015-12-17 13:15:12,864 WARN > org.dspace.app.webui.servlet.InternalErrorServlet @ > :session_id=0CFF63BC0604F2B56DD0EE375E575ED9:internal_error:-- URL Was: > https://dspace-novo.almg.gov.br/jspui/statistics > -- Method: GET > -- Parameters were: > > java.lang.NullPointerException > at > org.dspace.app.webui.servlet.StatisticsServlet.showStatistics(StatisticsServlet.java:121) > at > org.dspace.app.webui.servlet.StatisticsServlet.doDSPost(StatisticsServlet.java:68) > at > org.dspace.app.webui.servlet.StatisticsServlet.doDSGet(StatisticsServlet.java:49) > at > org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:119) > at > org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) > at > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) >
