We’ve opened up commenting on our Library Blogs platform so that non-McGill users can also post comments to our blogs.
Anyone who can’t login to the site with McGill credentials can click on the Register Now link on the login page and quickly create an account. We’ll send you an email with a link to click to confirm your registration (and help assure us that you are indeed a human and not a robot), provide you with a password (and instructions on how to reset it), and you’re good to go!
We’re soft-launching this feature today. We’ve done some internal testing of the features, but wouldn’t mind getting some feedback from a few outside folks. If you are so inclined, please scroll down to the comments section, follow the instructions for logging on, and once you are successful, leave a comment on this post with your feedback.
If for some reason you are not able to complete the registration process, please let me know via email at email@example.com and I’ll look into it.
One of my goals for the coming year is to implement a new internal blog for the McGill Libraries, a space that will make it easy for news and information to be shared within and between the different branches and units that make up the Library.
We currently have a staff blog that is running on a WordPress installation administered by central IT. The blog is private, meaning that you have to login and be authenticate as a member of the Library staff to be able to access the blog.
The requirement to keep the information private makes it harder to share the information and get it out to everyone who needs to see it. RSS is essentially useless, since you can’t authenticate with popular newsreaders such as Google Reader. Yes, there is a proposed workaround with Internet Explorer and Outlook that on paper seems to allow you to subscribe to an RSS feed that requires authentication, but in my experience, the setup process is very cumbersome and doesn’t really work anyway.
To get around this, every Monday I manually compose and send out an email digest of new posts to the staff blog. Here again, the need for privacy gets in the way. I always include direct links to articles in my email message. However, when a user clicks on the link they are prompted to login, at which point they are taken to the home page and not the blog post they were interested in.
Before I start to dig into this problem, I though I would ask for advice/pointers from other folks who have tackled this problem to narrow down my field of research. Have you implemented internal blogs and how have you addressed the RSS/authentication issue?