School grade vs age
Posted by: Joelle Tegwen
Date: March 22, 2006 03:16PM

I've never asked a question like this online before so I hope I've managed the line between too much information and not enough information appropriately. Comments on style welcome as well. :)

I'm working with standardized testing (assessment) data. Data is organized by state. One of the pieces of information is when each state requires each assessment to be given to the children. 99.9% of the time, that "when" is by grade. However, for "Alternate Assesments" the assessments are *sometimes given by age. (Sometimes we don't have this information too)

For example:
Iowa gives the Alternate Assesment for Reading and Math in grades 4, 8, & 11
Kansas gives the Alternate Assesment for Reading and Math at ages 10, 13, & 16

I've got an assesment table:
Assesment
---------
id INT
title VARCHAR
isAlterante TINYINT

I've got a subject table:
Subject
------
id INT
title VARCHAR

Then I've got the join table:
AssessmentSubject
---------------
assessmentID INT
subjectID INT
[?how to do this age grade thing here?]
nonstandard

Do I have another table that has grade/ages like this:
delivery
---------
id INT
indicater CHAR(2) [grade could be K so it can't be TINYINT]
isAge TINYINT

and then put deliveryID in the AssessmentSubject table

or do I add them to AssessmentSubject directly
AssessmentSubject
---------------
assessmentID INT
subjectID INT
deliveryYear CHAR(2)
isAge TINYINT
nonstandard

Would it be better to do it in a join table to more easily spot the ones with no delivery information?

Or is there something else that I'm not thinking of.

Thanks for help in advance

Options: ReplyQuote


Subject
Written By
Posted
School grade vs age
March 22, 2006 03:16PM
March 22, 2006 03:56PM
March 22, 2006 04:35PM
March 22, 2006 05:39PM
March 23, 2006 11:46AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.