Over the past few months, about end of October-ish, minus december, I've been working on a scheduler for calls. I call it a call scheduler, but it's not there yet, it can schedule calls, but that functionality is not ready, so I won't demo that today. Hopefully next presentation, whenever that may be.
This "call scheduler" is really right now a "call explorer" where you give it a lot of monthly schedules, and then it gives you the tools to explore the data. I've been testing it with our own call schedule going back to beginning of 2019 academic year until March 2021. So, this would be too much data for a human to analyze at once and try to make sense of the nuancces which means it's a perfect fit for a computer - mundane, repetitive, analytical work.
Before we move any further, at this time, this project is a proof of concept. A way for me to get feedback, and to make sure it's actually feasible, and that it's something that's useful to the program and residents.
Which brings me to my next point, this project is mainly geared for residents. That's the population I have in mind, but I've architected it as a generic solution to the daily scheduling problem, and so nothing should stop its use in other venues, like attending call scheduling for example.
Just to reiterate, it has a long way to go, so please don't be disappointed by what you see today.