That Blue Square Thing

Copyright Free Images

Copyright protects people's work.

It means that other people can't use images, sounds or writing that you've made unless you allow them to. The © symbol means that something is copyrighted.

This means that it's not OK to copy these sorts of things from the internet (or other sources) and use them in your work.

Dealing with Copyright

Assume every image, sound or other work you find on the internet is protected by copyright unless it says it isn't.

If you can't find anything that says whether it's copyrighted then it is copyright and you can't use it. There are no exceptions to this.

In general work this probably isn't a big deal. But if you put your work on the internet at all or share it with other people then it becomes a big deal.

You can ask if you can use something, but don't expect you will get permission.

There are, however, good places to look for copyright free material.

Copyright Free Images

These are all good places to look for copyright free material:

There are other good places to get copyright free material from that you might not be able to access at school. Ask if you need to and a teacher may be able to access them for you.

Recording Assets

You need to keep an accurate record of where your assets come from. This includes any that you make yourself (including sound and video files).

An assets table is essential, but classic ones have lots of columns and can get very confusing very quickly. I favour a 3 or 4 column approach with columns for:

PDF iconExample assets table - this uses a 3 column approach. There are lots of other ways to do this.

Maintain your assets table as you do your work. It will make your life much easier later on - and you'll get a lot more marks with a good assets table.

The word "Google" should never appear in an assets table. You use Google for finding assets but in almost every case the asset is actually stored somewhere else. It's that url I need to see please.

Development Diaries

As well as knowing where your assets came from I also need to see how you developed them. This includes any editing. You can show this in the assets table to an extent, but to get more marks it's better to use a development diary as well - certainly on some of the assets you used.

This means that you need to take screenshots of your work to show how (and why) you developed it. It can be helpful to link this to feedback as well - you can screenshot your first attempt at something and annotate it to show the feedback you got. You can then screenshot the final copy and annotate it to show what you did to edit the work.

PDF iconExample annotation - the sorts of things you can show in a development diary

PDF iconExample feedback on a screenshot - this is a good way to keep a record of feedback from a named test buddy. I could extend this to show how I'd improved my work. This is the sort of thing that gains marks in multiple areas of the markscheme.