Sylvia Currie

Stephanie, I think you may have fixed your head yourself, but it took a log out and log in before you could see the changes.

Let's see what happens when Rod fixes his head. :-)

Stephanie, I think you may have fixed your head yourself, but it took a log out and log in before you could see the changes.

Let's see what happens when Rod fixes his head. :-)

We've had an ongoing discussion since the beginning of this community project about what to call it. We were looking for one word, easy to remember, carries some meaning, etc.  Scope was suggested and then we began to play with what it could stand for.

SFU's community of practioners of elearning
SFU's community of practicing educators
SFU's community of practice for educators
Scholarly centre of ...

You get the idea.

Anyway, despite the fact that we couldn't find an ideal long name, the short name, Scope, has remained. It has some clever bits to it -- Liz pointed out that we could emphasize the CoP part, which has become the standard way to abbreviate Communities of Practice. Also in designing the spaces, we started to play with the words, like telescope and periscope (Thanks for noticing, Steph!)

This brings us to part 2. You may have noticed if you've logged in more than once that we are cycling through some logo examples on the main page. Jason Toal is busy behind the scenes. We'll organize a way for you to view, vote, and provide feedback on these logos so stay tuned!

Obviously we need to be sure about the name SCoPE before investing too much time in designing a logo based on that name. But both of these are basic items we need to decide to prepare for launch. So first things first:

We've had an ongoing discussion since the beginning of this community project about what to call it. We were looking for one word, easy to remember, carries some meaning, etc.  Scope was suggested and then we began to play with what it could stand for.

SFU's community of practioners of elearning
SFU's community of practicing educators
SFU's community of practice for educators
Scholarly centre of ...

You get the idea.

Anyway, despite the fact that we couldn't find an ideal long name, the short name, Scope, has remained. It has some clever bits to it -- Liz pointed out that we could emphasize the CoP part, which has become the standard way to abbreviate Communities of Practice. Also in designing the spaces, we started to play with the words, like telescope and periscope (Thanks for noticing, Steph!)

This brings us to part 2. You may have noticed if you've logged in more than once that we are cycling through some logo examples on the main page. Jason Toal is busy behind the scenes. We'll organize a way for you to view, vote, and provide feedback on these logos so stay tuned!

Obviously we need to be sure about the name SCoPE before investing too much time in designing a logo based on that name. But both of these are basic items we need to decide to prepare for launch. So first things first:

Thanks for the excellent ideas, and teh offer to update the resources from your presentation for SCoPE, Stephanie! This brings us to the best way to organize and hook into SFU resources, and other communities. I'll start thinking out loud about this, using the SCoPE - LIDC connection as an example.

Looking at the technical side of things, here are some advantages of the current SCoPE community environment:
- Resources are available to the public. You don't need to log in to access forums, documents, etc. You do need to log in to contribute to the community, manage interaction, and access tools requiring user input.
- All resources in Moodle have a fairly tidy URL (unlike some software that has mile-long URLS, or sometimes limited ability to link directly to resources)

Given these conditions, it will be easy to link directly from the LIDC website to resources generated through participation in the community. This is better than copying them from one location to another. Also, they can be accessed in context.

Working the other direction -- linking to LIDC resources -- maybe the best way to do this is according to resource type. For example, there may be resources specific to SFU that wouldn't be of general interest to SCoPE members. On the other hand, the LIDC website may have a collection of "how to" resources that would be of general interest for anyone interested in instructional design, appropriate use of multimedia, etc.

Maybe we need a special area (course, in Moodle language) that focuses on SFU work, events, resources, etc. Or I wonder if there is a way to integrate SFU interests directly with other defined areas.

Stephanie's suggestions raise bigger questions (isn't that always the way!)


How do we achieve both?
What are the implications for site design?

As you can see, we need your help in figuring this out! :-)