Google Drive has been out for a week so those who had been waiting for it should have it running by now. If you did not grab it early then you typically waited at least a day to be provisioned to load it. We have intentionally kept the announcement quiet at our university so that we could evaluate and formulate a plan for how we might transition our employee/student web storage to Google. So far it is all that I had hoped it would be. If you have jumped on the Google Collaboration bandwagon you are aware of the strategic advantages and that the “Drive” component was the missing link.
We have used Xythos (now Blackboard) web storage solution for 7 years and it provided the web storage flexibility that we desired but it never reached that ease of use level that would have commanded our loyalty. So now it does appear that we will formulate a plan to migrate from Xythos to Google Drive. And for this move I want to be proactive. We allowed our users to adopt Google Apps as they desired and for the most part we are happy with their usage. When we replaced our university email with gmail there was a major uptick in the strategic use of the Google Collaboration suite and again we were pleased with the overall usage patterns. This has driven new IT coaching initiatives to promote the most effective ways to utilize Google Docs.
Google Drive is the completion to the overall cloud based solution. With the increasing use of Google Docs, management of those app files was starting to be a problem, especially with all of the sharing relationships. Google Drive’s initial task migrated all of your Google Docs into a folder based organization that returned control to you for of those original Cloud files. Now with the option to move or co-locate our traditional drive based files to G-Drive with collaboration flexibility, and providing access for all of our computing devices (IOS version coming soon), we are happy.
Of course we can’t adopt another Google tool without dealing with the privacy question. Google’s Terms of Service are clear. Google does not own your files. By accepting Google’s Terms, you authorize Google to provide the services you have requested. They may learn more about us from the file names we use, but they are not mining our files for secrets. Doesn’t mean we should have secrets in our files, because the real security issue is still maintaining our own account security.
Now we begin to strategize how best to leverage this completed collaboration tool kit. And what is great is that we have the Summer to prepare for a university rollout. It does not look like we have any concerns about early adopters for our .edu domain accounts. I am optimistic that the pricing model for education will allow us to easily provision additional storage quotas for our power users and management of our domain with Google has never been a problem. So we just focus on the Google Drive features and encourage migration from our Xythos, but we are not looking at any hard transition milestones. Life does get better for Higher Education IT.
So let the dreams continue. It is encouraging to know that Google already has API’s addressing some of the Web based access options. I’ll be looking for Moodle LMS plugins. Maybe the next gift from Google will be an expanded Video distribution system complete with sharing controls and streaming options.