-
Notifications
You must be signed in to change notification settings - Fork 35
4.0.0 Migration From Vireo3 For TDL Hosted ETDs
Migration from Vireo3 to Vireo4 will happen in several steps and will require several interactions with TDL. There will be a period where a Vireo4 migration server and the current Vireo3 server will both be active. This will allow time to customize and test drive Vireo4. When it is time to completely migrate to Vireo4 then a final migration of all interim activity on Vireo3 can be ported to the running Vireo4 instance.
A Vireo4 server will be established for your institution. Initially this server will have a URL which is comprised of the name of your institution followed by '-migrate-etd.tdl.org.' When it is time to close down Vireo3 and use Vireo4 exclusively then the current Vireo3 URL can be updated to point to the Vireo4 server and the '-migrate-etd' domain name will be dropped.
You will then be asked to create an account for administering the site for the entire institution. This will just be created as a regular account. (Depending on what is in place at this time for your institution this could be a shibboleth account or an email password account).
Once this account is created please contact TDL and identify the account. A TDL developer will provide administrative role privileges to this account.
Go to 'Settings' and declare the institutional name and structure under settings. Once that is done please contact TDL and a developer will determine the mapping between the vireo3 college, department, and program settings and the new organizational structure. This may require some conversation between you and TDL to complete.
The migration of data from Vireo3 to Vireo4 will take about a day. This will include all user accounts, user submissions, data files for those submissions, action log entries and custom actions. After that you will be asked to confirm that the data looks intact and there are no obvious errors.
You will be able to use both Vireo3 and Vireo4 simultaneously with some restrictions. Data creation (user accounts, submissions) should be mutually exclusive though - data entered into one should not be replicated in the other.
Once you decide to move all work completely to Vireo4 then a final incremental migration can be requested. This will update data in Vireo4 which was previously migrated from Vireo3.