Skip to end of metadata
  • Created by Former user, last modified by Former user on Jul 01, 2010
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

01 Jul 2010

Attendees: Philip Uys, Marian Tulloch, Gregory Hardham, Jacques Raynauld, Daphne Ogle, Keli Amann, Yitna Firdyiwek, Trisha Gordon

 Preferred meeting times:
6pm ET (depending on who wants to join) every 2 weeks; next meeting Thursday, July 15th at 6 pm ET

Next Steps

  • Many overlaps that should help us come with something for 3.x
  • Interest in sakai 3 or 2?
    • interest in hybrid at CSU; provide input into sakai3
    • what is contract w/student; what are parts in tool that need to be tied down
    • csu - contractual document, once published, fairly tied down; policy-driven, top-down implementation
    • uva - generally interested in providing input in 3.x; faculty are involved in decision-making; we are using 2.x; hoping to make syllabus more efficient and full-featured in 3.0;
    • uva - 2 things to carry forward: instructional dashboard to construct learning experiences; flexibility; looking to learn more about 3.0
    • berkeley/stanford - syllabus is one of the most important tools; something more interactive as a jumping off point for designing learning opportunities; will be doing research analysis, info gathering, etc to pass off to design team; starting from the roadmap phase 2, 3, 4 (syllabus is in phase 3); hope to be involved at that point in the roadmap; this group will help to provide the input their looking to put forward; may need to hightlight features included in the wireframe
    • toolkit - methodologies/technologies used to make sure requirements are right for design process; to be shared with sakai 3 steering committee
    • philip - design process comments: link to design model from manage probject page in confluence; how to get input from wider community; touch base with alan marks
    • final decisions will be made by the project leadership team
    • HEC - opensyllabus for 2.x - contribute ideas for use in sakai3; similar needs/features as CSU; learning activities as separate component?; need examples of things faculty want to do
  • could rethink how we do things in sakai3; being exposed to ideas may reveal how to bring this about in sakai3
  • syllabus tool? what is different about subject outline and syllabus?
    • subject outline mirrors syllabus content essentially; what topics will be and how they will be assessed and requirements - not necessarily the activities involved in the class? official contract with students
  • new column for activities on confluence
  • also syllabus provides a component that provides general course description for general consumption, not the classroom itself; this may be considered separate from the syllabus; the interactive component is not standard but is made possible by the technology
  • sakai 3 lends itself to much more integrative, flexible approach
  • access options: public v private up to the instructor - can these decisions translate to the institution?
  • semantic is needed for institutional reporting purposes; flexibility needed to allow instructor creativity
    • need both of these aspects in the design for sakai3
  • sakai3 is public by default! more open direction
    See Future directions site on sakaiproject as well as michael korcuska's presentation on sakai3 - see Themes slide for overaching goals

Try to avoid instructors creating so many templates that studnets are confused.

?

Next steps:

  • No labels