Wiki source code of OSI-EDU-WG-notes-4mar2014

Last modified by XWikiGuest on 2023/02/17 01:53

Show last authors
1 OSI-EDU-WG Meeting Notes from 4 March 2014
2
3 __**Participating**__
4
5 Joseph Potvin
6 Patrick Masson
7 Wayne Mackintosh
8 Ken Udas
9
10 = Discussion Notes =
11
12 == 1: Presentation about the OSI-EDU-WG in May 2014 ==
13
14 * At "PM-Connect" https://wiki.state.ma.us/confluence/display/projectmanagerforum/Home
15 ** Massachusetts government employees, project managers
16 ** OSI was invited to put together a presentation
17
18 == 2. Participation in OSI-EDU-WG ==
19
20 * We'll be preparing a general invite soon, but if you have colleague who may like to participate in the OSI-EDU-WG, feel free to bring them along to the teleconf
21 * New content on project management in the Syllabus needs feedback, eg the "learning outcomes". Good responses so far
22
23 == 3. FLOW Syllabus Usability ==
24
25 * It's a bit overwhelming
26 * Being able to tag the modules/items would be helpful
27 * Tag at what level of granularity?...hard to say, but that will be an emergent process
28 * Joseph will communicate with someone involved with Protege Ontology Manager at Stanford for some ideas ...if you haven't seen http://protege.stanford.edu/ take a look. Very cool for the relatively sophisticated folk who organize information. It's been around a long time (it has a quarter million users today, and had 50,000 users back in 2006). There might be one or more existing [[Projects.OSI-EDU-WG-notes-4mar2014.Project Management Ontology.WebHome]] that the FLOW Syllabus ought to conform to (or at least map to)
29 * There are a few different aspects:
30 ** "What my students would learn"
31 ** "Outcomes"
32 ** "Learning activities"
33 * It may be useful to write short "use case" scenarios for using the Syllabus
34 ** Each use case will have implications
35 ** This will help the WG to understand the audiences
36 ** And will help a course designed understand what
37 parts/emements of their course would likely be essential/useful to each audience type
38 * Basically, we now need to provide "tour guides" through the syllabus... By analogy, "Going to Venice":
39 ** ...for architects
40 ** ...for culinary arts
41 ** ...for business
42 ** ...for etc.
43 * These can supply some audience-tailored guidance
44 ** granular (bullet point level)
45 ** tags would enable the separate views
46
47 == 4. FLOW Syllabus Scope ==
48
49 **Question:** Should "activities" be in or outside the syllabus?
50
51 * This would help to outline the topics and sources
52 * Courses include activities
53 * Educators/community can create courses and share those
54 * Activities help learners engage and practice the use of the information to develop understanding
55 * What we should not do...
56 ** We don't want to poorly usurp the role of online learning sites, rather we want to provide them useful resources
57 ** We don't want to miss engaging those partners by only having the learning activity collection distributed amongst multiple environments
58 ** Narrow the potential community because learning activiteis are designed for a particular audience (there's an inverse relationship between embedded pedagogy and reusability)
59
60 * Learning activities can form a coherent package however
61 * What is the ideal nature of content developmemt to hand-off from the syllabus and the course designers?
62 ** Technical
63 ** Conceptual
64 ** Operational
65 * OSI-EDU-WG would structure the syllabus
66 * Independent educators (including folks on the working group) can contribute supplemental content and learning activites
67 * One can't quite take the syllabus on its own and say "This is my 7-day course"
68 * One can take a section and add it to something else, or take specific items
69
70 == Notes prepared by: ==
71
72 Joseph Potvin
73 **Chair, OSI Working Group on Management Education About Free/Libre/Open Methods, Processes and Governance**
74 [[jpotvin@opman.ca>>path:mailto:jpotvin@opman.ca]]
75 Mobile: [[819-593-5983>>path:tel:819-593-5983]]

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation