[Koha-devel] Notifications RFC

[Elliott Davis]

Jesse,

In response to your first question, it will correspond directly to the collection codes that are currently in koha.  Essentially what I would like to do is give users another dimension of control when defining overdue rules.  For example, If I have 10 items with the collection code of “media” then I would like to set a blanket rule for “media” instead of having to set a rule for each separate item.

The thing I really want to get changed on the backend is the 3 notification limit.  Currently for our ILL’s we send out notices every day until the end of time or until the book is returned.

Let me know if that makes sense or if I am totally crazy.

Elliott Davis

From: Jesse [mailto:pianohacker at gmail.com]
Sent: Thursday, August 25, 2011 2:00 PM
To: Elliott Davis
Cc: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Notifications RFC


2011/8/25 Elliott Davis <tdavis at uttyler.edu<mailto:tdavis at uttyler.edu>>
Hey Guys,

I have noticed of late that notifications is in quite a state of disarray.  At my library we have had to resort to running queries from a script and manually sending out mail because notifications just don’t work in a usable way.  I am proposing an overhaul of the notifications system.  The only information I have to go on is what my library wants but since we are an academic library that may vary from what the vast majority of Koha wants.  Before I made an official wiki for this RFC I wanted to get a general feel for how everyone felt about this.  I also wanted to see if someone or a group was willing to pitch in and help me out with some coding.

Essentially what I would like to do is model notifications to do the following:


1.       Base notification rules on patron type, item type, and a new grouping I am hoping to write that I am calling the collection code
This sounds like it's a bit up in the air at the moment, but how does this relate to the item collection codes that are already in Koha?

2.       Define a frequency for notifications based on the previously stated groupings

3.       Base the start time and end time for notifications on the due date rather than the checkout date

I am very open to other suggestions and I hope to get some.  I know that this idea is far from fully developed.

Best,

Elliott Davis

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org<mailto:Koha-devel at lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Everything else sounds good. The notifications backend is pretty good, really, but the UI at least needs some love and updates.

--
Jesse Weaver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/3bade025/attachment.htm>