Data transfer and manipulation

Changing your processes and data structure when you’ve got several years of data held in a different way can be a daunting thought. My database experience means you don’t have to throw your legacy data away, or expend days of effort typing it back in.

The great advantage of Facility CMIS is the way all your data can be stored in one central database, giving you real management information that can inform your school's decision making. But data that was collected in previous years may well be in old Management Information Systems or a variety of standalone applications or spreadsheets. Or you may continue to use different software in some areas of the school environment - to manage behaviour, or staff development, for example - but wish to synchronise that data with CMIS on a periodic basis.

Spreadsheet showing student data


Examples of circumstances where you might want to import data into CMIS might be:
  • Importing Assessment data about current students that is stored in an old Management Information System. This might involve creating the appropriate assessment structures within Facility first before transferring the data.
  • Collating pupil background information from an ad-hoc collection of spreadsheets and importing it into Facility. Even when information is stored in different ways by different teachers, or using different pupil names, a bit of forensic analysis can usually be used to piece things together and provide it with a logical structure.
  • Copying data from an MS Access database used by the school to store details of INSET attended by member of staff. This would probably involve setting up a number of user defined fields on the staff record to start with, and then using the data transfer tool to set up a CMIS Data Transfer that the school can run whenever it wishes to transfer data. The original Access database can continue to be used for day to day data entry.
Comments