| I guess I have three questions here. 1) What happened to the days when universities published their own software, like pine from UW? It seems like Washington of St Louis, which offers a PhD in computer science, should have some students capable of writing a database to run the university. 2) Why have universities not collaborated to develop a modular, expandable system for running a university, instead of putting themselves at the mercy of Workforce, SAS, etc? 3) These same processes were at some point in the past handled on paper, for far less than $16k/student. At what point did the university so lose its organizational competence that the filing system (that's what a database is) ate the budget? |
A common theme is limited or no budget for updating or expanding systems such that the go from "nice" to "acceptable" to "clunky" and then worse.
Politics also becomes an issue. That aged home rolled service might have a palpable price tag to fund a major update for, but once you do discovery and scope every specialized integration made for every department and reality sets in. Whatever path is chosen is going to burn a number of parties, and using a vendor provides a baseline for functionality and a convenient scapegoat
2 - see federated auth via shibboleth, or any number of incommon tech. Or even Kerberos
This stuff exists and often works well, but brings it's own operational maintenance challenges and required specialized skill sets.
3 - only a subset of these processes were handled on paper. expectations on both the timelines and breadth of services have gone up significantly since this was all on paper