Migrating Your Data
Below are the Labs & Hospital Scripts. If you are only installing Labs or only Hospital, follow the directions in one section and ignore the other. If you are installing both, you'll need to follow both sets of instructions.
Expand | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
|
...
title | Click here to expand the Hospital Scripts |
---|
...
bgColor | FF66FF |
---|---|
borderWidth | 2 |
borderStyle | dashed |
title | Hospital Scripts |
Note |
---|
Script Instructions Scripts should be run in the specified order. Also, in the header of each script, there may be variables that need to be set with local values. Also in each file there is a placeholder DBLink of @UHOSPITAL.VETVIEW.UGA.EDU that will need to be either removed if migrating within the same database or replaced with the appropriate DBLink. |
...
Now, execute the Security & Roles script, which will take all the roles migrated from UVIS and upgrade them to fit in VetView. We aren't able to do a 1-to-1 mapping of UVIS privileges to VetView privileges, so we've given each UVIS role ALL privileges (making them like a super-admin). You'll need to tailor each role yourself before deploying in a production environment (Using the Role Management Screen).
Finally, execute the VetView Admin Account script. This script will create an admin account (username is administrator, password is VETVIEW-ADMIN). This will allow you to be able to get into the application to create other users if you aren't hooking it into LDAP.
Migrating Your Data
- Contact Client Support for help migrating data
Previous Step
...
Info |
---|
For anyone interested in how we mapped the data... |
...
Gliffy | ||||
---|---|---|---|---|
|