Re: [dspace-tech] Custom logout page/redirect

2020-01-13 Thread Paul Münch
Hello,

in our systems works the redirect to main page after logout per default.
Which authentication method do you use? There are configuration files
for each authentication method. You may check out these.

Kind regards,

Paul Münch

Am 13.01.20 um 17:25 schrieb Hawk, Patrick:
> Anyone have a suggestion?
>
> On Mon, Jan 6, 2020 at 4:20 PM Patrick Hawk  > wrote:
>
> Currently, if I log out of dspace I get a blank log out page.  I
> want to redirect to the main page instead.  How is this accomplished?
> -- 
> 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/af3a4c73-cb0b-4f81-8c06-0c5fcc4854c2%40googlegroups.com
> 
> .
>
>
>
> -- 
>
> 
>
>   
>
> Patrick Hawk
>
> Computer and Technology Specialist
>
> Miami University Libraries
>
> 314 King Library
>
> 151 S. Campus Ave.
> 
>
> Oxford, OH 45056
> 
>
> O: 513-529-6122 | haw...@miamioh.edu 
>
> -- 
> 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/CAH_HnmUtA572NR4XFVf_aDNsPFb%3DUbX28_kiH8vBa0vZCOqntQ%40mail.gmail.com
> .

-- 
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/9d90835c-46b6-9a2b-bbc6-5c4e4c1c7f1d%40staff.uni-marburg.de.


signature.asc
Description: OpenPGP digital signature


[dspace-tech] Re: ORCID Patch Functionality Missing

2020-01-13 Thread Alex Fletcher
Glenn:

I downloaded the orcid_icon.png file that Jolene mentioned earlier and put 
it here:

- [dspace]/webapps/xmlui/themes/Mirage2/images
>

That seemed to do the trick for us.

Alex


On Monday, 13 January 2020 11:11:12 UTC-5, Glenn G wrote:
>
> Jolien,
>
> Our DSpace installation does not have the path you mentioned.  The Mirage2 
> directory is located here:
>
> [dspace]/webapps/xmlui/themes/Mirage2
>
> Our [dspace] directory is not literally "dspace".  It has the format, 
> id-dspace.  Also, our modules directory is located here:
>
> [dspace]/config/modules
>
> There are various possible reasons why our installation is different from 
> that anticipated by the patch:
>
> - It has been upgraded multiple times.
> - It was moved to a standalone server after being hosted on a server with 
> several other DSpace installations.
> - It was originally upgraded to 6.3 using the binary install.  I added the 
> [dspace-source] later in order to install patches.
>
> Nonetheless, Alex indicates the patch could be installed if I do one or 
> both of the following beforehand:
>
> - Put a copy of orcid_icon.png in [dspace]/webapps/xmlui/themes/Mirage2
> - Create a directory, 
> [dspace]/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 and put 
> orcid_icon.png there.
>
> Does either approach seem reasonable?
>
> Thanks,
> Glenn
>
> On Monday, January 13, 2020 at 2:16:51 AM UTC-6, Jolien (Atmire) wrote:
>>
>> In fact, the file should be contained in the patch. You can see that here 
>> (for the DSpace 6 version): 
>> https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png.
>>  
>> For some reason, it looks like it is not accessed correctly when you do the 
>> installation. 
>>
>> What could be happening is that in your DSpace installation, the path 
>> dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist 
>> or exists under a different name. Could you check that? 
>>
>> On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote:
>>>
>>> After applying the ORCID patch, the functionality my users were most 
>>> interested in is missing.  The ORCID logo does not appear next to the 
>>> author's name, and the name is not clickable, so a list of the author's 
>>> publications cannot be retrieved from ORCID as promised.  The ability to 
>>> search by ORCID number does now appear in the list of search modifiers, but 
>>> it only works when the entire number is supplied with the "equals" 
>>> operand.  The patch and functionality are described here:  
>>> https://atmire.github.io/expanded-ORCID-support/#/
>>>
>>> If you have any idea why the logo and linked name don't appear, please 
>>> let me know.  We are using the Mirage 2 theme.
>>>
>>> Thanks,
>>> Glenn
>>>
>>

-- 
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/316c040c-32dd-4780-9db3-ba641f629ecd%40googlegroups.com.


[dspace-tech] Re: ORCID Patch Functionality Missing

2020-01-13 Thread Glenn G
Oh, now it occurs to me that you meant 
[dspace-source]/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2.  
Yes, we have that directory, and no, orcid_icon.png does not exist there.  
Should I copy it there before applying the patch?

Thanks,
Glenn

On Monday, January 13, 2020 at 10:11:12 AM UTC-6, Glenn G wrote:
>
> Jolien,
>
> Our DSpace installation does not have the path you mentioned.  The Mirage2 
> directory is located here:
>
> [dspace]/webapps/xmlui/themes/Mirage2
>
> Our [dspace] directory is not literally "dspace".  It has the format, 
> id-dspace.  Also, our modules directory is located here:
>
> [dspace]/config/modules
>
> There are various possible reasons why our installation is different from 
> that anticipated by the patch:
>
> - It has been upgraded multiple times.
> - It was moved to a standalone server after being hosted on a server with 
> several other DSpace installations.
> - It was originally upgraded to 6.3 using the binary install.  I added the 
> [dspace-source] later in order to install patches.
>
> Nonetheless, Alex indicates the patch could be installed if I do one or 
> both of the following beforehand:
>
> - Put a copy of orcid_icon.png in [dspace]/webapps/xmlui/themes/Mirage2
> - Create a directory, 
> [dspace]/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 and put 
> orcid_icon.png there.
>
> Does either approach seem reasonable?
>
> Thanks,
> Glenn
>
> On Monday, January 13, 2020 at 2:16:51 AM UTC-6, Jolien (Atmire) wrote:
>>
>> In fact, the file should be contained in the patch. You can see that here 
>> (for the DSpace 6 version): 
>> https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png.
>>  
>> For some reason, it looks like it is not accessed correctly when you do the 
>> installation. 
>>
>> What could be happening is that in your DSpace installation, the path 
>> dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist 
>> or exists under a different name. Could you check that? 
>>
>> On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote:
>>>
>>> After applying the ORCID patch, the functionality my users were most 
>>> interested in is missing.  The ORCID logo does not appear next to the 
>>> author's name, and the name is not clickable, so a list of the author's 
>>> publications cannot be retrieved from ORCID as promised.  The ability to 
>>> search by ORCID number does now appear in the list of search modifiers, but 
>>> it only works when the entire number is supplied with the "equals" 
>>> operand.  The patch and functionality are described here:  
>>> https://atmire.github.io/expanded-ORCID-support/#/
>>>
>>> If you have any idea why the logo and linked name don't appear, please 
>>> let me know.  We are using the Mirage 2 theme.
>>>
>>> Thanks,
>>> Glenn
>>>
>>

-- 
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/de6606ce-8715-4bde-b59a-67ca1428b22c%40googlegroups.com.


Re: [dspace-tech] Custom logout page/redirect

2020-01-13 Thread Hawk, Patrick
Anyone have a suggestion?

On Mon, Jan 6, 2020 at 4:20 PM Patrick Hawk  wrote:

> Currently, if I log out of dspace I get a blank log out page.  I want to
> redirect to the main page instead.  How is this accomplished?
>
> --
> 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/af3a4c73-cb0b-4f81-8c06-0c5fcc4854c2%40googlegroups.com
> 
> .
>


-- 



Patrick Hawk

Computer and Technology Specialist

Miami University Libraries

314 King Library

151 S. Campus Ave.


Oxford, OH 45056


O: 513-529-6122 | haw...@miamioh.edu

-- 
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/CAH_HnmUtA572NR4XFVf_aDNsPFb%3DUbX28_kiH8vBa0vZCOqntQ%40mail.gmail.com.


[dspace-tech] Re: Long loading time: DSpace 5.5/XMLUI

2020-01-13 Thread Evelthon Prodromou
Adding the following configuration to dspace.cfg make a tremendous 
difference in loading time. It is now very responsive!
metadata.hide.dc.contributor.author = true

Any suggestions on how I can have authors displaying and be fast at the 
same time ?

Thank you,
Evelthon


-- 
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/35996248-2ac2-46f1-8c08-75628f375978%40googlegroups.com.


[dspace-tech] [DSpace-CRIS 6.3] Cannot access my researcher page

2020-01-13 Thread 'André Langer' via DSpace Technical Support

Hello everybody,

probably, I am not the first user with this issue, but I have not found a 
similar description or recommended solution so far for the following:

We have set up a clean installation of DSpace-CRIS-6.3 on an Ubuntu/Linux 
Mint VM with tomcat8 by following the installation steps in the Lyrassis 
Wiki.
I also executed the xls data model file twice (dspace 
load-cris-configuration -f [dspace]/etc/configuration-tool-demo.xls) and 
added -Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true to the tomcat 
startup.

I registered a user account for my email address and everything worked fine.
Then, I logged on successfully as a researcher and created a researcher 
page which initially contained my prename and surname.
But when I clicked on the edit page button, I got an error message that I 
am unauthorized to access the page.
I checked [dspace]/bin/dspace database migrate and [dspace]/bin/dspace 
database repair and everything is fine there.

I then signed off as a researcher and logged in as an administrator and 
went to Administration -> View all researchers. 
When I then clicked on either the Internal ID or UUID, I got an exception 
via email stating

Exception:
org.springframework.web.util.NestedServletException: Request processing 
failed; nested exception is java.lang.ClassCastException: java.lang.Integer 
cannot be cast to java.math.BigInteger
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:963)
at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.springframework.orm.hibernate4.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:149)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:106)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.dspace.app.webui.cris.filter.DSpaceContextCleanupFilter.doFilter(DSpaceContextCleanupFilter.java:54)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:106)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at 
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:798)
at 
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at 
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at 

[dspace-tech] [DSpace-CRIS] Cannot edit my researcher page

2020-01-13 Thread 'André Langer' via DSpace Technical Support

Hello everybody,

probably, I am not the first user with this issue, but I have not found a 
similar description or recommended solution so far for the following:

We have set up a clean installation of DSpace-CRIS-6.3 on an Ubuntu/Linux 
Mint VM with tomcat8 by following the installation steps in the Lyrassis 
Wiki.
I also executed the xls data model file twice (dspace 
load-cris-configuration -f [dspace]/etc/configuration-tool-demo.xls) and 
added -Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true to the tomcat 
startup.

I registered a user account for my email address and everything worked fine.
Then, I logged on successfully as a researcher and created a researcher 
page which initially contained my prename and surname.
But when I clicked on the edit page button, I got an error message that I 
am unauthorized to access the page.
I checked [dspace]/bin/dspace database migrate and [dspace]/bin/dspace 
database repair and everything is fine there.

I then signed off as a researcher and logged in as an administrator and 
went to Administration -> View all researchers. 
When I then clicked on either the Internal ID or UUID, I got an exception 
via email stating

Exception:
org.springframework.web.util.NestedServletException: Request processing 
failed; nested exception is java.lang.ClassCastException: java.lang.Integer 
cannot be cast to java.math.BigInteger
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:963)
at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.springframework.orm.hibernate4.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:149)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:106)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.dspace.app.webui.cris.filter.DSpaceContextCleanupFilter.doFilter(DSpaceContextCleanupFilter.java:54)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:106)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at 
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:798)
at 
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at 
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
at 

[dspace-tech] Re: ORCID Patch Functionality Missing

2020-01-13 Thread Jolien (Atmire)
In fact, the file should be contained in the patch. You can see that here 
(for the DSpace 6 version): 
https://github.com/atmire/expanded-ORCID-support/blob/stable_6x/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/images/orcid_icon.png.
 
For some reason, it looks like it is not accessed correctly when you do the 
installation. 

What could be happening is that in your DSpace installation, the path 
dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2 does not exist 
or exists under a different name. Could you check that? 

On Tuesday, December 3, 2019 at 12:10:42 AM UTC+1, Glenn G wrote:
>
> After applying the ORCID patch, the functionality my users were most 
> interested in is missing.  The ORCID logo does not appear next to the 
> author's name, and the name is not clickable, so a list of the author's 
> publications cannot be retrieved from ORCID as promised.  The ability to 
> search by ORCID number does now appear in the list of search modifiers, but 
> it only works when the entire number is supplied with the "equals" 
> operand.  The patch and functionality are described here:  
> https://atmire.github.io/expanded-ORCID-support/#/
>
> If you have any idea why the logo and linked name don't appear, please let 
> me know.  We are using the Mirage 2 theme.
>
> Thanks,
> Glenn
>

-- 
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/9555c45e-cabf-4874-9724-7ce6b3ed719e%40googlegroups.com.