11.11. Experimentelle Funktionen

As site administrator you have the following experimental features available to you:

  • Export mehrerer Leap2A-Dateien

  • Import mehrerer Leap2A-Dateien

  • PDF export

  • usersuniquebyusername Variable

Sie können diese Funktionen nicht von jeder Navigationsebene aufrufen. Geben Sie die URL für Bulk-Aktionen direkt ein oder hinterlegen Sie eine config.php-Variable.

Warnung

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 accounts instead of an entire institution at once.

11.11.1. Bulk export of accounts

[Ihre normale Mahara URL]/admin/users/bulkexport.php

If you need to export the portfolios of multiple accounts 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

Experimentale Funktion: Bulk-Export

  1. new in Mahara 20.04 Choose an export format: Select in which format you want to export accounts. Per default, HTML and Leap2A are available. If you enabled PDF export, you will see that as an option as well.

  2. Institution: Choose the institution from the drop-down menu for which you want to export all accounts.

  3. Usernames to export: Alternatively, choose this option if you only wish to export some people’s accounts. Each username must be on a separate line.

  4. Click the Export accounts button to start the export process. This might take a while.

Bemerkung

You can look up the usernames on the people search page or if you exported a CSV file of account holders, you have the usernames in there as well.

11.11.2. Import accounts from Leap2A files

[Ihre reguläre Mahara URL]/admin/users/bulkimport.php

If you need to import the portfolios of multiple people 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 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.

11.11.2.1. Import mehrere Portfolios unter Verwendung einer Exportdatei.

Experimental feature: Bulk import

Experimentale Funktion: Bulk-Import

Ideally, you have exported the account data 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.

Bemerkung

Before importing these new accounts, you can change the usernames for these new accounts in the usernames.csv file that is included in the bulk export file.

  1. Institution: Choose the institution in which the accounts shall be created.

  2. Bulk export file: Choose the bulk export ZIP file which contains all accounts that shall be created. A new account will be created for each of them.

  3. Email people about their account: Check this option if people shall receive an email about their new account. This is especially important if they do not know that their account has been moved or if you want to change their username. Don’t use this option if you want to use an external authentication method for their account. They would be emailed their internal Mahara account details but then not be able to use them.

  4. Klicken Sie auf den Import-Button, um den Prozess zu starten. Haben Sie dabei Geduld, denn der Import braucht längere Zeit.

11.11.2.2. Komplett neuer Import

If you want to import 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.

  1. Erstellen Sie einen Ordner, z.B. mahara-bulk-import.

  2. Erstellen Sie eine CSV Datei usernames.csv im Ordner mahara-bulk-import.

  3. Create a line for each account that you are importing that contains the username and the name of the ZIP file that contains the corresponding Leap2A file.

  4. Erstellen Sie darin einen Unterordner users. Verwenden Sie keine andere Bezeichnung

  5. Kopieren Sie alle Leap2A-Dateien, die Sie in eine Institution importieren wollen, in den Unterordner users. Prüfen Sie, ob es zu jeder ZIP-Datei einen passenden Eintrag in der Datei usernames.csv gibt.

  6. Create a ZIP file from the folder mahara-bulk-import once you have all accounts in it.

  7. Rufen Sie im Browser [Ihre Mahara URL]/admin/users/bulkimport.php auf.

  8. Institution: Choose the institution in which the accounts shall be created.

  9. Bulk export file: Choose the bulk export ZIP file which contains all accounts that shall be created. A new account will be created for each of them.

  10. Email people about their account: Check this option if people shall receive an email about their new account. This is especially important if you change their username and if they do not know that their account has been moved.

  11. Klicken Sie auf den Import-Button, um den Prozess zu starten. Haben Sie dabei Geduld, denn der Import braucht längere Zeit.

Bemerkung

Die CSV-Datei usernames.csv sollte wie die folgende aussehen. Sie erhält keine Kopfzeile:

"petra","mahara-export-leap-user4-1334451885.zip"
"polly","mahara-export-leap-user5-1334451888.zip"

11.11.3. new in Mahara 20.04 PDF export

Siehe auch

See the config.php section on the PDF export for more information.

11.11.4. usersuniquebyusername Variable

usersuniquebyusername is a config.php setting that should be used with extreme caution as it could be misused.

Unten sehen Sie die Dokumentation, die Sie im Programmcode finden. Dieses Feature wird in den Foreneinträgen Mahara Moodle integration and bug? und SSO: Mahara to Moodle diskutiert.

Bemerkung

When turned on, this setting means that it does not matter which other application the person SSOs from. They will be given the same account in Mahara.

Die Einstellung hat sicherheitsrelevante Auswirkungen und sollte nur von Personen zum Einsatz gebracht werden, die sich der Konsequenzen bewusst sind. Insbesondere gilt gleicher Nutzername = gleiche Person. Wenn Nutzer per SSO von verschiedenen Systemen auf Mahara zugreifen und den gleichen Nutzernamen haben werden sie in Mahara dem gleichen Account zugeordnet. Dies ist sinnvoll wenn z.B. mehrere Moodle-Systeme per SSO auf Mahara zugreifen und über das gleiche LDAP-System verwaltet werden.

If this setting is on, it must NOT be possible to self register on the site for ANY institution - otherwise account holders could simply pick usernames of people’s accounts they wished to steal. That is why you should not see the registration checkboxes in any institution if you have this feature turned on.