Hi David, The Backend (meaning the REST API, OAI-PMH, SWORD, database, Solr, etc) is mostly unchanged *except* that everything has been moved over to Spring Boot & latest versions of Spring technologies (and Java 11 and Solr 7). In DSpace 6.x, we were stuck on some older/outdated dependencies because of the aging UIs (especially the XMLUI). So, we can now update the backend more easily.
That said, those changes did not impact most of the configurations or Java code on the backend. So, yes, the OAI-PMH interface is still there, and it's still pretty much the same as it was in DSpace 6.x (using the same configurations). 7.0 is only about a new REST API and Angular UI. We did not overhaul the entire system, but some other minor changes were necessary when updating to Spring Boot and similar. That said, most configurations in 6.x will work the same in 7.x (the only major exception I can think of is the submission configurations, which we are working on an automated migration for from 6.x to 7.x). We've started some early notes on the upgrade at https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace However, those instructions are not yet fully complete (and for example do not yet include the update of submission configurations, as that work is not yet completed). Tim ________________________________ From: [email protected] <[email protected]> Sent: Thursday, September 10, 2020 7:37 PM To: Tim Donohue <[email protected]>; 'Michael Plate' <[email protected]>; [email protected] <[email protected]> Subject: RE: [dspace-tech] Insight into DSpace 7 Thanks, Tim! Those links really are very helpful. It’s so interesting that Angular was chosen from a UI competition! I look forward to those production-level installation instructions. I have scale on my mind at lot these days. Would it be possible to run multiple REST API nodes and multiple UI nodes? How much of the existing DSpace system is going to be retained? I imagine a lot of the OAI-PMH code, handle server, and such will remain untouched? David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: [email protected] <[email protected]> On Behalf Of Tim Donohue Sent: Friday, 11 September 2020 1:25 AM To: Michael Plate <[email protected]>; [email protected] Subject: Re: [dspace-tech] Insight into DSpace 7 Michael, Yes, for the UI you need to have some form of HTTP server to serve the app. We will have production-level installation instructions forthcoming (as there's several options) but using something like PM2 (https://pm2.keymetrics.io/) would work. Depending on your local needs, you might want to proxy it behind Apache Web Server or similar. The UI may be on a separate server or on the same one as the REST API. You could even have both the UI and REST API behind the same Apache Web Server. We've got development-level setups/installations instructions available at https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7 . Those might give you more of a feel for what DSpace 7 is looking like. Tim ________________________________ From: [email protected]<mailto:[email protected]> on behalf of Michael Plate Sent: Thursday, September 10, 2020 9:32 AM To: [email protected]<mailto:[email protected]> Subject: Re: [dspace-tech] Insight into DSpace 7 Hi Tim, Am 10.09.20 um 15:53 schrieb Tim Donohue: > Hi David, > > The quick (and simple) answer is that we chose to use Angular Universal > to support better SEO (Search Engine Optimization). Angular Universal > allows spiders (or other tools) that cannot run Javascript to still work > with DSpace 7. Without Angular Universal, if something could not > support Javascript, it would not be possible to use DSpace 7....and that > would even include screen readers or specialized browsers (or similar > tools) that do not support Javascript. With Angular Universal, if you > are using a tool that doesn't support Javascript, you are still able to > interact with the application as if it were plain HTML (though not all > features are available). […] in other words… for Angular we need a HTTP-Server which proxies Node / PM2 ? Michael -- 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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/94f182fb-341f-7c7f-f834-c5497019a7af%40bibliothek.uni-kassel.de. -- 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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB1148F7A09C6015973B103A49ED270%40DM5PR2201MB1148.namprd22.prod.outlook.com<https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB1148F7A09C6015973B103A49ED270%40DM5PR2201MB1148.namprd22.prod.outlook.com?utm_medium=email&utm_source=footer>. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11485344A35BE27811459110ED240%40DM5PR2201MB1148.namprd22.prod.outlook.com.
