Teaching incorporating code media libraries in grade 6 does not have to be complicated. Picture a software developer using open source libraries to build applications faster, always crediting each dependency. That kind of thinking is exactly what Oklahoma's grade 6 computer science standard 6.AP.PD.02 asks students to practice \u2014 and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.<\/p>\n
\nIncorporate existing code, media, and libraries into original programs and give attribution.\n\u2014 Oklahoma Academic Standards for Computer Science (February 2023)<\/em><\/p>\n<\/blockquote>\n
In plain language: Oklahoma's standard asks sixth graders to use existing code, media, and libraries in their own programs while properly attributing (giving credit to) the original creators.<\/p>\n
In student-friendly terms, the learning target is: "I can incorporate existing code, media, and libraries into original programs and give proper attribution."<\/strong><\/p>\n
What Students Should Be Able to Do<\/h2>\n
\n
- I can identify when a scenario requires attribution and explain why.<\/li>\n
- I can provide complete, properly formatted attribution for code or media (creator, source, license).<\/li>\n
- I can distinguish open source, Creative Commons, fair use, and public domain and their requirements.<\/li>\n
- I can explain both the ethical and legal reasons attribution matters.<\/li>\n<\/ul>\n
Along the way, students pick up the working vocabulary of the topic: attribution, library, opensource, license, copyright, plagiarism, publicdomain, fairuse, citation, repository, creativecommons, remix.<\/p>\n
Incorporating Code Media Libraries: Misconceptions to Watch For<\/h2>\n
These are the wrong turns students reliably take with this standard \u2014 knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).<\/p>\n
1. "If something is on the internet without a visible copyright notice, it's free to use."<\/strong><\/p>\n
Use paragraph 2's key point \u2014 copyright protects work automatically, even without a notice. Absence of a visible notice does not mean absence of protection.<\/p>\n
2. "Changing variable names or making small edits to copied code means you don't need to attribute it."<\/strong><\/p>\n
Reference paragraph 8 \u2014 substantial similarity in logic and structure still requires attribution regardless of cosmetic changes.<\/p>\n
3. "Using existing code or libraries is 'cheating' or means you're not a real programmer."<\/strong><\/p>\n
Point to paragraph 8's framing \u2014 there is no shame in using existing solutions; the shame is in failing to acknowledge whose work you've built upon. Using libraries is smart, efficient programming.<\/p>\n
4. "Fair use means students can use any copyrighted material freely in school projects."<\/strong><\/p>\n
Clarify from paragraph 7 \u2014 fair use is limited, depends on several factors, and still requires attribution even when it applies.<\/p>\n
Discussion Starters You Can Use Tomorrow<\/h2>\n
\n
- Why might a company choose to release their code as open source instead of keeping it private?<\/li>\n
- What's the difference between giving credit because it's legally required versus because it's the right thing to do?<\/li>\n
- How might you find out whether an image or song is safe to use in a school project?<\/li>\n<\/ul>\n
Bringing It Home<\/h2>\n
This topic is a natural one for families. One ten-minute activity to try: Together, find an image or song online that has a Creative Commons license and write out the full, correct attribution for it together \u2014 creator name, title, source, and license type.<\/p>\n
Where This Leads<\/h2>\n
Students who can incorporate existing code, media, and libraries into original programs and give proper attribution are building skills used every day in software development, game development, open source maintenance, intellectual property\/legal tech, and computer science education.<\/p>\n\n
See the Unit in Action<\/h2>\n\n