Fluid and free form portfolio

[Sean Keesler]

Well, in fact there is a distinction.

While student¹s repositories are ³owned² by them, the portfolio tools DO
allow students to publish/share their portfolios for different purposes.
What I am talking about is that to tools don¹t lend themselves to
collaborative authoring.
At their best there is a means for someone to give feedback and/or evaluate
chunks of the portfolio.

For some schools looking to create a group portfolio consisting of multiple
contributors work, this is sort of awkward, given the other options for
collaboration.
Maybe others don¹t see this as OSP¹s niche, but it just seems like a natural
progression for the OSP free form portfolio tools.

Sean


On 12/10/07 8:46 PM, "Michael Feldstein" <michael.feldstein at oracle.com>
wrote:

> 
>>  
>> Part of the issue is that I think that the original uses of portfolios were
>> very focused on one student "owning" a portfolio, which REALLY limits it
>> use. After 3 years of using collaborative tools like wikis and Google Docs,
>> I believe that folks come to an authoring environment expecting to be able
>> to work together, if they want to. This would really change the educational
>> appeal of the tools for folks that are not into the other dimensions of the
>> tools.
>>   
> Part of the problem was a failure to make a distinction between the student's
> repository, which absolutely should be owned by the student, and the portfolio
> space, which usually needs to be collaborative. I'm attaching a picture from
> BECTA's ePortfolio analysis here, although I'm not sure whether it will come
> through the listserv intact:
> 
> 
> If you think of the bottom space as a (JCR-compatible) repository where
> individuals own content that the provision into the environment, the top
> rectangles as collaborative spaces (regardless of whether those spaces are
> thought of as "eportfolios"), and the "tool" arrows as collaboration services
> that get provisioned into the spaces for specific purposes, I think you have a
> flexible learning and collaboration environment that looks roughly like what
> Sean and John are talking about. From 30,000 feet, it's not so different from
> what Sakai offers today, but implementation is everything.
> 
> - m


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071210/5ba30126/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 13903 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071210/5ba30126/attachment.jpg>