Last Updated: 2020-04-17

Recent events have made it increasingly necessary for teachers of all types to shift towards virtual classrooms. This shift is challenging everyone to rapidly develop new skills and workflows for successfully teaching others. Fluid Numerics actively engages in teaching and tutoring and is ready to offer some of our tools, at no charge, to other teachers and educators.

Virtual Teaching/Tutoring Toolkit

Many of our tools are built around GSuite. GSuite is a suite of professional cloud-native tools such as Gmail, Google Meet, Calendar, Sheets, and more.

Google Meet is a secure video meeting service that is included with GSuite and GSuite for Education accounts. For teaching and tutoring, Meet gives you the ability to virtually connect with your students and other teachers.

Google Calendar is a calendar service from Google that you can use to schedule events for your classes and tutoring sessions. When you create calendar events and invite other people to join you, Google Calendar will automatically associate that event with a Google Meet session.

Google Sheets provides you with durable spreadsheets that are stored in your Google Drive. Fluid Numerics has developed a solution that allow you to manage your classes, create Calendar events with Meet sessions, and automatically log attendance records.

Data Studio is a service that allows you to connect a variety of data sources and enables you to rapidly create reports and visualize data with a variety of charts, graphs, and tables.

The Fluid Class Manager are based in a Google Sheet template that you can use to control your teaching schedule. In the main Setup worksheet, you provide a calendar name, class name, teacher e-mail address, description, student e-mail addresses, and scheduling details. By changing the class status to Create, the Calendar events and Google Meet sessions are created for you and the class status is automatically updated to Active once this is done.

This sheet also comes with Apps Scripts that you can use to update attendance records that are stored in a Logs worksheet. You can automate attendance tracking with time-driven triggers that execute these scripts daily. After an initial configuration, you can focus solely on teaching!

Fluid Numerics has also created a Data Studio Template that enables you to visualize attendance records to help you quickly gain an understanding of your students' attendance behaviors. This template includes a bulk summary of the number of hours each student has participated in your classes along with a time series chart that shows historical participation behavior. The quick filters embedded in this report allow you to quickly narrow in on date ranges, subsets of students, and classes.

What you will build

In this codelab, you will create and configure your Fluidyou will set up the triggers that automate your class management and attendance logging workflow, connect your attendance logs to the data studio report, and learn how to create and delete virtual classes.

What you will learn

In this codelab, you will learn how to install and test hip-fortran.

What you will need

In this section of the codelab you will create your first Fluid Class Manager Sheet, configure the triggers that create your Calendar events and Meet sessions, and configure the time-driven trigger to automatically record class attendance.

Getting Started

  1. Open the Fluid Class Manager Sheet Template
  2. Make a copy of this template into your own Google Drive by selecting File > Make a Copy. When you make the copy, be sure to give the sheet a meaningful name.
  3. Open the Apps Scripts editor by selecting Tools > Script editor. This opens the Apps Script project that is attached to your Google Sheet.
  4. Rename the Apps Script project by selecting the name Fluid Class Manager in the top left corner. We recommend that you give the Apps Script project the same name as the Google Sheet.

Create the Calendar Event Creation Triggers

  1. From the Apps Scripts editor, open the project triggers by selecting Edit > Current project's triggers.
  2. Select +Create New Trigger.
  3. Under "Choose which function to run", set the function to onSetupEdit.
  4. Under "Select event type", set the event type to On edit.
  5. Leave all of the other parameters as their default and click Save.

Create the time-driven trigger for attendance logging

  1. From the Project Triggers page, select +Create New Trigger.
  2. Under "Choose which function to run", set the function to postData.
  3. Under "Select event source", set the event source to Time-driven.
  4. Under "Select type of time based trigger", set the time based trigger type to Day timer
  5. (Optional) Under "Select time of day", set the time for the trigger to run.
  6. Leave all of the other parameters as their default and click Save.

At this point, you have created the necessary triggers to automate class management and attendance logging. You can now close the Project Triggers page and Apps Script Editor and go back to the Fluid Class Manager Google Sheet.

In this section of the Codelab you will learn about the three worksheets included in the Fluid Class Manager Google Sheet and will create your first class. Additionally, we will introduce you to a workflow for making updates to classes.

About the Fluid Class Manager Worksheets

The Fluid Class Manager Google Sheet has three worksheets

  1. Setup
  2. Config
  3. Logs

Setup Worksheet

The Setup worksheet is where you will define your classes and control the creation and deletion of Calendar events and classes.

Columns A-I are used to define the parameters for your classes.

Config Worksheet

The Config worksheet holds information that is necessary for the attendance logger to operate. Specifically, the Config worksheet maps each calendar name and class name to a Calendar ID and Calendar Event Series ID.

Logs Worksheet

The Logs worksheet holds all of the Google Meet attendance records for meetings that are associated with any of your classes. When we build the Data Studio attendance report, we will connect to this worksheet.

Create your first class

  1. Modify Columns A-I in Row 2 to define your first class.
  2. Set the Status in to Create using the dropdown menu in Column J. This will trigger the creation of the Calendar Event Series and Google Meet sessions for this class. Once these have been created, the field will automatically be updated to Active, and the Config worksheet will be updated.
  3. Navigate to the Config worksheet and verify that your Calendar Name and Class Name are present along with the corresponding Calendar ID and Event ID.
  4. Open and verify that your Calendar has been created and the Events appear on your calendar.

Update a class

If you need to make changes to a class, you will need to delete the associated Calendar Event Series, make your changes in the Setup worksheet, and Create the class again. Here, we will walk through the deletion process.

  1. To delete the Calendar Event Series associated with a class, navigate to the Setup worksheet.
  2. Change the Status in column J to Delete Events.
  3. Once the Calendar Event Series are deleted and the Status is returned to Draft, navigate to the Config sheet and verify the class is no longer present.
  4. Open and verify that your Calendar Events for this class are no longer present.
  5. Make the necessary edits to your class in the Setup worksheet.
  6. Change the Status in column J to Create.
  7. Once the Status is returned to Active, verify these actions by inspecting the Config sheet and your Google Calendar.

At this point you should have at least one Active class and a Calendar Event Series equipped with Google Meet sessions. Feel free to create additional classes as needed in your Setup worksheet. When you are ready, continue to the next section to learn how to connect your Logs worksheet to Data Studio.

In this section of the codelab, we will make a copy of the Data Studio Attendance Report template and connect the Logs worksheet from your Fluid Class Manager Google Sheet. If you just created your classes and have not held any meetings, you will not have data for your classes; this is ok. We have included sample data in the Logs spreadsheet that will allow you set up the Data Studio connection.

Getting Started

To set up your own Attendance Records report, you will need to make a copy of the provided template and set up the data connection to your Fluid Class Manager Google Sheet.

  1. Open the Attendance Records Data Studio template.
  2. In the top right portion of the Data Studio panel, click the icon to make a copy of the report.
  1. In the Copy this report dialogue, click on the drop-down menu under New Data Source and select Create New Data Source.
  2. Select the Google Sheets connector and Authorize the connection to Google Sheets.
  3. Click on the name of your Google Sheet in the Spreadsheet column and then click on Logs in the worksheet column.
  4. Click Connect in the top right corner of the Data Studio panel.
  5. Change the data-type for the Duration to Numeric > Duration (sec).
  6. Click Add to Report in the top right corner of the Data Studio panel.
  7. Click Copy Report.

At this point, you now have a Data Studio Report that is connected to your Fluid Class Manager Google Sheet. In the Share menu, you can download snapshots of the report, schedule email delivery, and obtain links for embedding the report in a website.

As you teach through Google Meet, the Logs will automatically be recorded and the Attendance Records Data Studio report will automatically be updated.

In this codelab you automated attendance tracking and reporting for your virtual classes. You now have a Google Sheet that provides you with a way to organize your teaching schedule and automatically generates an auditable record of your and your students' time spent in your virtual classroom. You also connected this sheet to Data studio to help you quickly understand attendance behaviors for your students across all of your classes.

Let us know how we did

Submit your feedback and request new codelabs

Additional Codelabs

Hang tight! We've got more on the way!

Reference docs