<?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: ILS Migration: SirsiDynix and III on exit support and maintenance</title>
	<atom:link href="http://www.parser.ca/z678/2009/02/02/ils-migration-sirsidynix-and-iii-on-exit-support-and-maintenance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.parser.ca/z678/2009/02/02/ils-migration-sirsidynix-and-iii-on-exit-support-and-maintenance/</link>
	<description>systems librarian / information specialist</description>
	<lastBuildDate>Mon, 30 Aug 2010 23:07:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Peter Ivanick</title>
		<link>http://www.parser.ca/z678/2009/02/02/ils-migration-sirsidynix-and-iii-on-exit-support-and-maintenance/comment-page-1/#comment-165</link>
		<dc:creator>Peter Ivanick</dc:creator>
		<pubDate>Mon, 02 Feb 2009 22:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.parser.ca/z678/?p=75#comment-165</guid>
		<description>Ours was signed in &#039;99 (and I wasn&#039;t here, either) but we came up on Millenium. But in looking over our contract from then, it doesn&#039;t look to me like it&#039;s explicitly stated one way or another, although my reading would be that indeed we could hang onto the software w/o maintenance if we chose to.

I would of course get our University General Counsel to take a look at it before I proceeded, and I could just be plain wrong in our case.  I wonder if they changed the contract between &#039;99 and &#039;02?</description>
		<content:encoded><![CDATA[<p>Ours was signed in &#8217;99 (and I wasn&#8217;t here, either) but we came up on Millenium. But in looking over our contract from then, it doesn&#8217;t look to me like it&#8217;s explicitly stated one way or another, although my reading would be that indeed we could hang onto the software w/o maintenance if we chose to.</p>
<p>I would of course get our University General Counsel to take a look at it before I proceeded, and I could just be plain wrong in our case.  I wonder if they changed the contract between &#8217;99 and &#8217;02?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: parser</title>
		<link>http://www.parser.ca/z678/2009/02/02/ils-migration-sirsidynix-and-iii-on-exit-support-and-maintenance/comment-page-1/#comment-164</link>
		<dc:creator>parser</dc:creator>
		<pubDate>Mon, 02 Feb 2009 19:19:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.parser.ca/z678/?p=75#comment-164</guid>
		<description>I wasn&#039;t employed here at the time, however, it was originally signed around 1992. Contract has been renewed annually since then. 

I came on board around 2002, just before our required upgrade to Millennium. A very expensive upgrade indeed - it was like &quot;buying&quot; the ILS all over again.</description>
		<content:encoded><![CDATA[<p>I wasn&#8217;t employed here at the time, however, it was originally signed around 1992. Contract has been renewed annually since then. </p>
<p>I came on board around 2002, just before our required upgrade to Millennium. A very expensive upgrade indeed &#8211; it was like &#8220;buying&#8221; the ILS all over again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Ivanick</title>
		<link>http://www.parser.ca/z678/2009/02/02/ils-migration-sirsidynix-and-iii-on-exit-support-and-maintenance/comment-page-1/#comment-163</link>
		<dc:creator>Peter Ivanick</dc:creator>
		<pubDate>Mon, 02 Feb 2009 19:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.parser.ca/z678/?p=75#comment-163</guid>
		<description>Good points all. I&#039;m curious when your site signed your III agreement?</description>
		<content:encoded><![CDATA[<p>Good points all. I&#8217;m curious when your site signed your III agreement?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
