Main Menu

SIS 2000+ Behavior History

Sec. 7, Edit Data

• To edit data in the master list, see Steps 7.1 - 7.1.7
• To edit data in an involvement record, see Steps 7.2 - 7.2.5

7.1.1 Open the master list

The master list can be accessed from any student Behavior record. Click on the Add command button at the bottom of the main Behavior History screen to open the 'Behavior Events' master list (Fig. 54)

Fig. 54 - master list

7.1.2 Select incident to edit
Click on the entry line of an incident to edit until it is selected by a small black pointer on the left (Fig. 54).

7.1.3 Activate edit mode
Click on the Edit command button to open the 'Edit Incident' form (Fig. 55)

Fig. 55

7.1.4 Edit incident data
Use the Tab key to move from field to field. Modify data as needed.

7.1.5 Save incident changes
Click on the Save command button to save the changes (or Cancel to abort). The save action will close the form and return the view to the master list .

Because student involvement records reference incidents in the master list, any changes in incident data in the master list will be reflected in the Behavior records of those students who are linked to the incident.

7.1.5 Edit Faculty data
If data for faculty members involved in the selected incident needs to be edited, select the target faculty name in the Faculty Involved list (Fig. 56)

Fig. 56

and then click on the Edit command button to open the 'Edit Faculty Incident' form (Fig. 57). Use the Tab key to move from field to field. Modify data.

Fig. 57

7.1.6 Save Faculty changes
Click on the Save command button to save the changes in Faculty data, close the form and return to the master list (or Cancel to abort).

To delete a Faculty Incident record altogether, select the target faculty name in the list and then click on the Delete command button.

7.1.7 Exit master list
To exit the master list and return to the main Behavior History screen, click on the Cancel command button.

7.2 Edit an involvement record

7.2.1 Find student
(See Sec. 1 for details on the Find procedure)

7.2.2 Select originating incident
Involvement records originate from incidents referenced from the master list. Select the originating incident in the summary list of the 'Incidents' tab on the main screen Behavior History screen.

7.2.3 Activate the first-level edit mode

With the target incident selected, click on the Edit command button to activate the first-level edit mode. Four sub tabs will be displayed with the default focus on the 'Involvement' sub tab (Fig. 58).

Fig. 58 - sub tabs

7.2.4 Modify data
Involvement records are sum total of data in the 'Incident', 'Involvement', 'Penalties', and 'Policies' sub tabs. Move the focus to the sub tab to be edited. Use the Tab key to move from field to field within the sub screen. Modify data.

• 'Incident' data -

This sub screen displays universal attributes of the originating incident. These attributes cannot be edited in this mode because they are merely being referenced from the master list - not copied. To edit the universal attributes of an incident the user must go to the edit mode in the master list. See Steps 7.1 - 7.1.7. Although the attributes of originating incident cannot be edited in this mode, the originating incident can be changed. To do this, click on the Change Incident command button to open the master list. Then select another incident in the master list and click on the Select command to copy that incident back to the current student's record. The old reference will be replaced with the new reference in the 'Incidents' tab.

• 'Involvement' data -

This is the most important data for the involvement record. It shows precisely how the student was involved in the incident. Use the Tab key to move from field to field within the screen. Modify data as needed. See Sec. 4, Step 4.3.2, "Enter 'Involvement' data" for details on the each data field.

• 'Penalties' data -



Select a penalty to edit in the summary list. Then click on the Edit Penalty command button to open the 'Edit Penalty' form. Use the Tab key to move from field to field within the form. Modify data as needed. Save. See Sec. 5, Step 5.3, "Enter Penalty data" for more information on each data field.


• 'Policy' data -

Select a policy to edit in the summary list. Then click on the Edit Policy command button to open the 'Edit Policy' form. Select another Policy Code from the drop-down list and then Save (or Cancel to abort).

Setting dates:
A Behavior Date field always displays the current system date as the default - also called "today's date." To enter a date than the default date, use of drop-down calendar (Fig. 59). To activate a drop-down calendar, click on the field button of any Date field.


Fig. 59

Use the small, single VCR buttons at the bottom of the calendar to navigate forward or backward to the target month. Use the double arrows to navigate to the target year. Click on the target date until it is highlighted in yellow and then click on the Select command button to post that date to the Date field, or Cancel to exit the calendar without changing the default date. The calendar will close automatically after the Select command is executed. To restore today's date, activate the calendar and click on the Today command button until today's date is highlighted in yellow on the calendar. Click on the Select command button to post the date in the field.

7.2.5 Save changes and exit the edit mode
Changes to 'Penalties' data and 'Policies' data are automatically saved with their respective sub-routines as described in previous steps. If these are the only tabs that were edited, click on the Undo or Done command button to exit the edit mode and return to the main Behavior History screen. If any changes were made in the 'Involvement' sub screen, click on the enabled Save command button to save the 'Involvement' changes and return to the main screen or click on Undo to cancel changes made to 'Involvement' and return to the main screen.



Caution! If a penalty associated with a "suspended" attendance code is deleted, the attendance records written by that penalty will not be reversed. If a date range for a suspension penalty is being changed by this action to a range of less days than the original date range, then another type of warning will appear (Fig. 28) before the final confirmation message. This is to remind the user that previous attendance codes entered by the original date range will not be reversed in the Attendance tables. If the codes need to be changed they will have to be overwritten by initiating another suspension penalty or by editing the student's attendance records using the various other applications in the Attendance program module. See Step 5.4.1 for details.