Data Quality Assurance

27
Jolene Hamm *Portions of presentation developed by Shea Dunifon

description

Data Quality Assurance. Jolene Hamm *Portions of presentation developed by Shea Dunifon. Quality Assurance Processes. Data Quality Assurance at FAEIS. Annual system check by institution Program Manager runs reports by area Quality Assurance Review - PowerPoint PPT Presentation

Transcript of Data Quality Assurance

Page 1: Data Quality Assurance

Jolene Hamm*Portions of presentation developed by Shea Dunifon

Page 2: Data Quality Assurance

Quality Assurance Processes

Page 3: Data Quality Assurance
Page 4: Data Quality Assurance

Data Quality Assurance at FAEISAnnual system check by institutionProgram Manager runs reports by areaQuality Assurance ReviewNew Features in FAEIS to support quality

assuranceData Source Entry for College InformationSurvey Info as quality assurance tracking interface

FAEIS conducted Quality Assurance for all institutions going from 2003-2009 reporting year for data accuracy

Page 5: Data Quality Assurance

FAEIS Contacted all institutions in FAEIS starting in

June and is ongoingTotal contributed hours: 1941 man hours to

dateEfforts of 4 Helpdesk GRAs

Page 6: Data Quality Assurance
Page 7: Data Quality Assurance
Page 8: Data Quality Assurance
Page 9: Data Quality Assurance

University of Florida: After

Page 10: Data Quality Assurance
Page 11: Data Quality Assurance

The Ohio State University: After

Page 12: Data Quality Assurance

Texas A & M University

Page 13: Data Quality Assurance
Page 14: Data Quality Assurance

University of Minnesota, St. Paul: After

Page 15: Data Quality Assurance

How did we “clean data?”Merging CIPsDeleting CIPsRecording institutional correspondences in

the Survey Info SectionAdding IR data to fill in gaps

Page 16: Data Quality Assurance

CIP Discipline 2004

2005

2006

2007

2008

2009

01.1001 Food Science

55 72 90 01.1099 Food Science and

Technology, Other55 48 52

• “Alternating CIPs” can often be identified as changes in CIP code reporting.

Page 17: Data Quality Assurance

Deleting CIPsCIP Discipline 2004 2005 2006 2007 2008 2009

01.0905

Dairy Science

10

Instances when CIPs should NOT be deleted:

• Programs are no longer offered (make note in Survey Info)• New users report from year to year (can merge CIPs)?• Data is confirmed by Department or IR

Instances when CIPs should be deleted:

• One year is reported and no explanation is available why• Reported in the wrong College

Page 18: Data Quality Assurance

Institutional InquiriesContact Institutions to identify:1.Mergers between Colleges and Departments2.List of CIPs (by Majors)3.Multiple users4.Deleted or new Programs

Page 19: Data Quality Assurance
Page 20: Data Quality Assurance
Page 21: Data Quality Assurance
Page 22: Data Quality Assurance
Page 23: Data Quality Assurance

The University of Idaho

Page 24: Data Quality Assurance

The University of IdahoEach year, data was reported by a new userAll of those users have since been “deleted”The College of Agriculture stopped reporting

to FAEIS in 2007IR began reporting to FAEIS in 2007IR data used Fall 10th day numbers for FAEIS

and are not the same as the Fall end of semester numbers it used to verify past data

Page 25: Data Quality Assurance

University of Idaho: After

Page 26: Data Quality Assurance

Future Issues to be AddressedEncouraging Institutions to develop a

consistent & reliable means of reportingReminding Institutions to verify and update

CIPs annuallyDeveloping and maintaining strong

relationships with reporting InstitutionsTools for tracking users

Page 27: Data Quality Assurance