TS1988

Great, no problem!

Not sure if this gives you what you want..take a look at the screenshot and let me know. Easily exported to excel.

Hi Jonathon, Your best bet will be to search for the SWF census documentation on Serco firstline - Facility Support. All of the required user function restrictions are detailed within this manual to prevent access from the salaries tabs/data being extracted in reports. Thanks

The SEN dept. within my establishment requires a means of tracking SEN provisions/interventions in greater detail which can then help with in depth analysis requested by our LA. To give you an idea of the sort of detail required please see below: - Creation of an inclusion register. - Ability for all SEN dept. to track their own provisions/interventions. - Automated review date reminders. - Linking of staff to specific intervention mappings, including time & cost allocation. We are currently trialling an option, whilst reviewing other 3rd party options that allow integration with CMIS. Do any schools out there do anything similar and if so, what? I have toyed with the idea of having a unique result entry template/UDFS to control the majority of the information, but due to the in depth features required, I'm not sure this is the best means. The current method used for the recording of this data is Microsoft Excel (whilst also maintaining the statutory SEN data required for Census). Thanks

It is a powerful product that provides great flexibility - often there are multiple ways to do things which can provide a challenge with trying to learn the system, due to the numerous methods that data/functions can be accessed/implemented.

All of the above advice regarding backups and test runs is very important and must not be ignored - the option of setting up a stand alone for testing purposes may also be worthwhile if other data is being entered. Generally for target data as long as the following fields are in the spreadsheet and populated you can then transfer straight into nsturesults. - Setid (This can be specified during the import routine - however I usually just included this in my spreadsheet, e.g. 2011/2012) - Moduleid (Id for subject - this is case sensitive) - Deptid (Id for department - this is case sensitive - only include if your school use departments and have these setup within facility under Data|Academic|Departments) - Criteriadata (This is the column for the target) - Examid (This can be specified during the import routine - however I usually just included this in my spreadsheet, e.g. KS3TRGT) - Assessid (This can be specified during the import routine - however I usually just included this in my spreadsheet, e.g. _KS3TRGT) A quick note that the details column names I have defined above can be called anything within the spreadsheet. Try to avoid any fancy formatting and generally the spreadsheet should be formatted as text, with the obvious exception for numbers which can be set as integers. During the transfer routine, all data will usually go in with data set as varchar.