Skip to main content

Posts

Making Your Own Version of Appointment Slots with Apps Script

Making Your Own Version of Appointment Slots In a previous post I showed an alternative version of Google Calendar's Appointment Slot's functionality created in Apps Script. You can see it in action here . Since making this app Google have, rather fantastically dropped their dropping of the Appointment Slots feature. This app may be useful to anyone wondering how to make an Apps Script Web App that loads jQuery and uses HTML templates. If you want to edit the code that runs it, you can get a copy of the script here: https://script.google.com/d/1Helzgu286Rh9QuHh4dbUq9SloMpb3USwygXSyXP9JcL6erToXpoVK_o5/edit Then you need to go to... File > Make a copy ... and then... File > Manage Versions ... and create a new version of the app. This is needed when you want to publish your web app. So next, then go to ... Publish > Deploy as web app You might want to restrict  Who has access to the the app  setting to just people from y...

An Alternative To Google Calendar's Appointment Slots

You might not know but Google are dropping the Appointment Slots feature from Google Calendar. The academic community has been pretty miffed about this decision because it's one of the features they've really taken to their hearts and were actively using. Appointment Slots are a great way of making any number of tutorial slots available for tutorials and letting students pick which times suit them. Google responded to the academic outcry with a list of alternatives . This list included paid for services with no clear pricing model for enterprise, downloadable open source software and, rather desperately, a few web2.0 tools that weren't even relevant. Few of these tools integrated with Google Calendars or Contacts, none would have worked with our log ins, and of course, none would be embedded in your Google Calendar making it easy to create overlapping or clashing appointments. So, I wondered how useful a tool I could create using Apps Script. Of course I couldn...

Missing Media in Blogger - Boo!

When someone leaves the University of York, their account is suspended which has the knock on effect that in Blogger your blog posts are written by "Unknown".  You can still see the blog posts. Worse than that, all the media uploaded by that person also disappears. See this post here . I'm looking into the Blogger API to see if I can at least find a user's posts and re-create them as someone else as an awful workaround. I've added an Issue to the Blogger forum.... tumbleweed ... and nobody is interested. This all comes about because Blogger isn't a "Core App" of Google Apps but it's rubbish. Boo Google!   At least let us be able to transfer ownership of blog posts or something. People regularly come and go at a University and hobbling their blog posts seems ridiculous. This may force us to have to think about using Wordpress ... which will be a shame.

Ten Tough Collaborative Inbox Questions

I had an interesting meeting with the Law & Management team about the possibility of using a Collaborative Inbox ( which is a kind of Google Group ) rather than our current in-house issue management system. We went through what they wanted to do when people report problems and they came up with a heap of great questions. With almost all their questions, my answer was, "Ooh, I'll have to look that up and get back tomorrow". Here are the answers. For the purposes of trying to answer the questions, I am using a Google Collaborative Index Group called "Silly Questions" which has been set up to allow people to email it ( without being a member ) and has two members ( Mike and I ). I will be mailing the group from a test account called "Not Tom". Q1. Can an issue be automatically given an ID? This was an based on someone having mailed in an issue, then later calling in and being able to refer easily to the particular issue. An ID can be the quic...

Collaborative Inboxes Now Work!

Google Groups' different types of groups ( Web Forum, Email List and Collaborative Inbox and the other one ) do more to muddy the waters of understanding Google Groups than actually describe what it is they actually do. Anyway...  I previously have blogged here that Collaborative Inboxes didn't work because in order to receive a reply to an enquiry - it meant that you had to be a member of a group - and therefore able to see everyone else's enquiries. This is the equivalent of group therapy for a clap clinic, in that as a question asker, you get to see everyone else's questions. I was only now, just showing someone interested in using Collaborative Inboxes, that particular quirk when I discovered a "cc The original sender" checkbox which is by default checked. Yay! This means you could now use Collaborative Inboxes for private issues, that get responses from the experts who are members in that group. AND fellow experts can see your response. AND the pers...

Platform Dilemma ( UI Builder vs HTML application )

I'm currently working with the Chemistry dept. to help use Google Docs for recording students lab experiment marks. It sounds simple enough until you find there are over 170 students in a year and there are at least 20 tests to be done, and the students get broken down into groups and rotated, and different people need to log different bits of information (that the student attended, their mark, that their mark has been agreed etc ). That's well over 2000 marks a year.... which in the scale of numbers isn't the biggest, I know, but that's not where the dilemma is. Part of the problem is the different ways different people need to access creating the students marks but I'll come to that another day. The dilemma is that, I have the need for a really simple to use interface for entering students' marks. I could either use the UI Builder built into AppsScript OR I could create an HTML application in AppsScript. With an HTML application, it's a breeze to a...

The Day I Dropped Round The Security Guy's

After discovering that my direction of work for the Booking System was from a security perspective , deeply flawed, I thought that I could perhaps work around giving people access to the code by embedding a web application within a Google site. I thought this would be a big structural change, but it only took a few minutes. It looks like this. There's a slightly different approach. Firstly the spreadsheet is embedded as view only. The spreadsheet is only used a visualisation of availability now - there's no direct manipulation of any data.  Because, almost without thinking, I made the published web app a HTML based one, it meant that I could easily add jQuery and interface niceties like the date choosing dropdown (shown above). Because all the code runs as me, and I've already authorized the code, the end user isn't presented with any awful dialogs. I make adding the booking something that the end user does, by hand themselves. You can pre-populate a Goog...