Local API - Multi School Training Data

Introduction

Multi school training data is not offered by ESS. It may however be possible for TIs to modify training data (at their own risk) to enable multi school testing.

What needs to be updated?

Key IDs apply to SIMS.SIMS_Person and Base Groups

Recommendation

We would recommend perhaps the use of colours to identify the clones.

 In this way, you can clearly see which school the person came from and yet it still looks like a real(ish) school.

The following SQL will set Red Abbey but the unique IDs will still need to be fixed up.

update sims.sims_person set forename = 'Rory' where gender = 'M'
update sims.sims_person set forename = 'Scarlett' where gender = 'F'
UPDATE SIMS.sims_school SET school_name = 'Red Abbey' WHERE status = 'S'

Fixing up the GUIDs

In essence what is needed is a lookup table.

Store this is some form of suitable way… Possibly in another database.  Possibly an XML document.

One possible way is to insert a column say old_externalID and copy the Green Abbey GUID in to it for each of the tables identified.

You then need to identify all of the new GUIDs that are not in your lookup add them to the lookup and assign new guids for each clone.

Then simply update the proper GUID to the lookup value.

Repeat for the other tables.

NB: It almost doesn’t matter if this is slow!  It will be run once for each clone 3 times a year.