The development of the annual Academic Calendar is a key responsibility coordinated by the Registrar’s Office to ensure timely communication of important academic dates and institutional deadlines. The UTC Web Team (both Marketing and the Web Dev Team) provides support to implement the Academic Calendar each school year during the previous spring.
The Registrar’s Office
To initiate this process, the Registrar will provide three CSV files (fall, spring, and summer) containing the foundational data needed to build the calendar. These spreadsheets will be uploaded to the Localist calendar. These spreadsheets should include the following. (Where prompts are in quotes, the words must match exactly.):
- Title
- Description (optional)
- Date From
- Date to
- Start time (if applicable): ex., 10:00 am
- End time (if applicable): ex., 10:00 am
- Event website
- Keywords: “Academic Calendar”
- Department: “Registrar”
- Allow User Activity: “N”
- Allow User Interest: “N”
- Visibility: “Public”
- Owner Email: “registrar@utc.edu”
- Experience: “In-Person”
- Event Types: “Academic Calendar”
- Topics: “Academic Calendar”
- Audience: “Current Students, Grad Students, Undergraduate Students, Faculty & Staff, Executive Leadership, Faculty, Management, Staff, Families, General Public, Prospective Students”
- Photo URL: “https://localist-images.azureedge.net/photos/44031580074721/featured/33ff2cc587c38886df5d46e088d1544e17838066.jpg”
Each spreadsheet requires careful analysis and coordination to ensure all dates align with institutional policies and operational needs. Specific actions will be taken to consolidate, validate, and sequence this information accurately. Once finalized, the calendar serves as an essential reference tool to support academic planning and operations across the institution.
Marketing
Marketing is responsible for uploading the CSV files and ensuring that all the events are uploaded correctly. They are also responsible for adding “tags” to each event as follows. They can be added as a single item or in combination:
Fall:
- full term-f[YY]
- part term 1-f[YY]
- part term 2-f[YY]
Spring:
- full term-sp[YY]
- part term 1-sp[YY]
- part term 2-sp[YY]
Summer:
- full term-sm[YY]
- part term 1-sm[YY]
- part term 2-sm[YY]
Other items to check for:
- Missing dates
- Duplicate text in the description (ex., “No Classes”) may exist in both the title and the description. The description should be removed.
- Breaks and holidays missing end dates, “Through [MM-DD]”, for extended off-times. These should be added to the description. Ex., For the fall break, the end date would look similar to “Through Oct. 15” in the description field.
- Duplicate events
- Time entry error: ex., “9:00 am to 9:00 am”. Only one is needed.
- Tags are wrong.
- “Registrar” is missing from the “Department” field.
The Web Development Team
The Web Development Team will need to work both on the Localist website to create the widget as well as the Drupal website to create the page and add the widget.
Widget Settings: Overview
- Template: UTC List Classic Registrar
- Number of Results: 100
- Days Ahead: 365
- Experience: In-Person
- Keywords and Tags:
- full term-[f, sp, sm][YY], ex., full term-f25
- part term 1-[f, sp, sm][YY], ex., part term 1-f25
- part term 2-[f, sp, sm][YY], ex., part term 2-f25
- Content must match: Any place or group, and at least one keyword or tag, and one filter item
- Preview
- Generate Embed Code (this provides the code to copy to your clipboard)
NOTE: BC these calendars are usually created in May, 365 days past May of the following year past will not show, for example the summer school terms. This will be corrected in the Drupal side, when you set the data range parameters.
Double check duplicate events, duplicate texts in the description, missing events, missing “Through” dates in the description, and poorly formatted timeframes, ex., “9:00 am to 9:00 am”.
NOTE: IT IS MUCH EASIER TO MAKE ANY EDITS IN LOCALIST BEFORE YOU COPY THE WIDGETS TO DRUPAL AS EVERY CHANGE MADE WILL REQUIRE A NEW WIDGET CREATION.
Drupal Side—Cloud Test Set-up:
- In text editor, convert to “Full HTML”, click “Source”, and create three blocks with headings centered in a blue bar each:
<h3 class="text-align-center blue-bar">Fall 20[yy]: August [dd]-December [dd], 20[yy]</h3>
<h3 class="text-align-center blue-bar">Spring 20[yy]: January [dd]-May [dd], 20[yy]</h3>
<h3 class="text-align-center blue-bar">Summer 20[yy]: May [dd]-August [dd], 20[yy]</h3>
- Click “Source” again to get back into the text editor window.
- Create an accordion in each. You will need three rows for each accordion. For each of the three accordiond titles, type the following:
- Full Term
- Part Term 1
- Part Term 2
- Add an extra empty paragraph for spacing.
- Click “Source” to get back into the source code window. You’ll need this to paste the widget code in between the
<dd></dd>
tags. - From this point forward, you will need to have both the calendar widget page open and the Drupal layout builder page open.
Back to the Localist Widget page:
- Enter the Keyword and Tag: full term-f[YY]
- Preview
- Generate Embed Code: Copy that code to your clipboard.
- You will repeat this for each of the following terms in the Keyword and Tags field of the Widget Page:
- full term-f[YY]
- part term 1-f[YY]
- part term 2-f[YY]
- full term-sp[YY]
- part term 1-sp[YY]
- part term 2-sp[YY]
- full term-sm[YY]
- part term 1-sm[YY]
- part term 2-sm[YY]
Back to the Drupal page:
- in the first accordion (in “Source” mode) paste your widget between the and tags.
- In the
<script>
tag, look fornum=100
. - Type in the following parameters:
&start=20[YY]-08-01&end=20[YY]-12-31
.
NOTE: If you copy and paste from another widget previously created, you will need to remove the “amp;
” after the ampersand that Drupal inserts upon updating the text editor. - Click Update.
- Save Layout.
- Check your block.
- On the Drupal side the parameters should be
- For fall full term, part term 1, and part term 2, use:
&start=20[YY]-08-01&end=20[YY]-12-31
(Aug. 1 through Dec. 31) - For spring full term, part term 1, and part term 2, use:
&start=20[YY]-12-15&end=20[YY]-5-15
(Dec. 15 through May 15) - For summer full term, part term 1, and part term 2, use:
&start=20[YY]-05-10&end=20[YY]-8-31
(May 10 through Aug. 31)
- For fall full term, part term 1, and part term 2, use:
- Double check the calendars and make any edits.
- Get approvals.
- Once final approvals are made, copy code to the live site.
NOTE: If for whatever reason you need to make an edit in the Calendar, and you’ve already placed the widget in Drupal, you will need to regenerate the widget and copy the code to Drupal again. It does not automatically update.