Migrating from Repository Tools 1 to Repository Tools 2

If you are planning to migrate your repository integration from Repository Tools 1 to a newer Repository Tools 2 integration, there are a number of steps in the process that you will need to consider and plan for:

1. Decide whether to use the Symplectic Migration Service or to self-migrate

2. Plan field mappings for Harvest and Deposit crosswalk maps

3. Customise harvest and deposit crosswalk map

4. Configure the Repository Tools 2 connector

5. Test Crosswalks (and adjust if needed)

6. Configure additional RT2 features as desired (eg. automated metadata updates)

7. Run process to transfer RT1 deposit links to RT2 (optional)

8. Review and adjust OA Policy

9. Adjust other integrations which make use of RT1 metadata fields in other systems and review other system settings as required

10. Plan go-live & cut-over from RT1 to RT2

11. Remove RT1 code from repository server

For further guidance on planning a migration, please see the attached PDF.

For additional information about how to configure RT2, please see the documentation in the Repository Tools and Open Access Monitor folder.

If you choose to use the Symplectic RT2 Migration Service a member of our technical services team will:

• Help you plan your new crosswalk mappings,

• Write your new crosswalk maps (a harvest crosswalk map and a deposit crosswalk map),

• Help you configure the integration including configuring a relevance scheme and setting up automated metadata updates if desired.

They will also guide you on what you'll need to do to adjust any other existing integrations (eg. that you are sending handles etc to from Elements) and give your team an introduction to how to work with your crosswalks so that your team feels empowered to be able to maintain (eg. add extra fields from time to time) the crosswalks going forward.

For pricing information or further information about the RT2 Migration Service, please submit a support ticket.

• Preparing for an RT2 Migration (1).pdf