| Time |
Nick |
Message |
| 05:57 |
|
dbs joined #evergreen |
| 07:10 |
|
kworstell-isl joined #evergreen |
| 07:13 |
|
kworstell_isl joined #evergreen |
| 07:57 |
|
collum joined #evergreen |
| 08:03 |
|
BDorsey joined #evergreen |
| 08:41 |
|
rfrasur joined #evergreen |
| 08:41 |
|
mmorgan joined #evergreen |
| 08:42 |
|
dguarrac joined #evergreen |
| 09:05 |
|
Christineb joined #evergreen |
| 09:14 |
|
terranm joined #evergreen |
| 09:54 |
pinesol |
News from commits: LP2008918: (follow-up) standardize on the info cyan for the modal headers <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=52703be80f17061cafac3757b0ff7dd7759d9f12> |
| 09:54 |
pinesol |
News from commits: LP2008918: use new default colors for modal headers <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=aea3327f0149c6fa68937ca527a0aa139fa4dc14> |
| 09:54 |
pinesol |
News from commits: LP2008918: default modal background color <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=7dd34bd9853946cbd9f2d438bf056bce2d2aae9e> |
| 10:24 |
pinesol |
News from commits: LP#1828468 Release note <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=a3b37fc20a559f0201d1b0d687528ce8f6a4c57d> |
| 10:24 |
pinesol |
News from commits: LP1828468 keyboard navigation for Angular nav bar <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=06df8dcd8255d7fafad9c12a661ba0117d5f7741> |
| 10:31 |
JBoyer |
After a very frustrating morning trying to determine why a hold policy is not being used I came up with this helper function to make it more obvious. |
| 10:32 |
JBoyer |
https://gist.github.com/HitScan/7043f6db1be4791731cda6970e91b880 |
| 10:34 |
JBoyer |
It returns the top 5 hold matrix matchpoints and shows you the weights so you can see why. For my use case it didn't return the policy I'm working on at all, so that's no help, but that is technically useful information. :/ |
| 10:37 |
mmorgan |
JBoyer++ |
| 10:37 |
collum |
JBoyer++ |
| 10:38 |
* mmorgan |
has used action.find_hold_matrix_matchpoint in the past, but that only returns one. |
| 10:38 |
JBoyer |
I'm sure a circ policy version would be handy but that's not what I'm troubleshooting today. :D |
| 10:39 |
JBoyer |
And given how it works (it doesn't return every chmm row), the limit 5 can probably just be removed, but there we go. |
| 10:39 |
terranm |
Coincidentally, we're actually troubleshooting circ policy matchpoints right now |
| 10:43 |
|
mantis1 joined #evergreen |
| 10:53 |
JBoyer |
^ Followup, it all came down to requestor_grp and usr_grp being swapped. cool. cool, cool, cool. Love how all of that shook out. |
| 11:04 |
mmorgan |
Interesting. |
| 11:05 |
* mmorgan |
doesn't understand the global flag circ.hold.usr_not_requestor, but ours has always been set to TRUE. |
| 12:16 |
|
kworstell-isl joined #evergreen |
| 12:39 |
|
collum joined #evergreen |
| 12:45 |
|
jihpringle joined #evergreen |
| 12:54 |
pinesol |
News from commits: LP1808016: improve error handling by open-ils.pcrud <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=1ef377fd76ef3988db17198c10649b50b7b67e08> |
| 13:07 |
|
terranm joined #evergreen |
| 13:13 |
jeffdavis |
I'm seeing truly abysmal performance when trying to use metabib.wide_display_entry or metabib.flat_display_entry for anything other than directly retrieving rows for a specific source value. I guess anything that would do a join on those views should use reporter.materialized_simple_record instead? |
| 13:17 |
berick |
jeffdavis: metabib.display_entry would certainly be faster (it's a plain table) if you know what metabib fields you're looking for |
| 13:22 |
jeffdavis |
at the moment I just need a title and author to display (for carousel items) so I want to avoid having to deal with metabib fields |
| 13:25 |
berick |
reporter.materialized_simple_record should work then |
| 13:33 |
|
kco joined #evergreen |
| 13:56 |
jeffdavis |
This is for bug 2009891, including both title and author in the open-ils.actor.carousel.get_contents API response. I'll go ahead and use rmsr but I wonder if there ought to be a good way to use display entries for this |
| 13:56 |
pinesol |
Launchpad bug 2009891 in Evergreen "Add author and non-override name to carousel APIs" [Wishlist,Confirmed] https://launchpad.net/bugs/2009891 - Assigned to Jeff Davis (jdavis-sitka) |
| 14:03 |
berick |
jeffdavis: i think reporter.materialized_simple_record is generated from metabib.display_entry data.. |
| 14:03 |
berick |
have a vague memory it was updated thusly |
| 14:20 |
jeffdavis |
ah, ok - I was thinking of rmsr as not really intended for public consumption |
| 14:20 |
berick |
yeah, kinda, but since it already was so heavily used... |
| 14:32 |
jeff |
it used to be a very normalized, forced-to-lowercase mat view, but yes, it was updated to use more friendly, display-suitable (and in many cases, longer!) data. |
| 14:33 |
jeff |
I don't remember without looking right now if assumptions changed about deleted records being present, all records having been reingested and therefore materialized to be display field based, etc. |
| 14:39 |
jeffdavis |
looks like it was recreated from metabib.wide_display_entry (via the reporter.old_super_simple_record vie) in 3.0, with a reingest of display entries at the end for good measure |
| 14:39 |
jeffdavis |
not sure about deleted records |
| 14:56 |
jeff |
I generally do a LEFT JOIN on it out of habit when writing reports. |
| 14:57 |
jeff |
but I've stopped wrapping it in UPPER() now :-) |
| 14:59 |
|
mmorgan1 joined #evergreen |
| 15:35 |
|
mantis1 left #evergreen |
| 15:44 |
|
kworstell-isl joined #evergreen |
| 16:44 |
Stompro |
Success getting password auth working with NCIPServer !! |
| 17:09 |
|
mmorgan left #evergreen |
| 17:18 |
jeff |
Stompro: congrats. :-) |
| 19:22 |
|
jihpringle joined #evergreen |
| 19:34 |
|
kco joined #evergreen |
| 20:22 |
|
kmlussier joined #evergreen |
| 20:24 |
kmlussier |
I noticed that there is something wrong with yesterday's IRC log - http://irc.evergreen-ils.org/evergreen/2023-05-10. It only shows that rhamby entered the channel at some point, which is always a momentous event, but probably not the only thing that happened yesterday. |
| 20:36 |
* jeff |
looks |
| 20:42 |
kmlussier |
Why am I not surprised that jeff is still here? :) |
| 21:03 |
jeff |
unknown cause, but fixed! |
| 21:04 |
jeff |
(which, given the choice between only one of the two, I'll take) |
| 21:04 |
jeff |
kmlussier++ |
| 21:04 |
kmlussier |
jeff++ |
| 21:38 |
jeff |
hrm. |
