Digital skills for collaborative OER development/Develop learning pathway/OER inventory tasks

Tasks

 * 1) Go to the planning homepage you created for your course development.
 * 2) Create a new subpage for your "OER inventory" under the development resources section. Remember when creating a subpage link you must prefix the page name with a forward slash "/" for example "/OER inventory" to avoid creating a page of the same name in the main wiki area.
 * 3) Plan how you would like to structure your OER inventory, for example:
 * 4) * By topic or theme, using headings and subheadings with a bullet list providing links to each resource, annotated review and notes about license and format.
 * 5) * A separate OER inventory subpage for each topic, with subheadings for: 1) Resources to use as is without modification, 2) Resources for minor adaptation, 3) Resources for remix and substantive adaptation, and 4) New resources to create from scratch.
 * 6) * A table with columns for different components. Note that this will require a working knowledge of wiki table syntax or you can use this online tool to generate the wiki text for a table layout.
 * 7) Conduct a mini audit to source and record prospective OER. (Revisit the Find OER page in this course for ideas.) Remember to include on your inventory page a short evaluative annotation of the resources you find.
 * 8) * Important: When listing potential resources, be sure to include the url links to the original source materials. You will need these resource links when attributing the materials. For example, it is not sufficient to reference "Butterfly image on http://www.flickr.com" as there are millions of images on flickr. You should reference the unique url for the individual image, for example: https://www.flickr.com/photos/adriaancoetzee/6950706381/. You will save yourself time and frustration by paying attention to referencing and recording the exact source. The wiki community may delete images which are in breach of copyright including cases where the source cannot be verified, for instance where the url does not point to the source image.
 * 9) Remember to share your learning journey with our community by posting on  and include the hash tag "" where appropriate.