Evergreen ILS Website

IRC log for #evergreen, 2024-05-17

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
01:44 rlefaive joined #evergreen
04:33 rlefaive joined #evergreen
06:51 rlefaive joined #evergreen
07:26 collum joined #evergreen
07:27 kworstell-isl joined #evergreen
08:01 cbrown-isl joined #evergreen
08:07 rlefaive joined #evergreen
08:08 BDorsey joined #evergreen
08:55 mmorgan joined #evergreen
08:56 rlefaive joined #evergreen
08:58 Dyrcona joined #evergreen
09:01 rlefaive joined #evergreen
09:09 mantis1 joined #evergreen
09:20 dguarrac joined #evergreen
09:24 cbrown_isl joined #evergreen
09:39 kworstell_isl joined #evergreen
09:46 rlefaive joined #evergreen
10:17 rlefaive joined #evergreen
10:23 sleary joined #evergreen
10:55 sandbergja joined #evergreen
11:45 Christineb joined #evergreen
12:03 jihpringle joined #evergreen
13:42 cbrown-isl joined #evergreen
13:52 sleary joined #evergreen
14:20 mmorgan Is there any way to place a block on a Library A patron record such that Library B's items are not holdable for that patron?
14:21 mmorgan I have tried applying a staff block at Library B that prevents CIRC|FULFILL|HOLD|CAPTURE|RENEW, but it doesn't prevent holds placed for pickup at Library A from targeting Library B's items.
14:27 csharp_ yeah, I don't think the hold targeter has any awareness of penalties/blocks
14:28 csharp_ the HOLD there would be "hold placement"
14:30 csharp_ huh - but CAPTURE I'm not sure about...
14:30 csharp_ or FULFILL
14:30 csharp_ hmm - looks like I don't know anything!
14:30 mmorgan csharp_: Looks like I'm not alone, then!
14:30 mmorgan :)
14:36 csharp_ mmorgan: the SQL in the "nearest_hold" sub does appear to care about CAPTURE penalties: https://git.evergreen-ils.org/?p=Evergreen.git;​a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/Appl​ication/Storage/Publisher/action.pm;h=2afc327b5​eb42113f1affdeb334f8a2c85d521fa;hb=HEAD#l526
14:36 mmorgan So I can't capture a B item if the hold is for B pickup, but the item captures just fine if the pickup is Library A
14:37 csharp_ maybe there needs to be more subtlety in the assumptions behind the holds query
14:38 csharp_ PINES penalties are fairly straightforward and apply everywhere, so we've not hit the Library A vs B situation
14:38 csharp_ or at least not in a long time
14:41 mmorgan Straightforward penalties are always preferred, but once in a while there's a unique edge case.
14:47 * mmorgan is looking at nearest_hold to see how the penalty is consulted, but can't make out where the penalty context is determined.
14:48 cbrown_isl joined #evergreen
15:07 mmorgan csharp_++ # Thanks for looking!
15:36 cbrown-isl joined #evergreen
16:54 mantis1 left #evergreen
17:04 mmorgan left #evergreen
17:27 rlefaive joined #evergreen
18:02 pinesol News from commits: Docs: updates to 3.13 release notes <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=03c8b1​9af0dfd9527617f10ff4d7ba335e50ce21>
18:52 jihpringle joined #evergreen
19:33 rlefaive joined #evergreen
20:10 dmoore joined #evergreen
21:46 rlefaive joined #evergreen
23:47 ejk_ joined #evergreen
23:48 goood joined #evergreen
23:49 tsadok joined #evergreen
23:53 jweston_ joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat