Re: [dspace-tech] Handle Server is not resolving new handles created on Dspace 6.2
Hi Tim, Our handle server is back to regular life now! We've applied the change on dspace-api as suggested on github page you've mentioned. Besides that, we've rebuilt SITEBDN.ZIP (and registered ) it again on CNRI. Finally, our network infrastructure team has assured the port permissions used by handle server plugin (TCP 2641 and HTML 8000). After all those adjustments, our Dspace 6.2 handle server plugin came back to work properly. Thanks for your help, P.S.: I suggest an update on Dspace 6.x handle server plugin documentation (https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-TheHandleServer), that mention TCP 2641 port as mandatory only, although CNRI documentation and an old Dspace Wiki page (from 2015) mention that HTTP 8000 port is mandatory too. CNRI page: http://handle.net/hnr_support.html - Dspace wiki page: https://wiki.duraspace.org/display/DSPACE/Handle+server+performance+tips Edmilson, São Paulo, Brasil Em segunda-feira, 20 de maio de 2019 12:05:33 UTC-3, Tim Donohue escreveu: > > Hello Edmilson, > > That ticket you referenced (https://jira.duraspace.org/browse/DS-3956) > has a possible bug fix available at > https://github.com/DSpace/DSpace/pull/2119 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FDSpace%2FDSpace%2Fpull%2F2119=D=1=AFQjCNFkX1avZVqHVoZtfZsqws9Z-G7Tow> > > It's a simple one line fix which removes the "handle" database table from > any database caching. It's possible this is what you are seeing locally, > if you find the new Handles are only temporarily missing or slow to appear > (as this database cache is cleared after Tomcat restarts or after a > specific period of time). If that's what you are seeing in your local > behavior, then I'd recommend applying that fix locally and reporting back > on how it works for you. If it's successful, we'd like to hear that, since > it will help us "fast track" this fix into the next DSpace 6.x (and 7.x) > release. > > If this is not the behavior you are seeing, or if this doesn't work, then > I'd recommend looking more closely at any code you may have customized in > your system. From the look of your site, it has received some > customizations, and it's possible something in those customizations could > be breaking the Handle Server functionality. As of yet, we've not heard of > any widespread bugs in the DSpace 6.x Handle Server Plugin (beyond that > caching issue). Also, I'm not able to reproduce this issue on other DSpace > 6.x sites (If anyone else on this list *is able to reproduce this issue in > DSpace 6.x* please report it on this list, as it will help us all narrow > down what the problem may be) > > I wish I had a better answer for you here, but hopefully that bug fix > above will actually fix the issues you've encountered. > > Tim > > > On Mon, May 20, 2019 at 8:28 AM Edmilson José Boregas > wrote: > >> >> >> Tim, >> >> My point is that handle server plugin on Dspace 6.2 is not working as >> expected. >> >> I've just found a post on Dspace Jira DS-3956 reporting that handle >> server is not resolving new handles: >> https://www.google.com/url?sa=t=web=j=https://jira.duraspace.org/plugins/servlet/mobile%23issue/DS-3956=2ahUKEwjG377jiaXiAhX9E7kGHUNmCaYQFjAAegQIAxAB=AOvVaw1udl7lrpqci6yXiWgeo7Hr >> >> >> It seems to be exactly what is going on here. >> >> Could you help us to find a workaround and immediate solution for that? >> >> Edmilson >> >> Em sexta-feira, 17 de maio de 2019 11:53:10 UTC-3, Edmilson José Boregas >> escreveu: >>> >>> Hi Tim, >>> >>> Let me clarify the situation by using other examples: >>> >>> 1. The point is that both *items exist on our Dspace site and are >>> public*: >>> >>> Older item (created on Dspace 5) : http://hdl.handle.net/10438/27419 >>> è handle server redirect correctly to: >>> http://bibliotecadigital.fgv.br/dspace/10438/27419 >>> <http://www.google.com/url?q=http%3A%2F%2Fbibliotecadigital.fgv.br%2Fdspace%2F10438%2F13788=D=1=AFQjCNFVq5I-lzo1gxhWQLO9XqqDwRCgtA> >>> >>> >>> New item (created on Dspace 6.2): http://hdl.handle.net/10438/27425 >>> è handle server *does not* redirect to: >>> http://bibliotecadigital.fgv.br/dspace/10438/27425 and shows a handle >>> page with a NOT FOUND message >>> instead of displaying the item page ( >>> http://bibliotecadigital.fgv.br/dspace/10438/27425) >>> >>> 2. In the other hand, not existing items are resolved by the handle >>> server on the ex
Re: [dspace-tech] Handle Server is not resolving new handles created on Dspace 6.2
Tim, My point is that handle server plugin on Dspace 6.2 is not working as expected. I've just found a post on Dspace Jira DS-3956 reporting that handle server is not resolving new handles: https://www.google.com/url?sa=t=web=j=https://jira.duraspace.org/plugins/servlet/mobile%23issue/DS-3956=2ahUKEwjG377jiaXiAhX9E7kGHUNmCaYQFjAAegQIAxAB=AOvVaw1udl7lrpqci6yXiWgeo7Hr It seems to be exactly what is going on here. Could you help us to find a workaround and immediate solution for that? Edmilson Em sexta-feira, 17 de maio de 2019 11:53:10 UTC-3, Edmilson José Boregas escreveu: > > Hi Tim, > > Let me clarify the situation by using other examples: > > 1. The point is that both *items exist on our Dspace site and are public*: > > Older item (created on Dspace 5) : http://hdl.handle.net/10438/27419 > è handle server redirect correctly to: > http://bibliotecadigital.fgv.br/dspace/10438/27419 > <http://www.google.com/url?q=http%3A%2F%2Fbibliotecadigital.fgv.br%2Fdspace%2F10438%2F13788=D=1=AFQjCNFVq5I-lzo1gxhWQLO9XqqDwRCgtA> > > > New item (created on Dspace 6.2): http://hdl.handle.net/10438/27425 > è handle server *does not* redirect to: > http://bibliotecadigital.fgv.br/dspace/10438/27425 and shows a handle > page with a NOT FOUND message > instead of displaying the item page ( > http://bibliotecadigital.fgv.br/dspace/10438/27425) > > 2. In the other hand, not existing items are resolved by the handle server > on the expected way, that is: displaying our Dspace page for Page not found. > See this example of an item that dos nos exists: > http://hdl.handle.net/10438/8 > è handle server display the page: > http://bibliotecadigital.fgv.br/dspace/handle/10438/8 > > 3. But there are other inexisting items that handle server displays that > Handle.net page instead of our Dspace page. > See this example: http://hdl.handle.net/10438/300020202 > > Those situation are puting me crazy!!! > > Edmilson, São Paulo, Brasil > > > Em quinta-feira, 16 de maio de 2019 15:52:33 UTC-3, Tim Donohue escreveu: >> >> Hello Edmilson, >> >> I'm not sure I have an answer, but on my end, the second URL doesn't work. >> >> So, this item exists & is public, and it's hdl.handle.net URL works: >> http://bibliotecadigital.fgv.br/dspace/10438/13788 >> >> However, this item either does *not* exist (or maybe it exists but is not >> public), and the hdl.handle.net URL doesn't work: >> http://bibliotecadigital.fgv.br/dspace/10438/12 >> >> When I visit that second URL, I see a 404 (Page Not Found) page, which >> may also be why the hdl.handle.net URL ( >> http://hdl.handle.net/10438/12) is returning a 404 error. >> >> I'm not sure if that helps, but it could be a clue as to what is >> different about these two Items. >> >> Tim >> >> On Wed, May 15, 2019 at 11:39 AM Edmilson José Boregas < >> ejsbo...@gmail.com> wrote: >> >>> Hi folks, >>> >>> We've just upgraded from Dspace 5 to Dspace 6.2. >>> >>> Since last Monday, our handle server is not resolving the new items >>> created on Dspace 6.2. >>> >>> Only the old ones are being resolved. >>> >>> >>> >>> Take a look: >>> >>> >>> Older handle: http://hdl.handle.net/10438/13788 è redirected to >>> http://bibliotecadigital.fgv.br/dspace/10438/13788 >>> >>> New handle: http://hdl.handle.net/10438/12 è not found, but it >>> exists on http://bibliotecadigital.fgv.br/dspace/10438/12 >>> >>> >>> >>> Could someone help us to solve this problem? >>> >>> >>> >>> Edmilson José Boregas >>> >>> Fundação Getulio Vargas >>> >>> São Paulo, Brasil >>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> 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 dspac...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/dspace-tech/a3bdd5d7-9db1-4bde-9fcb-49d0de6b0cc5%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/dspace-tech/a3bdd5d7-9db1-4bde-9fcb-49d0de6b0cc5%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> >> >> >> -- >> >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> >> -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/491b6a2e-47bf-45af-b62f-57675ce5b495%40googlegroups.com.
Re: [dspace-tech] Handle Server is not resolving new handles created on Dspace 6.2
Hi Tim, Let me clarify the situation by using other examples: 1. The point is that both *items exist on our Dspace site and are public*: Older item (created on Dspace 5) : http://hdl.handle.net/10438/27419 è handle server redirect correctly to: http://bibliotecadigital.fgv.br/dspace/10438/27419 <http://www.google.com/url?q=http%3A%2F%2Fbibliotecadigital.fgv.br%2Fdspace%2F10438%2F13788=D=1=AFQjCNFVq5I-lzo1gxhWQLO9XqqDwRCgtA> New item (created on Dspace 6.2): http://hdl.handle.net/10438/27425 è handle server *does not* redirect to: http://bibliotecadigital.fgv.br/dspace/10438/27425 and shows a handle page with a NOT FOUND message instead of displaying the item page ( http://bibliotecadigital.fgv.br/dspace/10438/27425) 2. In the other hand, not existing items are resolved by the handle server on the expected way, that is: displaying our Dspace page for Page not found. See this example of an item that dos nos exists: http://hdl.handle.net/10438/8 è handle server display the page: http://bibliotecadigital.fgv.br/dspace/handle/10438/8 3. But there are other inexisting items that handle server displays that Handle.net page instead of our Dspace page. See this example: http://hdl.handle.net/10438/300020202 Those situation are puting me crazy!!! Edmilson, São Paulo, Brasil Em quinta-feira, 16 de maio de 2019 15:52:33 UTC-3, Tim Donohue escreveu: > > Hello Edmilson, > > I'm not sure I have an answer, but on my end, the second URL doesn't work. > > So, this item exists & is public, and it's hdl.handle.net URL works: > http://bibliotecadigital.fgv.br/dspace/10438/13788 > > However, this item either does *not* exist (or maybe it exists but is not > public), and the hdl.handle.net URL doesn't work: > http://bibliotecadigital.fgv.br/dspace/10438/12 > > When I visit that second URL, I see a 404 (Page Not Found) page, which may > also be why the hdl.handle.net URL (http://hdl.handle.net/10438/12) > is returning a 404 error. > > I'm not sure if that helps, but it could be a clue as to what is different > about these two Items. > > Tim > > On Wed, May 15, 2019 at 11:39 AM Edmilson José Boregas > wrote: > >> Hi folks, >> >> We've just upgraded from Dspace 5 to Dspace 6.2. >> >> Since last Monday, our handle server is not resolving the new items >> created on Dspace 6.2. >> >> Only the old ones are being resolved. >> >> >> >> Take a look: >> >> >> Older handle: http://hdl.handle.net/10438/13788 è redirected to >> http://bibliotecadigital.fgv.br/dspace/10438/13788 >> >> New handle: http://hdl.handle.net/10438/12 è not found, but it >> exists on http://bibliotecadigital.fgv.br/dspace/10438/12 >> >> >> >> Could someone help us to solve this problem? >> >> >> >> Edmilson José Boregas >> >> Fundação Getulio Vargas >> >> São Paulo, Brasil >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> 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 dspac...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/a3bdd5d7-9db1-4bde-9fcb-49d0de6b0cc5%40googlegroups.com >> >> <https://groups.google.com/d/msgid/dspace-tech/a3bdd5d7-9db1-4bde-9fcb-49d0de6b0cc5%40googlegroups.com?utm_medium=email_source=footer> >> . >> > > > -- > > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/c0028a69-93f0-42c6-9885-a0f6950a683d%40googlegroups.com.
[dspace-tech] Handle Server is not resolving new handles created on Dspace 6.2
Hi folks, We've just upgraded from Dspace 5 to Dspace 6.2. Since last Monday, our handle server is not resolving the new items created on Dspace 6.2. Only the old ones are being resolved. Take a look: Older handle: http://hdl.handle.net/10438/13788 è redirected to http://bibliotecadigital.fgv.br/dspace/10438/13788 New handle: http://hdl.handle.net/10438/12 è not found, but it exists on http://bibliotecadigital.fgv.br/dspace/10438/12 Could someone help us to solve this problem? Edmilson José Boregas Fundação Getulio Vargas São Paulo, Brasil -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/a3bdd5d7-9db1-4bde-9fcb-49d0de6b0cc5%40googlegroups.com.
Re: [dspace-tech] Dspace 5.5 - How to extract from dspace log the event of downloaded bitstreams
Hi Terry, The statistis on XMLUI are not exactly what I want. Could you help me with the SOLR queries to obtain a list of downloaded bitstreams during an specific period of days? Or even point me some SOLR documentation that can be usefull for that. TIA, Ejsboregas Em quarta-feira, 15 de fevereiro de 2017 15:00:15 UTC-2, Terry Brady escreveu: > > The usage statistics are stored in SOLR for DSpace 5. It is possible to > write queries to see the most downloaded bitstream. > > XMLUI provides a listing of the most downloaded bitstreams. See > http://demo.dspace.org/xmlui/statistics > > (The landing page for demo.dspace.org/xmlui will provide instructions on > how to log in so you can see this information.) > > Would that provide the information you would like to see? > > On Wed, Feb 15, 2017 at 7:51 AM, Edmilson José Boregas <ejsbo...@gmail.com > > wrote: > >> Hi all, >> >> >> I have to produce a ranking of the most downloaded bitstream (Dspace 5.5). >> >> >> At the dspace log file I've found the following messages: >> >> >> 2017-02-04 00:20:22,663 INFO org.dspace.usage.LoggerUsageEventListener @ >> anonymous:session_id=826A711DAFC58FA021873BA5F1D7DDE1:ip_addr=157.55.39.41:view_bitstream:bitstream_id=22895 >> >> >> >> 2017-02-04 00:20:24,737 INFO org.dspace.app.xmlui.cocoon.BitstreamReader >> @ >> anonymous:session_id=9446A033674E101C86BE2CAE2BAA4592:ip_addr=173.252.88.95:view_bitstream:handle=10438/2674,withdrawn=true >> >> >> >> I ask: >> >> >> 1. Which of those lines mean that a bitstream was downloaded? Is there >> any others? >> >> >> 2. Is there some tool in Dspace 5.5 that can help me to extract this kind >> of event from dspace log file? >> >> >> Thanks a bunch >> >> >> Ejsboregas >> >> >> -- >> 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. >> > > > > -- > Terry Brady > Applications Programmer Analyst > Georgetown University Library Information Technology > http://georgetown-university-libraries.github.io/ > <https://www.library.georgetown.edu/lit/code> > 425-298-5498 (Seattle, WA) > -- 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] Dspace 5.5 - How to extract from dspace log the event of downloaded bitstreams
Hi all, I have to produce a ranking of the most downloaded bitstream (Dspace 5.5). At the dspace log file I've found the following messages: 2017-02-04 00:20:22,663 INFO org.dspace.usage.LoggerUsageEventListener @ anonymous:session_id=826A711DAFC58FA021873BA5F1D7DDE1:ip_addr=157.55.39.41:view_bitstream:bitstream_id=22895 2017-02-04 00:20:24,737 INFO org.dspace.app.xmlui.cocoon.BitstreamReader @ anonymous:session_id=9446A033674E101C86BE2CAE2BAA4592:ip_addr=173.252.88.95:view_bitstream:handle=10438/2674,withdrawn=true I ask: 1. Which of those lines mean that a bitstream was downloaded? Is there any others? 2. Is there some tool in Dspace 5.5 that can help me to extract this kind of event from dspace log file? Thanks a bunch Ejsboregas -- 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.
