SIX THINGS THE US DEPT OF EDUCATION DID TO DEPRIVE YOUR CHILD OF PRIVACY 46 comments
The story of Common Core and data mining begins as most stories do, with a huge, unmet need.
Self-appointed “stakeholder” know-it-alls at the federal level (also at state, corporate, and even university levels) determined that they had the right, and the need, for open access to personal student data– more so than they already had.
They needed state school systems to voluntarily agree to common data core standards AND to common learning standards to make data comparisons easy. They didn’t care what the standards were, as teachers and parents and students do; they only cared that the standards would be the same across the nation.
So, without waiting around for a proper vote, they did it. The CEDS (Common Education Data Standards) were created by the same people who created and copyrighted Common Core: the Council of Chief State School Officers (CCSSO). No surprise.
Because the federal “need” to control schools and data was and is illegal and unconstitutional –the federal government “needed” to do (and did) at least six sneaky things.
SIX SNEAKY THINGS THE U.S. DEPARTMENT OF EDUCATION DID TO DEPRIVE YOUR CHILD OF PRIVACY:
1. Sneaky Thing Number One: It bribed the states with ARRA Stimulus monies to build 50 linkable, twinlike State Longitudinal Database Systems (SLDS). This act created a virtual national database.
These SLDS’s had to be interoperable within states and outside states with a State Interoperability Framework. Utah, for example, accepted $9.6 million to create Utah’s SLDS. Think about it. All states have an SLDS, and they are built to be interoperable. How is this not a de facto national database?
2. Sneaky Thing Number Two: It altered the (previously privacy-protective) federal FERPA (Family Educational Rights Privacy Act) law to make access to personally SIX THINGS THE US DEPT OF EDUCATION DID TO DEPRIVE YOUR CHILD OF PRIVACY | COMMON CORE: