Prerequisite update and transition to entities
Slate Instance | TUV |
Requestor | Elizabeth Storrs |
Date | Feb 1, 2024 |
Status | WAITING for cycle prep |
Summary Description | The custom app pages for collection of prerequisite data are the original xslt files that are writing directly to custom replicate app-scoped fields, which need to be updated. This data needs to be displayed in in the new workflow. |
Detailed description of desired deliverable:
From a technical standpoint
migrate off off the delivered xslt pages (realistically, this means custom app pages, but the priority is getting out of the xslt)
shift custom app fields. There are two options: (1) use Prerequisite Entity (app-scoped), where the 2023 DVM student data is. (2024 was not imported, except for a small test file, but should we ever import it again, this is where it should go.) [It has to be app-scoped because the CAS does not send unique identifiers for their course data]. (2) use the delivered courses module, which are folio, so the courses are persistent across (Slate-hosted) applications. Although the second option is counter-intuitive to the idea of maintaining all of the data in the same place, building as much of it in the way that most directly benefits the student (and that we would do universally if we could), is a strong argument. In addition, TUSMGP (who has the same CAS issues) has chosen to use the delivered courses module for their Slate-hosted applications.
- use the native courses functionality for Slate-hosted application data; put VMCAS data into application-scoped courses entity
Immediately, this data needs to be available for reading in the current workflow
confirmed that ‘course in progress’ is not necessary
IMMEDIATE FIX: use custom .pdfs for MAPP, MCM, and BDVM. (MIDGH not accepting applicants this year; PhD only used the ‘courses in progress’ piece. The prereq.pdf template already existed for the reader, but was only mapped for BDVM.
TDVM is test case for new prereq widget and new form for application, which is ultimately the direction we want to go
Research:
The MS and PhD programs have relatively simple prereqs:
MAPP one year of biology
MCM two semesters of biology, one of statistics, one of science lab
MS IDGH two semesters of biology, one of statistics, one of science lab, one of chemistry
It is the TDVM and BDVM that have the full list that matches the VMCAS list:
one year of bio with lab
one year of gen chemistry with lab
one year of org chemistry with lab
biochemistry
genetics (unless included in biology)
one year of physics
one year of math (may include stats)
one year of English composition
one year of social/behavioral science
one year of humanities/fine arts
This is currently built via xslt files with a drop down for each subject in each area:
There is also the ‘Review Coursework' Summary sheet, which is part of both TDVM and BDVM--it does not appear until after clicking the 'Continue’ button at the bottom of the Prerequisite Coursework page, but it looks like this:
These are displayed to the Readers via custom .pdfs in the format apply/round/*prereq.pdf
[when this is transitioned to portals, these .pdfs will still potentially be useful as an option for students to see their applications upon submission/be included in an admin .pdf]
Outcome:
Delivered Field Name and Key | Type | Notes |
---|---|---|
School Name | linked to suggest list based on previously entered courses | used as delivered |
Course Name | free text | used as delivered |
Level | requires prompt list with ‘course_level’ key | not used *updated the default view into this data from the courses tab to remove this and include calendar |
Course Number | free text | used as delivered |
Course Credits | free text | used as delivered |
Type | requires prompt list with ‘course_type’ key | originally had quarter/semester/trimester in it, but those are also on the app_crse_system prompt list, which is what is being used by the xslt files for all programs.; those prompts were inactivated and replaced with the list of Requisites (Biochemistry, Genetics, Physics, etcetera) |
Grade | for select list, requires prompt list with ‘course_grade’ key | used for the grade earned in the course--is left as text field |
Grade_Level | requires prompt list with ‘course_grade_level’ key | describes the Academic Year in which the course was taken (e.g. freshman, sophomore) |
Term | requires prompt list with ‘course_term’ key | Is not being used. Prompts (winter, spring summer 1, etc) existed, but are not being used anywhere in the app. Values were inactivated, and the prompt list deprecated. |
Custom Field Name and Key | Type | Notes |
---|---|---|
Status | course_status prompt | used for complete, in progress |
Semester/Year | free text e.g. “Winter 2025” | not really searchable or sortable, but useful when trying to find courses on a transcript |
Course Calendar System course_system | app_crse_system prompt | the only values are semester and quarter/trimester |
Lab or Lecture course_lab_lecture_format | course_format prompt | lab, lecture, or both are the options; only used for Gen Chem, OChem, and Biology |
Prerequisite Review |
| not currently set up--designed for internal use only; exists on the widget form as a hidden field, but has not been created in this instance |
VMCAS Verified Credits | free text; VMCAS import only | not currently used (VMCAS prereqs, if they were to be imported, are set up tp map to an application scoped entity) |
VMCAS Verified Grade | free text; VMCAS import only | not currently used (VMCAS prereqs, if they were to be imported, are set up tp map to an application scoped entity) |