January 15, 2004
Hmm, is there a meta category?
So, I've committed to undertaking a couple CNTV-IMD web related projects during the upcoming year and would be interested in getting some feedback on what types of site improvement/collaborative tools would be useful...
The three main things I'm planning on working on this semester is:
- Improving the IM blog
- Calendar sharing
- Knowledge Base tool
I'm open, however to spending time working on other things if anyone thinks there's a big need. Would be interested in hearing what kind of collaboration tools would be most useful to the CNTV-IMD community.
Hmm, so I'll just hit each of these points separately. Since the IMblog has been pretty neglected, now that I have some time I'm just going to start working on improvements (unless anyone has any objections).
Most of these changes can be seen in a comp that Scott asked me to do last summer:
- 'Last Updated' blogroll - I just implemented a preliminary version on the left column of my IMblog. Basically, allowing one to see at a glance when a blog has been recently updated. Good for those who aren't using feed-readers/notification services; Hopefully, this will make it easier to keep up with what everyone's writing.
- Multi-blog aggregation - the idea here is instead of posting multiple posts into say class blogs, the front page blog, etc., everyone can just post into their own blog, and then select (my feeling is that this can simply be done by category mapping) which other blogs they wish their posts to go to. What's fun about this is that in theory, all kinds of groupings could be done, like say a '1st year' or '2nd year' blog, and of course that changes will propagate and everything's all well normalized.
- Various MT plugins. Say, better text entry via MT-Textile or Smarty Pants, and something like MTThreadComments for better commenting.
- Blogs are good for entering into, not as good for reading en-masse, keeping up on comments, etc within a community. If there's time/motivation, I may try dinking on some ideas I have on improving those aspects.
I've been giving a lot of thought to the pubsub calendaring problem. The main problem is that there's no industry standard for calendar synchronization (the closest is SyncML/Jabber w/ xCal, but it's all pretty much dead in the water). Without a real way of things to talk to each other, we're left with some almost-there solutions. But, something is probably better than nothing.
- pub/sub iCalendars - thanks primarily to Apple, uni-directional calendar publishing and subscription (WebDAV, HTTP) has made some headway. Besides iCal, both Mozilla Calendar and Evolution support this now, so in theory every platform is covered. Sync everything up to phpMyCal, write some custom handlers with separate 'entry' and 'subscription' calendars, and you have an 80% solution
- thoughts? can continue discussion offline if anyone has anything substantive to add. there are certain tricky issues with all of this, especially with handling event editing, clearing the entry calendars, etc
Umm, my fingers are tired... I'm probably not going to get around to working on the KB tool until the summer or later anyway, but the basic idea is to create segmentable, multi-faceted, semi-self-organizing graph structures. Oh, that will be as easy if not easier to enter data into than blogging.
Posted by leonard at January 15, 2004 10:47 PMComments
leonard. this all looks good. I think we should maybe try and implement a version of your (im) blogroll on the main page. I think maybe ditch the 'viewpoints on interactivity' thing, or make it more circumscribed, and then add some more info about recent posts. also, we'd probably want to have a rule that only allowed new posts from people to be shown. i.e. if I posted something on 1/15, it would show up on the main page on 1/15-1/20 if I didn't post anything else -- it would be considered 'current'. However, once 1/20 rolled around, and I hadn't posted anything new, I would be left off the 'current posts' roll.
Posted by: William Carter at January 15, 2004 11:56 PM
i like these ideas. the calendar is less critical to me, but thats just how i work personally.
the mockup i like. i think to introduce the shorter categories you list towards the left, we will have to limit the input somehow, so they dont get all huge and bloated. but i know thats a no brainer.
im not a fan of the dhtml drop down 'last updated' bit. i want last updated and will and i worked on it some last semester, sadly, we couldnt get it to work. (i just dont have mt experience.) i thinkt hey way its mocked up, it looks sharp. i think once you have about...40 people on that list, its going to be a nightmare.
perhaps a solution in the middle is this: list those that have posted since your last visit to the site automagically, the rest in teh drop down (though the drop down adds almost nothing, as you wont put any content under where the menu would drop anyway. and the idea of rearranging the list based on posting freq is a nightmare too.) you thoughts?
other than that, from a usability/practical point of view, i think its nice. and i think with a few more tools, the site will be well on its way.
Posted by: tripp at January 16, 2004 12:50 PM
Right now, we have about 30 people on the 'faceroll' on the homepage. I think having multiple views (defaults to last updated, by current group (2nd years, 1st years, staff/faculty) might make sense, with a cookie that will store both your pref and last visit (for new post highlighting).
The DHTML bit was basically an idea to figure out how to best scale w/ the # of people, or to allow multiple views simultaneously or show posts, but that may be unnecessary.
Another feature that might be interesting is latest comments... That could easily just fit in as another block.
If you're interested, you can check my 1/14 post at http://randomfoo.net/ and see what I did. The MT part was trivial, but working w/o SQL subselects was a slight PITA, still only an hour or two's work. Because MT defaults to baking not frying (and using mt-view.cgi is sorta messy and inefficient), I think I'll be moving the last updated into straight PHP code. It's too cumbersome to have to keep republishing to debug anyway.
Posted by: leonard at January 16, 2004 07:27 PM
Hi Leonard,
Do you have a preferred method for incorporating external RSS feeds into MT? I/We are running both MT and pMachine, and pMachine has a dead-simple XML parser built in with a single tag for putting feeds wherever you want within your .php page. It appears as though MT needs some external help. I looked at zfeeder. Any others, or do you roll your own?
thx,
Todd
Posted by: todd at January 30, 2004 02:14 PM

