[Koha-cvs] CVS: koha/updater updatedatabase,1.115,1.116

[Paul POULAIN]

Update of /cvsroot/koha/koha/updater
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3371/updater

Modified Files:
        updatedatabase 
Log Message:
Letters / alert system, continuing...

* adding a package Letters.pm, that manages Letters & alerts.
* adding feature : it's now possible to define a "letter" for any subscription 
created. If a letter is defined, users in OPAC can put an alert on the 
subscription. When an issue is marked "arrived", all users in the alert will 
recieve a mail (as defined in the "letter"). This last part (= send the mail) 
is not yet developped. (Should be done this week)
* adding feature : it's now possible to "put to an alert" in OPAC, for any 
serial subscription. The alert is stored in a new table, called alert. An alert 
can be put only if the librarian has activated them in subscription (and they 
activate it just by choosing a "letter" to sent to borrowers on new issues)
* adding feature : librarian can see in borrower detail which alerts they have 
put, and a user can see in opac-detail which alert they have put too.

Note that the system should be generic enough to manage any type of alert.
I plan to extend it soon to virtual shelves : a borrower will be able to put an 
alert on a virtual shelf, to be warned when something is changed in the virtual 
shelf (mail being sent once a day by cron, or manually by the shelf owner. 
Anyway, a mail won't be sent on every change, users would be spammed by Koha 
;-) )

Index: updatedatabase
===================================================================
RCS file: /cvsroot/koha/koha/updater/updatedatabase,v
retrieving revision 1.115
retrieving revision 1.116
diff -C2 -r1.115 -r1.116
*** updatedatabase      2 Aug 2005 16:15:34 -0000       1.115
--- updatedatabase      4 Aug 2005 08:55:54 -0000       1.116
***************
*** 81,87 ****
--- 81,97 ----
                                        PRIMARY KEY  (module,code)
                                )",
+       alert           =>"(
+                                       alertid int(11) NOT NULL auto_increment,
+                                       borrowernumber int(11) NOT NULL default 
'0',
+                                       type varchar(10) NOT NULL default '',
+                                       externalid varchar(20) NOT NULL default 
'',
+                                       PRIMARY KEY  (alertid),
+                                       KEY borrowernumber (borrowernumber),
+                                       KEY type (type,externalid)
+                               )"
  );
  
  my %requirefields = (
+       subscription => { 'letter' => 'char(20) NULL'},
  #    tablename        => { 'field' => 'fieldtype' },
  );
***************
*** 359,362 ****
--- 369,383 ----
  
  # $Log$
+ # Revision 1.116  2005/08/04 08:55:54  tipaul
+ # Letters / alert system, continuing...
+ #
+ # * adding a package Letters.pm, that manages Letters & alerts.
+ # * adding feature : it's now possible to define a "letter" for any 
subscription created. If a letter is defined, users in OPAC can put an alert on 
the subscription. When an issue is marked "arrived", all users in the alert 
will recieve a mail (as defined in the "letter"). This last part (= send the 
mail) is not yet developped. (Should be done this week)
+ # * adding feature : it's now possible to "put to an alert" in OPAC, for any 
serial subscription. The alert is stored in a new table, called alert. An alert 
can be put only if the librarian has activated them in subscription (and they 
activate it just by choosing a "letter" to sent to borrowers on new issues)
+ # * adding feature : librarian can see in borrower detail which alerts they 
have put, and a user can see in opac-detail which alert they have put too.
+ #
+ # Note that the system should be generic enough to manage any type of alert.
+ # I plan to extend it soon to virtual shelves : a borrower will be able to 
put an alert on a virtual shelf, to be warned when something is changed in the 
virtual shelf (mail being sent once a day by cron, or manually by the shelf 
owner. Anyway, a mail won't be sent on every change, users would be spammed by 
Koha ;-) )
+ #
  # Revision 1.115  2005/08/02 16:15:34  tipaul
  # adding 2 fields to letter system :
***************
*** 745,748 ****
--- 766,780 ----
  
  # $Log$
+ # Revision 1.116  2005/08/04 08:55:54  tipaul
+ # Letters / alert system, continuing...
+ #
+ # * adding a package Letters.pm, that manages Letters & alerts.
+ # * adding feature : it's now possible to define a "letter" for any 
subscription created. If a letter is defined, users in OPAC can put an alert on 
the subscription. When an issue is marked "arrived", all users in the alert 
will recieve a mail (as defined in the "letter"). This last part (= send the 
mail) is not yet developped. (Should be done this week)
+ # * adding feature : it's now possible to "put to an alert" in OPAC, for any 
serial subscription. The alert is stored in a new table, called alert. An alert 
can be put only if the librarian has activated them in subscription (and they 
activate it just by choosing a "letter" to sent to borrowers on new issues)
+ # * adding feature : librarian can see in borrower detail which alerts they 
have put, and a user can see in opac-detail which alert they have put too.
+ #
+ # Note that the system should be generic enough to manage any type of alert.
+ # I plan to extend it soon to virtual shelves : a borrower will be able to 
put an alert on a virtual shelf, to be warned when something is changed in the 
virtual shelf (mail being sent once a day by cron, or manually by the shelf 
owner. Anyway, a mail won't be sent on every change, users would be spammed by 
Koha ;-) )
+ #
  # Revision 1.115  2005/08/02 16:15:34  tipaul
  # adding 2 fields to letter system :