https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
Katrin Fischer changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
Nick Clemens changed:
What|Removed |Added
See Also||https://bugs.koha-community
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #12 from Christopher Brannon ---
(In reply to Katrin Fischer from comment #11)
> (In reply to Christopher Brannon from comment #10)
> > (In reply to Kyle M Hall from comment #9)
> > > With the Real Time Holds Queue
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #11 from Katrin Fischer ---
(In reply to Christopher Brannon from comment #10)
> (In reply to Kyle M Hall from comment #9)
> > With the Real Time Holds Queue implemented, this is no longer needed, right?
>
> Kyle, can
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #10 from Christopher Brannon ---
(In reply to Kyle M Hall from comment #9)
> With the Real Time Holds Queue implemented, this is no longer needed, right?
Kyle, can you enlighten me on this? This is the first I've heard
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
Kyle M Hall changed:
What|Removed |Added
CC||k...@bywatersolutions.com
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #8 from Sally ---
Hi Christopher,
Our cron job does rebuild hourly; this is what Martin refers to when he says,
"In their workflows, having to wait for an hour between runs is an annoyance."
The request here is to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
Christopher Brannon changed:
What|Removed |Added
CC|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
David Cook changed:
What|Removed |Added
CC||dc...@prosentient.com.au
---
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
Katrin Fischer changed:
What|Removed |Added
See Also|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #5 from Katrin Fischer ---
Hi Sally, sorry I didn't get back to that. I totally understand your use case.
Maybe we could start small by highlighting holds already filled (or removing
them) on the report page? This way
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #4 from Sally ---
Hi Katrin, I was one of the people who requested this - hopefully this bit of
background might be useful.
We have over 40 sites where books can be transferred to/from. We only use
biblio level
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #3 from Katrin Fischer ---
Maybe to explain better: hold information = the library picked to get the item
off the shelf. I think the reason it's on a slow schedule by default is that
the idea was to give people time to
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #2 from Martin Renvoize ---
Definitely optional Katrin :)
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
___
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
--- Comment #1 from Katrin Fischer ---
Hm, woudl this be optional or that you could still pick the schedule? If you
use the randomized hold targetting it would mean that the holds information
would likely change with every hold
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25891
Sally changed:
What|Removed |Added
CC||sally.healey@cheshireshared
16 matches
Mail list logo
