Powered by Twitter Tools

Powered by Twitter Tools

I could have gone on for pages on this topic (in fact, I did, for about 2000 words before cutting to around 600). That’s my way of saying there’s plenty of room for exploration and discussion, so go ahead, check it out, and leave a comment.

Powered by Twitter Tools

Kruse has also posted his paper that expands on this topic.

I’m sharing this particular post with some of our Sales team as a baby step toward understanding some of the fundamental underlying challenges of teaching with technology.

Powered by Twitter Tools

1. Install a REST client extension.

Chrome has several great extensions to this end, but so far I like Advanced Rest Client. It lets you save requests and view your history.

For Firefox the most popular REST client is intuitively named RESTClient. Same basic functionality, but with nice tabs to view the output in different ways.

2. Create a Canvas Access Token in your account profile.

The access token will provide a secure key, if you will, to Canvas with all your own unique permissions and enrollments. Most modern web services help you create these to securely talk with other systems.

Login to Canvas, click on your name, and scroll down to Approved Integrations. If you don’t already have a token, click New Access Token.

Give your token a label (purpose) and expiration date (if you want).

Copy that really long string that Canvas generates and paste it into a text document for later reference–you’ll need it to talk to Canvas via your REST client.

3. Pick an API resource or action from the Canvas documentation

Start by going to the Canvas API documentation. Browse through the Authentication page as well as the Resources, which contain all the currently possible the API actions and outputs.

I don’t have a lot of time to get into API calls and REST, but you can think of it as simply a message sent to a server with an authorization method that tells the server how to respond based on the target and the access token. In this case we’re using the GET method. The API calls will simply be HTTPS URLs with the access token appended as a variable. The URL will change based on what data in Canvas you want to access.

For example, if I want to see all of my page view data, I start with the base Canvas HTTPS URL:

I then append the location of the API resource or action:

Be sure to replace :user_id with the numeric value of the user id (or course or account id) you want to access. In this case I want my own. It’s easy to grab this from the end of the URL of my profile page (which happens to be https://canvas.instructure.com/users/123456, so my user id = 123456)

Finally, you’ll need to append your access token as the value of a variable:

So it looks something like this:

This URL is what we’ll feed our REST client in the next step.

4. Run the API through the browser REST client

Open your REST client add-on/extension and paste in the URL customized for the API action you want to perform plus the course/account/user id plus your access token.

Be sure you’re using the right method (typically GET) before clicking send.

You’ll end up with output below. I recommend looking at the JSON formatted response. This data is organized in name/value pairs, but can also contain objects, so a whole lot of data in a very simple format is possible here.

This gives you a glimpse of the possible data exchanges that Canvas makes available via its open API. Your ability to get data will depend upon your role and permissions within Canvas. Obviously student and teacher users will have far less access than admins at any sub-account level.

In real-world practice, you’ll need to know a bit more than this. But the essence is that you’d use any number of scripting languages to request the data from the Canvas API, parse it in JSON format, then do wonderful, magical things–like calculate an individual user’s course progress in order to dynamically generate a badge. Or not.

So check it out and leave a comment there if you can!

When creating a Canvas question choose either Fill in Multiple Blanks or Multiple Dropdowns. Multiple Blanks is similar to short answer, and the blanks may need to be manually assessed to provide latitude with spelling etc. Multiple Dropdowns works like matching or multiple choice.

In either of these cases you build the question and the answers in the rich text editor for the question field. Start by introducing the question, e.g. “Match the following constellation images to their names.”

Follow this by one or more images, videos–whatever.

For each of those media items type in the Canvas-standard markup for the blank/dropdown variable name, e.g. [fig1]. It looks something like this:

…where each [fig1] is for a single blank or dropdown choice. Don’t worry–this makes more sense when you’re in the editor!

Then simply use the area below the editor to show the correct answers with feedback.

Voila!

If this works for you, please share some examples.

..isn’t it a little sad that even in Second Life, an environment where almost everything is possible, universities build campuses with classrooms where their avatar students can sit at their desks, watch power point slides and listen to lectures?

This brings me back once again to Gardner Campbell‘s No Digital Facelifts stance. Read more on the Morning Blend blog