Ladies and gentlemen: I am pleased to introduce the finest court interpreter management system the world has ever known.
I have been working on this project basically for 20 years. You could say I’m a programmer with a one-project career (so far). The story is that when I started my employment as a federal staff court interpreter in the 1990s, we were running our office with pen and paper, and it was not scaling well. But we could find no software product, commercial or otherwise, that was remotely adequate to our peculiar requirements. Even today there really is nothing else out there, to the best of my knowledge. Anyway: I set about creating our own solution for us with MySQL and PHP. Been working on it – single-handedly – ever since, updating it to keep up with the times (and changing requirements, and lessons learned, and my improving skills). The latest and greatest iteration has a name:
The github repo: https://github.com/davidmintz/court-interpreters-office
The project website (don’t laugh, I know it’s crude): https://interpretersoffice.org.
The app requires authentication in order to do anything interesting, so I can’t really point to a public production website. We do have a demo of sorts: https://demo.interpretersoffice.org.
One more thing: I am soon to retire from my federal court gig, leaving this beast behind. No one in the organization has a clue about this except me. Some hapless IT dudes plan to assume partial responsibility for maintenance, and have encouraged me to create prose documentation. So, I have written a lot of words for https://interpretersoffice.org/documentation, sort of a cross between documentation of the app and a tutorial on Laminas MVC. It is asking way too much to ask you guys to review it – too long, too boring. But if you should happen to skim it and something jumps out at you that you want to comment on, by all means.