| Data element |
Definition |
BITMAP
Indexed - no
Format - number (10)
May be null? yes |
This data element is not intended to be used in reports.
|
CATEGORY
Indexed - no
Format - varchar2 (80)
May be null? yes |
A character string that identifies
the group of related codes (if any) within the code set (TYPE) to
which the LMS_DEFINITION record belongs. The CATEGORY is often null (especially
for codes used in the tables in the Data Warehouse), but may
include
letters and/or
numerals
and/or other characters. The letters in CATEGORY may be in upper case,
lower
case,
or mixed case.
See also TYPE.
The
LMS_DEFINITION table is a reference table storing sets of codes used
to specify various
attributes
of the
records
stored
in
the
Knowledge
Link system. The DEF_ID may be used to link a code in another table to
its decoded value. For example, given a KNODE record that
has a TYPE code of 160, one can retrieve the LMS_DEFINITION record
where DEF_ID = 160, and find that its NAME -- the decoded value -- is
'Knowledge Position'. In this example, the LMS_DEFINITION table's TYPE
for 160 is 'KNODE_TYPE', and its CATEGORY (subtype) is 'KPOS'.
Examples: 'KPOS', '1', 'Document'
Values:
Refer to the LMS_DEFINITION table for values. |
DEF_ID
Indexed - yes
Format - number (10)
May be null? no |
A number used as a code to specify
an attribute of a record stored in the Knowledge Link system. The DEF_ID
uniquely identifies the LMS_DEFINITION record.
See also NAME.
The LMS_DEFINITION table is a reference table
storing sets of codes used to specify various attributes of the records
stored in the Knowledge Link system. The DEF_ID may be used to link
a code in another table to its decoded value. For example, given a
COURSE_ITERATION record that has a STATUS code of 51, one can retrieve
the LMS_DEFINITION record where DEF_ID = 51, and find that the decoded
value is 'Closed'.
Example: 51
Values:
Refer to the LMS_DEFINITION table for values. |
DESCRIPTION
Indexed - no
Format - varchar2 (3000)
May be null? yes |
A character string that clarifies the decoded
value of the code (DEF_ID) stored in the LMS_DEFINITION
record. It is possible
for more than one LMS_DEFINITION record to have the same value for DESCRIPTION.
The DESCRIPTION is
often null (especially
for codes used in the tables in the Data Warehouse), but may
include
letters and/or
numerals
and/or other characters. The letters in DESCRIPTION may be in upper case,
lower
case,
or mixed case.
See also NAME.
The LMS_DEFINITION table is a
reference table storing sets of codes used to specify various attributes
of the records stored in the Knowledge Link system. The DEF_ID may
be used to link a code in another table to its decoded value. For example,
given a GEN21_USER record that has a STATE code of 75, one can
retrieve the LMS_DEFINITION record where DEF_ID = 75, and find that
its NAME
-- the decoded value -- is 'CO'. In this example, the code's
DESCRIPTION is 'Colorado'.
Every DEF_ID has a non-null NAME; some also have a non-null DESCRIPTION.
In some cases, when retrieving the decoded value of a code in a report,
it might be better to retrieve the DESCRIPTION than to retrieve the NAME.
Examples: 'AREA', 'It is past the last
enrollment date.', 'SCORM 1.2 compliant courses'
Values:
List of values not available |
NAME
Indexed - no
Format - varchar2 (80)
May be null? no |
A character string that is the decoded value of a code used to specify
an attribute of a record stored in the Knowledge Link system. It is possible
for more than one LMS_DEFINITION record to have the same value for NAME.
The NAME may include letters and/or numerals and/or other characters.
The
letters
in NAME
may be in upper case, lower case,
or mixed case. See also
DEF_ID.
The LMS_DEFINITION table is a reference table storing sets of codes
used to specify various attributes of the records stored in the Knowledge
Link system. The DEF_ID may be used to link a code in another table to
its decoded value. For example, given a COURSE_ITERATION record that
has a STATUS code of 51, one can retrieve the LMS_DEFINITION record where
DEF_ID = 51, and find that its NAME -- the decoded value -- is 'Closed'.
Every DEF_ID has a non-null NAME; some also have a non-null DESCRIPTION.
In some cases, when retrieving the decoded value of a code in a report,
it might be better to retrieve the DESCRIPTION than to retrieve the
NAME.
Examples: 'Closed', 'CUSTOM_V1', '1'
Values:
Refer to the LMS_DEFINITION table for values. |
SPECIAL_ID
Indexed - no
Format - varchar2 (20)
May be null? yes |
This data element currently is not used.
|
STATUS
Indexed - no
Format - number (1)
May be null? yes |
A numeral indicating whether the code (DEF_ID) is active
or inactive.
When a record with a coded attribute is entered or updated in the Knowledge
Link system, the list of values for that attribute includes only the
values for the active codes for that attribute.
Values:
0 (the code is inactive)
1 (the code is active) |
TYPE
Indexed - yes
Format - varchar2 (80)
May be null? no |
A character string used to identify the set of codes to which
the LMS_DEFINITION record belongs. See also CATEGORY.
The LMS_DEFINITION table is a reference table storing sets of codes
used to specify various attributes of the records stored in the Knowledge
Link system. The DEF_ID may be used to link a code in another table to
its decoded value. For example, given a COURSE_ITERATION record that
has a STATUS code of 51, one can retrieve the LMS_DEFINITION record where
DEF_ID = 51, and find that the decoded value is 'Closed'. In this example,
51 belongs to the set of codes that specify the status of a course
iteration; its TYPE is 'CI_STATUS'.
Examples: 'CI_STATUS', 'US_STATE', 'LANGUAGE'
Values:
Refer to the LMS_DEFINITION table for values. |
