Child pages
  • 2009-02-23 Conference Call

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Meeting minutes for February 23, 2009

  1. Sakai/OSP 2.6 Issues and Status
    • 2.6 QA Testing Status. VA Tech developer has not started on testing yet. Teggin will let us know when he does. Sean has found several issues. Charles Hedrick has filed 2 null pointer exception Jiras, SAK-15734 and SAK-15736. Sean brought up that SAK 15693 describes unexpected behavior: a user trying to share a portfolio removes users rather than saving them.
    • SAK-15348 Imported Matrices do not retain links to global forms. Chris Mauer is looking at this.
    • SAK-15579 Supporting files for template based portfolios not making it through to the browser. This is a blocker that is still unassigned. There were no volunteers.
    • SAK-15276 Edit links appears for all reviewers/evaluators on feedback/evaluation, though they cannot edit. This is marked critical, but should be changed to major, since it was already in 2.5. You get a stack trace if you try to edit a portfolio you do not have permission to edit.
    • SAK-15541 Evaluators from different groups click on evaluations and get a 500 error. Michigan can't work on anything this week, but maybe next week they can look at this.
    • SAK-15540 Matrix in "Preview" status is unavailable to users. This is fallout from SAK=13371, which introduced this as a feature (avoid the situation where users think a matrix is published and start working in it). But some people, particularly Delaware, use preview mode for testing from the students perspective. Most people seem to meet this need by giving the maintain user "use" permission on the matrix. We need to come up with a scenario that meets the need of Deleware, but protects users who want to be protected from overeager users. Could be handled with a new permission, then create special roles that use that permission, such as "student-test". Or a new matrix setting. Beth will write it up as a bug.
    • SAK-15722 sort order does not remain consistent through 'previous' and 'next' page movements in the OSP evaluations tool. Jim Doherty reported this.
    • SAK-15748 Add owner name information to form metadata for view renderer use. This would make it possible to show the owner's name in the formView mode, which cannot currently be done. Anonymous reviewing would still be possible, because you would have to take the step of creating a custom renderer that shows this information in order for the user to see it. Will be in use in production at Michigan next week. Agreed that it should be merged into trunk.
    • Additional JIRAs: SAK-15734, SAK-15736 Null Pointer Exceptions.
  2. Sakai/OSP 2.7 and beyond Development Status
    • Content Authoring and Sakai 3 Development Updates. Peter Knoop has done a couple demos of Sakai 3.0, but the notification was not sent out to the portfolios list. There will be another demo tentatively scheduled for 3:00 March 9. Noah will circulate information about it.
    • OSP Functionality for 2.7/3.0 and beyond
      • Portfolio-related vignettes Mark Zaldivar set up a page where people can enter short user scenarios about what they would like portfolios to do in 3.0. Think of it as a wish list. Noah pointed out that the term vignettes is now being used by 3.0 people to refer to widgets that can be embedded in a page. People are encouraged to add suggestions/ideas on the page, which is now linked to from the Meetings page.
    • OSP Design and Development The remainder of the meeting was spent discussing a vision for the future. We need to be more ready to contribute to ideas on Sakai 3.0 long before meetings at the July Sakai Conference in Boston. There was discussion of coming up with a small project, like the Portfolio tool reworking, that we could do as a group and have some confidence that the task would be completed. There was also discussion of more "blue sky" ideas. Jan Smith noted that many new clients are clustering around Schools of Education, and are interested in features that were present in Goal Management. In addition, we talked about making use of the Sakai 3.0 Portfolio-related vignettes.
      • The first subject we focused on was the general idea of tagging with goals. The ability to create goal sets and make them available to users. What are the first few things we would like users to be able to do? Just as groups transcend sites, goal sets should. Some sets might be available to everyone, some just to a group, some even individual. Goal Management is a good place to start a project, because there are no issues of backwards compatibility. Josh Ryan at AZ State has done a lot of work on this in connection with the IDEAL Project being done in conjunction with the AZ Dept. of Ed. This is a pool of questions that are each associated with one or more goals. The questions can be browsed and used by teachers in tests. The questions are in an external data store, but the browser is a Sakai contrib tool. We could learn something from them about how to deal with large goal sets.
      • Another possible focus is rethinking what matrices and wizards do. Michigan and IU, for example, have had some discussion of rewriting the tools to complete their integration.
      • There was also discussion of social networking in Sakai: ways to get students to look at each other's portfolios, tagging, finding friends. This is important to LaGuardia.