|
Subject Attributes
Strategy Selection Attributes
Use Attributes
Linking Attributes
Management Attributes
|
|
T O P I C A T T R I B U T E S
Attributes are the characteristics of content objects and topics information about those objects, stored with them in the database.
A topic's attributes must each have a single value to reflect the single purpose of the topic. If two or more values seem appropriate for a particular attribute of a topic, it should serve as a signal that the content should be divided into two topics.
Like those for content objects, topic attributes fall into five categories: subject, strategy selection, use, linking, and management attributes.
|
|
|
Subject attributes are used by learners, administrators, and authors to search for topics and topic groups by the subject matter of the content.
|
|
Subject Attributes
Attribute |
|
Purpose |
|
Examples |
Subject Area |
|
The subject area of the content. These should be predefined (but customizable) values of the system, not free form. This could also be a link to a knowledge management system's hierarchy or network. |
|
Management, IT, telecom, soft skills, human resources, arts, agriculture, user-defined |
Keywords |
|
Search keywords defined and entered by the creator. |
|
Vacation accruals, 6290 internal schema, camper shell waiver, potassium channel defect |
Description |
|
A free-form description entered by the creator and intended for the end user. |
|
"How to properly remove the power supply of an XQ2000." |
Objective |
|
A free-form objective entered by the creator and intended for creators and administrators. |
|
"This topic teaches experienced repair technicians how to properly remove the power supply of an XQ2000 using the Simplifying Conditions Method." |
|
|
|
|
|
|
|
|
Strategy selection attributes are closely tied to topic templates.
|
|
Strategy Selection Attributes
Not all combinations of values are valid. For instance, if the outcome is "unaided procedural performance," then the format "wizard" does not make sense.
For valid combinations, there could be several topic templates to choose from. These attributes can also be used to select appropriate topics to combine into a topic group.
These attributes will be used primarily by creators and administrators.
Attribute |
|
Purpose |
|
Example |
Outcome |
|
The desired final result for the end user. Do we want to inform the user, or to improve performance? Is the performance procedural (step-by-step) or principled (requires judgment)? Are we aiding them with EPSS or are they learning to perform unaided? |
|
Inform: awareness, motivation Procedural Performance: aided, unaided Principled Performance: aided, unaided User-defined: user-defined |
Task |
|
The end user's task - what the creator intends the user to be able to do after or while using the topic. This is a two-level hierarchy. The top level is Bloom's Taxonomy. The second level has a set of work-related tasks that can be customized and extended. |
|
Knowledge: define, locate, describe, etc. Comprehension: explain, predict, compare, extend, generalize, etc. Application: classify, modify, choose, solve, interpret, repair, etc. Analysis: construct, contrast, subdivide, survey, infer, etc. Synthesis: design, organize, plan, etc. Evaluation: diagnose, critique, etc. User-defined: user-defined |
Format |
|
The type of interaction provided by the topic and the form it takes. |
|
Screen tour, tutorial lesson, searchable reference, practice, assessment, online help, job aid, demo, cue cards, tips, tool tip, system messages, user-defined |
Delivery Mode |
|
How the topic is delivered to the end user. |
|
Web, stand-alone CBT, classroom, print, hybrid, user-defined |
User Level |
|
The background level of the end user with respect to the content. |
|
Novice, Intermediate, Expert |
|
|
|
|
|
|
|
|
Use attributes provide information about how a topic will be used.
|
|
Use Attributes
Attribute
|
|
Purpose
|
|
Examples
|
Use Conditions
|
|
Rules about how content should or may be used. |
|
Western region only, senior managers and above, all new employees, etc. |
Duration
|
|
The approximate time to complete the content. Allows user to match content to time available, or to track hours needed for organizational requirements. |
|
15 minutes, 3 hours, 2 weeks, etc. |
Context
|
|
For integration of performance support. Context specifies under what circumstances this topic should be used. (Not planned for Phase 1.) |
|
"Pop-up tip when using MS Word in Outline view and clicking on the button..." |
Certification
|
|
Whether a topic is part of a track that leads to a certification. |
|
Yes, No |
Collaboration Resources
|
|
What, if any, collaboration resources are available for this topic. |
|
Virtual classroom, chat room, newsgroup, e-mail, etc. |
|
|
|
|
|
|
|
|
Linking attributes show the connections that exist among topics and topic groups.
|
|
Linking Attributes
Attribute
|
|
Purpose
|
|
Examples
|
Prerequisites
|
|
What conditions should be met before using this topic, including both previous learning and organizational issues.
|
|
Passed Topic X, Has not taken Topic Y, Is a member of sales team, Date is after 12/14/97
|
Hierarchy Links
|
|
Which other topics or topic groups link to this topic.
|
|
System IDs for parent and child topics
|
Content object Links
|
|
Which content objects this topic includes and their sequence.
|
|
System IDs for content objects (Not planned for Phase 1)
|
History
|
|
Who created, edited, or approved the topic on what dates.
|
|
System generated values
|
Template
|
|
The template used to create this topic.
|
|
The system ID for the template
|
|
|
|
|
|
|
|
|
Management attributes are used by the system and administrator for maintenance of the system.
|
|
Management Attributes
Attribute
|
|
Purpose
|
|
Examples
|
Name
|
|
To identify this topic to end users, creators, and administrators. |
|
Quoting a Policy, WatchSAT Features and Benefits, Border Procedures |
ID
|
|
To identify this topic in the system. |
|
System generated values |
Effective date
|
|
The date when the content of the topic becomes valid. |
|
Date |
Expiration date
|
|
The date beyond when the content of the topic is no longer valid. |
|
Date |
Enrollment Status
|
|
The permission for users to view a topic. |
|
Open, Closed, Required |
Authorization
|
|
Who is authorized to edit, delete, or view this topic. |
|
System links to people and organizations |
Vendor
|
|
The vendor who produced the topic. |
|
Vendor name. |
|
|
|
|
|
|
|
|
|
|
home |
glossary |
credits |
tell us what you think | © 1997 Oracle Corp.
|
|