Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

See also Community Ideas for Future OSP Releases for recent OSP community discussions on OSP functionality for Sakai 3.0.

See also OSP Blue Sky Notes from Sakai Amsterdam and OSP Future Enhancement Notes from Sakai Paris for ideas leading up to this discussion.

Sakai 3.0 Planning

We invite your contribution to the following list of OSP-related functionality to preserve and expand in Sakai 3.0 - using a list of core portfolio functions created at Sakai Paris and based on discussion at Sakai Amsterdam.

What portfolio functionality do we want to preserve and expand for each of these core functions?

Portfolio Function

Sakai 3.0 General Planning

OSP 3.0 Needs

Guide

-

-

Collect

-

-

Reflect

-

-

Tag

-

- We would like to see better ability to move work between portfolios, matrices, and personal resource areas.  Multiple portfolios should be easy to combine into single ones; items from matrices should be able to be collectively downloaded and collected together, etc. T.Summers, VT

Associate

-

-

Evaluate

-

-

Share

-

-

Report

-

We are interested in this function, to be restored or enhanced, allowing access to the portfolio artifacts and meta-data such as counts. More details and use cases on request. R. Hill, UWyo
- We would like to see more ability to report out other statistical information about matrices without the need for a separate reporting tool to be customized per matrix.  For example, retrieving statistics such as a report of who has Cell A2 empty/full, number of items added to Cell C3, or an overall percentage of who have cell F22 in the "Completed" status would be very useful. T. Summers, VT

Flow

-

- We would like to see improved interaction between the OSP tools and the XSD-based forms that drive them.  For instance, we need to be able to edit and replace forms after matrices are in place (published); to have a better tool for creation of these forms; and to have a system that isn't going to slow down the more forms we create. T.Summers, VT

- It would be nice to have one interface for creating presentation portfolios. T.Summers, VT

Marc Zaldivar's original post on ideas for Sakai 3.0:

  • A goal set could be opened as a widget on the page.
    • That goal set could be searched through, browsed through, etc.
    • Goals could be either selected or dragged onto an assignment widget, a matrix widget, etc.
  • Goals could be associated with tags. These tags could be added to assignments, blog posts, discussion posts, resources, wizard pages, quiz questions, and probably more. Reports and presentation pages could be created using these tags as quick selectors (as in an administrator collecting evidence across several individuals (say a graduating class of seniors), looking for referenced submissions for the "Critical Thinking" tag; or, a student would be able to create a quick presentation portfolio by displaying all references to the "Portfolio" tag.
  • Assignments should be able to be "tagged" as well, with goal tags or by an individual's own tag. An instructor would need to tag an assignment and then have all student responses automatically receive that tag. A student may wish to tag their individual response with a different tag, in addition to the one(s) the instructor adds.
  • Portfolio presentations would be more easily configurable by users, including an array of style and layout choices for pages, with easy ways to add content of various types (artifacts, blogs, guided reflection forms) to those pages.
  • Users still will need varying levels of permissions on resources because of portfolios. Some items will need to be public to the WWW; others may be public only to a specified group of individuals; some items should remain private and unreachable. Permissions on all items added to portfolios need to be able to be customized by the user.
  • No labels