Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Removed

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
titleClick here to expand the Labs Scripts
Panel
borderWidth2
borderStyledashed
titleVetView Labs Scripts
Note
titleScript 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 @LABS.VET.UGA.EDU that will need to be either removed if migrating within the same database or replaced with the appropriate DBLink.

 

  1. Execute the Pre-Migration Script.
  2. Run the script named Migration Scripts 1-9.sql.
  3. Run the Missing Employee Script.
  4. Run the script named Migration Scripts 10-15.sql.

 

Tip

All employees come over associated with the role they were in UVIS.  However, every role imported into VetView is given ALL privileges by default.  You'll need to go through and edit each role's privileges.

Warning
titleBad Accession Numbers

With VetView we are making the assumption that Accessions Number have a basic structure of PREFIX - NUMBER - SUFFIX, so we are now storing in the accession table both a formatted accession number, but also the components of an accession number. The following script will help identify the accession numbers that are formatted incorrectly.

         SELECT * FROM uvis_dl_accessions a WHERE  A.ACCESSION_NO not like '%-%' OR A.ACCESSION_NO like ' %';

 

 

...

titleClick here to expand the Hospital Scripts

...

bgColorFF66FF
borderWidth2
borderStyledashed
titleHospital 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
sizeL
namedlab clinpath Migration