Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Overview

The purpose of this document is to provide the manual steps required within the Slate+Advising instance whenever a new advisor is added to the team. Over time, this list of tasks should decrease as more processes are automated.

Actions

Each of the sections below must be completed for each new advisor.

User Configuration

  • Add the advisor as a new active user with login access
  • Add the user to the following roles:
    • Advisor
  • Download the advisor's photo from the external facing advisor web site and add it to the static image folder in Slate
    • This is done in the Configuration / Files section under Database through the Slate web UI
    • The file name MUST be the advisor's UNI with a .jpg extension (e.g., ab1234.jpg)
  • Add the advisor's Google calendar to the configured Calendar Feeds 
  • Add two Active Scheduler components for the advisor
    • One active schedule should be based on the advisor's in-person availability and have "(In Person)" in the title and one based on virtual and have "(Virtual)" in the tile, (e.g. "John Smith (In Person)" and "John Smith (Virtual)."
    • The date range in the active schedule should end as of 12/31 of the subsequent year. If we are in 2023, the end date should be 12/31/24. Those dates will need to be updated annually.
    • After entering the basic information of each active scheduler component, click "Edit Templates." The virtual component should be assigned the template "Scheduled Advising Session Virtual." The in person component should be assigned the template "Scheduled Advising Session In Person."
    • Configure the time slots based on advisor's preferences (this can be changed later as needed)
  • In the portal's main view page, add two Active Scheduler widgets (one for virtual and one for in person).
    • This is easiest done by copying existing in person and virtual widgets from other advisors.
    • Ensure the advisor's uni and the class names "hidden" and "advisor" are in the "CSS Class Name" section for any scheduler parts in the "Meet Our Advising Team" portal (e.g., "ab1234 hidden advisor")
      • The UNI is used to match the active scheduler widget to the appropriate advisor. 
      • Hidden is required to ensure the component is not displayed by default
      • Advisor is required because when we want to unhide all of the advisors' schedules (in the case where the user can choose between multiple advisors' schedules), we use the "advisor" class to select them all.


  • No labels