<node id="622267">
  <nid>622267</nid>
  <type>news</type>
  <uid>
    <user id="34945"><![CDATA[34945]]></user>
  </uid>
  <created>1559764168</created>
  <changed>1559764168</changed>
  <title><![CDATA[Tech Treks Southeast: An Outdoor Orientation Experience Like None Other]]></title>
  <body><![CDATA[<p><strong>Tech Treks Southeast: An Outdoor Orientation Experience Like None Other</strong><br />
<strong>Incoming Freshmen ONLY</strong><br />
Join incoming Georgia Tech classmates for a three-day rock climbing, rafting and camping adventure. Challenge yourself on this high-adventure freshman orientation trip! Meet new friends including upper-class mentors. It is a great kick-off to a great experience at Georgia Tech!<br />
Tech Treks trips do not interfere with any FASET session.<br />
<strong>Tech Treks Southeast 2019</strong></p>

<ul>
	<li>Session A-Summer Freshmen June 15 (Friday) &ndash; June 17 (Sunday)</li>
	<li>Session B (Before FASET 1): June 22 (Saturday) &ndash; June 24 (Monday)</li>
	<li>Session C (After FASET 2): June 28 (Friday) &ndash; June 30 (Sunday)&nbsp;</li>
	<li>Session D (After FASET 3): July 12 (Friday) &ndash; July 14 (Sunday)</li>
	<li>Session E (Before FASET 4) July 20 (Saturday) &ndash; July 22 (Monday)</li>
	<li>Session F (After FASET 5) July 26 (Friday) &ndash; July 28 (Sunday)&nbsp;</li>
</ul>

<p>Note: You can attend any Tech Treks Southeast Session (Summer Freshmen, A,B,C,or&nbsp;D) even if you are attending a different FASET Session. For example, you could attend Tech Treks B even if you are going to FASET 5.&nbsp;For more information visit:&nbsp;<a href="http://www.crc.gatech.edu/tech-treks-south-east">http://www.crc.gatech.edu/tech-treks-south-east</a><br />
&nbsp;<br />
<strong>Tech Treks Expeditions</strong><br />
Tech Treks Expeditions spaces for Montana and Alaska are still open. Our Expeditions are a great way to kick off your career at Georgia Tech!&nbsp;For more information visit:&nbsp;<a href="http://www.crc.gatech.edu/outdoor/treks">http://www.crc.gatech.edu/outdoor/treks</a></p>
]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2019-06-05T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Join incoming Georgia Tech classmates for a three-day rock climbing, rafting and camping adventure. Challenge yourself on this high-adventure freshman orientation trip! Meet new friends including upper-class mentors.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>1298</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>1298</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Parent and Family Programs]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
