[Koha-devel] Rewriting the Dev_Week Reserves Updates

[Wagner, Jane]

" Expiration Date: An optional date after which the reserve would be
automatically canceled. This one would be pretty easy."

There is the holdCancelLength syspref -- is that what you're working
with?  Does the code not obey it now?  (Haven't checked...).

We also have some related development in the works (see bug 3474,
http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3474 ) that adds
an expiration date to the reserves once the hold is triggered, then
moves it from reserves to old_reserves if that date passes without the
patron picking up the item.

Jane Wagner
Library Systems Analyst
PTFS Inc.
Content Management and Library Solutions
6400 Goldsboro Road, Suite 200
Bethesda, MD  20817
(301) 654-8088 x 151
jwagner at ptfs.com


-----Original Message-----
From: koha-devel-bounces at lists.koha.org
[mailto:koha-devel-bounces at lists.koha.org] On Behalf Of Kyle Hall
Sent: Friday, September 18, 2009 9:06 AM
To: koha-devel
Subject: [Koha-devel] Rewriting the Dev_Week Reserves Updates

Hey all,
  I'm rewriting my dev_week reserves patch for koha3 and I need some
input on whether certain features I had are truly useful. So here they
are:

Expiration Date: An optional date after which the reserve would be
automatically canceled. This one would be pretty easy.
Set to Lowest priority: When the reserve was set to this it would
always stay at the bottom of the reserves list, even if a new reserve
was added. This one is a bit harder, but still very do-able.

Thanks,
Kyle

http://www.kylehall.info
Information Technology
Crawford County Federated Library System ( http://www.ccfls.org )
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel