Translations by Jong-Dae Park

Artefact: Blog address

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Network servers</h1> <p>Click on a link in this list to be automatically logged on at the other website.</p> <p>If you log off at the other site, your session here will also end.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>LDAP field for surname</h1> <p>Enter the name of the field in the LDAP record that contains the person's last name.</p>

Reset ALL indexes

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Contexts</h1> <p>List of contexts where accounts are located. Separate different contexts with ';', e.g. 'ou=users,o=org;ou=other,o=org'.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Name</h1> <p>A name to identify your system to the remote site.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Password</h1> <p>The password for the 'Distinguished name'.</p>

Number of institutions

In queue

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Update account information on login</h1> <p>Enable this option to bring over account data from the remote site on login and update your account record with any changes.</p>

Confirm

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Group attribute</h1> <p>Which LDAP attribute maps to a group's name (often "cn").</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Group member attribute</h1> <p>Which LDAP attribute the group's members are stored in (often "uniqueMember").</p>

Number of wall posts

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Wrong login message</h1> <p>When people are only able to log in via Moodle and cannot use the standard login form.</p> <p>Enter a message to show to people who try to log in via the standard login form. This message should contain instructions on how they can gain access to Mahara through Moodle.</p> <p><strong>Note</strong>: The message is displayed right above the login form in the sidebar. Therefore, do not make it too long.</p>

Cancel

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Sync groups automatically via cron job</h1> <p>Enable this setting to activate a task in the cron which will automatically create and/or update groups and their membership based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line scripts supplied in htdocs/auth/ldap/cli/ if you wish to schedule it to run at other times or with other settings.</p> <p><strong>Note:</strong> You'll also need to activate the "Sync groups stored as LDAP objects" and/or "Sync groups stored as user attributes" settings in order for groups to be synced.</p> <p>Group members can be removed as well as added by this setting. If a group is no longer found in the LDAP records, all of its members will be removed from the group.</p> <p>This setting will have no effect if the cron is not running. See the <a href="https://wiki.mahara.org/wiki/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Application</h1> <p>The application that is running at the remote site that you want to communicate with.</p>

Number of groups

Copy this portfolio

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Process nested groups</h1> <p>Enable this option if your groups can contain other groups as members. If enabled, the sync process will recursively include the members of these nested groups into the parent group. It will safely cease recursing if it detects a circular reference.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>SAML metadata for the Identity Provider (IdP) to connect to</h1> <p>This element requires the XML formatted metadata for the IdP that you want to connect to.</p> <p>If you add a new IdP, please select "Add new Identity Provider" from "Available Identity Providers" and add in the relevant metadata to the "Institution Identity Provider SAML metadata" field.</p> <p>Otherwise, select an existing IdP from "Available Identity Providers". If you make any changes to the metadata, it will be updated for the other institutions using that metadata as well. Therefore, be careful what you change.</p>

Artefact: Career goals

Edit access

Manage access

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>SAML 2.0 field for email</h1> <p>Enter the name of the attribute passed by the Identity Provider (IdP) that contains the person's email address.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Member attribute is a DN</h1> <p>Enable this setting if each entry in the "Group member attribute" field is a Distinguished Name. Disable this setting if each entry in "Group member attribute" field is a username only.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Sync groups in these contexts only</h1> <p>List of contexts where groups are located. Separate different contexts with ';'. (e.g., 'ou=groups,o=org;ou=other,o=org').</p> <p>If this field is left empty, the group sync cron will fall back to using the same list of contexts as the "Contexts" setting for where accounts are located.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Update account information on login</h1> <p>Enable this option to update a person's first and last name profile fields from the LDAP server when they log in.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>If an account is no longer present in LDAP</h1> <p>This setting determines what the cron will do if a person in your institution has no matching record in your LDAP server.</p> <p><strong>Note:</strong> This setting only applies to people who have this authentication instance as their authentication method.</p> <dl> <dt>Do nothing</dt> <dd>No action will be taken. (This is the recommended setting.)</dd> <dt>Suspend account</dt> <dd>The account will be suspended. The account holder will no longer be able to log in, and their content and portfolios will not be viewable. However, none of their data will be deleted, and the person can be un-suspended by the cron when their LDAP record reappears, or manually by an administrator.</dd> <dt>Delete account and all content</dt> <dd><strong>Use with caution!</strong> The account will be deleted along with all the content and portfolios held within it. The data is fully deleted from the server. If anything from this account is still needed, a full backup of the instance is needed to retrieve the account.</dd> </dl>

Number of forum posts

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>User attribute</h1> <p>The attribute used to search for people. It is often 'cn'.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Additional LDAP filter for sync</h1> <p>Provide an LDAP filter here, and the sync will only see accounts in LDAP that match this filter.</p> <p>Use this setting with caution if you have auto-suspend or auto-delete enabled, as doing so will cause all accounts in your institution which <strong>do not</strong> match the filter to be suspended or deleted.</p> <p>Example: uid=user*</p>

Artefact: Business phone

Artefact: Academic goals

Artefact: Work skills

Artefact: City/region

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Only these group names</h1> <p>When creating groups based on user attributes, only create groups with these names. This will not affect groups created via the "Sync groups stored as LDAP objects" setting, if it is active.<p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Remote account</h1> <p>Match the user attribute value to the remote username field assigned to a given account (not the real Mahara username).</p>

Artefact: Certifications, accreditations and awards

Artefact: Video file

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Group class</h1> <p>The LDAP objectclass that groups are expected to have.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Sync accounts automatically via cron job</h1> <p>Enable this setting to activate a task in the cron which will automatically create and/or update accounts based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line script supplied at htdocs/auth/ldap/cli/sync_users.php if you wish to schedule it to run at other times or with other settings.</p> <p>This setting will have no effect if the cron is not running. See the <a href="https://wiki.mahara.org/wiki/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Sync groups stored as user attributes</h1> <p>Enable this option if each LDAP user record has an attribute which indicates a group the person should be in. This setting will cause the LDAP sync cron to create a group for each unique value in the specified user attribute (or in those listed in the "Acceptable group names" field) and place each person in the appropriate group (or groups, if they have multiple values for the attribute).</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Distinguished name</h1> <p>If you want to use bind-user to search people, specify it here. Something like 'cn=ldapuser,ou=public,o=org'. Leave this blank for anonymous bind</p>

Artefact: Postal address

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Plans</h1> <p>Plans are task lists. They are particularly well-suited to plan medium and long-term endeavours. A plan can consist of a number of individual activities with which completion dates are associated.</p> <p>You could use the functionality to:</p> <ul> <li>set yourself individual goals for a large task.</li> <li>manage your personal learning activities and keep an eye on how many you have already accomplished during the time frame that you have set yourself.</li> <li>keep track of workshops you have attended for your professional development over time.</li> </ul> <p>You can set up template plans in your personal account. You can then use them when you want to create plans for groups of learners in multiple groups.</p> <p>Learners can copy plans that contain assignments into their own accounts to complete these assignments.</p>

Artefact: Journal entry

Artefact: Books and publications

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h1>Host URL</h1> <p>Specify hosts in URL form, e.g. <em>ldap://ldap.example.com</em>. Separate multiple servers with <em>;</em> for failover support.</p>