My first experience of the MyUA Portal portal (since starting Learning 2.0) is that it is unfriendly to my browser. I’m using Konqueror, a browser and file-manager for the K Desktop Environment (KDE) on Linux operating systems. MyUA tells me, “The browser you are using is not supported.” It kindly adds, “You do not need to use a supported browser to enter, but it is highly recommended.” But, really, what the hell does “not supported” mean, if you can still use the site? And why the browser chauvinism?
My main thought while using MyUA is, “Why is this page so busy?” It’s got stuff all over it, and it makes my simple brain ache.
Here’s another thought: Wouldn’t it be nice if it could integrate my MeetingMaker calendar with its other calendar app? Apparently, it “can” — that is, you can go to MeetingMaker, export a date range of events to a file, then upload that file to your MyUA calendar, giving yourself quick access to a static, quickly dated calendar of events. Why not just use MeetingMaker?
My general opinion of the portal echoes that thought. I don’t feel that I need a “seamless” information experience, at least where this kind of information is concerned. I would much rather use MeetingMaker for my appointments, Thunderbird for my e-mail, and Bloglines for my RSS feeds.
I appreciate that OIT wants to create a one-stop experience for my UA-related information, the way Bloglines does with RSS feeds. But it incorporates too much technology that’s not my first choice, with not enough additional useful information to make it worth my while for now.
I have a nagging feeling that I’m not giving it the chance I’m supposed to. But these days I have too many technology pieces on my plate to bother with something that doesn’t seem useful right out of the box.
I played with “groups” and became a member of the Rasmuson Library Database Group (or whatever). It offers an RSS feed, which is swell — however, the MyUA portal seems incapable of rendering that feed’s information in a useful way. Again, I’d rather use Bloglines.