<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Looking to Connect: Technical Challenges that Impede the Growth of Virtual Reference</title>
	<atom:link href="http://www.rusq.org/2008/01/06/looking-to-connect-technical-challenges-that-impede-the-growth-of-virtual-reference-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rusq.org/2008/01/06/looking-to-connect-technical-challenges-that-impede-the-growth-of-virtual-reference-2/</link>
	<description></description>
	<lastBuildDate>Sun, 10 Apr 2011 13:16:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: A propos des défis techniques des services de références virtuels &#171; pintiniblog</title>
		<link>http://www.rusq.org/2008/01/06/looking-to-connect-technical-challenges-that-impede-the-growth-of-virtual-reference-2/comment-page-1/#comment-220</link>
		<dc:creator>A propos des défis techniques des services de références virtuels &#171; pintiniblog</dc:creator>
		<pubDate>Sun, 27 Dec 2009 17:07:06 +0000</pubDate>
		<guid isPermaLink="false">http://rusq.org/test/2008/01/06/looking-to-connect-technical-challenges-that-impede-the-growth-of-virtual-reference-2/#comment-220</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] A propos des défis techniques des services de références&nbsp;virtuels    Looking to Connect: Technical Challenges that Impede the Growth of Virtual Reference [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Johnson</title>
		<link>http://www.rusq.org/2008/01/06/looking-to-connect-technical-challenges-that-impede-the-growth-of-virtual-reference-2/comment-page-1/#comment-102</link>
		<dc:creator>Kris Johnson</dc:creator>
		<pubDate>Tue, 22 Jan 2008 17:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://rusq.org/test/2008/01/06/looking-to-connect-technical-challenges-that-impede-the-growth-of-virtual-reference-2/#comment-102</guid>
		<description></description>
		<content:encoded><![CDATA[<p>While I agree that improvements can and should be made to the technical aspects of providing a virtual reference service (and I&#8217;m really looking forward to those improvements and innovations), it continues to concern me that much of our blame for a perceived low use of these services focuses primarily on the software. How can we definitively state that because an &#8220;&#8230;abundant evidence that millions of teenagers and young adults are using commercial chat and instant messaging (IM) services regularly, but that isn&#8217;t translating to the library realm&#8221;? I don&#8217;t understand that logic. It&#8217;s like saying billions of humans use phones, but it just isn&#8217;t translating to the library realm because our phones aren’t ringing off the hooks. What is our benchmark for sufficient usage? And how are you making the service know to your users?</p>
<p>Here at AskColorado we struggle to keep up with demand. We do very little marketing. Use is generated from link placement at participating library websites, library catalogs and databases, and word of mouth. Our primary users (more that 60%) are the same demographic cited as being avid IM users in the article; teenagers.</p>
<p>My main concern is that libraries first need to set benchmarks for sufficient use of any reference service (in-person, phone, e-mail, IM, VR) then assess usage. If you&#8217;re not happy with usage you need to look at how you are making your service available. Can users find the VR service on your website? No? Then you need to make it more visible (&#8216;Goal of Convienence&#8217;.) Try this experiment: Add Live Help links throughout your library&#8217;s website and in your library catalog. Assess usage of the service. If your numbers still do not meet your goals then perhaps you need to assess whether it is the technology preventing usage of your service.</p>
<p>I know it’s not as simple as I’ve explained above. My main point is to caution librarians not to discount a service based on technology alone, without looking at other factors that may impact usage of that service.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

