Sunday, September 20, 2015

Dipping a toe into Schoology

Back in the late 1990s, I was keen to establish a presence on the nascent World Wide Web. I created pages with Adobe's PageMill in hopes of creating in a WYSIWYG environment rather than get bogged down in the intricacies of HyperText Markup Language (HTML).

By 2000, I was creating and posting Portable Document Format (PDF) files of my curriculum materials. That process is intertwined with meeting and befriending Paul G. Hewitt. It was in the early 2000s that I registered the domain name. In 2006, I started The Blog of Phyz.

In the late 2000s, my school district began providing a website generation service (SchoolWorld). I already had a relative "palace" on the web. By comparison, the district's service allowed teachers to create quaint cottages. I wasn't interested.

The district has discontinued its relationship with SchoolWorld in favor of a new relationship with SchoolWires. It also has an enterprise account with Schoology.

I'm exploring the utility and capabilities of Schoology. I use it primarily as an organizational tool for the curriculum in my courses. It seems useful in that regard. But nothing's as useful as the palace I've built at

One bright spot is the fact that tests created with ExamView can be exported to Blackboard format. Tests in Blackboard format can be imported by Schoology at online tests. Schoology can be configured in terms of test administration and the results are posted in class roster lists. Pretty slick! (It would be nice if ExamView showed any signs of life since 2012.}

In a way, it appears the logistics of Schoology make it possible to violate copyright law without interference or consequence. Only students and parents of students enrolled in courses can see the Schoology pages (and links and materials) associated with the course. So the violations are small-scale, I suppose.

Anyway, we'll see how it all goes. 

We could be evolving from an era of world-wide curriculum sharing on the web to closing back in ourselves. We shall see.

No comments: