Anchor | ||||
---|---|---|---|---|
|
...
This document tells us of potential course relations i.e. classes that are in the same timeline but not related which can be a conflict.
Report is read left to right comparing CSN1, UNQ 1 etc. on the left with CSN2, UNQ 2 etc. on the right
There are 2 types of is 1 type of accepted missing course relationsrelation:
- Classes with class meets dates :
Leave as potential course relations
- Classes without class meets dates:
...
- that do not overlap e.g. Class A meets Jan 1-Jan 15 and Class B meets Feb 1-Feb 15 but have the same timeline
Potential course relations and conflicts
- If same department, title, or instructor set to room share unless Same-as is obvious. Leave log note 'Defaulting to room share' or 'setting course relations'
- If a conflict, try to find solution
Anchor | ||||
---|---|---|---|---|
|
This output tells of errors with classes that are related together
Report is read left to right comparing CSN1, UNQ 1 etc. on the left with CSN2, UNQ 2 etc. on the right
In the error field it will display what type of error:
- Classes are related but have differing timelinesÂ
- NIV1: Course relation inventory discrepancy e.g. Courses are a same as in class manager but are not in inventory
- NFOS: Same field of study meeting as a same-as e.g. ARC 696 and ARC 692K listed as a same-as
- Classes that are related but in different timelines
...
Anchor | ||||
---|---|---|---|---|
|
Updated 1/31/17 by ah
Running the Report
- Mainframe; txtask – set the following fields:
- Command: SSJ
- Name: rgjgsch4
- Version: p
- Dept: RG
- Scroll until you see RGJNHRS, and select by placing a 'Y' in the field, and inserting the proper YYS.
...