Page Comparison

...

1. Sakai/OSP 2.6 Issues and Status (Bug fixes can be verified on the following QA servers Nightly Build (HSQLDB) or Nightly build (Oracle))
   • SAK-12914 Database error when importing osp matrix
   • SAK-15958 Slow performance in Wizards Waiting on verification
   • SAK-16863 Error when saving page in Freeform Portfolio. Still open. Fixed and verified. Marist will add comment on Jira. Brooke's fix.
   • SAK-16869 backtrace in share when a user has been deleted should be verified.
   • SAK-16871 osp share sends wrong password.
   • SAK-17055 Matrix group filtering does not differentiate Sections from Groups. Needs a fix.
   • SAK-17086 Entity Too Large error in Portfolios share screen If users shared portfolio from large list of users or groups, when they go back to the summary screen, they get an error. Michigan is working on verifying. Not related to problem with, when creating external email, sharing by email generates an account. People don't like this behavior. Marist and Delaware have turned the option off.
     
     
2. Sakai 2.7/2.8 Development Status
   • SAK-16785 Sortable columns in OSP Portfolio tool - patch on ticket. Moved to 2.7, because it would require more work and is an enhancement.
     
     
   • QA Testing Resources for OSP 2.7 release? Institutions should try to prepare to have resources available for testing.
   • Portfolio UI Suggestions (IU): Portfolios 2.6 Suggestions.pdf, Portfolios 2.6 Suggestions.doc.
   • Status Update (IU): SAK-13838 Add Forms and Attachments User Interface Rework, Version 2
   • Status Update (IU): SAK-16693 Synchronize Portfolio Site Rosters with Associated Course Sites. No change.
   • Status Update (IU): Indiana University Matrices Enhancements. No change.
     • SAK-15822 In Matrices, "manage status for all users" only changes current user No change.
     • SAK-16261 Make the Manage Status function in Matrices and Wizards Group Aware No change.
   • Status Update (CRIM): Finer Grained Document-Level Matrix Permissions Updates. Nothing new.
   • Status Update (UM): Collaborative Portfolio Contributions. Changes are on OSP nightly server for review. Beth would like to merge into trunk. Teggin submitted two Jira requests: ability to transfer ownership and something else. By the end of the day Beth will merge to trunk.
     
     
3. Standing Agenda Updates
   • Sakai 3 Development & Content Authoring (Sakai 3 ePortfolio). People should think more about John Norman's "Manifesto" about grading.
     • Moving content from http://osportfolio.rsmart.com to www.sakaiproject.org. Site should go live this week. OSP content may be added later.
       
4. Functional & General Issues
   • Status updates on OSP Help Updates(October review; November commit). Jan reports that reviews and updates are moving along.
5. Discussion of Lynn's Proposed Changes to Portfolios Tool
   1. Modify page to select template so that it also includes the step of adding the portfolio name. Suggestion: move Name to top of form. Comment: in the future most people may not see this page, when there is only one template.
   2. Move editing the portfolio name down to the Details section.
      • Need to clarify what problem is being solved by the change
      • Why is default internal name important or need to be changed?
      • Suggestion: remove Edit link from top portfolio name and only keep the Edit link by the portfolio name in the Details section
   3. How to encourage users to fill out required settings?
      • Moving 'Required Content' to tab is not technically feasible
      • Alternatives:
        • Move required settings FIRST prior
        • disable sharing if 'required settings' not
        • copying 'required settings' link to Add/Edit content
        • Adding required settings in wizard-like in portfolio creatiion
   4. Moving Active/Inactive & Allow/Disable comments to share screen
      • maybe doesn't need to be here if Active is the default, plus we don't want to highlight comments
      • Adding to the share screen could confuse an already confusing page
      • Active/Inactive does, however, related to sharing
   5. Return to Wizard like workflow?
      • Needs more thought...