This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| scheduling:maintenance:masterschedule:campus:prooxies [2016/12/02 21:59] – jstanford | scheduling:maintenance:masterschedule:campus:prooxies [2016/12/14 17:12] (current) – removed jstanford | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======Proxies====== | ||
| - | |||
| - | <div # | ||
| - | |||
| - | // | ||
| - | |||
| - | <WRAP round intro> | ||
| - | of the individual courses. | ||
| - | |||
| - | * **Normal proxies** allow you to quickly assign a group of courses to students. The students are scheduled into the courses during the scheduling load. When you add the normal proxy number for the student and when you click Save, the group of courses are added as requests; the proxy number is not part of the student requests. | ||
| - | |||
| - | * **Control proxies** allow you to schedule students into specific courses identified by the course and section numbers of the proxy. Control proxies are used to schedule students manually. | ||
| - | |||
| - | * **Match proxies** are used to match two courses when you want one course taken half of the school year and the other course taken the other half of the school year. Match proxies allow you to schedule a student into courses with the same section numbers for each course. The match proxy number assigned to the student ensures that he will have the matched courses the same period of the day. Match proxies are used to ensure that students are scheduled into two one-semester courses in different semesters in the same period of the day. | ||
| - | * If you are using Maintenance > Master Schedule Generator > Generate Campus Schedule, the courses contained in the match proxy are generated with matching periods of the day for each section created. | ||
| - | * For match proxies, you have the option of selecting additional fields: Include in Conflict Matrix, Exclude from Stu Crs Requests, Pregrid Restriction, | ||
| - | * Before running a scheduling load, sections must be built for each course using matching section numbers and the same period of the day, but opposite semesters. | ||
| - | |||
| - | Match Proxy Example: | ||
| - | ^Course^Section^Semester^Course^Section^Semester^ | ||
| - | |Government|01|1|Economics|01|2| | ||
| - | |Government|02|1|Economics|02|2| | ||
| - | |Government|03|2|Economics|03|1| | ||
| - | </ | ||
| - | |||
| - | ====Add proxies: | ||
| - | |||
| - | Click **Retrieve**. | ||
| - | * Existing proxies are displayed. The list ++ can be re-sorted.|{{page> | ||
| - | * If more courses are retrieved than can be displayed on one page, you can ++ page through the list.|{{page> | ||
| - | |||
| - | Click **+Add** in the upper grid to add a new proxy. The fields in the free-form area below the grid are enabled. | ||
| - | |||
| - | ^Field^Description^ | ||
| - | ^Proxy|{{page> | ||
| - | ^Title|{{page> | ||
| - | ^Type|{{page> | ||
| - | |||
| - | To add courses to the proxy, click {{: | ||
| - | <WRAP box>Each proxy must contain at least two courses.</ | ||
| - | |||
| - | ^Field^Description^ | ||
| - | ^Course|{{page> | ||
| - | ^Sec|{{page> | ||
| - | ^Sem Cd|{{page> | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | The Sem field displays the semester for the selected section. | ||
| - | |||
| - | |||
| - | Continue adding courses to the proxy as needed. | ||
| - | |||
| - | |||
| - | To delete a course from the proxy (from the lower grid), click . The course is deleted | ||
| - | from the grid. | ||
| - | |||
| - | |||
| - | Click Save. | ||
| - | |||
| - | |||
| - | To delete a proxy (from the top grid), click . The row is shaded red to indicate | ||
| - | that it will be deleted when the record is saved. | ||
| - | |||
| - | |||
| - | You can select multiple rows to be deleted at the same time. | ||
| - | |||
| - | |||
| - | Click Save. The selected rows are deleted. | ||
| - | |||
| - | |||
| - | Note: You can save changes and delete records in the same step (i.e., the changes | ||
| - | are all committed when the record is saved). If any changes do not pass validation | ||
| - | (i.e., cannot be deleted or have validation errors), none of the changes are saved. | ||
| - | |||
| - | ====Other functions and features: | ||
| - | |||
| - | ^{{: | ||
| - | ^{{: | ||
| - | |||
The Texas Computer Cooperative (TCC) is committed to making its websites accessible to all users. It is TCC policy to ensure that new and updated content complies with Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. We welcome comments and suggestions to improve the accessibility of our websites. If the format of any material on our website interferes with your ability to access the information, use this form to leave a comment about the accessibility of our website.