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.

After the allocation algorithm assigns students to projects, the platform opens a report submission window. Assigned students upload a final report document to confirm their participation. The supervising researcher then reviews the report and marks it as approved or rejected. Students who complete the program successfully can generate a PDF participation certificate.

Report submission (students)

Only students with an accepted application (isAccepted = 1) can upload a report. To submit your report:
  1. Go to My Applications and click the accepted project entry.
  2. On the project detail page, use the Upload report form to select your file.
  3. Click Submit. The platform validates the file and saves it.
Reports must be in .docx format (Word document). The platform rejects any other file type. Your report is stored as uploads/reports/{userId}_{projectId}.docx. If you need to replace your report, delete the existing one first using the Delete report button, then upload the new version.
The report submission window is defined by startCreateReportDate and endCreateReportDate in the summer period configuration. Submit your report before the deadline shown on your dashboard.

Report validation (researchers and coordinators)

Researchers (role 4) and coordinators (roles 2 and 3) review submitted reports from the project detail page. Navigate to My Projects, open the relevant project, and scroll to the list of accepted students and their report statuses.

Changing report status

Click Set status next to a student’s report to update it via set_report_status. You can set the status to approved or rejected. The student’s project detail page reflects the updated status immediately.

Validating a report

Click Validate report on the project detail page to run the validate_report action. This confirms that the researcher owns the project and finalizes the report validation. Only the researcher assigned to the project can validate its reports — the platform denies access if the project does not belong to the logged-in researcher.
The report validation window is controlled by startValidateReportDate and endValidateReportDate in the summer period configuration. Coordinate with your students to ensure reports are submitted before the validation window opens.

Certificate generation

Participants who completed the program can generate a PDF certificate of participation. The certificate includes the participant’s full name and, for students and researchers, the title of the associated project.

Who can generate a certificate

RoleEligibility check
Student (5)Student::isEligibleForCertificate() — must have an accepted application
Researcher (4)Researcher::isEligibleForCertificate() — must have a project in the active summer
Campus Coordinator (3)Coordinator::isEligibleForCertificate()
Institutional Coordinator (2)Coordinator::isEligibleForCertificate()
Administrators (role 1) do not generate certificates through this flow.

Generating your certificate

  1. Click Certificate in your dashboard navigation to open the certificate page (showCertificatePage).
  2. If you meet the eligibility criteria, the page shows a Generate certificate button.
  3. Click Generate certificate to trigger the generate_certificate action. The platform invokes CertificateGenerator (located in services/CertificateGenerator.php) to build the PDF and initiates a browser download immediately.
If you do not yet meet the eligibility requirements, the page displays a message explaining that you are not yet eligible. Check back after your report has been validated or your participation has been confirmed.

Build docs developers (and LLMs) love