I won't copy the whole post, but Meredith Farkas writes at great length about her exploration of and struggle with library subject pages. In light of the introduction of the same topic at our faculty meeting yesterday, I found this very interesting.
http://meredith.wolfwater.com/wordpress/index.php/2007/10/24/the-long-road-towards-subject-guide-20/
~Sarah
Subscribe to:
Post Comments (Atom)
1 comment:
I thought the response below was intriguing -- anyone know what he means by putting "databases in a database"?
I also think making their library site into a wiki is an interesting idea. http://library.williams.edu/
Nick Baker Says:
October 24th, 2007 at 3:51 pm
Hey Meredith, we struggled with the same issues at Williams. Having all our databases in a database helped - we have one link that points to an authority record like yours and another that bounces the user straight to the resource. Since it’s in the database, we only have to make the change once.
You’re also right on about using a wiki. We’ve made our entire site into a wiki, so that any librarian who’s logged in can make changes. If you see a broken link, fix it. If you see an outdated statement, update it. It’s been working really well. I’m not sure what my successor will someday make of the homegrown PHP/MySQL CMS and Wysiwyg editor but it works.
Post a Comment