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 22 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

Current OSP 2.6 Functionality

Ideal OSP 3.0 Functionality

Specific OSP 3.0 Needs

Guide

- Organizers may use the FCK editor in Matrices and Wizards to provide instructions, rationale, and/or examples for participants completing each Matrix cell, approaching a Wizard as a whole, or completing each Wizard page. Forms and Form fields allow organizers to add simple text instructions. Form fields may also be given more elaborate prompts using a custom renderer. Portfolio Templates allow organizers to provide simple text instructions for each item participants select and/or for participants add text to Portfolios via Outline Options.

- Guidance must be more closely associated with workflow and an overt way to allow participants to easily understand what is expected of them.

Collect

- Participants collect items for association with Forms, Matrix cells, Wizard pages, and Portfolio Templates in Resources. Matrices, Wizards, and Portfolio Templates allow participants to select a portion of their items from Resources to submit for evaluation in a Matrix or Wizard or share with other via a Portfolio.

- Any item created by the user in Sakai should be available in the user's collection for reflection, tagging, association, sharing, evaluation, and reporting.

Reflect

- Organizers may supply prompts in Forms for Reflection to be included in Matrix cells, Wizards, or Wizard pages. Reflection forms may also be included in Portfolio Templates as options for participant selection or via automatic inclusion from matrices or wizards. Organizers may also add reflection prompts for participants to fill in via Outline Options in Portfolio Templates.

- Any items in Sakai should allow a reflection to be associated with it.

Tag

- Participants may tag resources item with metadata in Resources, but this data (with the exception of copyright prompts) is only available to the participant. The Goal Management tools allow tagging of goals from the same site or from associated sites, but this tool is still in Contrib. Matrix cells may also be tagged with goals from the Goal Management tool.

- Any item a user creates in Sakai should be taggable.

-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

- Items from Resources may be associated with Forms, Matrix cells, Wizard pages, and Portfolio Templates. Participants may complete Form instances to associate with Matrix cells, Wizards, Wizard pages, and Portfolio Templates. Organizers may automatically associate submitted Assignments with Matrix cells.

- Users should be able to associate any item they have created in Sakai with a portfolio workflow.

Evaluate

- Users with permission may evaluate student submissions for Matrix cells, Wizards, or Wizard pages by filling out and saving Evaluation Forms. Users with permission may also provide feedback at any time to ongoing work in Matrix cells, Wizards, or Wizard pages. Users with permission may grade submitted Assignments and/or rate goals linked to submitted Assignments. Participants may allow comments in Portfolios shared with others.

- Evaluation should be a much more flexible activity involving flexible workflows and multiple participants.

Share

- Participants may share Portfolios with any other user in the site, with users in other sites in which the user is a member, with any email address, or as a public URL. Participants may also submit Matrix cells, Wizards, Wizard pages, and Assignments for evaluation by other users with permission to evaluate.

- Users should be able to assemble, display, and share any item they have created in Sakai.

Report

- Users with permission may use Report definitions to run predetermined queries on data in pre-populated data warehouse tables. The data is displayed according to the specifications of the report definition, which may include more than one view of the data.

- Users with permission should be able to write queries on any item in Sakai and determine how the resulting data is displayed. - 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

- The OSP tools are used in combination to provide a workflow for participants. The lefthand menu bar and/or the home page for the site may be customized with prompts to assist participants with the intended workflow.

- Workflow must be much more closely coordinated with guidance and must include options for organizers to make the intended workflow within a site much more understandable for participants. - 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