<?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: Overdue Notices</title>
	<atom:link href="http://www.nexpresslibrary.org/overdue-notices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nexpresslibrary.org/overdue-notices/</link>
	<description>A service of the Northeast Kansas Library System</description>
	<lastBuildDate>Thu, 05 Jan 2012 00:16:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sonny Gore</title>
		<link>http://www.nexpresslibrary.org/overdue-notices/comment-page-1/#comment-27</link>
		<dc:creator>Sonny Gore</dc:creator>
		<pubDate>Mon, 08 Sep 2008 22:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.nexpresslibrary.org/?p=270#comment-27</guid>
		<description>Weekly reports rather than daily would be nice. I&#039;d like to know about the status of ALL overdue items both new and old once a week.  That would take care of the redundancy in the daily report that Catherine is talking about, right?  If our reports are for those patrons w/o email, can we have the phone numbers on the report so we don&#039;t have to look it up?</description>
		<content:encoded><![CDATA[<p>Weekly reports rather than daily would be nice. I&#8217;d like to know about the status of ALL overdue items both new and old once a week.  That would take care of the redundancy in the daily report that Catherine is talking about, right?  If our reports are for those patrons w/o email, can we have the phone numbers on the report so we don&#8217;t have to look it up?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smoreland</title>
		<link>http://www.nexpresslibrary.org/overdue-notices/comment-page-1/#comment-25</link>
		<dc:creator>smoreland</dc:creator>
		<pubDate>Mon, 08 Sep 2008 18:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.nexpresslibrary.org/?p=270#comment-25</guid>
		<description>The following Help Request was sent to LibLime this morning.  

Hello,
We need to make a few changes to our overdue list cron job, based on feedback from our member libraries.

1. We would like this job to run weekly, rather than nightly
2. We would like it to include new overdue items or new changes in status
3. Our member libraries would like a .csv file rather than a long text report</description>
		<content:encoded><![CDATA[<p>The following Help Request was sent to LibLime this morning.  </p>
<p>Hello,<br />
We need to make a few changes to our overdue list cron job, based on feedback from our member libraries.</p>
<p>1. We would like this job to run weekly, rather than nightly<br />
2. We would like it to include new overdue items or new changes in status<br />
3. Our member libraries would like a .csv file rather than a long text report</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Catherine Newlan</title>
		<link>http://www.nexpresslibrary.org/overdue-notices/comment-page-1/#comment-24</link>
		<dc:creator>Catherine Newlan</dc:creator>
		<pubDate>Mon, 08 Sep 2008 17:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.nexpresslibrary.org/?p=270#comment-24</guid>
		<description>yes-list should only have NEW overdue items and NEW changes in status.  otherwise it will be very difficult to trac what we have done and should do.  we have decided to call those folks who do not have email addresses for the first two notices.  then send letter for the third [barred] notice.  however, we haven&#039;t mailed any notices yet - we have done some calling.  and we have received replies from patrons who did receive emails.  some saying thanks - they will return the item(s) and some saying gee I thought I did return the item(s).</description>
		<content:encoded><![CDATA[<p>yes-list should only have NEW overdue items and NEW changes in status.  otherwise it will be very difficult to trac what we have done and should do.  we have decided to call those folks who do not have email addresses for the first two notices.  then send letter for the third [barred] notice.  however, we haven&#8217;t mailed any notices yet &#8211; we have done some calling.  and we have received replies from patrons who did receive emails.  some saying thanks &#8211; they will return the item(s) and some saying gee I thought I did return the item(s).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smoreland</title>
		<link>http://www.nexpresslibrary.org/overdue-notices/comment-page-1/#comment-23</link>
		<dc:creator>smoreland</dc:creator>
		<pubDate>Mon, 08 Sep 2008 17:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.nexpresslibrary.org/?p=270#comment-23</guid>
		<description>Hi all,
If a patron has a valid E-mail address, then Koha automatically sends them an overdue.  The list of overdue notices you received is for everyone else.  Everyone who does NOT have an e-mail address.  What we need to decide and work on is what to do with everyone else.  Ideas include, changing the frequency you get a list from daily to weekly, changing the format from a text file to a .cvs file that can be put into a spreadsheet and asking Koha to only include on the overdue list NEW overdue items and NEW changes in status (from slightly overdue to very overdue and from very overdue to barred).</description>
		<content:encoded><![CDATA[<p>Hi all,<br />
If a patron has a valid E-mail address, then Koha automatically sends them an overdue.  The list of overdue notices you received is for everyone else.  Everyone who does NOT have an e-mail address.  What we need to decide and work on is what to do with everyone else.  Ideas include, changing the frequency you get a list from daily to weekly, changing the format from a text file to a .cvs file that can be put into a spreadsheet and asking Koha to only include on the overdue list NEW overdue items and NEW changes in status (from slightly overdue to very overdue and from very overdue to barred).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gwen Battis</title>
		<link>http://www.nexpresslibrary.org/overdue-notices/comment-page-1/#comment-22</link>
		<dc:creator>Gwen Battis</dc:creator>
		<pubDate>Mon, 08 Sep 2008 16:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.nexpresslibrary.org/?p=270#comment-22</guid>
		<description>So, are the notices being automatically mailed to the patrons?  Or do we need to mail them out ourselves?  We are a bit confused also.</description>
		<content:encoded><![CDATA[<p>So, are the notices being automatically mailed to the patrons?  Or do we need to mail them out ourselves?  We are a bit confused also.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy Lassiter</title>
		<link>http://www.nexpresslibrary.org/overdue-notices/comment-page-1/#comment-21</link>
		<dc:creator>Amy Lassiter</dc:creator>
		<pubDate>Mon, 08 Sep 2008 16:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.nexpresslibrary.org/?p=270#comment-21</guid>
		<description>okay, so none of the notices actually went to the patron&#039;s e-mail account this time?  I think I am a bit confused.</description>
		<content:encoded><![CDATA[<p>okay, so none of the notices actually went to the patron&#8217;s e-mail account this time?  I think I am a bit confused.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

