SharePoint learning kit Core Content Overview (6)

ArticleDirectory

• Number of final points recorded by the learner Course
• Changes in calculated points and final points
• SCORM 2004 sucess status
• SLK Verification
• SCORM 2004 reactivate

Continue to introduce the scoring mechanism.

Automatic score (LRM) for each interaction)

Each interaction in LRM that can be automatically scored has an auto-score ). The lrm automatic score may be calculated at any time, but it is available until the learner's course is in the completed or final state. The SLK uses the automatic score of each interaction as the default score of each interaction instructor. The automatic scores of each interaction are saved separately to facilitate daily report output. This value cannot be modified when the learner course record is completed and is automatically scored unless the course record is reactivated.

If the question is not answered, the score is zero automatically. The initial score value of the corresponding instructor is the same.

Instructor score (LRM) for each interaction)

For each interaction in LRM, instructors can set an instructor score. For the interactions that are automatically scored, the score is initially the auto score of the interaction. If this interaction is not automatically scored, the instructor score is initially blank. The instructor can edit the score in the grading view.

Scores of non-eLearning content

Non-elearing content cannot be automatically scored or scored. Therefore, the final score is initially zero.

Number of final points recorded by the learner Course

The final point is the score of a learner's course record. This value is initially calculated as the number of points, but can be modified by the instructor (when the course record is in the "completed" or "final" status ).

Instructors can clear the final points to indicate that the course record has no score. This is usually used to kick a user out of the course.

If the calculated point value changes, the final point value changes to the same amount.

The learner cannot access the final point before the course record status is "final. In all other States, the score displayed to the learner is null.

Changes in calculated points and final points

Changing the number of computing points will update the final number of points with the same change volume at the same time, specifically:

• If the calculated point is null, the final point is updated to the new calculated point after the instructor changes it.
  If (computedpointsold = NULL ){
  Finalpointsnew = computedpointsnew}
• If a calculated vertex value already exists, if the final vertex number is not null, the corresponding change vertex number is updated. If the final number of points is null, it indicates that it is cleared by the instructor. Therefore, it should not be changed based on the number of points.
  Else {
  If (finalpointsold! = NULL)
  Finalpointsnew = finalpointsold + (computedpointsnew-computedpointsold )}

How to calculate the number of points affects the final number of points:

• Points in the score table are transmitted when the courseware playing frame page in the grading view is closed through the internal communication mechanism of the form.
• The instructor can also update the score table when this framework page is opened in the grading view.
• When each frame page is saved, the latest computing points and final points are stored on the server.
• When saving the score table, the final points currently displayed in the table are stored.

• The calculated points can only be modified by the content score, but cannot be modified in the score table. This makes it a good "primary score" reference when the final points cannot be synchronized and must be updated by the instructor.

SCORM 2004 sucess status

For SCORM 2004 E-leanring courseware content, there is a success status concept, which exists independently of the score. The success status is determined by the content and e-Learning runtime environment, and cannot be modified or manually set by the instructor.

The success status indicates the success status of the root activity's primary objective. The development specification of the assigned workflow defines the value displayed on the SLK interface for the successful status.

 

Next, go to the Q & A (FAQ) section.

SLK verification uses roles rather than groups

In earlier designs, SLK developers used groups rather than roles to specify learners and instructors in SLK. In WSS V3, the concept of Website user group is cut down and replaced with a role. We cannot create a group at the spweb level and use independent permissions. The group in V3 exists in the spsite layer and is shared in spweb. However, different roles can be inherited from these groups at the spweb layer by disconnecting the roles. A typical school website hierarchical structure has a school spsite and some independent spweb and sub-spweb classes or courses. We need to allow users to specify a set of unique learners and instructors at the spweb level. For example, if you create an assignment on history6 spweb, you only need to assign the assignment to the relevant users and groups within history6. You don't want to see all the users and groups in the school. To use a group independently, a set of mandatory group configuration structures and naming conventions are required to match the corresponding spweb and group names. Because the group is shared within the spsite.

Different from the group, roles are more suitable for marking the user type within a given spweb range (SLK learners or SLK instructors ). The role also provides greater flexibility in the final implementation. On a single spweb, multiple groups can be assigned to the SLK learner role, or you can directly assign users to this role instead of groups.

Why not use a default role, but SLK learners and SLK instructors roles?

We recommend that you use SLK learners and SLK instructors, so that you can apply a role to a user or group for identification in SLK without affecting other permissions used in Sharepoint. The administrator can select to use a default role (such as full control, design, participate in discussion, and read ), however, these roles may be applied to more users than expected, resulting in too many instructors and learners or incorrect tags.

The use of SLK learners and SLK instructors enables the spweb administrator to have full control over these roles in the SLK without worrying about changing the existing SharePoint permission system.

Why does SLK use permissions to indicate learners, rather than allowing all members of the website to be learners?

The question is how to determine the "All members" of a spweb "? Users and groups are within the spsite level, but the permissions assigned to these users and groups can be within the spweb level. We need to mark learners within the scope of spweb. In this way, the instructor can only list all SLK learners roles in the given spweb for this course when creating an assignment. One option is to allow all users and groups with any permissions on the website to be assigned, however, a specific permission is used to allow instructors to have more control to determine which users and groups are allowed to create and assign permissions (SLK instructor permissions ), which of the following plans and groups are available learners in the assignment (SLK learner permissions ).

Note that the specified actual learners and instructors are stored in the SLK database. SharePoint permissions are used to determine the user's availability on the CREATE/edit an assigned attribute page, and to verify that the user is an instructor on the target spweb when creating an assignment.

The administrator can use an existing permission, such as "Participate in the discussion", to assign permissions by using the created permissions. For example, the default "<spweb Name> member" group is automatically created after spweb is created. It has the permission to participate in the discussion on the spweb. In this case, you can specify the "participate in discussion" permission to indicate the learner permission in the SLK. This is exactly why we allow the Administrator to specify permissions on the spsite for marking learners and instructors in the SLK.

SCORM 2004 reactivate

The original design of SCORM 2004 re-activation was to create a new learning record (attempt) for learners to continue learning. Although this will delete all previous work of the learner, it aims to provide it with a clean Sequencing data model and work. In some cases, sequencing rules may not allow users to perform operations on the entire course again and exit automatically upon re-entry.

When evaluating the design, we found that it could not completely solve the problem. Courseware often uses global objectives to save sequencing decision information. These objectives are global to learners and packages. When globaltosystem is true, they can also become global attributes at the learner and LMS levels. That is to say, even if the learner's learning (attempt) records are cleared, no new sequencing is available.

Because this design cannot completely solve the potential problems of sequencing, SLK developers finally decided to retain the consistency of the re-activation behavior, so that SCORM 2004 uses the same mechanism as other e-Learning courseware. In this way, the courseware behavior can be unified to eliminate the data loss that may occur when a new learning record is created on the activity tree.

For the originally designed purpose (new learning), it is necessary to allow learners to continue learning on this course, instructors can still create a new course record for the learner by deleting and re-adding the course records.

 

(End)