As Brett mentioned, this project has been mothballed for a while. It is something that needs to be on the radar as a priority ... but given the complexity and scale of the systems that the coding group is working on, they'll need to focus on the events system and then go on to other priorities. Obvisouly, given the good work that Brett has already done on this system, we think it's a very high priority.
In addition to all of the public ways we can expose this data when it's complete, there has also been talk of building a reporting system for academic administrators that would, for instance, build reports out of the data in the system. Say, Publications between (date) and (date) for all professors in such-and-such department.
Something like that would not only assure that professors are properly credited for their contributions, it would compel them to keep content up-to-date.
This app should be authenticated through LDAP, like anything else we do going forward, so that access is as transparent as possible for authorized users.
A blog system is probably a nonstarter, at least if the point is to have the flexibility of a database, along with a recognized schema, behind the data. A blog system is just a sort of limited CMS; too much of the data in a blog system is free-form. To make this truly flexible and to build good data, we need something more structured. (Yes, I know that sounds like a contradiction in terms.)
Robert J Crisler
Manager, Internet and Interactive Media
321 Canfield Administration Building
University of Nebraska-Lincoln