A Poor Man’s Portal
May 14th, 2007
In large institutions, the varying audiences of the website can cause it to pull and stretch in ways that can make the web staff cringe. Site navigation suffers most in this continuous battle to please the on-campus constituents at the risk of alienating your external audiences. Most colleges and universities have moved over to a faceted navigation, allowing prospective students easy access to admissions and residential life while still providing effective information to the news media, donors, alumni and current students. But all is not well with the staff and faculty jump-pages in most instances.
Staff and faculty usually have very strict data silos, and are often quite demanding of having information at their fingertips matching their department’s organization. These users won’t touch your jump pages because they are too generic and don’t meet their needs. Perhaps a universal portal system could take care of this, personalizing the content for the individual; however, these systems are costly and time consuming to build and tailor to faculty and staff needs in a day where student services are the only items on the budgetary menu. The answer is simple: create static department portal page (aka a Poor Man’s Portal).
What do I mean when I say static department portal page? It’s simple, create a basic HTML document that can be housed on a web sever or file share that points to exactly what members in a data silo need. Have them set it as their homepage, so any time they need answers they just pull up a web browser.
The information desk, or admissions office is an ideal candidate for such a simple solution. Every day the staff and student workers answer phone calls with highly creative questions about diverse facets of the institutions policies, people, and programs. One of these static departmental portal homepages in an admissions office could offer a quick redirect to Residential Life room rates, the Registrars Office policy on in-state residency, and scholarships for minorities.
With a couple questions to the staff, and 10 minutes of a web developer’s time, an entire department can have in place a portal that is just as functional as one that would cost many thousands of dollars to implement, and you could even include an email/Citrix/SharePoint login form too. For a 10 minute job, this will save tons of time for those on the front line while providing faster and better support to your students-talk about a return on investment.
If it meets the needs of a large portion of your staff, it could serve as a messaging platform (perhaps most useful with work-study students, who aren’t on the office distribution list.)
I’ll be implementing this type of a project for my admissions office some time soon. I’ll post a follow-up after I see how well it actually works.
the shirts from 