Teaching Incorporating Code, Media & Libraries in Grade 6: Oklahoma Standard 6.AP.PD.02

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 — 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.

What Does Standard 6.AP.PD.02 Actually Ask?

Incorporate existing code, media, and libraries into original programs and give attribution. — Oklahoma Academic Standards for Computer Science (February 2023)

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.

In student-friendly terms, the learning target is: "I can incorporate existing code, media, and libraries into original programs and give proper attribution."

What Students Should Be Able to Do

• I can identify when a scenario requires attribution and explain why.
• I can provide complete, properly formatted attribution for code or media (creator, source, license).
• I can distinguish open source, Creative Commons, fair use, and public domain and their requirements.
• I can explain both the ethical and legal reasons attribution matters.

Along the way, students pick up the working vocabulary of the topic: attribution, library, opensource, license, copyright, plagiarism, publicdomain, fairuse, citation, repository, creativecommons, remix.

Incorporating Code Media Libraries: Misconceptions to Watch For

These are the wrong turns students reliably take with this standard — 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).

1. "If something is on the internet without a visible copyright notice, it's free to use."

Use paragraph 2's key point — copyright protects work automatically, even without a notice. Absence of a visible notice does not mean absence of protection.

2. "Changing variable names or making small edits to copied code means you don't need to attribute it."

Reference paragraph 8 — substantial similarity in logic and structure still requires attribution regardless of cosmetic changes.

3. "Using existing code or libraries is 'cheating' or means you're not a real programmer."

Point to paragraph 8's framing — 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.

4. "Fair use means students can use any copyrighted material freely in school projects."

Clarify from paragraph 7 — fair use is limited, depends on several factors, and still requires attribution even when it applies.

Discussion Starters You Can Use Tomorrow

• Why might a company choose to release their code as open source instead of keeping it private?
• What's the difference between giving credit because it's legally required versus because it's the right thing to do?
• How might you find out whether an image or song is safe to use in a school project?

Bringing It Home

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 — creator name, title, source, and license type.

Where This Leads

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.

See the Unit in Action

Get the Complete 6.AP.PD.02 Unit

I built a complete, no-prep unit for this standard — Incorporating Code, Media, and Libraries with Attribution — covering 3-4 days of instruction across 38 pages:

• Teacher guide — day-by-day pacing, misconceptions to watch for, discussion questions, differentiation for support / ELL / extension, and a 4-point rubric
• Student learning target page — a kid-friendly "I can" statement with success criteria
• Full content lesson with 3 embedded "Check Your Understanding" checkpoints
• 12-question assessment (6 multiple choice, 4 true/false, 2 short answer) with a complete answer key, explanations, and exemplar responses
• Group activity — "Open Source License Comparison Project" (45-60 minutes)
• Individual activity — "Attribution Documentation Challenge" (30-40 minutes)
• Crossword and word search built from all 12 vocabulary terms (with answer keys)
• Family connection letter — a plain-language page for parents, with dinner-table questions and a 10-minute home activity
• Certificate of achievement — ready to sign and send home
• Open Source License Comparison Template (separate printable, 1 page)
• Attribution Guidelines Template (separate printable, 2 pages)

Get Incorporating Code, Media & Libraries on Teachers Pay Teachers →

Every Sooner Standards resource is built directly from the official Oklahoma Academic Standards for Computer Science (February 2023) — standard text verified, never paraphrased from memory.