As I was reviewing the blog and putting up my post about my new guitar build project, I realized I forgot to talk about two more PowerSchool plugins I published on PowerSource.
PowerSchool’s student contacts permit some detailed information about contacts associated to a student, but lacks any meaningful automated validation with the “Lives With” flag. This is, of course, a natural constraint as a student can live part time with one parent and another, even if their designated home addresses don’t match (to avoid sounding like I’m criticizing PowerSchool here).
This plugin compares a student’s address to the addresses of contacts claimed to be living with the student. If the addresses don’t match within a large percentage, an alert icon appears to signal a need for review of both the student’s address in Addresses or General Demographics pages or the contacts themselves.
It could be a simple misspelling or order of the components of the address (123 Main Street East versus 123 E. Main). Or it could be a custodial arrangement, but not everyone may be aware of it.
Download from PowerSource.
Publish a directory of links to parents or students or both, at either the district level or school level. Manage them in the admin panel and enable or disable as needed.
Available on PowerSource.
Plugin #2 is out on PowerSource. Like the Medical Alerts visual enhancement, this adds some additional icons under the student header in the admin portal to visually indicate whether extra attention should be drawn to the guardian page.
This initial version will include blue icons for the existence of a restraining order and whether an adult should have limited contact with a student.
I wrote and published my first plugin for PowerSchool. It adds some custom alert icons to a student page in both the admin and teacher portals to show specific medical conditions. These are managed in the admin portal on the Emergency/Medical page.
Available for download on PowerSource.
Our English Language Development department wants to track students who are considered “former English learners” in Illuminate. The criterion is if they’ve been exited from the EL program within the last four years. This requires a few preparations.
First, set the code within Illuminate to display the former EL status. I just chose the next one available. I’ll use this variable in my SQL script, which comes next.
From the cog, choose Code Management
Look for English Proficiency. I just start typing “english,” and it appears:
Then add the new code. In our case, plain number 6 was the next available one. I have to remember this value:
Next, I need to edit studemo.sql on the server where the SQL extract scripts are installed. These are the scripts that build queries from the PowerSchool database, assemble the files, and then SFTPs them to Illuminate’s server.
The column that provides English proficiency status is column 14. For that column, I use a CASE statement:
case when (sc.flaglep = 1) then 3 when (sc.lepexitdate > to_date('6/15/'||to_char(extract(year from sysdate)-4),'mm/dd/yyyy')) then 6 else null end
The prefix sc refers to an alias for our state reporting code. PowerSchool users outside of Michigan may have different column names. Walking through this CASE statement, here’s what I’m saying:
- If the “is an English learner” checkbox is marked, the value is 1 in the database, so I want to return the value of 3 to send to Illuminate (note in the screen shot above of the code table, where 3 indicates “English Learner”).
- If the EL exit date is greater than a date of June 15 of the year that’s 4 earlier than the current system date, then return a 6.
- Otherwise, return nothing
So the possible output values will be 3, 6, or nothing. This is proven when looking at studemo.txt in Excel:
Once uploaded to Illuminate, this value can then be used in filters for reports, student groups, and assessments: