Preapplication Administration and Processing
This page covers specifications and tasks for the preapplication processing phase (May 15 thru June 2). At the end of this phase, Quest will deliver CD's containing selected applications (PDF format) and a spreadsheet of candidates to partner colleges.
Milestones
Date |
Task |
Responsible |
|---|---|---|
4/25 |
Print out HTML "preview" of preapp and determine requirements for PDF generation |
Quest |
5/12 |
Review student record and current draft Student "view contact" page and create spec / mockup of desired view and listings screens. |
Quest |
5/12 |
Create Profile on sandbox for Student search listings and review w/ appropriate Quest staff. |
Quest |
5/15 |
Last day for application completion. |
Quest |
5/16 |
Applicant review period begins. New (trunk) admin functionality for search, listings and flat export should be available to Quest staff (see tasks / issues below). |
Quest/CiviCRM |
6/1 |
PDF Generator function and Hierarchical Data export (XML) function and script(s) to invoke them are ready for use by Quest staff |
CiviCRM/Quest |
6/1 |
Quest begins receiving faxed transscripts and testing documents. Hopefully can "upload" these to CiviCRM so that student records have "pointers" to the "attached" docs (see issue noted below regarding data model). |
Quest/CiviCRM |
Bugs / Issues for Applicant Review Phase
- On HTML Preview: Testing Info section is missing last question, 'If yes for which test?' (CiviCRM)
- Add cookie crumb page element to quest theme for back-end (CiviCRM) pages. (Paras)
- Need a way to segment students w/ completed pre-app from those who didn't complete. Completed. Run bin/assignContactToGroup.php from command line. This script assigns students to either Preapp Completed or Preapp Not Completed group. It can be run multiple times if student statuses are changing. (CRM-960).
- Expose all Student record fields in Export -> Select Fields for Export. Completed (CRM-951).
- Option value fields in search results rows are displaying the KEY not the VALUE (e.g. 168 instead of 3.5 for GPA, etc.). Completed (CRM-804).
- Expose application task status on Contact view. Completed (dgg).
- Contact view not using Student.tpl in latest trunk rev. (resolved as of r5380)
- Add conditional navigation ("Back to Branner") to pre-app header when app is accessed from CiviCRM "back-end". Also display app status. (resolved as of r5381)
- I've created an Export mapping but when I go to export the data again, I can't select my export mapping. I need to re-enter the fields I want to export. Can not replicate.
Excel export for Reviewing ApplicantsÂ
Paras has requested that we allow the following additional fields to be selected/included in Exports. These fields are NOT stored in the quest_student record.
The Excel export should include:
- 'Have you received tutoring or taken test prep classes for any of the standardized tests above?' (Testing Information section). (This field is available as of Friday 5/12 rev.)
- AP Test Data - Subject, Score, Date for up to 5 tests, sort by date descending.
- PSAT Test Data - Total (already available), Math, Reading, Test Date.
- SAT Test Data - Total (already available), Math, Reading, Test Date.
- PLAN Test Data - Total (already available), English, Math, Reading, Science, Test Date.
- ACT Test Data - Total (already available), English, Math, Reading, Science, Test Date.
Tasks for Applicant Review Phase
- Provide list of anticipated attachments (e.g. transcripts, test results, tax returns...) throughout annual cycle (Quest) - so that we can determine the correct data model for storing attachment pointers (CiviCRM) - e.g. custom fields (type=file) vs. Student record additions.
- Official Transcript
- Official Test scores (ACT, SAT, SATIIs)
- Tax Returns (ALL pages)
- W2s
- NCP (Non-custodial profile) form: each school might have their own version of this form
- Other school specific forms
- Modify permission for Student role to remove Edit Application permission at end of day on 5/15. (Quest)
- Determine best way of exposing trunk functionality to Quest admins w/o impacting stability of production servers for public (student) access. (CiviCRM)
- Define needed "tags" for marking Award Recipients and add to production DB (while cleaning up sample tags). Completed. Using custom fields. (Quest)
PDF Generation
- CiviCRM will create a function which can be invoked via command line or ... which will generate PDF output based on the provided PDF template - for a specified contact ID.
- Each Application step should start on a new page (we think this is encoded in the template).
- If possible, empty sub-sections should be omitted.
NOTE: One approach to avoiding empty sub-sections in the PDF is to divide the template into files for each section. Then have the generator function take both the contact ID and the desired section. Using this approach, a master PHP script could loop through a given student record generating sections/sub-sections as needed for a particular student's data. The assumption is that the script could then call some other function (in PDFLib?) which would merge the generated sections into a single PDF file.
Hierarchical (Complete) Data Export
- CiviCRM will create a function which can be invoked via command line or ... which will generate XML output representing all contact and student data for a specified contact ID.
- Quest is responsible for scripting the invocation of this function as needed, and converting the XML to Excel Worksheets.
Specs for Student Listings and Contact View Pages
(TBD)
Additional "sub-tasks" for Pre-application
(TBD)
