Sorry mark80 - I thought you were talking about the events log rather than the assessment data.Originally Posted by mark80
To understand the data you need to understand some of the terminology CMIS uses (forgive me if you already know this bit - but others may not)
Criteria - this is a single collection of data with its rules, for example a KS3 level that is going to be either 2, 3, 4, 5, 6 etc. You only have to define this once and it can be used repeatedley and the same rules always applied to give continuity. Another example could be effort, forecast grade, expected grade etc. This allows life for like grades taken at different times to be based on the same logic and therefor comparable.
Assessment - this is a collection of different criteria. For example a simple assesssment could be an effort and KS3 attainment level. This might be collected every term, once a year etc. Collecting the two criteria together into one assessment makes it easier to do the next step which is:-
Examination - this is the actual event you are asking staff to enter information against. So the simple assessment example above might be collected every term - so you set up a different examination for each of those terms that consists of that assessment. Maybe Year 7 Autumn Term, Year 7 Spring Term etc. All containing the simple KS3 assessment above.
OK - bare with me, I am getting to the important bit now:-
All the results are stored in NSTURESULTS which reference the StudentID, the ExamID and the AssessID as well as the actual results which are in the CriteriaData field (not recognisable as a result just yet - you need to read on because it is not that simple!)
Also in this table is the ModuleID - this is how you determine which subject the particular results were for (so a student may have several lines in this table with the same assessment and exam information - once for maths, science, technology etc.)
Hopefully you will notice that the SetID is also in the table, but remmber that this refers to the dataset the results were recorded in, so do not automatically just strip out this years dataset, or you will only get this years results.
The next table is the EXAMINATIONS table, useful if the examid is not enough to identify the exam you are after - sometimes itis only the name of the assessment (which you will find in this table) that gives this away, rather than the examid found in the examinations table. This table also tells you the relevant AssessID for this exam, but you should already know that from the nsturesults table. So this table may prove to be unecessary for you.
The ASSESSMENTS table will give you the nme of the assessment relating to the assessid field in the results table - again only necessary if you cannot identify what you need from the assessId field.
Next is the ASSESSCRITERIA table will give you the information you need to be able to extract the data from the results table - this is the bit that is not so simple.
If you look up the relevant assessid in this table you will see there are multiple lines for many of the assessments - the difference being the criteriaID (and related Critlabel). What you are really interested in from this table is the mapvalue field - a numeric field.
Take this numeric field and look back at the criteriadata field in your NSTURESULTS table (and it will need to be one with the right assessid for this mapvalue) - you will hopefully see the mapvalue appear in the criteriadata field followed perhaps by a control character and then another value. This second value is the result for that critiera. So an assessment will generate a string in the criteriadata field that contains several of these map values followed by the result.
All you have to do is search that string for the mapvalue and then the next piece of data after that is the result you are looking for.
Hope that all makes sense - I am going to a lie down now!
And again more details, if needed, about the individual criteria can be found in the CRITERIA table.