One of the key pieces, apparently, in the VLE jigsaw is providing students with an effective e-portfolio system; working out How to integrate VLEs/LMSs with other student-facing systems is another; interface aesthetics is something that's really important to the user of course, which is why I doubt it is on the list...;-)
So to everyone working in this area, might I suggest you take 20 minutes out of the crazy project development cycle you're probably in worrying about how to do all this, and go and look at box.net for an example of how to manage files via a browser, and how to integrate with other systems using public APIs.... please...
And to everyone working on repositories, wondering how to get your academics publishing stuff through your repository (i.e. storage service...), go and look at box.net for an example of how to edit and publish content stored in box.net using third party systems via their public APIs.... please... (you should probably also read what Andy Powell has been saying recently... latest here: Repositories follow-up - global vs. institutional.)
Even if you've looked at box.net before, months ago, go look now - go on, it's Friday, give yoursefl something to dream about over the weekend... ;-)
Here are some pointers:
There are more available, too - see the full list of box integrated services (includes, blogging on Blogger and Wordpress, the Picnik photo editor, and Autodesk Freewheel).
PS my Scribd iPaper bookmarklet (as mentioned in Lifehacker;-) is now back up without the need to get your own publisher key... so you can just grab the bookmarklet and start using it straightaway to view documents online...
Posted by ajh59 at February 22, 2008 02:26 PMThanks Tony, interesting option to add to our growing list of ePortfolio candidates:
http://ple-uol.wikispaces.com/ePortfolios
I'm slightly confused about access control son Box.net - do you have to have a paid account to make your portfolio public?
As I understand it, access control is as follows:
1) You can specify named collaborators, by emailing them an invite using the email address they registered on box.net with. These are collaboration folders and are viewable in your box.net account. If you edit a doc in a collaboration folder, I will see the changes. (See: 'What are collaboration folders?' http://box.net/help/195 )
2) You can make a folder or a file shared/public. There are two ways of doing this for a folder (get link to folder, or get a widget for the folder) and one for a single file (get link for this file).
Getting a link: a) makes the item shareable; b) makes it public via that url in a box.net 'sign up now' wrapper. The widget provides a public, read only view of the contents of the folder that you can embed in any web page.
The above services are free. There is a pay-to-play service, which provides a link directly to the file (so no box ad wrapper round it), and allows you to password protect it (see 'Direct links' http://www.box.net/help/32 )
Collaborators can be organised in subgroups (i haven't played with this yet, though - see here: http://www.box.net/help/203 )
Users also have a public box - I guess anything put into this is public by default?
If anyone from box.net wants to chip in and correct any misunderstanding on my part, please feel free :-)
Posted by: Tony Hirst at February 22, 2008 06:31 PMOn the other hand:
http://skydrive.live.com/
But how well does skydrive integrate with other online systems?
If the portfolio is just a filestore/filesystem, then fair enough (maybe).
But as far as I know, box.net is one of the few sites that's showing for real what you can do with API integration in this area...
Posted by: Tony Hirst at February 22, 2008 09:24 PM