http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9296
Bug ID: 9296
Summary: overduerules table needs restructuring to allow future
extension
Classification: Unclassified
Change sponsored?: Sponsored
Product: Koha
Version: master
Hardware: All
URL: http://intranet/cgi-bin/koha/tools/overduerules.pl
OS: All
Status: ASSIGNED
Severity: enhancement
Priority: P5 - low
Component: Architecture, internals, and plumbing
Assignee: [email protected]
Reporter: [email protected]
The overduerules table almost hard-wired to three standard notices, with fields
like delay1, delay2, delay3. I want to expand it in the future, so I plan to
change it to the following:
CREATE TABLE `overduerules` ( -- overdue notice status and triggers
`overduerules_id` mediumint NOT NULL AUTO_INCREMENT,
`branchcode` varchar(10) NOT NULL default '', -- foreign key from the
branches table to define which branch this rule is for (if blank it's all
libraries)
`categorycode` varchar(10) NOT NULL default '', -- foreign key from the
categories table to define which patron category this rule is for
`delay` int(4) default NULL, -- number of days after the item is overdue that
this notice is sent
`letter` varchar(20) default NULL, -- foreign key from the letter table to
define which notice should be sent
`debarred` varchar(1) default 0, -- is the patron restricted when this notice
is sent (1 for yes, 0 for no)
`typecode` varchar(10) NOT NULL default '1', -- 1 2 3 for first second third,
may be extended later
PRIMARY KEY (`overduerules_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
I think the existing user interface and cronjob can be made to work with this
structure pretty easily. Patch to follow.
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
