<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Advanced Settings on Documentation</title><link>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/</link><description>Recent content in Advanced Settings on Documentation</description><generator>Hugo</generator><language>en</language><copyright>FlightPatch Academics</copyright><atom:link href="https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/index.xml" rel="self" type="application/rss+xml"/><item><title>Requirement Types and Codes</title><link>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/requirement-types-codes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/requirement-types-codes/</guid><description>&lt;a id="requirement-types-and-codes" name="requirement-types-and-codes"&gt;&lt;/a&gt;



&lt;h1 id="requirement-types-and-codes-header"&gt;Requirement Types and Codes&lt;a class="anchor" href="#requirement-types-and-codes"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;When editing a degree and adding courses or groups to a degree plan, you can specify the &lt;strong&gt;type&lt;/strong&gt; of each course or group. FlightPath refers to this as the &lt;strong&gt;requirement type&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;For example, a course such as ENGL 1001 might be considered a &lt;strong&gt;Core&lt;/strong&gt; requirement, while another course might be a &lt;strong&gt;Major&lt;/strong&gt; requirement or an &lt;strong&gt;Elective&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Requirement types are identified by a letter code.&lt;/p&gt;
&lt;a id="assigning-a-requirement-type" name="assigning-a-requirement-type"&gt;&lt;/a&gt;

&lt;br&gt;

&lt;h2 id="assigning-a-requirement-type-header"&gt;Assigning a Requirement Type&lt;a class="anchor" href="#assigning-a-requirement-type"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When editing a degree, add the requirement type code after the course or group.&lt;/p&gt;</description></item><item><title>Course Repeat Policy</title><link>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/course-repeat-policy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/course-repeat-policy/</guid><description>&lt;a id="course-repeat-policy" name="course-repeat-policy"&gt;&lt;/a&gt;



&lt;h1 id="course-repeat-policy-header"&gt;Course Repeat Policy&lt;a class="anchor" href="#course-repeat-policy"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;FlightPath can handle repeated courses in several different ways. The way repeated courses are evaluated is controlled by the &lt;strong&gt;Course repeat policy&lt;/strong&gt; setting on the &lt;strong&gt;Configure School Settings&lt;/strong&gt; form.&lt;/p&gt;
&lt;p&gt;The available policies determine which attempt FlightPath uses when a student has taken the same course more than once.&lt;/p&gt;
&lt;blockquote class='book-hint '&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The course repeat policy applies to normal courses whose repeat hours are the same as their minimum hours. Courses that are specifically designed to be repeated are handled differently.&lt;/p&gt;</description></item><item><title>Term ID Structure</title><link>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/term-id-structure/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/term-id-structure/</guid><description>&lt;a id="term-id-structure" name="term-id-structure"&gt;&lt;/a&gt;



&lt;h1 id="term-id-structure-header"&gt;Term ID Structure&lt;a class="anchor" href="#term-id-structure"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Every course taken by a student must have a corresponding &lt;strong&gt;term ID&lt;/strong&gt; that identifies when the course was taken.&lt;/p&gt;
&lt;p&gt;For many schools, a term ID is a simple code that combines a year and a term code. For example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;2008SP&lt;/code&gt; might represent Spring 2008.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;2009FL&lt;/code&gt; might represent Fall 2009.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Each school may have its own system for representing terms. FlightPath can be configured to understand the school&amp;rsquo;s term ID structure and display terms appropriately.&lt;/p&gt;</description></item><item><title>Grade Logic</title><link>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/grade-logic/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.flightpathacademics.com/flightpath-settings/advanced-settings/grade-logic/</guid><description>&lt;a id="grade-logic" name="grade-logic"&gt;&lt;/a&gt;



&lt;h1 id="grade-logic-header"&gt;Grade Logic&lt;a class="anchor" href="#grade-logic"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;FlightPath uses &lt;strong&gt;grade logic&lt;/strong&gt; to determine how different grades affect a student&amp;rsquo;s degree plan.&lt;/p&gt;
&lt;p&gt;For example, grade logic determines whether a student has failed a course and needs to retake it. It also determines whether a grade is considered sufficiently high to satisfy a minimum-grade requirement.&lt;/p&gt;
&lt;p&gt;These settings can be configured from the &lt;strong&gt;Configure School Settings&lt;/strong&gt; page in the &lt;strong&gt;Admin Console&lt;/strong&gt;.&lt;/p&gt;
&lt;a id="grade-order" name="grade-order"&gt;&lt;/a&gt;

&lt;br&gt;

&lt;h2 id="grade-order-header"&gt;Grade Order&lt;a class="anchor" href="#grade-order"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This is the order, from highest to lowest, of all the grades in your system. This is how FlightPath understands than &lt;code&gt;B&lt;/code&gt; is better than &lt;code&gt;C&lt;/code&gt; and so on. In situations where courses are ordered by grade, this data is required.&lt;/p&gt;</description></item></channel></rss>