FIELD NAME |
DESCRIPTION |
||
Base Table |
the database table from which a security view is created. |
||
Basic Menu |
see System Menu |
||
Calendar Category Restriction |
defines the access of a user to data related to specific calendar categories. A user must first have been assigned a role which permits access to calendar category related data. If the role has been assigned the restriction object for calendar category restriction, the user will be restricted to data related to those calendar categories recorded as their calendar category restrictions. For example, a user with calendar category restrictions of TEACHING and EXAM would be able to view data associated with all calendar categories but would only be able to modify calendar category related data belonging to TEACHING and EXAM categories. Access can be further refined by selecting the Update, Insert and/or Delete checkboxes for each recorded calendar category. The user's ability to modify data would then be confined to the selected functions (Update, Insert etc.) for the calendar category. If no calendar category restrictions are defined, the user will have no restrictions and will be able to access all calendar categories. |
||
DBA |
database administrator - a computing professional who manages the complete operation of a database management system. |
||
Grant |
grants are a mechanism used to give users privileges to work with system objects and data. |
||
Object |
a logical structure defined within the Oracle database. An object has a name, a standard representation and a standard collection of operations that affect it. Tables, views and procedures are objects. |
||
Organisational Unit Restriction |
defines the access of a user to data related to specific organisational units. A user must first have been assigned a role which permits access to organisational unit related data. If the role has been assigned the restriction object for organisational unit restriction then the user will be restricted to data related to those organisational units recorded as their organisational unit restrictions. For example, a user with an organisational unit restriction of Faculty of Management would only be able to view organisational unit related data associated with this faculty. Users may have any number of organisational unit restrictions. If no organisational unit restrictions are defined, the user will not have access to any organisational unit related data. |
||
Restriction |
a grant which limits the set of data a user can view and the operations they can perform on the data. |
||
Restriction Object |
a name used to group the security views applicable to a particular security restriction. A restriction object relates to a specific restriction table. Restriction objects are defined by the restriction table to which they apply and the security views which are defined as being available to them. |
||
Restriction Table |
a database table which records the restricted access of users to particular data items. A different restriction table is used for restricting access to data from each different database table. The naming convention which has been adopted for the naming of restriction tables is that each restriction table should have the same name as the database table to which access is being restricted, with the addition of the suffix '_r'. For example, to restrict the access of users to certain calendar categories, a user restriction table (sys_cal_cat_r) based on the calendar category table (sys_cal_cat) is created. This is illustrated below. |
||
CAL_CAT |
USERNAME |
||
TEACHING |
peterxx |
||
TEACHING |
asmith |
||
DEET |
asmith |
||
This restriction table would ensure that user 'peterxx' is only able to access data relating to 'teaching calendars', while user 'asmith' is only able to access data relating to 'teaching and deet calendars'. |
|||
Security Role |
the primary means of controlling the access which users have to the System. Security roles are analagous to staffing functions in that a security role can be set up to provide the access which a person carrying out a particular function requires to be able to perform that function. The same person would be excluded from access to areas of the System not defined by the security role assigned to them. A person may have more than one role assigned to them, recognising that the person may have cross functional responsibilities. |
||
Security View |
used where a user is to be restricted to a sub-set of data within the role(s) assigned to them. The actual views are created by the System designers and the data to be viewed is defined in a restriction table. The restriction table is created through forms such as Maintain Calendar Category Restrictions (where data to be accessed is restricted to certain calendar categories) and Maintain Organisational Unit Restrictions (where data to be accessed is restricted to certain organisational units). |
||
Standard Menu |
see System Menu |
||
also called Standard or Basic Menu, describes the menus displayed on logging in to the System. These menus allow navigation to other menus, forms and jobs within the System. |
|||
Table |
a database object that holds data. |
||
View |
a database object that presents a customised slice of a table or a collection of tables. Unlike a table, a view contains no data, just an SQL query. The data retrieved by this query is presented like a table so that it can be worked on as if it were a table. |
||
Zoom |
the ability to navigate directly from a current form to another form by selecting the target form from a list under the current form's menu bar zoom option. |
||
Zoom Menu |
One of the items appearing in the menu bar above each form. When selected, a list of forms is displayed, enabling direct navigation to these forms. |
Last modified on 23 August 1999