Re: [dspace-tech] Problem indexing OAI
I just upgraded to DSpace 6.3 today and I have not yet been able to get the oai import to complete. ~400,000 items that I need to import. I am finding that the process keeps running out of memory. I had did not have problems running this in DSpace 5.x. I will post back if I discover something. On Fri, Jan 4, 2019 at 2:06 PM George Kozak wrote: > Tim: > I checked the max connections in postgres and dspace, and there was a > discrepancy, but after fixing that, I am still having the same problem. I > double checked the hibernate configs, and they are the defaults. So, I > have attached the error trace from my oai indexing job. Perhaps, that will > reveal something. > George Kozak > Cornell University > > On Fri, Jan 4, 2019 at 1:50 PM Tim Donohue wrote: > >> Hi George, >> >> That is an odd error. It almost sounds like Hibernate is losing access >> to the database (maybe a connection timeout or something?). >> >> Could you check your logs to see if there's more information around >> *when* and *how* this error occurs. You said it's occurring at different >> "intervals", but I'm wondering if there's any more information that can be >> gathered from the logs (or from the full stacktrace of the error, assuming >> one exists). >> >> For what it's worth, I've not seen this error before. It's hard to say >> right now if this is a configuration error or a bug. I think we'd need more >> information to narrow things down. It's *possible* there's something from >> your upgrade that resulted in a misconfiguration. You may want to double >> check that your Hibernate truly are the defaults, and that your Database >> connection settings & pooling info looks good. You also should double >> check that PostgreSQL (or Oracle) is configured to allow *at least* the >> number of connections that "db.maxconnections" allows -- if you increased >> the DSpace setting, it may be expecting more connections than your database >> is willing to provide. >> >> Just a few thoughts there. >> >> - Tim >> >> On Fri, Jan 4, 2019 at 12:02 PM George Kozak wrote: >> >>> Hi, Terry: >>> I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a >>> few months ago, and ran into trouble immediately with the OAI >>> index. Emilio Lorenzo and Adan Roman gave me a patch to >>> org.dspace.xoai.app.XOAI.java to print out records being indexed in verbose >>> mode, and that helped me locate a "bad" record that was causing our OAI >>> index to fail. I eliminated that record, and restarted our OAI process, >>> and then encountered the "org.hibernate.exception.JDBCConnectionException: >>> could not extract ResultSet". It doesn't appear to be a specific record >>> that is causing this because the crash occurs at different intervals during >>> the index. >>> I never adjusted the hibernate configuration (using defaults). Do you >>> think that may be the issue? >>> >>> George Kozak >>> Cornell University >>> >>> On Thu, Jan 3, 2019 at 4:36 PM Terry Brady >>> wrote: >>> George, I am not seeing this error. Is there any chance that you are using an older version of java (such as Java 7) when you run the dspace command? Did you upgrade recently? On Thu, Jan 3, 2019 at 11:02 AM George Kozak wrote: > Hi, > We are using DSpace 6.3 and we are seeing an error when running the > dspace oai import -c. The Import fails with > "org.hibernate.exception.JDBCConnectionException: could not extract > ResultSet". Has anyone else encountered this problem? > > -- > *** > George Kozak > Digital Library Specialist > Cornell University Library - IT > 218 Olin Library > Cornell University > Ithaca, NY 14853 > 607-255-8924 <(607)%20255-8924> > g...@cornell.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 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. > -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://github.com/terrywbrady/info 425-298-5498 <(425)%20298-5498> (Seattle, WA) -- 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 fr
Re: [dspace-tech] Problem indexing OAI
Tim: I checked the max connections in postgres and dspace, and there was a discrepancy, but after fixing that, I am still having the same problem. I double checked the hibernate configs, and they are the defaults. So, I have attached the error trace from my oai indexing job. Perhaps, that will reveal something. George Kozak Cornell University On Fri, Jan 4, 2019 at 1:50 PM Tim Donohue wrote: > Hi George, > > That is an odd error. It almost sounds like Hibernate is losing access to > the database (maybe a connection timeout or something?). > > Could you check your logs to see if there's more information around *when* > and *how* this error occurs. You said it's occurring at different > "intervals", but I'm wondering if there's any more information that can be > gathered from the logs (or from the full stacktrace of the error, assuming > one exists). > > For what it's worth, I've not seen this error before. It's hard to say > right now if this is a configuration error or a bug. I think we'd need more > information to narrow things down. It's *possible* there's something from > your upgrade that resulted in a misconfiguration. You may want to double > check that your Hibernate truly are the defaults, and that your Database > connection settings & pooling info looks good. You also should double > check that PostgreSQL (or Oracle) is configured to allow *at least* the > number of connections that "db.maxconnections" allows -- if you increased > the DSpace setting, it may be expecting more connections than your database > is willing to provide. > > Just a few thoughts there. > > - Tim > > On Fri, Jan 4, 2019 at 12:02 PM George Kozak wrote: > >> Hi, Terry: >> I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a >> few months ago, and ran into trouble immediately with the OAI >> index. Emilio Lorenzo and Adan Roman gave me a patch to >> org.dspace.xoai.app.XOAI.java to print out records being indexed in verbose >> mode, and that helped me locate a "bad" record that was causing our OAI >> index to fail. I eliminated that record, and restarted our OAI process, >> and then encountered the "org.hibernate.exception.JDBCConnectionException: >> could not extract ResultSet". It doesn't appear to be a specific record >> that is causing this because the crash occurs at different intervals during >> the index. >> I never adjusted the hibernate configuration (using defaults). Do you >> think that may be the issue? >> >> George Kozak >> Cornell University >> >> On Thu, Jan 3, 2019 at 4:36 PM Terry Brady >> wrote: >> >>> George, >>> >>> I am not seeing this error. >>> >>> Is there any chance that you are using an older version of java (such as >>> Java 7) when you run the dspace command? >>> >>> Did you upgrade recently? >>> >>> On Thu, Jan 3, 2019 at 11:02 AM George Kozak wrote: >>> Hi, We are using DSpace 6.3 and we are seeing an error when running the dspace oai import -c. The Import fails with "org.hibernate.exception.JDBCConnectionException: could not extract ResultSet". Has anyone else encountered this problem? -- *** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 <(607)%20255-8924> g...@cornell.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 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. >>> >>> >>> -- >>> Terry Brady >>> Applications Programmer Analyst >>> Georgetown University Library Information Technology >>> https://github.com/terrywbrady/info >>> 425-298-5498 <(425)%20298-5498> (Seattle, WA) >>> >>> -- >>> 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 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. >>> >> >> >> -- >> *** >> George Kozak >> Digital Library Specialist >> Cornell University Library - IT >> 218 Olin Library >> Cornell Un
Re: [dspace-tech] Problem indexing OAI
Thanks, Tim: I will take a look at the postgres configuration. When we upgraded, we, also, migrated to a new server and maybe there's a problem with the postgres settings. I didn't think about that, so I am glad you suggested it. If that's not it, I will be happy to send a more detailed trace of the error. George Kozak Cornell University On Fri, Jan 4, 2019 at 1:50 PM Tim Donohue wrote: > Hi George, > > That is an odd error. It almost sounds like Hibernate is losing access to > the database (maybe a connection timeout or something?). > > Could you check your logs to see if there's more information around *when* > and *how* this error occurs. You said it's occurring at different > "intervals", but I'm wondering if there's any more information that can be > gathered from the logs (or from the full stacktrace of the error, assuming > one exists). > > For what it's worth, I've not seen this error before. It's hard to say > right now if this is a configuration error or a bug. I think we'd need more > information to narrow things down. It's *possible* there's something from > your upgrade that resulted in a misconfiguration. You may want to double > check that your Hibernate truly are the defaults, and that your Database > connection settings & pooling info looks good. You also should double > check that PostgreSQL (or Oracle) is configured to allow *at least* the > number of connections that "db.maxconnections" allows -- if you increased > the DSpace setting, it may be expecting more connections than your database > is willing to provide. > > Just a few thoughts there. > > - Tim > > On Fri, Jan 4, 2019 at 12:02 PM George Kozak wrote: > >> Hi, Terry: >> I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a >> few months ago, and ran into trouble immediately with the OAI >> index. Emilio Lorenzo and Adan Roman gave me a patch to >> org.dspace.xoai.app.XOAI.java to print out records being indexed in verbose >> mode, and that helped me locate a "bad" record that was causing our OAI >> index to fail. I eliminated that record, and restarted our OAI process, >> and then encountered the "org.hibernate.exception.JDBCConnectionException: >> could not extract ResultSet". It doesn't appear to be a specific record >> that is causing this because the crash occurs at different intervals during >> the index. >> I never adjusted the hibernate configuration (using defaults). Do you >> think that may be the issue? >> >> George Kozak >> Cornell University >> >> On Thu, Jan 3, 2019 at 4:36 PM Terry Brady >> wrote: >> >>> George, >>> >>> I am not seeing this error. >>> >>> Is there any chance that you are using an older version of java (such as >>> Java 7) when you run the dspace command? >>> >>> Did you upgrade recently? >>> >>> On Thu, Jan 3, 2019 at 11:02 AM George Kozak wrote: >>> Hi, We are using DSpace 6.3 and we are seeing an error when running the dspace oai import -c. The Import fails with "org.hibernate.exception.JDBCConnectionException: could not extract ResultSet". Has anyone else encountered this problem? -- *** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 <(607)%20255-8924> g...@cornell.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 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. >>> >>> >>> -- >>> Terry Brady >>> Applications Programmer Analyst >>> Georgetown University Library Information Technology >>> https://github.com/terrywbrady/info >>> 425-298-5498 <(425)%20298-5498> (Seattle, WA) >>> >>> -- >>> 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 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. >>> >> >> >> -- >> *** >> George Kozak >> Digital Library Specialist >> Cornell University Library - IT >> 218 Olin Library >> Cornell Universi
Re: [dspace-tech] I want users to register their email
Unfortunately, we don't have enough information to help you resolve this issue. Please take a look at our guide on Troubleshooting Errors, which provides useful information about where to find error messages, where to search for answers, and what to send along to mailing lists for help: https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error After following that guide and searching for solutions, if you are still stuck, feel free to send the error messages to this list and we'll do our best to help out. Thanks Tim On Wed, Jan 2, 2019 at 7:53 AM Olamiji Gabriel wrote: > Dear sir, > I am very new to DSpace and I successfully installed version 6.0 but when > it generates error whenever a user tries to register. Pls what can I do to > fix this error. The error is error occur contact the administrator. > > -- > 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 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. > -- 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 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] IP-ADDRESS AUTHENTICATION
Hello, At this point in time, DSpace 7 IP based Authentication/Authorization is expected to function the same as DSpace 6 did. You can find DSpace 6 documentation on IP Authentication at: https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins#AuthenticationPlugins-IPAuthentication We always accept code enhancements/improvements. In fact, DSpace is almost entirely developed by its community of users and service providers. We have no centralized development team, and all feature planning & development occurs in a collaborative manner. If you, or anyone else, wishes to contribute to DSpace to improve or enhance IP Authentication (or any other feature), please see our Contribution guidelines at: https://wiki.duraspace.org/display/DSPACE/How+to+Contribute+to+DSpace and our Code Contribution Guidelines at: https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines If you have more specific questions regarding how IP authentication works, I'd recommend asking them on this mailing list or via one of the other Support options detailed at: https://wiki.duraspace.org/display/DSPACE/Support - Tim On Wed, Jan 2, 2019 at 7:53 AM 'Sami M. Abu Darbeya' via DSpace Technical Support wrote: > Dears, > > > Hope all is well with you, > > > Kindly, I have a question about Dspace (specially Dspace 7), how about > IP-Address Authentication? is there any plan to improve it. Why we can't > apply authentication directly even after we apply old authentication and we > add new items and plan to change authentication for all collection item. > > > Thanks > > -- > > The content of this email and its attachments and any views or opinions > presented in this email are solely those of the sender and do not represent > those of the Yarmouk University. Also, the recipient should check this > email and any attachments for the presence of viruses. Yarmouk University > will not accept any liability in respect of such communication or any > damage caused by any virus transmitted by this email or its attachments, > and the sender will be personally liable for any damages or other liability > arising. > ©Yarmouk University, Irbid-Jordan www.yu.edu.jo > > -- > 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 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. > -- 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 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] Problem indexing OAI
Hi George, That is an odd error. It almost sounds like Hibernate is losing access to the database (maybe a connection timeout or something?). Could you check your logs to see if there's more information around *when* and *how* this error occurs. You said it's occurring at different "intervals", but I'm wondering if there's any more information that can be gathered from the logs (or from the full stacktrace of the error, assuming one exists). For what it's worth, I've not seen this error before. It's hard to say right now if this is a configuration error or a bug. I think we'd need more information to narrow things down. It's *possible* there's something from your upgrade that resulted in a misconfiguration. You may want to double check that your Hibernate truly are the defaults, and that your Database connection settings & pooling info looks good. You also should double check that PostgreSQL (or Oracle) is configured to allow *at least* the number of connections that "db.maxconnections" allows -- if you increased the DSpace setting, it may be expecting more connections than your database is willing to provide. Just a few thoughts there. - Tim On Fri, Jan 4, 2019 at 12:02 PM George Kozak wrote: > Hi, Terry: > I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a few > months ago, and ran into trouble immediately with the OAI index. Emilio > Lorenzo and Adan Roman gave me a patch to org.dspace.xoai.app.XOAI.java to > print out records being indexed in verbose mode, and that helped me locate > a "bad" record that was causing our OAI index to fail. I eliminated that > record, and restarted our OAI process, and then encountered the > "org.hibernate.exception.JDBCConnectionException: could not extract > ResultSet". It doesn't appear to be a specific record that is causing this > because the crash occurs at different intervals during the index. > I never adjusted the hibernate configuration (using defaults). Do you > think that may be the issue? > > George Kozak > Cornell University > > On Thu, Jan 3, 2019 at 4:36 PM Terry Brady > wrote: > >> George, >> >> I am not seeing this error. >> >> Is there any chance that you are using an older version of java (such as >> Java 7) when you run the dspace command? >> >> Did you upgrade recently? >> >> On Thu, Jan 3, 2019 at 11:02 AM George Kozak wrote: >> >>> Hi, >>> We are using DSpace 6.3 and we are seeing an error when running the >>> dspace oai import -c. The Import fails with >>> "org.hibernate.exception.JDBCConnectionException: could not extract >>> ResultSet". Has anyone else encountered this problem? >>> >>> -- >>> *** >>> George Kozak >>> Digital Library Specialist >>> Cornell University Library - IT >>> 218 Olin Library >>> Cornell University >>> Ithaca, NY 14853 >>> 607-255-8924 <(607)%20255-8924> >>> g...@cornell.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 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. >>> >> >> >> -- >> Terry Brady >> Applications Programmer Analyst >> Georgetown University Library Information Technology >> https://github.com/terrywbrady/info >> 425-298-5498 <(425)%20298-5498> (Seattle, WA) >> >> -- >> 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 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. >> > > > -- > *** > George Kozak > Digital Library Specialist > Cornell University Library - IT > 218 Olin Library > Cornell University > Ithaca, NY 14853 > 607-255-8924 <(607)%20255-8924> > g...@cornell.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 post to this group, send email to dspace-tech@googlegroups.com
Re: [dspace-tech] Problem indexing OAI
Hi, Terry: I am using jdk1.8.0_74 so java 7 is not the problem. We did upgrade a few months ago, and ran into trouble immediately with the OAI index. Emilio Lorenzo and Adan Roman gave me a patch to org.dspace.xoai.app.XOAI.java to print out records being indexed in verbose mode, and that helped me locate a "bad" record that was causing our OAI index to fail. I eliminated that record, and restarted our OAI process, and then encountered the "org.hibernate.exception.JDBCConnectionException: could not extract ResultSet". It doesn't appear to be a specific record that is causing this because the crash occurs at different intervals during the index. I never adjusted the hibernate configuration (using defaults). Do you think that may be the issue? George Kozak Cornell University On Thu, Jan 3, 2019 at 4:36 PM Terry Brady wrote: > George, > > I am not seeing this error. > > Is there any chance that you are using an older version of java (such as > Java 7) when you run the dspace command? > > Did you upgrade recently? > > On Thu, Jan 3, 2019 at 11:02 AM George Kozak wrote: > >> Hi, >> We are using DSpace 6.3 and we are seeing an error when running the >> dspace oai import -c. The Import fails with >> "org.hibernate.exception.JDBCConnectionException: could not extract >> ResultSet". Has anyone else encountered this problem? >> >> -- >> *** >> George Kozak >> Digital Library Specialist >> Cornell University Library - IT >> 218 Olin Library >> Cornell University >> Ithaca, NY 14853 >> 607-255-8924 >> g...@cornell.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 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. >> > > > -- > Terry Brady > Applications Programmer Analyst > Georgetown University Library Information Technology > https://github.com/terrywbrady/info > 425-298-5498 (Seattle, WA) > > -- > 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 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. > -- *** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 g...@cornell.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 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.
