Dial 1-888-447-7153 begin_of_the_skype_highlighting 1-888-447-7153 end_of_the_skype_highlighting (International callers: 1-719-387-1138)
Enter in passcode: 917798 (the hit #)
Listen to music until "moderator" starts the call
Need help? Call tech support at 1-877-807-0970
- Welcome and Introductions
- Notetaker volunteers? Etherpad: http://titanpad.com/tl-lenses
- Today's topics:
- Sakai OAE Post June Functionality - facilitated by Jon Hays
- Jacques Raynauld, HEC Montréal
- Lynn Ward, Indiana University
- Jon Hays, UC Berkeley
- David Goodrum, Indiana University
- Janice Smith, Three Canoes
- Debbie Runshe, Indiana University/IUPUI
- Ann Jensen, TX State
- What do we expect t be released in June?
- Milestones for June release include clear expectations for what will be developed. Pretty honest estimations of where the developers are at. Currnetly about five days behind schedule. Not much ambiguity in broad terms. On nightly servers, most of what is promised for delivery is there in some form.
- Ability to share and create a profile, ability to create groups, ability to share content, find people, send messages. Some of areas not currently in nightly server are building on templates for different types of groups, easy ways for use. Keli has created a set of basic templates.
- Big things happening since January - back end was completely redone. But from our perspective, the UI framework, the general way the pages are laid out was fundamentally designed. There are still completing this work, determining how groups work.
- No classic teaching and learning functionality yet.
- Hybrid between 2.x and OAE needs to be emphasized. Breakthrough in past few days.Hybrid will be more important than was thought at first. Will see this functionality substantially in version 1 of OAE. Don't see this clearly in nightly build yet.Having to play catch up after redoing front and back ends.
- Since Nikko has been taking the lead on planning and synthesizing, the whole project has been going a lot better. Improved clarity for everyone. Even a discussion of permissions and roles. New interface offers renewed optimism.
- Will version 1.0 be usable for a normal course? (We know a normal course when we see it.) Regular faculty may not be using tests and quizzes and such things. Will this version be usable in June? UC-Berkeley will not be using it in the fall. CSU does plan to use it in the fall. Plan to use the hybrid model in order to back fill from Sakai 2.x. Allows use of new functionality for collaborative group spaces.
- Marist will likely use OAE in hybrid mode for quite some time. Otherwise might have to prioritize things like Gradebook. Hybrid mode changes the answer about which future featuer requests are most important. Right at the heart of the matter for deciding what needs to be done in the summer. How the hybid mode will factor into people's plans.
- For business case needs like managing grades allow for continued use of the Gradebook. Then more inclined to think about functionality for which there are not established tools. For Marist, faculty are used to the current Gradebook and would prefer to keep the one they have for now rather than introducing something new. Focus instead on a new interface for academic networking or content sharing.
- Use hybrid mode as foundation, examine areas that represent "cracks" and attend to those. Use the design lenses as a graph, cut across it to show what areas are handled more or less by Sakai 2 and what areas are not. Sakai 2 and OAE seem to complement each other pretty well. If they work reasonably together, then maybe one of the priorities is getting deeper into the integration in the hybrid mode. For example, being able to pass data back and forth, like being able to use Sakai OAE content in the assignments tool. The two systems integrated largely deliver a lot of the design lens capabilities.
- One question to be explored is how far to push. Our design lenses map really well to the OAE and CLE in complimentary ways. Go deeper with OAE and with integration between the two. Its that or starting to expand the OAE to encompass what the CLE already does. Struggling with this. Concerned about user experience with a mixed environment. If we could figure out some way to not have lots of hybrid, in some ways this would be ideal. When moving to the new platform users would find it fits all of their needs. Figure out what path makes sense in the long term and the short term (over the next two years).
- What about change management plans on other campuses? IUPUI new adopters may be drawn to OAE or to hybrid. Don't see masses of people leaving the current environment. Comfortable with assessment capabilities there. Work a lot with ePortfolio, but if using a matrix for assessment, OAE environment will not give them the functionality they need. Texas State plays if safe, still a couple of versions back on CLE, just the way the support group wants to proceed. Instructional design group is frustrated with Melete and is very anxious to get a better unified user experience. Asking faculty to jump to a hybrid situation and then jump again several years out not a a good idea. Better to make just one change.
- Coherence of user interface a concern once you start blending the two. Try out hybrid with experience faculty users, with new students, and with faculty not having experience in Sakai 2. WIll it be easy to adapt to radically different faces of the two platforms? Will they be able to work with them easily in one framework?
- How do we start testing in the pilots for the fall? (At UC-Berkeley) Planning to use OAE for other things than courses, avoiding the hybrid complexities. In fall, vision is to present the basic hybrid, be in Sakai OAE and see Sakai 2 sites, but not more advanced hybrid mixing the two. However it may be inevitable to get on the hybrid bandwagon depending upon how the community feels. If community decides that the OAE is to be a continuing complement to the CLE, then that will kind of force hybrids on anyone, even those who want to use it in the intermediate term.
- Hybrid started out as a quick fix because we were not going to have the full functionality we needed for the first release. Over time the hybrid has become a kind of a bridge, allowing community members not to have to deal with the big bang of shutting one system off and adopting another. Slowly introducing change and waiting for the users to ask for it in a progressive manner. Hybrid has become a much more important strategy to have. A challenge because ultimately we want to go to one product in the community. But if we look at how long it has taken for Sakai to mature, we see that it takes a while.
- Miami of Ohio - Ian Dolphin did a slightly different version of April report as an audio clip. The future of Sakai CLE and OAE - support for multiple products. Tremendous appetite for OAE product. Does this mean another system transition? Sakai can make its own decisions and does not have to move on other people's time tables. Sakai 2 tools can work alongside and within OAE. Potential carries a cost of supporting two technologies, but the cost is in the interest of the people who will use them. Run both separately, run a portal that bridges, or integrate them.
- IU trying not to over promise the future. Start in small units. Do evaluation of OAE and hybrid mode. People are starting to clammer to have more of that. If they want more of it, then how you bridge it becomes moot because people are motivated. Plans for 2.9 are now more like what the OAE offers.
- Mati Montreal - worked on Open Syllabus, a very strong way to integrate the tools in Sakai 2. Surprisingly Sakai OAE will be a sort of experience that will be fragmented. Not a first best design. Go this way for creating content, now a sort of add on, the main goal was not integration. We should think more about what kind of integration we want. Might do something more like Open Syllabus that is more workable and much nicer from the student point of view.
- Good user experience where people are able to create, like Open Syllabus does, to manage the content, manage the experience - its a very open question. This group looked at Clay's assignment design. Designs that Sam did quite a while ago. Might be interesting to share. Somewhat of an attempt to start addressing some of those concerns. How to create a student experienc that makes sense.
- Keli, Daphne were doing resarch culmiating in some wireframes that were shown at the last conference, around this time there was work done in the UK as well.
- What things to work on in future weeks during this meeting. Plans past R1. Set of activities fall in line with most of what we have talked about. It would be interesting to try to figure out if there are pieces of this that we would want to look at as a group for a meaningful contribution to the project.
- Montreal Mati working with U of Virginia and CSU for a vision of broad use of syllabi and Sakai OAE, have been discussing this over the last couple months. What kind of environment would answer the needs of users. Open Syllabus is the whole course site, a snapshoot of everything the users will need.How to meaningfully represent a syllabus, a roadmap of a course, and make that integrated with the content and the whole experience of the course. Timeline, deadlines, experiences, activities - in the system as data. Sending things to calendar, reminding you about things to be accomplished.Outline of a course that is the course - most elements are clickable and allow you (depending on your role) to interact with. Interesting in context of templates - creating templates for organizing and structuring course groups in OAE. Have a start but community is going to want more.
- Next week is the week off for this group because there will be a general teaching and learning meeting on the second Wednesday of the month.
- Jacques prepared a document and can share it with us to talk about it in two weeks. Will update the site for the group and Lynn will send it to the group along with the announcement. Jacques will invite his fellow contributors.
- As time passes, look at the nightly servers for OAE and think about how we can use this new release. What will we need the hybrid for? Come up for a priority for making recommendations to the project for what to do next. Share thoughts about what is missing an d what needs to be expanded on. Questions relevant to discussion at the confernece having to do with OAE and hybrid mode. Sakai 2 and 3 need to develop toward a common purpose instead of at cross pruposes (or reinventing each other's wheels).Things in Sakai 3 were developed because of limitations of Sakai 2. Community decided a new architecture was required to accomplish it.