Fluid and free form portfolio
Michael Feldstein
michael.feldstein at oracle.com
Tue Dec 11 06:31:45 UTC 2007
Ah, I got it now.
There's a real need for what you're describing; I just wouldn't use the
term "portfolio" for it. Semantics, I think.
- m
Sean Keesler wrote:
> 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
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work
>
--
Oracle <http://www.oracle.com>
Michael Feldstein | Principal Product Manager | +1.818.817.2925
Oracle Academic Enterprise Solutions Group
23A Glendale Road, Glendale, MA 01229
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071210/031c56ff/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 13903 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071210/031c56ff/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oracle_sig_logo.gif
Type: image/gif
Size: 658 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20071210/031c56ff/attachment.gif>