Paul POULAIN a écrit :
2-C tracking who does what Koha will save which librarian creates/modify a biblio, and when (but not what he changed ? open question here, as saving what he changed can be very complex) Needs a new table in DB, will be in head only.
2-D late orders in acquisitions, create a new page to see, for a given bookseller the order lines that are still not recieved (+ nice printing of this "late recieve" list using doNotPrint css rule). The page will be like bull/lateissues.pl where you can select a bookseller & see the late serial issues he has. the list will show order info, including basket #, order date,...) No change in DB, will be in head, backported asap in 2.2.x
For this topic, the librarian will also be able to send a "letter" to the bookseller (so, by mail) All mails sent will be tracked in the log tracker (see 2-C)
2-I "serial issue alert" With this feature, in serials, a user can subscribe the "issue alert". For every issue arrived/missing, a mail is sent to all subscribers of this list. The mail warns the user that the issue is arrive or missing. Will be in head. 2-J return date calculation
Done, still some tests to improve it.
For instance, the return date does not rely on the borrower expiration date. A systempref will be added in Koha, to modify return date calculation schema : * ReturnBeforeExpiry = yes => return date can't be after expiry date * ReturnBeforeExpiry = no => return date can be after expiry date will be in head & backported soon in 2.2.x
Done -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)