OERu/Planning/Technology working group/30 May 2014

When: NZST (Click on link for local time.) Where: Google hangout

Agenda

 * 1) Update on Course site design project
 * 2) * Feedback on custom pages & suggestions for alternate label for "Dashboard" menu item (See example which contains the schedule, announcements and WENotes feed]]). Possible candidates:
 * 3) **Learning console
 * 4) **Learning desk
 * 5) **Thumbnail
 * 6) **Roadmap
 * 7) **Layout
 * 8) **Inside scoop
 * 9) **Portal
 * 10) **The big picture
 * 11) **Essentials
 * 12) * Integrating SCAN pages
 * 13) Considered Draft outline for next OCL4Ed
 * 14) Wiki page to define OERu community source model
 * 15) Wiki page for defining OERu workflow
 * 16) * Collaboration with the partners manual working group
 * 17) * What are the main workflow steps?

Resources
Screen cast demo of SCAN page concept:



Summary

 * 1) Attendance: Tim Klapdoor, Tim McCallum, Jim Tittsler, Wayne Mackintosh.
 * 2) Discussed critique we have received in using Dashboard as a label
 * 3) * Will use "console" as label for OCL4Ed June prototype
 * 4) * Noted that Dashboard is used by edX for submitting assignments - still a useful concept
 * 5) Discussed draft outline for next OCL4Ed prototype
 * 6) * Short single word descriptors needed for main menu items
 * 7) Discussed the SCAN page prototype in detail
 * 8) * Designed by USQ to be a landing page and substitute navigation framework
 * 9) * Level 2 items should produce dynamic navigation of options unless it's a target page
 * 10) * Next OCL4Ed will prototype an implementation whereby the SCAN page is accessible from any page as a popup in main navigation
 * 11) * Considered providing navigation options for OERu partners in the future when making a snapshot (eg SCAN page as main navigation or conventional website navigation with a popup to display a SCAN page).
 * 12) * SCAN page could be used to indicate dynamically where a learner is situated within the course structure.
 * 13) Team will start developing ideas in the wiki for:
 * 14) * OERu workflow
 * 15) * OERu community source model
 * 16) Team are invited to comment and improve on the request for quotation