We haven’t posted about any of our projects lately, so let me tell you a bit about some of the things that we do behind the scenes. While plenty of our projects are highly visible, some of them go largely unnoticed and are part of the general university support system.
Every May and December hometown newspapers around the state publish lists of students from that town who have graduated from various colleges. Did you ever wonder how they got that information? For Texas A&M, our office provides that through an application that we call Hometowners (sorry, no links, it is a protected site.) We receive a list of graduates from EIS, and the system matches their home town to a list of newspapers which are published in and around that town. It then emails each newspaper the relevant list of graduates for them to publish.
The Hometowners application has had a rocky existence for as long as I have been in Marcomm. When I arrived it was running on a Windows machine all by itself…because half the time it ran it would throw a fault that was so bad that it killed the machine at the hardware level. That made it one of our first projects — at least making it work well enough that it could be put onto the production server with our other sites.
It stayed in that shape, relegated to a low-priority project, until a few weeks ago. We hired a new student worker and decided that this was the perfect project for her to learn our departmental procedures. She has completely rewritten the application into our newly adopted Yii PHP framework. We have now gotten the application pretty much completed and are in the testing/validation stages.
A few years ago, one of our sister schools in the TAMU System asked if we could share the Hometowners code so that they could use it for their campus. That code base was so specific to the data file that we received from the local campus student information management system (and equally important, it was still pretty broken and too embarrassing to be shown to anyone else) that we couldn’t in good conscience allow them to use it. Now, however, we plan to make it available as part of the general Shared Services model that the system is focusing on to help reduce costs.