<?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: Database Descriptions</title>
	<atom:link href="http://lib.byu.edu/sites/news/2006/12/18/database-descriptions/feed/" rel="self" type="application/rss+xml" />
	<link>http://lib.byu.edu/sites/news/2006/12/18/database-descriptions/</link>
	<description>Just another Lib.byu.edu weblog</description>
	<lastBuildDate>Sat, 06 Mar 2010 00:13:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jeff Belliston</title>
		<link>http://lib.byu.edu/sites/news/2006/12/18/database-descriptions/comment-page-1/#comment-83</link>
		<dc:creator>Jeff Belliston</dc:creator>
		<pubDate>Mon, 18 Dec 2006 22:07:23 +0000</pubDate>
		<guid isPermaLink="false">https://blog.lib.byu.edu/wwg/?p=15#comment-83</guid>
		<description>The idea of getting Subject Librarians to update database descriptions is a good idea. However, there is the issue that some of these databases are used by more than one Subject Librarian who is likely to want to emphasize something particular. How do you address this if every Subject Librarian can modify a database description? It occurs to me that multiple descriptions might be available for the same database with a &quot;generic&quot; or &quot;default&quot; description available to any Subject Librarian who did not want to modify a particular description. It seems to me that the database sponsor would be a good choice for writing the default description. If this is deemed unworkable, then Subject Librarians would have to work cooperatively to agree on a description for the database.</description>
		<content:encoded><![CDATA[<p>The idea of getting Subject Librarians to update database descriptions is a good idea. However, there is the issue that some of these databases are used by more than one Subject Librarian who is likely to want to emphasize something particular. How do you address this if every Subject Librarian can modify a database description? It occurs to me that multiple descriptions might be available for the same database with a &#8220;generic&#8221; or &#8220;default&#8221; description available to any Subject Librarian who did not want to modify a particular description. It seems to me that the database sponsor would be a good choice for writing the default description. If this is deemed unworkable, then Subject Librarians would have to work cooperatively to agree on a description for the database.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

