Subscribe: Comments on: How “open-source” is Sakai?
Added By: Feedage Forager Feedage Grade A rated
Language: English
application  brian lamb  brian  comment  information  lamb  larger heterogeneous  linktool  network reflect  sakai  tool  tools  university 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Comments on: How “open-source” is Sakai?

Comments on: How “open-source” is Sakai?

a "b" blog

Last Build Date: Fri, 19 Jan 2018 16:15:57 +0000


By: Syndicating Myself

Thu, 27 Nov 2014 05:35:38 +0000

[…] be, the architecture as Jim Groom metaphorized as the syndication bus (and properly attributes to a Brian Lamb comment quoting George Siemens, how far can you follow the attribution […]

By: Domain of One’s Own [visualized]]

Tue, 20 Aug 2013 07:37:38 +0000

[…] along, through posts and comments, you see great ideas being born from the fertile mind of Brian Lamb. Similarly Alan Levine is a […]

By: Imagining Cyberinsfrastructure | bavatuesdays

Thu, 28 Jun 2012 03:43:48 +0000

[...] Brian Lamb’s unbelievable explanation of this concept in regards to RSS in the comment thread here, this is a refrain I come back and refashion (or is it steal) for conference proposals regularly as [...]

By: The Design of Openess » “I’m on a mission from Lamb”

Sat, 08 Aug 2009 21:32:52 +0000

[...] quote Brian Lamb from this comment here: I’m reminded of something George Siemens said at a symposium on distributed tool strategies: [...]

By: University of Virginia and WPMu? Wahoo! at bavatuesdays

Fri, 01 May 2009 10:25:56 +0000

[...] we did get a rather in-depth look at Collab, their installation of Sakai, which I blogged about here. It seemed apparent after this outing that Sakai was going to meet the needs of UVA, and while WPMu [...]

By: Don’t Call it A Blog! at bavatuesdays

Sat, 29 Mar 2008 11:48:27 +0000

[...] idea for this paper was inspired by a comment by Brian on a post about the limitations of one of the most “promising” open source [...]

By: Aeroplane Software: Sakai Consulting » Blog Archive » Sunlight is the Best Disinfectant

Mon, 21 Jan 2008 23:35:43 +0000

[...] Groom has an excellent post about Sakai from the point of view of a savvy [...]

By: matt small

Sun, 21 Oct 2007 07:55:35 +0000

This debate opens up a few of the big problems with Sakai: 1) It is developed by research universities--and mostly by the top profs and their grad students at these universities. And naturally they use their own desires and dreams (in code!) for an online system as the primary use cases. But the majority of students in the US are not taught in small, highly independent groups. Maybe they should be, but that model does not scale. So for years now Sakai has been an application with great potential, and likely always will be, as it's funders really have little understanding or interest in facilitating the day to day activity of a common teacher teaching hundreds to thousands of students. As such, Sakai largely replicates the functionality of Postnuke, Drupal, Xoops, etc. and as they do, fails when matched with Blackboard for meeting the needs of usual teachers. Of course the white elephant in the room has a name with two os, and must not be taken seriously as it is not java and all the profs at all the R1s _know_ that serious applications are written in java--the big grantors don't give real money to PHP projects, period. And this is not about providing better teaching tools, improving student learning, or about making teachers lives easier, ok--it is about the 'best' faculty at the 'best' institutions getting funded to do work that interests them, people who are looking for a usable tool for common users at non-premier institutions to come from this process are going down the Huron with a theoretical paddle that has great potential to one day move water... But hey, "Together we stand, divided we fall...Goodbye Chenga" and all that.

By: Yitna Firdyiwek

Fri, 21 Sep 2007 15:42:27 +0000

Jim, LinkTool was originally created by folks at Rutgers University who designed it to address the need to hook "legacy applications" into Sakai. It is still not part of the core tools of Sakai, but is available for those who want to turn it on. In order for your application to be hooked in, it has to be able to consume web services supplied by Sakai. We work with ColdFusion and PHP and both scripting languages have built-in web service capabilities. What we had to do is retro-fit our applications' login pages to process the web service information from Sakai (user, role, etc.). LinkTool creates secure connections between Sakai and the application, so once the connection is made, we can trust the authenticated information about the user. Once your've got it to work, there is a lot more you can do to communicate other information between your application and Sakai. LinkTool works, but is not a finished product -- I'm not sure it's value is fully appreciated even by Sakai developers yet. But in my opinion, that's what makes me forgive a lot of the surface weaknesses of the tool and see the possibilities. Your last comment is right on target: "I wonder if Sakai promises more robust possibilities for collaboration than a handful of smaller, more agile tools that might be shaped into a larger, more heterogeneous learning network through which we can reflect and archive the mind of a university in a host of more flexible and portable formats."

By: jimgroom

Thu, 20 Sep 2007 16:04:27 +0000

Yitna, Thanks for the clarification about LinkTool, I was hoping the iframed integration was not the extent of it. How exactly is Sakai going to integrate these external tools using this tool? It was not clear to me and I would love some more information on this. I imagine this would be a key component of joining a number of the "smaller" best of breed tools. Is the integration of these tools through LinkTool something a Java programmer would have to create? --or is it out-of-the-box? --or are these extensions/modules already available? I guess I have a lot more to learn about the inner-working of Sakai, and I'm glad you responded here because I'm sure my impression of Sakai was far from entirely accurate. At the same time, I wonder if Sakai promises more robust possibilities for collaboration than a handful of smaller, more agile tools that might be shaped into a larger, more heterogeneous learning network through which we can reflect and archive the mind of a university in a host of more flexible and portable formats.