Forum Replies Created
-
Posts
-
New in OLab4, we now have Role-Based Node Access.
See https://olab.ca/role-based-node-access-in-olab4/This is a much more powerful way of controlling who can access which Nodes in a map.
We have improved the security levels in OpenLabyrinth in order to make it easier to manage and direct Turk Talk and other Scenarios. We now have the user level of Director.
A Director can:
1. Create, edit and manage Scenarios
2. Monitor the progress of users within a Scenario, including the Turker or facilitator role.
3. Create and edit their own casesWe have found that using a simple app called Auto Text Expander is helpful to facilitators, who are trying to keep up with the conversation flows.
We have more information on how to do this here: http://openlabyrinth.ca/keyboard-macros-for-openlabyrinth/
If you are feeling really ambitious, you can even connect OpenLabyrinth to a MOOC. The team lead by Andrzej Kononowicz at the Karolinksa Insitute has done some very nice integration within the edX MOOC, where they were supporting a very large number of concurrent users.
We have also been able to set up LTI connections with Moodle and other applications. It can be a bit quirky getting the various user levels set correctly. While IMS-LTI is a widely adopted protocol, how each vendor implements it can be frustratingly different. It is not quite as standard as we would like.
We now can use H5P widgets directly within OpenLabyrinth.
These also have the ability to report user activity metrics to an LRS, using xAPI.
We have also now incorporated H5P widgets (H5p.org) into OpenLabyrinth.
This greatly extends the range of input interfaces available, with some neatly crafted HTML5 interactivity. Some of these H5P widgets can report activity using xAPI to an LRS.
Widgets can also be shared with a WordPress or Moodle site.
We now have a more detailed posting about Dandelions here: http://openlabyrinth.ca/what-the-heck-is-a-dandelion-in-openlabyrinth/
We just found out today the default video that we were using to demonstrate our video mashup tool, the Beatles Twist and Shout clip, has been withdrawn for copyright reasons.
Kinda surprising on a scrappy black and white 50 year old clip. Oh well.
Accordingly, we have changed the links in our database to point to one of our own internal videos, where copyright is not an issue. Creative Commons licensed and all that.
For some others who used the default video and applied annotations and timing points, these will not make sense in the new video. Sorry about that. But we thought that this was better than linking to a dead clip.
If this causes problems with your existing mashups, please let us know.
I have some further suggestions from Yusuf, for which I am very grateful, where he figured out some problems that lay in his .htaccess file. I am reposting his note here because others may run into this:
—————–I have done some debugging on home.php on line 60
public function action_loginOAuthCallback()
With the issue #104 I have confirmed it is a htacess issue. So I have changed my htacess file as
Options +FollowSymLinks Turn on URL rewriting RewriteEngine On Protect hidden files from being viewed Order Deny,Allow Deny From All # Redirect Trailing Slashes... RewriteRule ^(.*)/$ /$1 [L,R=301] Allow any files or directories that exist to be displayed directly RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^ index.php [L]With this htacess, I was able to login with Twitter, Facebook and Google+ So I suggest to change htacess file as this.
————We are interested in hearing from new authors, especially if you get stuck with any particular aspect in case writing.
Tell us the sticking points. Tell us what should be made easier.
You can either do this here in the Forums. Or you can send us suggestions using this request form.
Prompted by a question from Yusuf, I have been exploring again how to set up OAuth authentication on your OLab server.
I am pleased to say that the process still works just fine for Facebook and Twitter logins, with only tiny changes in the steps needed, which are self-evident.
It is not so easy for Google+ logins. There are more steps needed now, and I seem to have run into a wee loop of steps where I can go no further. Happy to discuss this further with other groups who are trying to do this.
We also have some additional Teaching Tips here on how to use Turk Talk.
