FY25.2.x: Technical Design (Slate+Advising)

Executive Summary

The purpose of this document is to provide the full details of the technical solution to be used for the build of the Slate+Advising solution. Everything that is needed by the developer(s) to produce the required data model, forms and workflows will be included in this specification.

Technical Components

The following sections will detail the technical components within each functional area that are required to successfully implement this project.

Data Requirements

Purpose

Define any integrations or data that must be provided to deliver the solution.

• HBCU/CUNY Fellows
  • Create a bit (yes/no) field for HBCU Fellow
  • Create a bit (yes/no) field for CUNY Fellow
  • Create an HBCU source format so that a CSV file with columns for PID and HBCU can be mapped to the CUID and HBCU Fellow fields respectively in Slate
  • Create a CUNY source format so that a CSV file with columns for PID and CUNY can be mapped to the CUID and CUNY Fellow fields respectively in Slate.
  • Both source formats should have the following settings:
    • Type: Cumulative/Replaceable
    • Update Only: Update Only

Technical Design

Purpose

Define in detail the technical work that will need to be completed to deliver the final solution.

• HBCU/CUNY Fellows
  • Upload the HBCU and CUNY fellows lists 
  • Add a line for HBCU Fellow on the dashboard pages of current students, former students, and alumni. that displays "Yes" or "No". (Set null values to 'No.')
  • Add a line for CUNY Fellow on the dashboard pages of current students, former students, and alumni. that displays "Yes" or "No". (Set null values to 'No.')