Question 186 of 365: How should we submit our work?

- Image via CrunchBase
I think a lot about the submit button. The process of taking something that you own and uploading it to someone else is an act of trust. I am trusting that everything that I submit to Flickr will be there when I look for it, without some crazy provisions or copyright license on it. I am trusting that the presentations I upload to Slideshare will be embeddable wherever I want them to be. Whenever I submit an assignment in an online course, I am trusting that it will be valued by the person on the other end and not just put into a virtual file cabinet to make one more check on a class checklist.
This trust isn’t something that we should take lightly or that we should let rest as it is. There is inherently a problem with turning over your work to something else via a button. The transaction method of turning things in is all wrong. When we have to turn over all authority of the things we have authored, we are no longer able to take responsibility for where they end up. And we should be able to do that. We should be always able to make decisions about our content, continuing to extend its existence wi every link and collaboration.
I want to start making Dropbox the standard for submitting. The very idea of dropping your content into a folder on your desktop and having that sync into a space that other people and services have access to is he future of sharing. Removing content or revising it updates the files everywhere that they are referenced, preserving your control and your ability to revise and continue to come back to where you have already been without recreating or storing every ne version on every different service that comes into existence.
I want to turn in assignments by dropping files onto my desktop and revise my answers with a simple save. I want to share them with everyone else who is in my class and have the facilitator see that sharing as well. I want to have photo sharing sites get access to my collection through a sync from my computer. I want to always maintain the copies but know that they exist and are accessible easily.
The possibilities for creating are simple and elegant when you remove the pressure of the submit button. When you no longer have to wait until something is good enough to start syncing it our to the world, collaboration has the ability to take hold of everything that you do. When you don’t have to be connected to the web in order to check in on what other people have contributed, we aren’t tethered to any device or service. Sharing ownership of our work and also being able to continue to expand its use is the next journey that we must attempt.
This is the workflow I see:
Any file that is on your device is on the cloud is also shared with others and is found on other’s hard drives. The redundancy allows for backup after backup of our work. All of these drives and versions are networked and allow us to see as a work progresses because a visualization of all edits across the world will be a part of the metadata of the file itself. Each file will be editable on all devices either by a local program or a cloud based service. The file will not care which. Microsoft word and Google Docs will simply be the way we revise the much more powerful part of this process: the sharing. Each file will become linked and embeddable. And because of the way all of these hard drives are networked, the file will not be embedded just from the cloud service, but it will also be embedded from the original source (your device). This will mean that we will always be able to track where content has come from and where it goes to. The single source of truth will be the person that created it, and if they delete it, all that will be left will be the remixes and revisions that work under fair use.
None of this will happen if we keep on with the submit button as the only way to share (this button takes many forms, but it is the function that I think is going to hold us back). We need to move toward sharing responsibility for our files and our ideas. We need to submit by moving things around on our devices and not just on the services that seem to come and go every few weeks. We need share via a link that will always exist, instead of break with every whim of a few shareholders. The infrastructure isn’t what needs a tweak. It is us. We need to push what our own devices can do and what we are willing to pay for as well. We need to become our own data centers and wharehouses. We need to become our own cloud, all with the idea that Google or someone else will also have backups of our stuff too. Because you know they will.
Related articles by Zemanta
- Wuala – Linux friendly secure DropBox alternative (omgubuntu.co.uk)
- A startup should create this storage device. I would buy it. (arnorhs.com)
- 4 Best Sites To Get 10GB Free Online Backup & Storage (makeuseof.com)
- Get 10GB of Free Storage Instantly & Share Files on the Go with quanp (makeuseof.com)
- SyncToy: Yet Another Useful Windows Backup/Sync Tool (maketecheasier.com)
LiC Podcast: Design with Forever in Mind Archive
Although I was thrown a whole bunch by not having wifi for the first 45 minutes, I think that the session was worthwhile. Here is the archive of all that we have done. I am also including my planning podcast from my drive up to copper mountain.
Presentation:
Drop Box:
Important Links:
Ben Wilkoff Links:
- Learning is Change Blog and Podcast>
- Twitter Page
- Other Presentation on Thursday (The On Button: Instant and Always-on Collaboration)
Presentation Links:
Exit Plan for Vocaroo:
- Wav files backed up to a hard drive/server
Exit Plan for Drop.io:
- Everyone who downloads the podcast will have a copy.
Exit Plan for JamGlue:
- Mp3 files of mixes
Exit Plan for Screencastle:
- Download Direct Link to File and store on hard drive/server
Exit Plan for Screentoaster:
- Mov Downloads before uploading to screencastle site
Exit Plan for DimDim:
- Download and build own DimDim server and store recordings there.
Exit Plan for Twitter:
- Backup twitter with Tweettake
Exit Plan for Google Docs:
Ustream Archive:
Twitter Archive:
CosmoCat: @bhwilkoff was great to learn about screencasting and audio recording! Hope you enjoy Audioboo! #forevertie09Jun 23, 2009 09:46 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
bhwilkoff: Thanks to everyone for adding value to my session #tie09 #forevertie09Jun 23, 2009 09:40 PM GMT ·
from web
·
Reply
· View Tweet
Jun 23, 2009 09:13 PM GMT ·
from web
·
Reply
· View Tweet
toniobarton: Learning needs real purpose and real audience. #cotie09 #tie09 #forevertie09Jun 23, 2009 09:08 PM GMT ·
from web
·
Reply
· View Tweet
bhwilkoff: How do you capture learning? Add to the spreadsheet: http://tr.im/pvz2 #tie09 #forevertie09Jun 23, 2009 09:05 PM GMT ·
from Nambu
·
Reply
· View Tweet
Jun 23, 2009 08:40 PM GMT ·
from twhirl
·
Reply
· View Tweet
CosmoCat: I’m searching for #forevertie09 live on TweetGrid Search – http://bit.ly/4A1lo3Jun 23, 2009 08:19 PM GMT ·
from TweetGrid
·
Reply
· View Tweet
care507: I’m searching for #forevertie09 live on TweetGrid Search – http://bit.ly/4A1lo3Jun 23, 2009 08:13 PM GMT ·
from TweetGrid
·
Reply
· View Tweet
forevertie09: I’m searching for forevertie09 live on TweetGrid Search – http://bit.ly/MVxM0
#forevertie09Jun 23, 2009 08:13 PM GMT ·
from TweetGrid
·
Reply
· View Tweet
forevertie09: #forevertie09 Devonee – Technology Integration Specialist from Mesa CountyJun 23, 2009 08:12 PM GMT ·
from web
·
Reply
· View Tweet
forevertie09: I’m searching for #forevertie09 live on TweetGrid Search – http://bit.ly/4A1lo3Jun 23, 2009 08:11 PM GMT ·
from TweetGrid
·
Reply
· View Tweet
villagegreen: #forevertie09 to back channel: I’m Matthew Woolums, Integration Coordinator from DPS. My blog: http://villagegreen.edublogs.orgJun 23, 2009 08:08 PM GMT ·
from twhirl
·
Reply
· View Tweet
matthewadennis: SpEd in middle school in NW Denver. #forevertie09Jun 23, 2009 08:08 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
jcope50: #forevertie09 Hi! Jill – Skyline HS Teacher Librarian- St. Vrain – just moved to CO on Saturday from CA!!!Jun 23, 2009 08:08 PM GMT ·
from web
·
Reply
· View Tweet
toniobarton: #forevertie09 first year HS Computer Teacher from Manitou Springs High SchoolJun 23, 2009 08:08 PM GMT ·
from web
·
Reply
· View Tweet Sara24lynn: #forevertie09 Hello! I am a library media specialist in a K-5 school in Greeley, Colorado.Jun 23, 2009 08:08 PM GMT ·
from web
·
Reply
· View Tweet
lbreed: #forevertie09 Hi! Lisa from Evergreen Middle School! I am looking forward to learning about authentic assessments.Jun 23, 2009 08:08 PM GMT ·
from web
·
Reply
· View Tweet
matthewadennis: Name is Matthew (obvi). Work in DPS. #forevertie09Jun 23, 2009 08:08 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
Sara24lynn: #forevertie09 Audioboo.fm is an audio tool for iPhone My audioboos http://audioboo.fm/profileJun 23, 2009 08:07 PM GMT ·
from web
·
Reply
· View Tweet
matthewadennis: @forevertie09 mind being blown; didn’t realize so many tools out there that I didn’t know about. Not in the know at 25?? #forevertie09Jun 23, 2009 08:03 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
bhwilkoff: How do you use audio to capture learning? Call 646-402-5701 x 25286 #tie09 #forevertie09Jun 23, 2009 08:00 PM GMT ·
from txt
·
Reply
· View Tweet
Jun 23, 2009 07:54 PM GMT ·
from TweetGrid
·
Reply
· View Tweet
McTeach: I’m getting real-time search results at TweetGrid http://tweetgrid.com/ #forevertie09Jun 23, 2009 07:54 PM GMT ·
from TweetGrid
·
Reply
· View Tweet
RickTanski: @jenwagner Slide 10 on http://tieconference.wikispaces.com/1117 #cotie09 #tie09 #forevertie09Jun 23, 2009 07:51 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
toniobarton: #forevertie09 I like http://www.vocaroo.com/ recording website, easy to use.Jun 23, 2009 07:50 PM GMT ·
from web
·
Reply
· View Tweet
dlevesque: vocarro does not work on a eeepc #forevertie09Jun 23, 2009 07:47 PM GMT ·
from web
·
Reply
· View Tweet
erhubbell: @bhwilkoff Hi everyone! Looking forward to great conversations today. #forevertie09Jun 23, 2009 07:39 PM GMT ·
from TwitterGadget
·
Reply
· View Tweet
matthewadennis: Will the iPhone be forever, Ben? #forevertie09Jun 23, 2009 07:31 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
McTeach: @bhwilkoff was giving it rave reviews! RT @courosa: @zemote I see Edmodo on the screen at #forevertie09Jun 23, 2009 07:29 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
·Show Conversation
sroseman: #forevertie09 how do i get rid of the echoJun 23, 2009 07:29 PM GMT ·
from web
·
Reply
· View Tweet zemote: @courosa awesome!!!! thanks for letting me know #forevertie09 , if anyone has questions, forward them onJun 23, 2009 07:28 PM GMT ·
from web
·
Reply
· View Tweet
·Show Conversation
courosa: @zemote I see Edmodo on the screen at #forevertie09Jun 23, 2009 07:27 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
·Show Conversation
courosa: #forevertie09 re: learning that lasts 4ever,think about boyd’s media attributes” persistence,replicability,searchability,invisible audienceJun 23, 2009 07:25 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
dlevesque: #forevertie09 why last forever?Jun 23, 2009 07:23 PM GMT ·
from web
·
Reply
· View Tweet
RickTanski: @bhwilkoff Hello from an office in Colorado Springs#cotie09 #tie09 #forevertie09
Jun 23, 2009 07:22 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
·Show Conversation
McTeach: @bhwilkoff Hello from Sunny Northern California! #forevertie09Jun 23, 2009 07:22 PM GMT ·
from web
·
Reply
· View Tweet
·Show Conversation
ericolsen: Will the computers ever work?#forevertie09Jun 23, 2009 07:20 PM GMT ·
from TwitterFon
·
Reply
· View Tweet
courosa: #forevertie09 Hey Ben, hi from the St. Louis airport, soon to get back to Canada.Jun 23, 2009 07:20 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
villagegreen: Sitting in on design with forever in mind at tie #forevertie09Jun 23, 2009 07:20 PM GMT ·
from Twitterrific
·
Reply
· View Tweet
bhwilkoff: Say hello to all of the folks at #forevertie09Jun 23, 2009 07:19 PM GMT ·
from Nambu
·
Reply
· View Tweet
RickTanski: @bhwilkoff 3 hour session! I’m going to kill some bandwidth bits for sure. #cotie09 #tie09 #forevertie09Jun 23, 2009 07:10 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
·Show Conversation
mjmontagne: tuning in to a bit of @bhwilkoff ‘s workshop #forevertie09Jun 23, 2009 07:09 PM GMT ·
from TweetDeck
·
Reply
· View Tweet
debh2u: RT @bhwilkoff: Session wiki page http://tieconference.wikispaces.com/1117 #tie09 #forevertie09Jun 23, 2009 10:53 AM GMT ·
from twhirl
·
Reply
· View Tweet
bhwilkoff: Session wiki page http://tieconference.wikispaces.com/1117 #tie09 #forevertie09Jun 23, 2009 05:55 AM GMT ·
from Nambu
·
Reply
· View Tweet
bhwilkoff: Creating a hashtag for my session tomorrow at #tie09. Come and Join in the session with #forevertie09Jun 23, 2009 05:54 AM GMT ·
from Nambu
·
Reply
· View Tweet
Feeds in a workflow.
For as useful as they are for aggregating information, rss feeds are not all that easy to put into one’s workflow. You have to make a point of going to a special page and maintaining your reading list. Google reader (http://reader.google.com) makes it pretty easy to do this, but you still have to make a habit of going there.
At one point (not that long ago), I had over 2000 unread posts in my aggregator. It seemed unlikely that I would ever be able to sift through it all and pull off any kind of conclusions. I was under the infamous guilt of falling behind. More than that, I felt like my PLN was leaving me behind.
Well, no longer. I have found a way to make my rss feeds more immediate, a way for my feeds to literally alert me to their presence. Enter http://snackr.net/. This Air application (good on any platform) is the only way I have figured out to put feeds onto my screen in the way that Tweetdeck or Twhirl has done for my twitter account. I no longer go to google reader for anything other than maintenance because it syncs directly with Reader. If you have enough room on your screen for one more way to connect, I would recommend Snackr highly. If only for the ability to show others that Rss is not abstract. It is real, and it is a powerful way of exploring connected and authentic learning.
Reflective aside: What would anyone think of a collaboratively maintained educational Google Reader account that could be used by Snackr apps in schools? Which feeds should be included and why? Is it just one more thing or would this kind of workflow influence allow for real change?
Sent from my Verizon Wireless BlackBerry
Create your own MobileMe (Sync Everything, at all times).
An aside: it is too bad that every post I write seems like an attempt to get back into the habit of posting, but I suppose until I start blogging consistently again, that is just how it is going to have to be. I have missed way too many things that I have been thinking about to ever fully catch up, but perhaps I can start anew. Anyway, here are my latest thoughts.
Before I go into the details of how to sync yourself completely, I want to tell you why I even undertook this idea. Well, our school system uses an extremely proprietary e-mail and calendaring system called firstclass. Every person that uses firstclass in our schools is locked in to using the firstclass calendar for appointments and things of that nature. But, because I have seen the light of using Google Calendar (open API, shared calendars, embedding, etc), I refuse. In fact, I was so obsessed with the idea of converging the two that I speant an entire weekend (when I wasn’t having fun with my family) on getting Firstclass to sync with Google Calendar, and then eventually my new blackberry that the school district provided for me.
So, this is how you sync everything:
Calendars:

Contacts:
Now, for the details…
(Update: I didn’t put this in the initial post, but I think it is worth mentioning that Firstclass does have a way to sync with both Palm Desktop Software and SyncML directly, but since my district hasn’t set either of these up, I thought it was important to try and find a better way of doing things… there are also third party services that do some of this, but I want a FREE workflow)
In order to get your first class calendar to talk to anything else, you will need to export it as a iCal file:
Now, you may look at this picture and ask, why I wouldn’t just export it as a blackberry file and skip all of the steps in the middle. Well, there are a few reasons. One, if I did this, all of the events would be duplicated every time I exported and imported. Two, because I am on a Mac I do not have any blackberry desktop software to make this sync work.
So, onward we go to iCal. First, you will need to set up your Google Calendar to sync with iCal, using this handy dandy tutorial from Life Hacker.
Now that you have your Google Calendar set up to sync, simply import into iCal your latest and greatest export from Firstclass:
Now, if this isn’t your first time doing this, you will end up with a lot of duplicates. If that is the case, just use the iCal Dupe Deleter. This is also a good tool for deleting duplicates from Google Calendar if you have ever found yourself with too many of one item.
Now, you have synced completely to your Google Calendar and you are ready to sync to your blackberry. Simply point your device to this address and download your over-the-air sync application.
You can now enter an event in Firstclass, iCal, Google Calendar, or on your blackberry and they will sync with one another. Pretty cool, right. But, we are not done. If you would like to have your calendar in an even more universal Format, you can put it on a SyncML server, like Funambol.
All you have to do is download their blackberry application and you can sync to your heart’s content there.
For Contacts:
If you are also looking to sync your contacts, you can simply use your Blackberry or iPod touch to talk to Funambol using their built in programs (search for funambol in the App store, or use the above link to download the blackberry funambol application).
Then you can sync your contacts with the funambol server.
As for your Mac, you can use the Preference Pane sync.
This will let you put your contacts on your mac, on the funambol server, or on your blackberry and they will all sync.
I understand that MobileMe does a lot more than this, but I believe that if we can create a FREE workflow for each one of our teachers, students, and administrators that syncs information to the place that they need it, we will be able to have the conversations that truly matter. We will no longer be stuck trying to find information, it will always be ours. Although you may not geek out at all that I am proposing, I think there are some pretty heavy implications for continuity in the systems that we are creating. If you have figured out any more syncing tricks, please leave a comment and add to the value of our collective research.
The Ripe Environment: The Markers
The “I know it when I see it” form of collaboration is no longer valid.
We need new ways to tell if learning is happening through group contribution. We need to be able to assess collaboration, but we can’t do it the same way that we assess writing or proficiency. Those skills are much easier to boil down to a continuum or rubric. Others have tried, and we have been for the most part satisfied with their traditional, enigmatic, and mostly non-educational continuums for collaboration.
These forms, however, are not worthy of our cause. They provide us with a way to see things in an abstract sense, showing a fictional path to collaboration that is just as hopeless as using the term as a buzzword to show that change is occurring.
Instead, I would like to outline the types of collaboration that occur in The Ripe Environment. These are the markers that we should be striving for and looking for:
- Learning objects to be used by multiple learners, created by multiple learners. (This does not include one person writing or creating and the others supplying their input. True collaboration means that everyone has their fingerprints on the potting wheel.)
- Collaborative asynchronous lists. (Never underestimate the power of listing. And yet, the power is not in the listing. It is in the reordering, reorganizing, and reconstituting a list. Think of wiki collaboration here.)
- A followable thread of discussion (This can be through linking, commenting, or something like voicethread)
- Shared Space with over 10 revisions (Any object or space that has been edited or revised more than ten times by multiple authors can be considered a respectable work of collaboration).
- A mash-up or remix of anything (This type of collaboration marker is the halmark of true collaboration. The best examples are when the masher doesn’t know the mashee. That is when the unintended (but most amazing) concequences of sharing and collaboration kick in.)
Obviously this is not an exhaustive list. What are the other markers of collaboration in The Ripe Environment?
The Discovery School within a School

A colleague of mine and I were brainstorming all of the technology implementation possibilities for the next school, when he suggested that what we were talking about was not merely two classes (Social Studies and Language Arts) collaborating, but that we were shifting the paradigm of teaching to a School within a School.
On this podcast, I attempt to flesh out what a technology-centric School within a School would look like and I hit upon a couple of things:
1. Online interactive notebooks.
2. Collaborative note taking.
3. Curriculum wiki’s that are edited by students and teachers.
4. Teacher reflective blogging.
5. Strands of curriculum that students could learn all disciplines within.
6. Synchronous and Asynchronous online discussion.
Tags
Recent Comments
- Michael Wacker on Start Google Documents or Upload Files to Google Docs with an email.
- coursework on What I’m Learning: Hall.com
- essay writing service on What I’m Learning: Hall.com
- custom essays on Question 365 of 365: What is enough?
- resume help on What I’m Learning: How to make a secondary Google Calendar into a primary Calendar on iCal
Blog Post Calendar
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jan | ||||||
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | ||||











)







