Galen Charlton a écrit : > Hi, > > As noted in bug 2171 > (http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2171), the > transfers to-do report is not working. The intention of the report > seems to be: > > * get a list of hold requests grouped by branches; specifically, those > that already have a specific item associated with them to fill the > request (i.e., reserves.priority = 0 and reserves.itemnumber is not > null) but have not been transferred yet (i.e., don't have a > branchtransfers record). > > * let the operator initiate the transfer (this doesn't work at all at present) > > However, by the time any given hold request has priority set to 0, a > branchtransfer has already been initiated. In addition, the help for > the report implies that this is for potential transfers that are going > out other branches; however, the only time this report shows results > is when items are due into the current branch, thus duplicating the > functionality of circ/transferstoreceive.pl. > > Is anybody using this report? If so, can you explain what it is > supposed to do? If not, I suggest that this be removed prior to the > general release.
This is a SAN-OP dev. It's usefull for them. I cc: the dev who wrote this report to have an answer on how it's supposed to work, how they use it. cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19 _______________________________________________ Koha-devel mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-devel
