Hi Julius, It looks like you already got an answer to this on Slack as well. But, just to verify/validate the answer here.
DSpace 7 will support the same command line tools as DSpace 6 (including the package importer/exporter, AIP import/export, etc). DSpace 7 is built on the same backend. DSpace 7 is essentially a new User Interface and REST API on the existing backend. So the backend tools will be unchanged between DSpace 6 and DSpace 7. DSpace 7 is not yet easy to install and use, as it's still under very heavy development. We anticipate a Beta release later this year (hopefully by end of 2018). At that point, it should be easier to install and test against. Currently, I would not recommend using DSpace 7 as it is not yet guaranteed stable. My recommendation would be to use DSpace 6 for all your migration testing. As noted, the backend import/export tools in DSpace 6 and 7 should be nearly identical (currently they are identical -- I don't anticipate any changes, but if there are any, they will be minor). So, any migrations you can do to DSpace 6 should also be doable into DSpace 7. It's also worth noting that migrating/upgrading data from DSpace 6 to 7 will be a seamless process -- we have an automated DSpace database upgrade process that has been in place for some time. That automated database update will also work from DSpace 6 to DSpace 7. So, you could also choose to migrate your data to DSpace 6, and then simply install DSpace 7 against that database (once it is available), that will automatically upgrade your data to DSpace 7 compliance. More information on the usual DSpace upgrade process can be found at https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace I hope that helps explain things further! Do let us know on this list (or Slack) if you have more questions. And, welcome to DSpace!! - Tim On Tue, Aug 7, 2018 at 9:21 AM <[email protected]> wrote: > We (Technical University Vienna) are about to move the data in our > “homegrown” institutional repository to dSpace. We are planning to use > DSpace7. Inspired by this article ( > https://duraspace.org/migrating-to-dspace/ ) we want to use AIPs > (Archival Information Packages) to migrate the data. Concerning this I have > got two questions: > > > > > - Will the Package Importer and Exporter command line tool still be a > part of DSpace7 ? Does it make sense to implement the data migration using > AIPs and the command line tool if we are going to use DSpace7? > - As there is no release candidate yet: Can DSpace7 already be > installed and tested? Does it make sense to get the source from github and > try to install it? As dSpace 7 is still in development I do not expect that > it works perfectly fine. All I need to know is if it is already possible to > test out migration strategy on a DSpace7 instance. > > Thanks for your help > > Julius > > -- > 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 post to this group, send email to [email protected]. > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
