Commit 505ac3946303f361d52e4e2ebda20eea46276fef
1 parent
ce25025f
daniel's text fixes.
git-svn-id: https://kt-dms.svn.sourceforge.net/svnroot/kt-dms/trunk@4784 c91229c3-7414-0410-bfa2-8a42b809f60b
Showing
7 changed files
with
13 additions
and
10 deletions
plugins/ktcore/KTCorePlugin.php
| ... | ... | @@ -69,7 +69,7 @@ class KTCorePlugin extends KTPlugin { |
| 69 | 69 | _("Manage Groups"), _("Add or remove groups from the system."), |
| 70 | 70 | 'admin/groupManagement.php', null); |
| 71 | 71 | $this->registerAdminPage("units", 'KTUnitAdminDispatcher', "principals", |
| 72 | - _("Control Units"), _("Specify which organisation units are available."), | |
| 72 | + _("Control Units"), _("Specify which organisational units are available within the repository."), | |
| 73 | 73 | 'admin/unitManagement.php', null); |
| 74 | 74 | // disabled until it actually makes sense. |
| 75 | 75 | //$this->registerAdminPage("orgs",'KTOrgAdminDispatcher',"principals", "Control Organisations","Specify which organisations are available.", 'admin/orgManagement.php', null); |
| ... | ... | @@ -81,7 +81,7 @@ class KTCorePlugin extends KTPlugin { |
| 81 | 81 | _("Roles"), _("Create or delete roles"), |
| 82 | 82 | 'admin/roleManagement.php', null); |
| 83 | 83 | $this->registerAdminPage("conditions", 'KTConditionDispatcher', "security", |
| 84 | - _("Conditions"), | |
| 84 | + _("Dynamic Conditions"), | |
| 85 | 85 | _("Manage criteria which determine whether a user is permitted to perform a system action."), |
| 86 | 86 | 'admin/conditions.php', null); |
| 87 | 87 | ... | ... |
templates/ktcore/folder/roles_managegroups.smarty
| ... | ... | @@ -5,7 +5,7 @@ |
| 5 | 5 | {$context->oPage->requireJSResource('thirdpartyjs/MochiKit/Iter.js')} |
| 6 | 6 | {$context->oPage->requireJSResource('thirdpartyjs/MochiKit/DOM.js')} |
| 7 | 7 | |
| 8 | -<p class="descriptiveText"><strong>FIXME</strong> help text for role-editing. </p> | |
| 8 | +<p class="descriptiveText">{i18n}Groups must be allocated to roles to ensure that the workflow transition this role is supposed to support can be acted upon by a user.{/i18n}</p> | |
| 9 | 9 | |
| 10 | 10 | <form action="{$smarty.server.PHP_SELF}" method="POST" id="grouproleform"> |
| 11 | 11 | <input type="hidden" name="action" value="setRoleGroups" /> | ... | ... |
templates/ktcore/manage_permissions.smarty
| 1 | 1 | <h2>{i18n}Existing permissions{/i18n}</h2> |
| 2 | 2 | |
| 3 | -<p class="descriptiveText"><strong>FIXME</strong> add a useful explanation about permissions.</p> | |
| 3 | +<p class="descriptiveText">{i18n}Permissions are descriptors used to ascertain whether groups of users have access to certain functionality. The built-in permissions below facilitate the default functionality of the DMS and can't be changed. Plugin developers may choose to add additional permissions below that manage access to their plugins functionality.{/i18n}</p> | |
| 4 | 4 | |
| 5 | 5 | <form method="POST" action="{$smarty.server.PHP_SELF}"> |
| 6 | 6 | <fieldset> | ... | ... |
templates/ktcore/principals/roleadmin.smarty
| 1 | 1 | <h2>{i18n}Role Administration{/i18n}</h2> |
| 2 | 2 | |
| 3 | -<p class="descriptiveText"><strong>FIXME</strong> Overview of roles.</p> | |
| 3 | +<p class="descriptiveText">{i18n}Workflow actions may be assigned to certain roles within the DMS. User groups are allocated to roles on a per-directory basis and are inherited from the root folder of the DMS. Roles may for example include "Document Creator", "Document Reviewer", "Document Publisher".{/i18n}</p> | |
| 4 | 4 | |
| 5 | 5 | {if ($for_edit === false)} |
| 6 | 6 | ... | ... |
templates/ktcore/principals/unitadmin.smarty
| ... | ... | @@ -4,9 +4,9 @@ |
| 4 | 4 | |
| 5 | 5 | <fieldset> |
| 6 | 6 | <legend>Add New Unit</legend> |
| 7 | -<p class="descriptiveText">{i18n}Units allow you to delegate a portion | |
| 8 | -of the document management system to a particular part of your | |
| 9 | -organisation. Unit administrators have additional right within that | |
| 7 | +<p class="descriptiveText">{i18n}Units allow you to delegate the administration of a portion | |
| 8 | +of the DMS repository to a particular part of your | |
| 9 | +organisation. Unit administrators have additional rights within that | |
| 10 | 10 | portion of the document management system, and they can also adjust the |
| 11 | 11 | membership of groups that belong to the unit.{/i18n}</p> |
| 12 | 12 | <p><a href="{addQS}action=addGroup{/addQS}" class="ktAction ktAddGroup ktInline">Add Unit</a><a href="{addQS}action=addUnit{/addQS}">Add a new unit</a>.</p> | ... | ... |
templates/ktcore/principals/useradmin.smarty
| ... | ... | @@ -21,7 +21,7 @@ href="{addQS}action=addUser{/addQS}">{i18n}Add a new user{/i18n}</a></p> |
| 21 | 21 | <p class="descriptiveText">{i18n}Since there may be many users in the system, please |
| 22 | 22 | select a group from the list below, or type a few letters from the person's username |
| 23 | 23 | to begin. Alternatively, <a href="{addQS}show_all=1{/addQS}">view all users</a> (note that this may be |
| 24 | -very slow if you have many users.{/i18n}</p> | |
| 24 | +very slow if you have many users).{/i18n}</p> | |
| 25 | 25 | |
| 26 | 26 | {foreach item=oWidget from=$search_fields} |
| 27 | 27 | {$oWidget->render()} | ... | ... |
templates/ktcore/search/administration/conditions.smarty
| 1 | -<h2>{i18n}Conditions{/i18n}</h2> | |
| 1 | +<h2>{i18n}Dynamic Conditions{/i18n}</h2> | |
| 2 | + | |
| 3 | +<p class="descriptiveText">{i18n}Dynamic Conditions give the administrator the cability to define what permissions are applied to document within a folder based on a set of rules. These rules may be applied to the document's metadata, contents, or transactional information. Dynamic Conditions are applied on a per folder basis and may be setup from the folder's permissions section.{/i18n}</p> | |
| 4 | + | |
| 2 | 5 | |
| 3 | 6 | <h3>{i18n}Create a new condition{/i18n}</h3> |
| 4 | 7 | <form action="{$smarty.server.PHP_SELF}" method="POST"> | ... | ... |