Transitioning between IP to free up content
iFramed LRR resource in Mediawiki with DET authentication.
Video: Transitioning between IP to free up content
The video demonstrates how to embed content from the Learning Reference Repository (LRR) into the resource mediawiki. The LRR requires a DET username and password and the resources contained within are under a variety of IP conditions. CLI is working on LRR functionality whereby authenticated users will be automatically able to view the LRR resources stored on the CLI server within resource mediawiki pages. There is ALOT of really good existing stuff with new resources streaming in everyday. The authentication to view frees up the LRR content to be used within the resource mediawiki within the IP constraints. It would be really good if Institutes could work together to get the best stuff embedded and categorised within the resource mediawiki pages esp toolboxes. David Gilchrist has recommended re-categorising content under Industry Qualifications which I think is a good idea.
Calling all open mediawiki champions! A tabula rasa site has been set up at http://openwiki.illawarra.det.win with a view to developing an open resource Mediawiki proof of concept model. Put your visions into a blog post. The design aim is to come up with a solution whereby an open Mediawiki sister site can be accomodated with an DET authenticated resource Mediawiki. Make it work!!!!!
Comments
3 Responses to “Transitioning between IP to free up content”
Leave a Reply
-
Subscribe
·
The idea of “letting the system” handle who can see what makes sense. A wiki could then have both types and the DET authenticated users gets the extra stuff their account allows.
This might allow layers of content sharing.
The wiki content would be accessible to “the public” at what ever level was intended by the deliverer, but value added content to authenticated users.
I have been using I frame to embed LRR content into our Moodle platform which can be a considerable server space saving exercise besides allow for a centrally located asset that can be shared across more courses with out “update/version” pain.
Of course you can I frame just about any web content seamlessly (from the users point of view) into learning environments.
Having a shared Wikimedia space populated by embedded LRR content can be a time saving method of not duplicating the same learning materials.
Steven
I think this approach is looking very promising. It makes a lot of sense to be pointing to resources hosted through a repository, rather than downloading and installing many copies into many Wikis or Moodles. This holds true no matter what repository solution TAFE pursues at a state-wide level (eg. Equella, LRR, etc.)
CLI is looking into making changes to the existing Learning Reference Repository (LRR) to make resources accessible outside the DET network. The process you show in the video currently works only from a computer within the DET network. For home and work access, the LRR resource links will be modified to allow for single-sign-on through remote authentication – details need to be worked out but the project is underway. The solution will probably mirror the approach that TaLe has taken to authentication.
One of the key issues for me is metadata – how do you describe a resource so it can be found again? Comments from both you and David about how to organise the resource mediawiki pages point to the care that needs to be taken in categorising and how you set up storage, discovery or delivery systems. I don’t have a definitive answer but point out that for something like a federated search to work it may need to comply with metadata standards such as DET LRM. It may also need to include information such as; Units of Competency, RAM categories, industry areas, AQF levels, publisher, author, and publication date and importantly a thorough approach to keyword tagging. These are suggestions and I welcome further comment.
I am a little wary of commenting too much more on the shape that a resource mediawiki might take especially since I am not a front-line teacher. It would be great to hear more feedback on how these ideas would take shape and assist teachers with their students.
Rory
“Letting the systems” handle who sees is the way it’s going, Equella and the LRR being the two emergent systems to handle IP management.
Using LRR records to transition between different types of IP when linking to resources.pdf
I’ve put together this recommendation for how I would like the LRR and Equella to work in that the user can choose between public, private and public authenticated when they upload a resource. This puts the open/ closed issue in the hands of the end user and free’s up all types of content . Perhaps as the culture develops the public option will emerge as the prefered choice of teachers. Not there yet.
The big issue in my mind to the success of mediawiki is to enable repository objects to be uploadable, searchable and linkable from within Mediawiki itself, Equella can supposably integrate with Mediawiki. As the Resource and Open Mediawiki trial progresses it would be good to scope LRR integration. Rory, Grant?
PS. Just had a look at Moodle 2.0 last night, BIG changes in the upgrade with lots of cool new functionality in particular Moodle will be able to integrate with Mediawiki as a repository out of the box which will make use of Moodle and Mediawiki together more seamless.