Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

2024-07-26 Thread suresh patil
Hi All,

anybody running DSpace 7.6.1 in the LAN through LAN IP without HTTPS?

if so please give the complete settings.


 Repository works fine in the same system where i have installed DSpace 
through URL : http://IP:4000

but while trying to access it from another system within the LAN it shows 
500 service unavailable error.

i have done the following changes. HAVE I MISSED ANYTHING???

   1. local.cfg - replaced localhost with LAN IP & added  
rest.cors.allowed-origins 
   = ${dspace.ui.url}
   2. config.prod.yml - replaced localhost with LAN IP


Thanks & Regards
Suresh Patil

On Wednesday, July 24, 2024 at 2:26:28 PM UTC+5:30 suresh patil wrote:

> Any changes required to be done in the following files apart from 
> local.cfg  & config.prod.yml
>
>
> /etc/tomcat9/server.xml
> dspace.conf
>
> On Friday, March 3, 2023 at 4:38:48 PM UTC+5:30 Rupinder Singh wrote:
>
>> Hi everyone 
>> this is what I tried and resolved this issue 
>> edit your local.cfg file 
>> and search for the parameter where dspace UI URL is defined 
>> it should be something like this 
>>
>> *dspace.ui.url = http://{your IP Address}:4000*
>> below this line add the following directive 
>> rest.cors.allowed-origins = ${dspace.ui.url}  
>>
>> Restart your tomcat service and try accessing the dspace over the network 
>> via the server IP address. 
>> It should work just fine. 
>>
>> Thanks 
>> Rupinder Singh
>> Assistant Librarian 
>> Central University of Punjab
>>
>> On Tuesday, December 27, 2022 at 5:10:18 AM UTC+5:30 Mohammad S. 
>> AlMutairi wrote:
>>
>>> Hello Alex,
>>>
>>> I need you to send me these files. I'll modify them for you.
>>>
>>>
>>>1. /etc/tomcat9/server.xml
>>>2. local.cfg
>>>3. config.prod.yml
>>>4. dspace.conf
>>>
>>>
>>> Cheers
>>>
>>> On Tuesday, December 27, 2022 at 1:29:54 AM UTC+3 aperez...@gmail.com 
>>> wrote:
>>>


 [image: error3.PNG]
 El lunes, 26 de diciembre de 2022 a las 15:35:49 UTC-6, Alex Perez 
 escribió:

>  Dspace 7.4 CORS error.mp4 
> 
> Problem Blocked CORS  https / http
>
>
> Hello friends I hope you are very well, I would like to ask for help 
> with the following already set up my DSpace server in a test environment 
> and then get to do production and works well the backend communicates 
> well 
> with the frontend on port 8443 I set it in Tomcat 9. 58 and use the 
> Reverse 
> Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add 
> the module a2enmod headers to send the policy "X-Forwarded-Proto: https" 
> so 
> far so good but when loading the site https://ride2.tse.go.cr where 
> the proxy is responsible for redirecting to port 4000 the CORS policy 
> blocks me from sites like "https://api7.dspace.org/server/api;, 
> https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
>  
> ".  
>  I do not know what else can be changed to correct this blocking CORS 
> and already load my site as it does instantly and then already sends an 
> error 500 that I could not correct in this version in 7.2 I did not pass 
> that and worked fine.
>
> thank you very much in advance for the help you can give me
>
>
>
> El vie, 25 nov 2022 a las 7:05, Alex Perez () 
> escribió:
>
>> Hello friends, I followed the steps you indicate me I reinstalled the 
>> frontend and the video gave me an idea of what to do and work correctly 
>> thank you very much for the help.
>>
>> Regards
>>
>>
>> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, 
>> alo...@gmail.com escribió:
>>
>>> I had to try it on DSpace version 7.5-SNAPSHOT and it's working just 
>>> fine without any SSL configuration (HTTP Setup) so it's not hard coded 
>>> as I 
>>> thought. See the attached video as a confirmation. Try to pull a fresh 
>>> copy 
>>> of dspace-angular and start a front end fresh installation.
>>>
>>> Settings in dspace.cfg
>>> dspace.server.url = http:// 192.168.100.212:8080/server
>>> dspace.ui.url = http://192.168.100.212:4000
>>>
>>> Settings in config.prod.yml:
>>> ui:
>>>   ssl: false
>>>   host: 192.168.100.212
>>>   port: 4000
>>>   nameSpace: /
>>>
>>> rest:
>>>   ssl: false
>>>   host: 192.168.100.212
>>>   port: 8080
>>>   nameSpace: /server
>>>
>>> -- 
>> All messages to this mailing list should adhere to the Code of 
>> Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> --- 
>> 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 view this 

Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

2024-07-24 Thread suresh patil
Any changes required to be done in the following files apart from 
local.cfg  & config.prod.yml


/etc/tomcat9/server.xml
dspace.conf

On Friday, March 3, 2023 at 4:38:48 PM UTC+5:30 Rupinder Singh wrote:

> Hi everyone 
> this is what I tried and resolved this issue 
> edit your local.cfg file 
> and search for the parameter where dspace UI URL is defined 
> it should be something like this 
>
> *dspace.ui.url = http://{your IP Address}:4000*
> below this line add the following directive 
> rest.cors.allowed-origins = ${dspace.ui.url}  
>
> Restart your tomcat service and try accessing the dspace over the network 
> via the server IP address. 
> It should work just fine. 
>
> Thanks 
> Rupinder Singh
> Assistant Librarian 
> Central University of Punjab
>
> On Tuesday, December 27, 2022 at 5:10:18 AM UTC+5:30 Mohammad S. AlMutairi 
> wrote:
>
>> Hello Alex,
>>
>> I need you to send me these files. I'll modify them for you.
>>
>>
>>1. /etc/tomcat9/server.xml
>>2. local.cfg
>>3. config.prod.yml
>>4. dspace.conf
>>
>>
>> Cheers
>>
>> On Tuesday, December 27, 2022 at 1:29:54 AM UTC+3 aperez...@gmail.com 
>> wrote:
>>
>>>
>>>
>>> [image: error3.PNG]
>>> El lunes, 26 de diciembre de 2022 a las 15:35:49 UTC-6, Alex Perez 
>>> escribió:
>>>
  Dspace 7.4 CORS error.mp4 
 
 Problem Blocked CORS  https / http


 Hello friends I hope you are very well, I would like to ask for help 
 with the following already set up my DSpace server in a test environment 
 and then get to do production and works well the backend communicates well 
 with the frontend on port 8443 I set it in Tomcat 9. 58 and use the 
 Reverse 
 Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add 
 the module a2enmod headers to send the policy "X-Forwarded-Proto: https" 
 so 
 far so good but when loading the site https://ride2.tse.go.cr where 
 the proxy is responsible for redirecting to port 4000 the CORS policy 
 blocks me from sites like "https://api7.dspace.org/server/api;, 
 https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
  
 ".  
  I do not know what else can be changed to correct this blocking CORS 
 and already load my site as it does instantly and then already sends an 
 error 500 that I could not correct in this version in 7.2 I did not pass 
 that and worked fine.

 thank you very much in advance for the help you can give me



 El vie, 25 nov 2022 a las 7:05, Alex Perez () 
 escribió:

> Hello friends, I followed the steps you indicate me I reinstalled the 
> frontend and the video gave me an idea of what to do and work correctly 
> thank you very much for the help.
>
> Regards
>
>
> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, 
> alo...@gmail.com escribió:
>
>> I had to try it on DSpace version 7.5-SNAPSHOT and it's working just 
>> fine without any SSL configuration (HTTP Setup) so it's not hard coded 
>> as I 
>> thought. See the attached video as a confirmation. Try to pull a fresh 
>> copy 
>> of dspace-angular and start a front end fresh installation.
>>
>> Settings in dspace.cfg
>> dspace.server.url = http:// 192.168.100.212:8080/server
>> dspace.ui.url = http://192.168.100.212:4000
>>
>> Settings in config.prod.yml:
>> ui:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 4000
>>   nameSpace: /
>>
>> rest:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 8080
>>   nameSpace: /server
>>
>> -- 
> All messages to this mailing list should adhere to the Code of 
> Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> --- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/dd632e3d-837a-44aa-90e7-e37cf6671e70n%40googlegroups.com
>  
> 
> .
>


-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 

Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

2024-07-24 Thread suresh patil
Hi Rupinder,

i have added below part

*dspace.ui.url = http://{your IP Address}:4000*
below this line add the following directive 
rest.cors.allowed-origins = ${dspace.ui.url}  


still the website shows 500 error when tried to access from other system 
within the LAN (it works fine with the *{your IP Address}:4000* from the 
system where DSpace is installed)

Thanks

On Friday, March 3, 2023 at 4:38:48 PM UTC+5:30 Rupinder Singh wrote:

> Hi everyone 
> this is what I tried and resolved this issue 
> edit your local.cfg file 
> and search for the parameter where dspace UI URL is defined 
> it should be something like this 
>
> *dspace.ui.url = http://{your IP Address}:4000*
> below this line add the following directive 
> rest.cors.allowed-origins = ${dspace.ui.url}  
>
> Restart your tomcat service and try accessing the dspace over the network 
> via the server IP address. 
> It should work just fine. 
>
> Thanks 
> Rupinder Singh
> Assistant Librarian 
> Central University of Punjab
>
> On Tuesday, December 27, 2022 at 5:10:18 AM UTC+5:30 Mohammad S. AlMutairi 
> wrote:
>
>> Hello Alex,
>>
>> I need you to send me these files. I'll modify them for you.
>>
>>
>>1. /etc/tomcat9/server.xml
>>2. local.cfg
>>3. config.prod.yml
>>4. dspace.conf
>>
>>
>> Cheers
>>
>> On Tuesday, December 27, 2022 at 1:29:54 AM UTC+3 aperez...@gmail.com 
>> wrote:
>>
>>>
>>>
>>> [image: error3.PNG]
>>> El lunes, 26 de diciembre de 2022 a las 15:35:49 UTC-6, Alex Perez 
>>> escribió:
>>>
  Dspace 7.4 CORS error.mp4 
 
 Problem Blocked CORS  https / http


 Hello friends I hope you are very well, I would like to ask for help 
 with the following already set up my DSpace server in a test environment 
 and then get to do production and works well the backend communicates well 
 with the frontend on port 8443 I set it in Tomcat 9. 58 and use the 
 Reverse 
 Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add 
 the module a2enmod headers to send the policy "X-Forwarded-Proto: https" 
 so 
 far so good but when loading the site https://ride2.tse.go.cr where 
 the proxy is responsible for redirecting to port 4000 the CORS policy 
 blocks me from sites like "https://api7.dspace.org/server/api;, 
 https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
  
 ".  
  I do not know what else can be changed to correct this blocking CORS 
 and already load my site as it does instantly and then already sends an 
 error 500 that I could not correct in this version in 7.2 I did not pass 
 that and worked fine.

 thank you very much in advance for the help you can give me



 El vie, 25 nov 2022 a las 7:05, Alex Perez () 
 escribió:

> Hello friends, I followed the steps you indicate me I reinstalled the 
> frontend and the video gave me an idea of what to do and work correctly 
> thank you very much for the help.
>
> Regards
>
>
> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, 
> alo...@gmail.com escribió:
>
>> I had to try it on DSpace version 7.5-SNAPSHOT and it's working just 
>> fine without any SSL configuration (HTTP Setup) so it's not hard coded 
>> as I 
>> thought. See the attached video as a confirmation. Try to pull a fresh 
>> copy 
>> of dspace-angular and start a front end fresh installation.
>>
>> Settings in dspace.cfg
>> dspace.server.url = http:// 192.168.100.212:8080/server
>> dspace.ui.url = http://192.168.100.212:4000
>>
>> Settings in config.prod.yml:
>> ui:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 4000
>>   nameSpace: /
>>
>> rest:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 8080
>>   nameSpace: /server
>>
>> -- 
> All messages to this mailing list should adhere to the Code of 
> Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> --- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/dd632e3d-837a-44aa-90e7-e37cf6671e70n%40googlegroups.com
>  
> 
> .
>


-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To 

Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

2022-12-26 Thread Mohammad S. AlMutairi
Hello Alex,

I need you to send me these files. I'll modify them for you.


   1. /etc/tomcat9/server.xml
   2. local.cfg
   3. config.prod.yml
   4. dspace.conf


Cheers

On Tuesday, December 27, 2022 at 1:29:54 AM UTC+3 aperez...@gmail.com wrote:

>
>
> [image: error3.PNG]
> El lunes, 26 de diciembre de 2022 a las 15:35:49 UTC-6, Alex Perez 
> escribió:
>
>>  Dspace 7.4 CORS error.mp4 
>> 
>> Problem Blocked CORS  https / http
>>
>>
>> Hello friends I hope you are very well, I would like to ask for help with 
>> the following already set up my DSpace server in a test environment and 
>> then get to do production and works well the backend communicates well with 
>> the frontend on port 8443 I set it in Tomcat 9. 58 and use the Reverse 
>> Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add 
>> the module a2enmod headers to send the policy "X-Forwarded-Proto: https" so 
>> far so good but when loading the site https://ride2.tse.go.cr where the 
>> proxy is responsible for redirecting to port 4000 the CORS policy blocks me 
>> from sites like "https://api7.dspace.org/server/api;, 
>> https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
>>  
>> ".  
>>  I do not know what else can be changed to correct this blocking CORS and 
>> already load my site as it does instantly and then already sends an error 
>> 500 that I could not correct in this version in 7.2 I did not pass that and 
>> worked fine.
>>
>> thank you very much in advance for the help you can give me
>>
>>
>>
>> El vie, 25 nov 2022 a las 7:05, Alex Perez () 
>> escribió:
>>
>>> Hello friends, I followed the steps you indicate me I reinstalled the 
>>> frontend and the video gave me an idea of what to do and work correctly 
>>> thank you very much for the help.
>>>
>>> Regards
>>>
>>>
>>> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, 
>>> alo...@gmail.com escribió:
>>>
 I had to try it on DSpace version 7.5-SNAPSHOT and it's working just 
 fine without any SSL configuration (HTTP Setup) so it's not hard coded as 
 I 
 thought. See the attached video as a confirmation. Try to pull a fresh 
 copy 
 of dspace-angular and start a front end fresh installation.

 Settings in dspace.cfg
 dspace.server.url = http:// 192.168.100.212:8080/server
 dspace.ui.url = http://192.168.100.212:4000

 Settings in config.prod.yml:
 ui:
   ssl: false
   host: 192.168.100.212
   port: 4000
   nameSpace: /

 rest:
   ssl: false
   host: 192.168.100.212
   port: 8080
   nameSpace: /server

 -- 
>>> All messages to this mailing list should adhere to the Code of Conduct: 
>>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>>> --- 
>>> 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 view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/dspace-tech/dd632e3d-837a-44aa-90e7-e37cf6671e70n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/61fc0f80-a417-453a-bbe0-f2f1fd26ef1dn%40googlegroups.com.


Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

2022-12-26 Thread Alex Perez


[image: error3.PNG]
El lunes, 26 de diciembre de 2022 a las 15:35:49 UTC-6, Alex Perez escribió:

>  Dspace 7.4 CORS error.mp4 
> 
> Problem Blocked CORS  https / http
>
>
> Hello friends I hope you are very well, I would like to ask for help with 
> the following already set up my DSpace server in a test environment and 
> then get to do production and works well the backend communicates well with 
> the frontend on port 8443 I set it in Tomcat 9. 58 and use the Reverse 
> Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add 
> the module a2enmod headers to send the policy "X-Forwarded-Proto: https" so 
> far so good but when loading the site https://ride2.tse.go.cr where the 
> proxy is responsible for redirecting to port 4000 the CORS policy blocks me 
> from sites like "https://api7.dspace.org/server/api;, 
> https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
>  
> ".  
>  I do not know what else can be changed to correct this blocking CORS and 
> already load my site as it does instantly and then already sends an error 
> 500 that I could not correct in this version in 7.2 I did not pass that and 
> worked fine.
>
> thank you very much in advance for the help you can give me
>
>
>
> El vie, 25 nov 2022 a las 7:05, Alex Perez () 
> escribió:
>
>> Hello friends, I followed the steps you indicate me I reinstalled the 
>> frontend and the video gave me an idea of what to do and work correctly 
>> thank you very much for the help.
>>
>> Regards
>>
>>
>> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, alo...@gmail.com 
>> escribió:
>>
>>> I had to try it on DSpace version 7.5-SNAPSHOT and it's working just 
>>> fine without any SSL configuration (HTTP Setup) so it's not hard coded as I 
>>> thought. See the attached video as a confirmation. Try to pull a fresh copy 
>>> of dspace-angular and start a front end fresh installation.
>>>
>>> Settings in dspace.cfg
>>> dspace.server.url = http:// 192.168.100.212:8080/server
>>> dspace.ui.url = http://192.168.100.212:4000
>>>
>>> Settings in config.prod.yml:
>>> ui:
>>>   ssl: false
>>>   host: 192.168.100.212
>>>   port: 4000
>>>   nameSpace: /
>>>
>>> rest:
>>>   ssl: false
>>>   host: 192.168.100.212
>>>   port: 8080
>>>   nameSpace: /server
>>>
>>> -- 
>> All messages to this mailing list should adhere to the Code of Conduct: 
>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> --- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/dd632e3d-837a-44aa-90e7-e37cf6671e70n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/015a1143-4b7e-4041-bad5-1de8fd591220n%40googlegroups.com.


Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

2022-12-26 Thread Alex Perez
 Dspace 7.4 CORS error.mp4

Problem Blocked CORS  https / http


Hello friends I hope you are very well, I would like to ask for help with
the following already set up my DSpace server in a test environment and
then get to do production and works well the backend communicates well with
the frontend on port 8443 I set it in Tomcat 9. 58 and use the Reverse
Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add
the module a2enmod headers to send the policy "X-Forwarded-Proto: https" so
far so good but when loading the site https://ride2.tse.go.cr where the
proxy is responsible for redirecting to port 4000 the CORS policy blocks me
from sites like "https://api7.dspace.org/server/api;,
https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
".
 I do not know what else can be changed to correct this blocking CORS and
already load my site as it does instantly and then already sends an error
500 that I could not correct in this version in 7.2 I did not pass that and
worked fine.

thank you very much in advance for the help you can give me



El vie, 25 nov 2022 a las 7:05, Alex Perez ()
escribió:

> Hello friends, I followed the steps you indicate me I reinstalled the
> frontend and the video gave me an idea of what to do and work correctly
> thank you very much for the help.
>
> Regards
>
>
> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, alo...@gmail.com
> escribió:
>
>> I had to try it on DSpace version 7.5-SNAPSHOT and it's working just fine
>> without any SSL configuration (HTTP Setup) so it's not hard coded as I
>> thought. See the attached video as a confirmation. Try to pull a fresh copy
>> of dspace-angular and start a front end fresh installation.
>>
>> Settings in dspace.cfg
>> dspace.server.url = http:// 192.168.100.212:8080/server
>> dspace.ui.url = http://192.168.100.212:4000
>>
>> Settings in config.prod.yml:
>> ui:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 4000
>>   nameSpace: /
>>
>> rest:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 8080
>>   nameSpace: /server
>>
>> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> 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/dd632e3d-837a-44aa-90e7-e37cf6671e70n%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/CAM524nY-0k0LOxp79Hbebu%2Be8ku09eYddd2U0giyQuNODTGseA%40mail.gmail.com.