| Time |
Nick |
Message |
| 04:00 |
|
sleary joined #evergreen |
| 06:24 |
|
sleary joined #evergreen |
| 07:12 |
|
kworstell-isl joined #evergreen |
| 07:54 |
|
collum joined #evergreen |
| 08:23 |
|
sleary joined #evergreen |
| 08:38 |
|
mmorgan joined #evergreen |
| 08:47 |
|
tlittle joined #evergreen |
| 09:40 |
|
terranm joined #evergreen |
| 09:58 |
|
sleary joined #evergreen |
| 10:17 |
eeevil |
berick++ #rustolium-coated redis-srf |
| 10:35 |
|
BDorsey joined #evergreen |
| 10:37 |
|
kworstell_isl joined #evergreen |
| 11:15 |
|
jihpringle joined #evergreen |
| 11:46 |
|
dmoore_doppel joined #evergreen |
| 11:47 |
|
javier_guel joined #evergreen |
| 11:54 |
javier_guel |
Hi all, Does someone know how long does the metabib.reingest_metabib_field_entries script take? |
| 11:58 |
Stompro |
javier_guel, it depends on how many bib records you have, so it is hard to compare sites. |
| 11:59 |
javier_guel |
I have 123587 call_number records, and 43901 record entry records |
| 12:00 |
Stompro |
Has it already been noted that the 3.10.1-3.10.2 upgrade sql file is missing from the rel_3_11 branches? |
| 12:09 |
Stompro |
javier_guel, it also depends on your hardware. I think you can skip running that script in some situations and run pingest.pl afterwards... which upgrade version are you running this for? |
| 12:10 |
javier_guel |
I am runnig 3.9.1-3.10.0-upgrade-db.sql |
| 12:13 |
javier_guel |
I am trying to upgrade from 3.4.2 to 3.11.0 |
| 12:21 |
|
Christineb joined #evergreen |
| 12:28 |
|
collum joined #evergreen |
| 12:29 |
Stompro |
I commented that out and ran it later, I'll send you some links in a second. |
| 12:31 |
Stompro |
Here is our version of that upgrade script - https://gitlab.com/LARL/evergreen-larl/-/blob/rel_3_11_0-larl/Open-ILS/src/sql/Pg/version-upgrade/3.9.1-3.10.0-upgrade-db.sql-larl |
| 12:33 |
Stompro |
Here are the scripts to run it later - https://gitlab.com/LARL/evergreen-larl/-/commit/7a9667419df1616666b1ed95efd85766419cf355 |
| 12:35 |
Stompro |
That generates an sql file with an entry for each bib, so they are not all included in one transaction. |
| 12:35 |
Stompro |
Lets you run it during production without it causing things to slow down as much. |
| 12:37 |
Stompro |
You can also get a sense of how long it will take, you can turn on timing in psql so you know how long each update takes. |
| 12:39 |
javier_guel |
Great, so first run the 3.9.1-3.10.0-upgrade-db.sql-larl instead of the oficial |
| 12:39 |
javier_guel |
then, run psql -f ./3.10.0-partial-reingest-gen.sql |
| 12:39 |
javier_guel |
and then psql -a -f ./3.10.0-partial-reingest-run.sql |
| 12:39 |
javier_guel |
right? |
| 12:51 |
|
collum joined #evergreen |
| 13:03 |
Stompro |
javier_guel, yep, all that does is remove the reingest from the end and run it a little differently. |
| 13:03 |
Stompro |
Sorry for the delay, I'm working on my own test upgrade to 3.11 now also. |
| 13:05 |
javier_guel |
no problem, I will try, thanks for your help |
| 13:09 |
Stompro |
javier_guel, you could also add "\timing on" to the top of the -run.sql file to output how long each statement takes. |
| 13:09 |
javier_guel |
great, let me add, it, thanks |
| 13:17 |
|
collum joined #evergreen |
| 13:32 |
javier_guel |
It worked, thanks, |
| 13:32 |
javier_guel |
Now I am looking for the 3.10.1-3.10.2-upgrade-db.sql file but I think i is missing from the official tar |
| 13:39 |
|
kmlussier joined #evergreen |
| 13:40 |
kmlussier |
I didn't want to put this in my email, but on the IRC vs. Slack question, I would like to know if there is a way to give karma to parts in slack. Because we need to make sure we address the most important issues in this discussion. |
| 13:40 |
jeff |
(hah.) |
| 13:40 |
jeff |
kmlussier++ |
| 13:40 |
* kmlussier |
is only half joking. |
| 13:42 |
berick |
hm, i don't think you're joking at all |
| 13:42 |
jeff |
Slack does not have built-in support for the concept of karma, but we can certainly integrate or build a close approximation. |
| 13:42 |
kmlussier |
berick: You know me so well. :) |
| 13:44 |
kmlussier |
jeff: Well, supybot had to be built too. |
| 13:44 |
kmlussier |
Anyway, lunchtime is over. Need to get back to doing all the things that need to be done in the next 12 days. |
| 13:44 |
Stompro |
javier_guel, I noticed that also. I pulled it in from master |
| 13:44 |
kmlussier |
parts++ |
| 13:44 |
Stompro |
Er... I mean main |
| 13:46 |
jeff |
also, I just realized that I missed that your original message was referring specifically to karma for parts :-) |
| 13:48 |
berick |
kmlussier++ # couldn't agree more re: separate channels |
| 14:00 |
jeffdavis |
I don't have a strong opinion on IRC vs Slack but IMO it is critical to use something where the chat logs are fully searchable, linkable, and downloadable as text. |
| 14:02 |
|
sleary joined #evergreen |
| 14:27 |
mmorgan |
+1 to ALL chat logs being fully searchable, linkable and downloadable |
| 14:28 |
csharp_ |
having been a member of Code4Lib's IRC and Slack channels, I can say that 1) there is an effective IRC/Slack bridge that allows people in Slack to participate in IRC (though not vice-versa) and that kinda works and 2) most people are no longer in IRC at all |
| 14:29 |
sleary |
(catching up) I think a karma bot would be required in Slack, yes. There is at least one. I have never owned a Slack workspace and can't speak to the question of logging, but I'm sure there is someone here with more experience. |
| 14:29 |
sleary |
I agree that we don't want to lose the public logs. |
| 14:31 |
sleary |
I think Code4Lib's IRC bridge only captures the main channel, but that might be configurable. |
| 14:32 |
csharp_ |
yeah, it's just set up for #code4lib |
| 15:01 |
jeff |
the code4lib irc channel is almost as dead as the code4lib Discord and the code4lib Zulip. |
| 15:02 |
jeff |
and the code4lib Slack does not mirror the main Slack channel, but a specific #irc channel in Slack is bridged to the #code4lib irc channel on this network. |
| 15:04 |
|
tlittle joined #evergreen |
| 15:06 |
jeff |
if we move realtime communication to Slack, I would recommend that we opt to pay for it, or to apply for a free/discounted Pro plan (free if we're under 250 users). |
| 15:07 |
jeff |
there are a lot of other considerations before making that decision, and I'm not going to get into them all right now. :-) |
| 15:07 |
sleary |
yes, the more immediate question is the visibility of channels other than this one |
| 15:08 |
jeff |
also, if we want to log #evergreen-release or any other irc channels we can make that happen (barring reasons not to) |
| 15:09 |
tlittle |
I was poking around on Slack's website earlier and it *looks* like it's all searchable |
| 15:09 |
jeff |
tlittle: only if you pay (or qualify for a free plan under their nonprofit program) |
| 15:10 |
sleary |
yes, not-paid not-pro plans only let you search the last 90 days |
| 15:10 |
jeff |
I'm happy to help configure logging and improve channel visibility for IRC. If we decide (not tomorrow!) to move to Slack, I also have experience with outside-of-slack message archiving/etc. |
| 15:10 |
tlittle |
Ah, I must have been in the workspace area then. Fwiw, depending on how much that costs, that seems like a reasonable expense that the project could take on |
| 15:11 |
tlittle |
Well, and we're also a 501c3 so I'd assume we'd get the nonprofit plan |
| 15:13 |
jeff |
The Pro plan for Slack is $8.75 per user per month (defined as a user who has "taken an action" in the Slack workspace within the past 28 days), or free if you qualify for their nonprofit plan and are under 250 active users. |
| 15:13 |
jeff |
If you pay for the year in advance it comes down to $7.99 per month per user. |
| 15:14 |
jeff |
And if you've over 250 active users you aren't free, but you get the plan for 85% off. |
| 15:15 |
jeff |
That's all for the Pro subscription level, which is where I'd recommend we stop. The Business+ plan has features that we would find less useful, AND features that we would find problematic (like logging/archiving of private messages). |
| 15:26 |
gmcharlt |
noting that Slack (paid or free-for-nonprofits) will also be on the agenda of the next TEP meeting; though with more of a focus on defining more structures for acquiring paid services, not uniterally forcing a forum change right away |
| 16:35 |
|
jihpringle joined #evergreen |
| 17:02 |
|
kmlussier joined #evergreen |
| 17:05 |
kmlussier |
Speaking of the TEP meeting, I noticed the calendar still calls it the EOB meeting. I went here - https://wiki.evergreen-ils.org/doku.php?id=website_administration - to see who can update the name, but that page is a little dusty. It still thinks I have access. |
| 17:18 |
|
mmorgan left #evergreen |
| 18:36 |
|
jihpringle joined #evergreen |
| 18:38 |
|
javier_guel joined #evergreen |
