Using RSS feeds at work. Or not.
So we use this electronic document management system. It's a document repository, it allows for version control, and it we use it to electronically review/approve/sign documents.
Right now you use this thing called a Change Request to route a document for review/approval. The CR screen has all the info about that document and the routing (signers, dates, times, etc.).
I had this great idea a while back that they should have RSS feeds for each CR, so you could see what activity there has been on it. I'm most interested in who signs it and when. I don't like to have to keep refreshing that screen -- for each of the many CRs I usually have at any given time -- to see who I need to pester about reviewing something if we're in a hurry.
I mentioned this to the IT project manager. I don't think he knew what I meant by RSS feed. He referred me to someone who I think was a database specialist. She might have been a programmer, I don't know. We don't really have a need to keep programmers around. I knew the chances of it actually happening were slim anyway, but I thought I'd bring it up just to see what he said. No surprise it didn't go anywhere.
I thought it was a good idea anyway.
0 TrackBacks
Listed below are links to blogs that reference this entry: Using RSS feeds at work. Or not..
TrackBack URL for this entry: http://www.swirlspice.com/mt4/mt-tb.cgi/8078

It's a darn good idea. I proposed something similar where I work, to cover unexpected updates to existing documentation, open to the public so they won't have to call in and ask about them. The looks I got all said the same thing: "You can do that?"
Oh, see, that's great. It may not get you out of still having to mail out notifications, but yeah. That'd be something I'd subscribe to.
CR's ... EDMS ... You poor poor sole. :p