13. How the Structures Fit R 8 Module 1 R 1 R 2 R 3 R 4 R 5 R 7 R 6 Strategy 2 Strategy 1 Strategy 4 Strategy 3 Module 2
14. Example R 8 Show the Money R 1 R 2 R 3 R 4 R 5 R 7 R 6 Matching Business Stage with Investor Interactive Prez Show the Money Scenario Risk Management Standards Case Study Decision Making Where Risk is Involved Problem Solving How Much Risk?
Open Content is not curriculum “ Open” refers to the growing practice of providing, distributing, and reshaping content and creative works with few restrictions on its use or reuse. Wikis are: reusable - can be modified and versioned for different courses accessible - indexed and retrieved using metadata interoperable / portable - operate across different hard/software Successful Open Content is not written like an encyclopedia, it has a point of view, context, and meaning THAT’S WHERE THE MAPS COME IN! Like Curriculum there needs to be a statement of opinion about the nature of teaching and learning the content Like Curriculum it (should) include how to teach, what to teach, when to teach Unlike Curriculum it is open and flexible Using a system addresses the criticisms of collaborative design, teaching and learning, and helps solve some of the issues with audience and purpose. Teachers mine content silos (such as UTube, Rice’s Connexions, Merlot, WISC online, How Stuff Works) for what they really need to help convey (ideas) concepts, facts, principles, processes, procedures. -- my research (300 geographically dispersed faculty surveyed over the course of 3 years) Without a guiding hand Hoping that random lessons can knit themselves together
Wikiwiki is Hawaiian for quick. A wiki is a quick way to develop web pages. Cunningham didn’t like the name, quick-web. Cunningham’s first project, (Portland) Pattern Repository, came alive in 1995. It is a web site about design patterns (for object-oriented computer programmers). It spawned the development of clone wikis such as Wikipedia, the largest in the world, and AboutUs which also uses the standard markup language convention of wiki, CamelCase. Difficulty in knowing/recognizing contributors to wikis has raised valid concerns in the encyclopedia style wiki community. Precursors were HyperCard and Hyper texting Famous spinoffs include KMS (Knowledge Management System) Database is usually MySQL Programming language is usually PHP Advantages to each Flavor Software packages can be downloaded and managed from secure web server, reserved for very select number/group, customized (extensions added) Hosted services can be protected, easy to make available to the public (viewing/contributing) Interfaces are predominantly WYSIWYG or HTML
Wikis can be group tools or sources of information One issue faced is trying to understand different audiences (there are several) and what those audiences different purposes are (sharing content, working together collaboratively, modifying and creating collections to suit needs) and then what kinds of tools to give to each type of user. THAT’S WHERE THE MAPS CAN HELP!
Templates are required for maintenance Basic rules: Link only once Isolate external links Name very carefully Tag consistently (THAT’S WHERE THE MAPS HELP!)
Graphs and downloadable statistics on a monthly basis Number of views to the wikispace or per page Unique visitors (by country, by ip address) Activity (edits, messages, etc.) Key contributors can be tracked and information posted on the wiki (possible incentive?)
![[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)