A Clearer Google Docs Revision History View
It’s a bit awkward to see who did what in a Google Doc via the version history. That’s something faculty often want to do.
The easiest path I found was to name the oldest and newest versions. Then click to show only named versions. That does it pretty well. The video above shows it with more detail.
Related posts
Edubloggercon 2007 Google Earth Session
This branched out into Google Maps, Sketchup and even Swivel. I heard about some great projects being done by 4th and 5th graders using sketchup to create Incan (or Mayan?) ruins and then putting them in Google Earth. I’m really interested in seeing the examples but don’t have a link yet. The most interesting part of the discussion to me was a reminder of the googlelookup function in Google spreadsheets. You can use it to look up latitude/longitude coordinates for cities it appears and the use it to create an xml file. The cool thing to do would be to generate that data, the city’s population, avg. temp etc. (whatever interesting data you can pull through lookup or manually) and then push it to Swivel. And then, and then, and then you embed the Swivel data in the info window for each city. It’s sad how exciting that seems to me. Besides that I got some good links to look at later which are posted in del.icio.us if you’re interested.
Google Form to Google Sheets to Vue Website
When @cogdog & @twoodwar Were Building Websites From Google Spreadsheets Years Ago https://t.co/Im7oCecvpg — Keegan?Long-Wheeler (@KeeganSLW) February 28, 2018 This post from Keegan kicked of this demo.It also made me feel old. I can’t believe I’ve been doing this for so long. The goal is to create a pretty flexible template for using Google Forms to Google Sheets to simple website. I opted to do this one in Vue but may get around to doing it in plain JS or jquery if time allows. The first thing you need to do is make the form and put in some entries. You’ll be happier if your form prompts aren’t super long. Make them readable just keep them concise.There are ways to deal with that but they add steps so I’m ignoring them in this post. Once you’ve made a few entries so you have some data to work with, publish your spreadsheet as HTML. File>Publish to the Web. Click OK and what not. Don’t bother going to that link as Google has made that a fake promise. You just need the ID of the document in your current view. It’ll be something painful like 12WsyLvtfIPJkCXgEXsRkrI6dS0_K6brJikZqzkQa8TU and is visible in the URL after the /d/ but before the /edit. You can see the spreadsheet here. It doesn’t really matter but !full transparency! […]
Shifting out of IFTTT
Kin Lane mentioned that IFTTT, a service entirely built on APIs, doesn’t have an API. That bothered Kin and the more I thought about it it bothered me. So I figured I’d start disentangling myself from IFTTT. One of the things I did with IFTTT was to send out a Tweet any time I posted something new on my blog. Crazy to think I set that up in 2012. Granted, I could have replaced this with any number of plugins but I thought this would be fun and bit of API work but most interestingly it’d put me (mostly) in charge of how the tool worked. The following script is just cobbled together from something I found to get an RSS feed into a spreadsheet and a script I used a while back to send a tweet from a Google SS. Next steps will be to start playing with adding amusing variables to the message. The first message kicked through with a minor error but progress! Grabbing Flickr Photos was blogged & can be found athttp://bionicteaching.com/grabbing-flickr-photos/ — Tom Woodward (@twoodwar) March 20, 2016
Trackbacks and Pingbacks on this post
No trackbacks.
- TrackBack URL
Comments on this post