As site administrator you have three experimental features available to you:
You cannot access these features from any navigation, but you must type the URL directly in the case of the bulk options or set up a config.php variable.
Warning
The export and import of portfolios uses quite a lot of computing power. Therefore, these bulk options require even more memory. Please try them first out on a test installation or export / import only a small number of users instead of an entire institution at once.
[your regular Mahara URL]/admin/users/bulkexport.php
If you need to export the portfolios of multiple users at once, you can do so from the bulk export page. Please remember that this is an experimental feature at the moment.
Experimental feature: Bulk export
Note
You can look up the usernames on the user search page or if you exported a CSV file of users, you have the usernames in there as well.
[your regular Mahara URL]/admin/users/bulkimport.php
If you need to import the portfolios of multiple users at once, you can do so from the bulk import page. Please remember that this is an experimental feature at the moment. You must have Leap2A files to import. The import of HTML files is not possible.
The easiest option to import user portfolios in bulk is to use the bulk export file as all information is contained therein. If that is not possible, you can create the necessary ZIP file manually.
Experimental feature: Bulk import
Ideally, you have exported the users you wish to import using the bulk export functionality on the other Mahara instance. Then the bulk export file already contains all necessary files and mappings.
Note
Before importing these new user accounts, you can change the usernames for these new accounts in the usernames.csv file that is included in the bulk export file.
If you want to import user portfolios into one institution using their Leap2A files that you did not receive via the bulk export functionality, you can still import them in bulk.
Note
The CSV file usernames.csv should look like this and does not have a header row:
usersuniquebyusername is a config.php setting that should be used with extreme caution as it could be misused.
Below is the documentation that can be found in the code. This feature is discussed for example in the discussion topics Mahara Moodle integration and bug? and SSO: Mahara to Moodle.
Note
When turned on, this setting means that it does not matter which other application the user SSOs from, they will be given the same account in Mahara.
This setting is one that has security implications unless only turned on by people who know what they are doing. In particular, every system linked to Mahara should be making sure that same username == same person. This happens for example if two Moodles are using the same LDAP server for authentication.
If this setting is on, it must NOT be possible to self register on the site for ANY institution - otherwise users could simply pick usernames of people’s accounts they wished to steal. That is why you should not see the registration check boxes in any institution if you have this feature turned on.