Hi, Le Fri, 21 Nov 2008 12:15:04 -0500, "Joe Atzberger" <[EMAIL PROTECTED]> a écrit :
> Nahuel -- > > See perldoc C4::Reserves for the logic and database representation. > The holding branch should use the holds "pick list" report from the > staff client. Then when they scan in the retrieved items on that > list, the interface will tell them where to transfer it (and update > the hold to be paired to that item). What about available items? The user shouldn't be in the same branch, so cannot check out himself. > Holds can be complicated, so it is quite possible there could be > "leaks", but I think it happens often by libraries not following the > workflow correctly (i.e., not scanning the items picked). In my > opinion, this workflow is the correct process for Koha to use, > however. I think, someone should write some use cases of holding/checkin/checkout , with single, multiple branches and independantbranches to "on" and "off". There is some cases that it works great, but others that are really not supported, and the librarian is... blocked. bests, > --Joe > > On Fri, Nov 21, 2008 at 11:39 AM, Nahuel ANGELINETTI < > [EMAIL PROTECTED]> wrote: > > > Hi, > > > > I'm trying to debug some stuff in holding, and have a (big?) problem > > when a user hold an item from another branch and want to check out > > it in his branch. > > How the actual holding branch know which document it must be send to > > others? > > How is it in the database? > > How is managed the workflow to transfer an hold document to his > > check out branch? > > I think there are some leak of this feature, I want to know if it's > > an error from me, or if there is real leaks? > > > > Thanks, bests, > > > > -- > > Nahuel ANGELINETTI -- Nahuel ANGELINETTI Jabber/XMPP : [EMAIL PROTECTED] _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
