Mahara Repository Plugin
Functional Specification Revisions:
- 0.1 - 06/04/2009 - Jerome Mouneyrac - Draft Version
- not implemented (MDL-16909)
This document is a functional specification for a Mahara Repository Plugin. The Mahara Repository plugin allows users to browse a Mahara portfolio in the File Picker.
- Moodle administrator sets which Mahara peers will be available in the file picker
- Moodle Administrator needs to have "Enable SSO-IDP publish, and SSO-SP subscribe"
- Mahara Administrator needs to have "Enable SSO-IDP subscribe, and SSO-SP publish"
- Administrator can change the name and peer of a Mahara repository instance
- Administrator can add/delete a Mahara repository instance
- Administrator can add/delete a Mahara repository plugin
- A teacher cannot set a Mahara repository at the course level (except if the administrator allowed it)
- Moodle user cannot set a Mahara repository at personal level (except if the administrator allowed it)
- Only people with roles that have "Roam to a remote Moodle", moodle/site:mnetlogintoremote, will see the Mahara repository into the file picker (See Moodle Networking)
- Mahara repository display content as the Mahara user would see it in Mahara "My Files" page.
Administration: Peer Settings
In the Peer Service tab: the administrator can choose whether to activate the SSO for Repository services.
Administration: Plugin Settings
The administrator can add/delete the Mahara Repository plugin. No settings are needed at the plugin level.
Administration: Instances Settings
A Moodle administrator can add/delete/edit instances. For an instance he can set:
- Mahara Peer
When a user clicks on the Mahara repository, Mahara portfolio tree is displayed. It is exactly the same content that would be displayed if the user was displaying "My files" in Mahara.
Download a file from a Mahara repository
- User opens a file picker
- User selects a Mahara repository in the file picker
- System displays the file system of the Mahara site
- User selects a file
- - The Mahara Repository plugin is been installed and activated
- - Networking has been turned on and a Mahara peer has been set up
- - A Mahara Repository instance has been created called "Mahara" (in this example)
- - The file has been added to the html editor/parent field