It’s been a while since I’ve made a post with a technical trick. I always doubt if people will know them and it will look like I’ve discovered garlic soup. In any case, if you already know it, just skip the post and that’s it.
This summer I have been copying a few competences from the decrees of the new curriculum to make the new version of the qViC. The decrees are published in PDF and of course, when copying and pasting them into a spreadsheet or text document, line breaks appear.
Continue reading “Removing line breaks in documents or spreadsheets”
I have just published a new feature for CoRubrics in BETA phase: checklists. Assessing with rubrics, especially co-assessing and self-assessing, is very interesting, but it is certainly complicated. It is not easy to design a good rubric and have students make it their own.
Sometimes, another assessment tool can be used, such as checklists: a list of aspects or criteria that learners should consider when performing a task, and where they should indicate whether they have achieved them or not. Here is a simple example of an excerpt from a checklist for assessing a portfolio.
Continue reading “New functionality in CoRubrics: checklists (BETA)”
With this article, I finish the trilogy on web apps with Google apps script. In the first article we saw what they were and what we could develop. In the second, we saw the process of creating a specific web app. In this third one, we will see how we can make a web app that has several html pages.
As we said in the second article, only the doGet function can return html. In fact, when the URL of the application is accessed, the doGet function is executed, which is the one that returns the html. This html usually has a button that calls another function that saves data or triggers actions. But what if we want the application to have more than one screen? How do we do it with a single doGet function?
Continue reading “Using GAS to create web applications (3rd and last part)”
We will create an application for students to fill in a KPSI (Knowledge and Prior Study Inventory) when they start a unit or project and fill it in again when they finish it. For those of you who are not familiar with the KPSI instrument, it is nothing more than a set of questions about the topic, where students do not have to give the answer, but must indicate whether they know the answer. It serves as a way to be aware of prior knowledge and to make the student aware of the progress he/she has made at the end of the test.
To make it easier to follow, in this folder you can find the final files, both the spreadsheet and the script with the code and the html files.
Continue reading “Using GAS to create web applications (Part 2)”
I have been using GAS (google apps script) for several years to automate tasks. In fact, those of you who follow the blog will know different plugins I have published for spreadsheets: CoRubrics, CLASS-MON and ImExClass. But, until now, I had rarely used the GAS option to create web applications. Some limitations that they have, had made me not dive much into it.
In this first article, I will only present what these web apps are and what they can be useful for. In a second part, we will see how to create one.
Continue reading “Using GAS to create web applications (Part 1)”