<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>HCL 2.0 &#187; OPAC of the Future</title>
	<atom:link href="http://blogs.law.harvard.edu/hcl20/category/opac-of-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/hcl20</link>
	<description>\"The Web is unlocked--resistance is futile.\"</description>
	<lastBuildDate>Tue, 11 Sep 2007 19:45:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
		<item>
		<title>OPACS of the Future</title>
		<link>http://blogs.law.harvard.edu/hcl20/2007/05/04/opacs-of-the-future/</link>
		<comments>http://blogs.law.harvard.edu/hcl20/2007/05/04/opacs-of-the-future/#comments</comments>
		<pubDate>Fri, 04 May 2007 16:38:10 +0000</pubDate>
		<dc:creator>hcl20</dc:creator>
				<category><![CDATA[OPAC of the Future]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/hcl20/2007/05/04/opacs-of-the-future/</guid>
		<description><![CDATA[NOTES
There were quite a few sessions devoted to the updating/improvement of library OPACs, but because we are not directly involved with Havard&#8217;s OPAC we only attended a couple.  Highlights follow.

Library OPACS broken in 3 ways: usability, findability, remixability    
Bring OPAC/catalog front and center, don’t hide behind a website
Allow inbound links and [...]]]></description>
			<content:encoded><![CDATA[<p><font size="3"><font face="Times New Roman"><strong>NOTES</strong></font></font></p>
<p><font size="3" face="Times New Roman">There were quite a few sessions devoted to the updating/improvement of library OPACs, but because we are not directly involved with Havard&#8217;s OPAC we only attended a couple.  Highlights follow.</font></p>
<ul>
<li><font size="3"><font face="Times New Roman">Library OPACS broken in 3 ways: usability, findability, remixability    </font></font></li>
<li><font size="3"><font face="Times New Roman">Bring OPAC/catalog front and center, don’t hide behind a website</font></font></li>
<li><font size="3"><font face="Times New Roman">Allow inbound links and link outwards    </font></font></li>
<li><font size="3"><font face="Times New Roman">OLD web site – like a mall, tries to keep users in; NEW web sites link out as much as possible (in the end brings more users back to site)</font></font></li>
<li><font size="3"><font face="Times New Roman">Some universities are already employing RSS feeds to announce new acquisitions    </font></font></li>
<li><font size="3"><font face="Times New Roman">Users don’t want OUR content, they want THEIR content </font></font></li>
<li><font size="3"><font face="Times New Roman">Users don’t want just a book listing, they want information that they can work with&#8211;share, annotate, mashup</font></font></li>
<li><font size="3" face="Times New Roman">The creator of LibraryThing is about to roll out some tools for OPACS</font></li>
</ul>
<p><font size="3" face="Times New Roman"><strong>QUESTIONS</strong></font></p>
<p><font size="3" face="Times New Roman">What can HCL do to encourage the develoment of a facile, user-friendly OPAC?</font></p>
<p><font size="3" face="Times New Roman">How might we encourage ULC/OIS to do some usability testing of student users and use what they learn to inform new developments?<br />
</font></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/hcl20/2007/05/04/opacs-of-the-future/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
	</channel>
</rss>
