Proof of concept: Demographic data incorporation
Added by ben leinfelder over 14 years ago.
Updated about 14 years ago.
In lieu of providing an interface for importing [variable] demographic data, we can prescribe a table structure for the demographic data, upload it to the server (manually) and then reference it when joining assessment data and metadata.
added a menu option to select a csv and add it as another data file in the edml package.
we need to determine exactly what fields (and the order) this file should contain. so far i've only defined it as:
-minimal file checking (make sure it conforms or nearly conforms to the expected structure)
-encrypting the studentId such that it can match the assessment response data when joining the two data files
after soliciting advice from our FIRST group, this is a proposal for the structure of the demographic data:
student_id - Student ID
term - Semester/Quarter (when the data was pulled)
major - Major
gpa - GPA
citizenship - Citizenship (country)
ethnicity - Ethnicity
gender - Gender
dob - Date of birth
high_school - Name of high school
hs_zip - ZIP code of high school
hs_graduation_year - Year of high school graduation
hs_gpa - High school grade point
SAT_type - SAT Test Type
SAT_score - SAT Test Score
ACT_english_score - ACT English Test Score
ACT_math_score - ACT Math Test Score
ACT_reading_score - ACT Reading Test Score
ACT_science_score - ACT Science Test Score
ACT_composite_score - ACT Composite Test Score
AP_type - AP Test Type
AP_score - AP Test Score
other_test_type - Any other institution-specific Test Type
other_test_score - AP Test Score
student_id is now sharing the same encryption method used for importing assessment data.
as a proof-of-concept, this works. you can attach a standard demographic data file to an assessment data package and upload that with the student data.
on the server side, you are given the option to include that data in the download if it is present for the datapackage[s]
Original Bugzilla ID was 3519
Also available in: Atom