1. Documentation
2. 2024.1 (Latest) 2024.0 10.3 10.2 10.1 10.0 9.10 9.9 9.8 9.7 9.6 9.5 9.4 9.3 9.2 9.1 9.0 8.2 8.1 8.0 7.6
3. Studio
4. Getting started
5. Migrate a legacy Repository

Migrate a legacy Repository

Legacy Repositories

The behavior of a legacy Repository is unchanged. In a legacy Repository, the focus is on the file types that are central to RapidMiner Studio, such as data sets, processes, and models. As of RapidMiner Studio 9.7, a local Repository accepts arbitrary file types, to make it easier for you to keep all your work in one place.

If you want to migrate your legacy Repositories, a manual copy-and-paste migration is required, because file handling has been changed to accommodate arbitrary file types. In particular, when you copy or move a binary entry from a legacy Repository to a new Repository, you must rename it to properly reflect its content type. For example, if you had a PDF file in a legacy Repository, you must add the file extension .pdf to the name during migration. Any processes that need access to the file should to be modified to reflect the name change.

Migration

To migrate a legacy Repository, take the following steps:

1. Create a new local Repository.

   

   

2. Copy the connections from the legacy Repository to the new local Repository by selecting all the connections, then copying and pasting them into the new local Repository's Connections folder.

3. Copy the remaining contents from the legacy Repository to the new local Repository by first selecting all the files and folders in the legacy Repository, then copying and pasting them into the new local Repository.

4. In the new local Repository, rename blob entries by right-clicking the blob entry and selecting Rename (or press F2 with the blob entry selected).

5. In the new local Repository, update processes using the blob entries to match the new name.