Meeting minutes for March 9, 2009
- Sakai/OSP 2.6 Issues and Status
- SAK-15812 Unable to add evaluators to a matrix cell. New bug fixed.
- SAK-15579 Supporting files for template based portfolios not making it through to the browser. Fixed
- SAK-15722 Sort order
- SAK-15734 NPE Not reproducible in latest release, so Beth closed it.
- SAK-15736 NPE tomcat 5.5.27 Known problem. There is a workaround – Anthony will update release notes.
- SAK-15813 New Saturday Sean FCKeditor free form portfolio item plugin does not work. Only place it occurs is freeform portfolio.
- SAK-15348 Imported Matrices do not retain links to global forms. Chris Mauer is looking at this. Affects Indiana.
- SAK-15276 Edit links appears for all reviewers/evaluators on feedback/evaluation, though they cannot edit. Assigned to Noah. Also a delete issue.
- SAK-15540 Matrix in "Preview" status is unavailable to users. Beth sent out an email with a proposal, but didn't get any response. Beth will get it in either this week or next. Beth will put her proposal on the Jira ticket.
- Sean has verified the following fixes: SAK-14998, SAK-14884, SAK-14637, SAK-14635
- Sean couldn't address these: SAK-15553 - not running Oracle, SAK-15236 - or DB2, SAK-14995 - DB2 again
- SAK-14781 Create a portfolio based off of a previewed matrix, then publishing, breaks the portfolio. Form data from previewed matrix still hangs around and is still visible in portfolios created from the previewed matrix. Is this the behavior we want? It is a problem that forms created in preview mode are still checked when a change to a form is validated. Data entered into the "deleted" (actually orphaned) form can prevent a form from having its schema updated. This should be written up as a separate Jira.
- Lynn has started work on document on IU's changes. She would like us to get the conversation started again. Next week IU will do a walkthrough as a refresher. A number of changes to the matrix tool. Additional permissions.
- Sakai/OSP 2.7 and beyond Development Status
Peter Knoop will do another demo of Sakai 3.0 at 3pm Wed. 11th. People should rsvp to Peter.
Towards the goal of identifying the things that OSP does that we want preserved and extended in 3.0, Jan listed seven thing that we do (Select, Reflect,Tag, Associate, Evaluate, Share, Report) on the Vignettes page. The group added the word Guide as the first item on the list. The question arose whether the term Tag covers defining a controlled vocabulary for outcomes/goals with associated rubrics and the like (Structuring of goal sets). Tag v. Associate: both have to do with drawing connections between your object and a concept. Free tagging is going to be done for 3.0, but we'll have to contribute to get controlled vocabularies/goal management. There are things that will be built by the Sakai community, and things we'll need to add. Vignettes page was modified to have two new columns, one for what the Sakai community is likely to contribute anyway, and the second for input we need to have. David Goodrum's post is a good model for us for speaking to the larger community. Flow (workflow) was added as the last category. Clay Fenlason has done a lot of work relevant to workflow. We should define the user experience we'd like users to have (learners and mentors)
Three Canoes offering to give a full-day intro to OSP. But Teaching and Learning doesn't want us to conflict with their half day. Should they keep full day, or just do 1/2 day to not conflict. Maybe if 3C published an agenda, and then did the more technical stuff during T&L session, it wouldn't be a bad conflict.