Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AngelZurita28/VeranoRegional/llms.txt

Use this file to discover all available pages before exploring further.

A Summer Program record is the central configuration object that governs every time-sensitive action on the platform. All operations — researcher validation, student applications, report uploads, and report validation — are gated by date windows stored in the single active summer record. Only the record with the highest id and status = 1 is used; all other records are ignored at runtime.
Changing any date window takes effect immediately for all users. If you close a window early, researchers and students lose access to the corresponding action until you reopen it.

Active summer record

The Summer model resolves the active period with the following query:
SELECT * FROM summer WHERE status = 1 ORDER BY id DESC LIMIT 1
Only one summer record is active at a time. To rotate to a new program year, set the old record’s status to 0 and create a new record.

Program date fields

Physical program dates

FieldPurpose
summerStartDateFirst day researchers and students are physically present at the host institution
summerEndDateLast day of the program — used as a reference for certificates and reports

Registration window

FieldPurpose
startDateWhen user registration opens for the current summer period
endDateWhen user registration closes

Phase windows

Each workflow phase has an independent open/close window. Outside these windows, the corresponding action is unavailable to all users.
Controls when admins and coordinators can approve or reject researcher accounts for the active summer.
FieldDescription
startValidateResearcherDateStart of the window to validate researcher accounts
endValidateResearcherDateEnd of the window to validate researcher accounts
Controls when students can create and manage their project applications.
FieldDescription
startCreateApplicationDateStart of the window for students to submit applications
endCreateApplicationDateEnd of the window for students to submit applications
Controls when coordinators can accept or reject student applications and run the allocation process.
FieldDescription
startValidateApplicationDateStart of the window to validate student applications
endValidateApplicationDateEnd of the window to validate student applications
Controls when students can upload their final project report documents.
FieldDescription
startCreateReportDateStart of the window for students to upload reports
endCreateReportDateEnd of the window for students to upload reports
Controls when researchers and coordinators can review and approve submitted reports.
FieldDescription
startValidateReportDateStart of the window to validate submitted reports
endValidateReportDateEnd of the window to validate submitted reports

Capacity parameters

These integer fields define the structural limits that apply to all projects and applications in the active summer period.
FieldDescription
pendingResearchProjectsMaximum number of projects a researcher may submit for validation
studentApplicationMaximum number of project applications a student may create (up to 5)
studentPerProjectMaximum number of students that can be assigned to a single project
studentProgressMinPercentageMinimum career progress percentage a student must have to be eligible
The application limit enforced in the platform is 5 — ApplicationController::createApplication rejects a sixth application with an error message regardless of what value is stored in studentApplication. The studentProgressMinPercentage value is compared against each student’s careerProgressPercentage during allocation.

Phase sequence overview

The phases are designed to run in the following order:
1

Registration

Users self-register or are added by coordinators between startDate and endDate.
2

Researcher validation

Coordinators review and activate researcher accounts during the startValidateResearcherDateendValidateResearcherDate window.
3

Student applications

Validated students submit up to studentApplication project applications during the startCreateApplicationDateendCreateApplicationDate window.
4

Application validation and allocation

Coordinators validate applications and run the allocation algorithm during the startValidateApplicationDateendValidateApplicationDate window.
5

Report upload

Assigned students upload their final reports during the startCreateReportDateendCreateReportDate window.
6

Report validation

Researchers and coordinators review and approve reports during the startValidateReportDateendValidateReportDate window.

Build docs developers (and LLMs) love