<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Instant Messenger Or Virtual Reference?</title>
	<atom:link href="http://maisonbisson.com/blog/post/11143/instant-messenger-or-virtual-reference/feed" rel="self" type="application/rss+xml" />
	<link>http://maisonbisson.com/blog/post/11143/instant-messenger-or-virtual-reference</link>
	<description>A bunch of stuff I would have emailed you about.</description>
	<pubDate>Thu, 24 Jul 2008 20:24:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: jade</title>
		<link>http://maisonbisson.com/blog/post/11143/instant-messenger-or-virtual-reference#comment-193524</link>
		<dc:creator>jade</dc:creator>
		<pubDate>Thu, 01 May 2008 11:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=11143#comment-193524</guid>
		<description>iyahh use all okiieh 
eeverythin is blcoked 
ARGHHHHH tell me summert for msn 
and my syt is defo not finished
xx</description>
		<content:encoded><![CDATA[<p>iyahh use all okiieh<br />
eeverythin is blcoked<br />
ARGHHHHH tell me summert for msn<br />
and my syt is defo not finished<br />
xx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bajram</title>
		<link>http://maisonbisson.com/blog/post/11143/instant-messenger-or-virtual-reference#comment-131841</link>
		<dc:creator>bajram</dc:creator>
		<pubDate>Wed, 13 Dec 2006 07:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=11143#comment-131841</guid>
		<description>I have to install web mesenger</description>
		<content:encoded><![CDATA[<p>I have to install web mesenger</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caleb t-r</title>
		<link>http://maisonbisson.com/blog/post/11143/instant-messenger-or-virtual-reference#comment-32114</link>
		<dc:creator>caleb t-r</dc:creator>
		<pubDate>Fri, 24 Feb 2006 02:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=11143#comment-32114</guid>
		<description>Casey, I love it when you make my library technology fantasies into reality, but not so much that I won't call you out here.

There is no doubt there is a huge opportunity to reach out to instant-messaging using patrons. Web-based chat offers a greater opportunity to reach out to the rest of the internet users - if the reason to offer IM services is because people are already using those tools, there are more than twice as many people with web browsers than there are with screen names (http://www.pewinternet.org/pdfs/PIP_Instantmessage_Report.pdf).

I think the failure of some libraries to successfully implement web-based chat reference services is an example of libraries taking a wrong approach to technology and online services, not that web-based chat (vis a vis IM) is a mistake. 

Failed services may have been poorly managed to begin with. Some libraries may not have had any experience implementing web-based services at all. What went wrong? Was there staff buy-in? Did they look at server logs to see how many of their patrons would have compatible browsers? How about focus groups to see who was interested? Was the service piloted? Did the library market the service? What was the criteria for success? yadda-yadda.

Embracing and implementing services that rely on decaying technological conditions (co-browsing! works great with Netscape 4.7 on Windows 95!) was one of the bigger mistakes, but it certainly isn't one exclusive to co-browsing applications. 

Not that it's an ideal approach, but I think libraries as a whole are doing a much better job letting patrons know about requirements for downloading audio books than we ever did warning them about browser requirements for web-based chat.

In contrast, I think IM has been successful in libraries because it doesn't *need* a whole lot of management, other than being diligent about setting the away message. 

Insofar as things that work in libraries are easy for staff to implement, IM doesn't have to suck on human resources the way web-based chat can, tying librarians to desks, contracting for 24/7 service.

Yet, with all of web-based chat's failures, IM services haven't come close to their successes. Or else, show me an IM service that took on &lt;a href="http://www.knowitnow.org/enews/summer2005.pdf" rel="nofollow"&gt;100,000 questions&lt;/a&gt; in it's first year (not us, we took only got about 5,000). 

I'm a fan of IM for reference service, and am encouraging local libraries to offer it, but the insistence that IM is the right and only way to offer chat virtual reference has got to stop.

p.s. my thesaurus:

virtual reference
 used for digital reference
 narrower term chat reference
 narrower term web-based chat
 narrower term instant messaging reference
 narrower term text-messaging reference
 narrower term e-mail reference
 narrower term blog-based reference
 broader term reference
 broader term public service
 related term co-browsing</description>
		<content:encoded><![CDATA[<p>Casey, I love it when you make my library technology fantasies into reality, but not so much that I won&#8217;t call you out here.</p>
<p>There is no doubt there is a huge opportunity to reach out to instant-messaging using patrons. Web-based chat offers a greater opportunity to reach out to the rest of the internet users - if the reason to offer IM services is because people are already using those tools, there are more than twice as many people with web browsers than there are with screen names (http://www.pewinternet.org/pdfs/PIP_Instantmessage_Report.pdf).</p>
<p>I think the failure of some libraries to successfully implement web-based chat reference services is an example of libraries taking a wrong approach to technology and online services, not that web-based chat (vis a vis IM) is a mistake. </p>
<p>Failed services may have been poorly managed to begin with. Some libraries may not have had any experience implementing web-based services at all. What went wrong? Was there staff buy-in? Did they look at server logs to see how many of their patrons would have compatible browsers? How about focus groups to see who was interested? Was the service piloted? Did the library market the service? What was the criteria for success? yadda-yadda.</p>
<p>Embracing and implementing services that rely on decaying technological conditions (co-browsing! works great with Netscape 4.7 on Windows 95!) was one of the bigger mistakes, but it certainly isn&#8217;t one exclusive to co-browsing applications. </p>
<p>Not that it&#8217;s an ideal approach, but I think libraries as a whole are doing a much better job letting patrons know about requirements for downloading audio books than we ever did warning them about browser requirements for web-based chat.</p>
<p>In contrast, I think IM has been successful in libraries because it doesn&#8217;t *need* a whole lot of management, other than being diligent about setting the away message. </p>
<p>Insofar as things that work in libraries are easy for staff to implement, IM doesn&#8217;t have to suck on human resources the way web-based chat can, tying librarians to desks, contracting for 24/7 service.</p>
<p>Yet, with all of web-based chat&#8217;s failures, IM services haven&#8217;t come close to their successes. Or else, show me an IM service that took on <a href="http://www.knowitnow.org/enews/summer2005.pdf" rel="nofollow">100,000 questions</a> in it&#8217;s first year (not us, we took only got about 5,000). </p>
<p>I&#8217;m a fan of IM for reference service, and am encouraging local libraries to offer it, but the insistence that IM is the right and only way to offer chat virtual reference has got to stop.</p>
<p>p.s. my thesaurus:</p>
<p>virtual reference<br />
 used for digital reference<br />
 narrower term chat reference<br />
 narrower term web-based chat<br />
 narrower term instant messaging reference<br />
 narrower term text-messaging reference<br />
 narrower term e-mail reference<br />
 narrower term blog-based reference<br />
 broader term reference<br />
 broader term public service<br />
 related term co-browsing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Standards Cage Match &#171; MaisonBisson.com</title>
		<link>http://maisonbisson.com/blog/post/11143/instant-messenger-or-virtual-reference#comment-32087</link>
		<dc:creator>Standards Cage Match &#171; MaisonBisson.com</dc:creator>
		<pubDate>Thu, 23 Feb 2006 15:23:02 +0000</pubDate>
		<guid isPermaLink="false">http://maisonbisson.com/blog/?p=11143#comment-32087</guid>
		<description>[...] Final example: it&#8217;s pretty obvious to all of us now that chat reference should be done using common and freely available IM tools, but that didn&#8217;t stop us from investing huge sums of money in building and buying custom, library specific chat reference tools. Where else will history show we&#8217;ve made similar mistakes? [...]</description>
		<content:encoded><![CDATA[<p>[...] Final example: it&#8217;s pretty obvious to all of us now that chat reference should be done using common and freely available IM tools, but that didn&#8217;t stop us from investing huge sums of money in building and buying custom, library specific chat reference tools. Where else will history show we&#8217;ve made similar mistakes? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
