History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-10140
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Beth Kirschner
Reporter: Beth Kirschner
Votes: 9
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Sakai

Portfolio tool with share of aggregated sites, roles, users

Created: 22-May-2007 08:59   Updated: 23-Oct-2008 08:51
Component/s: OSP: Portfolios
Affects Version/s: 2.4.0, 2.4.1
Fix Version/s: 2.5.0

Time Tracking:
Not Specified

Issue Links:
Depend
Relate
 

2.4.x Status: None
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
(There is be a dependency between this and SAK-10135)

Description:
Student is building a portfolio with portfolio tool in My Workspace or in any worksite (course, project, portfolio)
Student is a member of three sites, "CIG"1, "CIG2", "Course1"

In Step 3 of 3, user should be given the option to share:
- with any role in any worksite (in which they are a member)
- with any user in any worksite (in which they are a memer)
- with guest users specified by email address (existing functionality)
- with public web access (existing functionality)

Student should be able to select a group, multiple groups and / or individuals to share a portfolio.

This may require a UI change to provide the ability to drill down into a site/roles. List may become unwieldy when a student is a member of many sites.

My Workspace users should have access to global templates.

Porfolios created in My Workspace must continue to function even if the worksite containing templates/layouts is removed.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Beth Kirschner - 10-Jul-2007 06:02
Notes from 7-9-07 conference call:
* publish portfolio within worksites other than where tool resides
* Original OSP functionality - ability to share portfolios with any user (not constrained by worksites)
* Share with individuals, worksites, worksite groups or worksite roles
* Purpose is to reduce boundaries (including restrictions on site-types, i.e. allow share with users in portfolio and non-portfolio sites)

Beth Kirschner - 31-Jul-2007 09:16
Additional features that may be done in conjunction with this issue (or separated into another), include
1. Optional email notification when sharing with individual users
2. Optional single password protection for public web access to provide nominal privacy

Outside the scope of this issue is the ability to create guest user accounts when Sakai is configured with a external authentication provider. If this was available, portfolio could share with 'guest' users without considering what the underlying authentication scheme is.

Beth Kirschner - 07-Aug-2007 14:01
Note that selecting evaluators for Matrix/Wizards is affected by this feature -- those screens have been redesigned to be consistent with portfolio share (separating user from role selection).

Beth Kirschner - 08-Aug-2007 08:10
Checked into trunk -- optional features mentioned above not included. Support for "browse for individuals" now enabled if worksite list has more than 20 users (formerly 100). Support for share by users & roles both within and without worksite.

Beth Kirschner - 08-Aug-2007 08:53
additional notes:
- the separate 'browse for individuals' page is now enabled for greater than 20 worksite users (was 100).
- if notifyNewUserEmail=false (in sakai.properties), portfolio users will not be given the option of creating guest user accounts (but if one already exists, they can share with that user)

Chris Maurer - 18-Aug-2007 18:33
r34118
Fixing the parameter in setSelectedRoleList to actually be used in the method

Megan May - 06-Feb-2008 11:59
Tasks for 2.5.0 have been completed. We're nearing the end of the QA cycle and A lot of general regression testing has been going on for the past few months - the changes have likely been reviewed via this method of testing