| Time |
Nick |
Message |
| 04:20 |
|
serflog joined #evergreen |
| 04:20 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
| 04:21 |
|
csharp joined #evergreen |
| 04:21 |
|
pinesol joined #evergreen |
| 04:30 |
|
pinesol` joined #evergreen |
| 04:31 |
|
csharp_ joined #evergreen |
| 04:31 |
pinesol |
News from qatests: Failed cloning Evergreen git repository <http://testing.evergreen-ils.org/~live/test.24.html#2019-07-11T04:28:32,372035808-0400 -0> |
| 04:31 |
pinesol |
News from qatests: Failed Evergreen developer steps <http://testing.evergreen-ils.org/~live/test.25.html#2019-07-11T04:28:32,398579854-0400 -2> |
| 04:31 |
pinesol |
News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~live/test.26.html#2019-07-11T04:28:32,424469023-0400 -4> |
| 04:31 |
pinesol |
News from qatests: Failed Installing Evergreen pre-requisites <http://testing.evergreen-ils.org/~live/test.27.html#2019-07-11T04:28:32,450430528-0400 -6> |
| 04:31 |
pinesol |
News from qatests: Failed Installing AngularJS web client <http://testing.evergreen-ils.org/~live/test.28.html#2019-07-11T04:28:32,476370743-0400 -8> |
| 04:31 |
pinesol |
News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~live/test.29.html#2019-07-11T04:28:32,502300896-0400 -10> |
| 04:31 |
pinesol |
News from qatests: Failed Building Evergreen <http://testing.evergreen-ils.org/~live/test.30.html#2019-07-11T04:28:32,528244132-0400 -12> |
| 04:31 |
pinesol |
News from qatests: Failed Running Evergreen tests <http://testing.evergreen-ils.org/~live/test.31.html#2019-07-11T04:28:32,554250981-0400 -14> |
| 04:31 |
pinesol |
News from qatests: Failed Installing Evergreen <http://testing.evergreen-ils.org/~live/test.32.html#2019-07-11T04:28:32,581608579-0400 -16> |
| 04:31 |
pinesol |
News from qatests: Failed Installing Dojo <http://testing.evergreen-ils.org/~live/test.35.html#2019-07-11T04:28:32,608470485-0400 -18> |
| 04:31 |
pinesol |
News from qatests: Failed configure apache <http://testing.evergreen-ils.org/~live/test.36.html#2019-07-11T04:28:32,634442673-0400 -20> |
| 04:31 |
pinesol |
News from qatests: Failed configure EG Action/Trigger <http://testing.evergreen-ils.org/~live/test.38.html#2019-07-11T04:28:32,661434258-0400 -22> |
| 04:31 |
pinesol |
News from qatests: Failed Installing Evergreen database pre-requisites <http://testing.evergreen-ils.org/~live/test.39.html#2019-07-11T04:28:32,687372908-0400 -24> |
| 04:31 |
pinesol |
News from qatests: Failed Create PostgreSQL superuser <http://testing.evergreen-ils.org/~live/test.40.html#2019-07-11T04:28:32,713406894-0400 -26> |
| 04:31 |
pinesol |
News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~live/test.41.html#2019-07-11T04:28:32,740334785-0400 -28> |
| 04:31 |
pinesol |
News from qatests: Failed Running autogen.sh <http://testing.evergreen-ils.org/~live/test.44.html#2019-07-11T04:28:32,767387782-0400 -30> |
| 04:31 |
pinesol |
News from qatests: Failed Running pgTAP live tests <http://testing.evergreen-ils.org/~live/test.47.html#2019-07-11T04:28:32,793340892-0400 -32> |
| 04:31 |
pinesol |
News from qatests: Failed Running settings-tester.pl <http://testing.evergreen-ils.org/~live/test.48.html#2019-07-11T04:28:32,821412178-0400 -34> |
| 04:31 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live/test.49.html#2019-07-11T04:28:32,847372095-0400 -36> |
| 04:31 |
pinesol |
News from qatests: Failed Log Output: srfsh.log <http://testing.evergreen-ils.org/~live/test.58.html#2019-07-11T04:28:32,873266185-0400 -38> |
| 04:31 |
pinesol |
News from qatests: Failed Building the AsciiDoc output formats <http://testing.evergreen-ils.org/~live/test.61.html#2019-07-11T04:28:32,900231157-0400 -40> |
| 05:55 |
|
dbwells_ joined #evergreen |
| 06:02 |
|
dbwells joined #evergreen |
| 06:57 |
|
csharp joined #evergreen |
| 06:59 |
|
agoben joined #evergreen |
| 07:05 |
|
rjackson_isl joined #evergreen |
| 07:34 |
|
Dyrcona joined #evergreen |
| 07:37 |
|
kenstir joined #evergreen |
| 08:05 |
|
bos20k joined #evergreen |
| 08:22 |
|
collum joined #evergreen |
| 08:37 |
|
mmorgan joined #evergreen |
| 08:51 |
|
aabbee joined #evergreen |
| 09:18 |
|
Dyrcona joined #evergreen |
| 09:21 |
|
jvwoolf joined #evergreen |
| 09:22 |
Dyrcona |
@blame Kernel 5.0 Intel WiFi driver |
| 09:22 |
pinesol |
Dyrcona: Kernel 5.0 Intel WiFi driver HAXORED Dyrcona's SERVERZ!!!! |
| 09:59 |
|
sandbergja joined #evergreen |
| 10:19 |
|
khuckins joined #evergreen |
| 10:21 |
|
finnx joined #evergreen |
| 10:21 |
|
finnx left #evergreen |
| 10:23 |
Dyrcona |
CALL: open-ils.pcrud open-ils.pcrud.search.pgt null,{"parent":null},{"flesh":-1,"flesh_fields":{"pgt":["children"]}} is followed by a segfault in liboils_pcrud.so.2.0 on one of my brick drones' logs. That -1 looks quite wrong to me. |
| 10:28 |
mmorgan |
Dyrcona: The null after search.pgt looks wrong to me |
| 10:30 |
Dyrcona |
Yeah, that, too. :) |
| 10:31 |
Dyrcona |
I'm going to try exactly that call on a test vm. See if it leads to a crash. |
| 10:31 |
berick |
the -1 is OK |
| 10:33 |
mmorgan |
In the web client, when you choose Print Full Grid from the Actions menu, can you control which printer is used? |
| 10:34 |
Dyrcona |
berick: OK, but I won't just take your word for it. I'll look at the code, too, because I want to see why it is OK and how it works. I always thought flesh depth, etc., had to be > 1 and correspond to the actual depth of the fleshing.... |
| 10:35 |
berick |
Dyrcona: -1 means no limit fleshing -- keep fleshing until you run out of links |
| 10:36 |
Dyrcona |
And, ooh... I just searched for segfault in the logs again, and I found more. Than I did yesterday. Which isn't exactly surprising, but considering that logs were rotated and a number of the hits were in the "last" log.... |
| 10:37 |
Dyrcona |
berick: After you said it was OK, that's what I thought, but I wanted to look, and I probably will anyway... :) |
| 10:38 |
berick |
mmorgan: i would expect it to use the 'default' print context/configuration -- so whatever printer is configured for that |
| 10:38 |
Dyrcona |
I'm going to see if I can find a proximate cause for each of these segfaults. |
| 10:38 |
berick |
Dyrcona: +1 to trust-but-verify :) |
| 10:40 |
mmorgan |
berick: ok, thanks. I was hoping there was a way to force a context. |
| 10:41 |
berick |
mmorgan: no, but I could see that being handy |
| 10:42 |
Dyrcona |
Yeah, looks like that call causes a segfault as-is. |
| 10:44 |
Dyrcona |
Chaning null to "ANONYMOUS" causes it to return no data immediately and does not cause a segfault. The client times out when the drone(?) segfaults. |
| 10:44 |
Dyrcona |
So, why are we getting null for an authtoken? |
| 10:44 |
|
Christineb joined #evergreen |
| 10:45 |
mmorgan |
Timed out session? |
| 10:45 |
Dyrcona |
mmorgan: Probably... At least, that's my suspicion. |
| 10:46 |
Dyrcona |
But, we shouldn't ever have null for an authtoken... |
| 10:56 |
Dyrcona |
Anyone else using the web client, if you want to find instances of similar segfaults, grep for segfault in /var/log/syslog on your drone servers. This kernel message doesn't get sent to a syslog server. |
| 11:00 |
|
khuckins joined #evergreen |
| 11:16 |
|
seymour joined #evergreen |
| 11:16 |
|
remingtron joined #evergreen |
| 11:28 |
|
BAMkubasa joined #evergreen |
| 11:37 |
Bmagic |
Dyrcona: not seeing any |
| 12:05 |
|
jihpringle joined #evergreen |
| 12:21 |
JBoyer |
Dyrcona, I think I've got a line on the pcrud crashes. We've had 4 today, and in every case it followed 5 mins and a single digit number of seconds after the last action performed by the authtoken used in the previous thread trace. |
| 12:22 |
JBoyer |
I think it's temporary (5 min) account operator changes timing out |
| 12:28 |
pastebot |
"JBoyer" at 168.25.130.30 pasted "PCrud crash logs" (29 lines) at http://paste.evergreen-ils.org/10034 |
| 12:29 |
* JBoyer |
tacks strings between pictures of API calls. |
| 12:31 |
JBoyer |
Yeah, here we go, during the threadtrace when one of those hashes was initially logged in there's this call: ... CALL: open-ils.actor open-ils.actor.ou_setting.ancestor_default 90, auth.temp_timeout |
| 12:34 |
Dyrcona |
JBoyer: Cool! I'll see if I can find something similar. |
| 12:35 |
JBoyer |
So 2 things that need doing: make some level of pcrud to parameter verification and just short circuit on null, and secondly stop the web client from trying to refresh the pgt cache (I assume) on logout. |
| 13:46 |
dluch |
Reminder that DIG will be meeting in 15 minutes! |
| 14:01 |
dluch |
Hi, everyone. I have 1:00, so |
| 14:01 |
dluch |
#startmeeting 2019-07-11 - Documentation Interest Group |
| 14:01 |
pinesol |
Meeting started Thu Jul 11 14:01:17 2019 US/Eastern. The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:01 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:01 |
|
Topic for #evergreen is now (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:01 |
pinesol |
The meeting name has been set to '2019_07_11___documentation_interest_group' |
| 14:01 |
dluch |
The agenda can be found here: |
| 14:01 |
dluch |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20190711-agenda |
| 14:01 |
dluch |
#topic Introductions |
| 14:01 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:01 |
dluch |
Please paste "#info <username> is <name>, <affiliation>" to identify who you are and what organization, if any, you represent. |
| 14:01 |
dluch |
#info dluch is Debbie Luchenbill, MOBIUS - DIG meeting facilitator |
| 14:02 |
abneiman |
#info abneiman is Andrea Buntz Neiman, Equinox |
| 14:02 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
| 14:03 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
| 14:03 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin University) |
| 14:05 |
dluch |
Thank you all for coming! Anyone joining us later, feel free to introduce yourself then! |
| 14:06 |
dluch |
Jumping into some FYIs |
| 14:06 |
dluch |
#topic Ongoing Information: Documentation contributions and collaboration |
| 14:06 |
|
Topic for #evergreen is now Ongoing Information: Documentation contributions and collaboration (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:06 |
dluch |
#info You can find the Documentation Needs List at |
| 14:06 |
|
PaILSCarrie joined #evergreen |
| 14:06 |
dluch |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs |
| 14:06 |
Christineb |
#info Christineb is Christine Burns, BC Libraries Cooperative |
| 14:06 |
dluch |
There are LOTS of documentation needs and several that have been identified as easy tasks for new folks. |
| 14:06 |
dluch |
#info DIG Roles can be found at |
| 14:07 |
dluch |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:digparticipants |
| 14:07 |
dluch |
If anyone would like to fill a particular role, please feel free to volunteer! |
| 14:07 |
dluch |
#topic Old and Ongoing Business: Evergreen Quick Start documentation |
| 14:07 |
|
Topic for #evergreen is now Old and Ongoing Business: Evergreen Quick Start documentation (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:07 |
dluch |
I see the Quick Start section added to the Docs Needs wiki: |
| 14:07 |
dluch |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs |
| 14:07 |
dluch |
remingtron: was that you? |
| 14:08 |
dluch |
There are also a few topics there, so thanks, folks, for getting that started. As we mentioned last time, we can all add things there. |
| 14:09 |
dluch |
#idea At the last meeting, we'd talked about making very simple, no-jargon very short text guides plus short video guides for new or "casual" users. |
| 14:09 |
remingtron |
dluch: uh, yes, I think so! |
| 14:09 |
dluch |
#idea We also decided to stick with asciidoc for now, with a possible future goal of converting into single-page documents (pdf or something) |
| 14:09 |
dluch |
remingtron: Thanks! |
| 14:09 |
dluch |
sandbergja has a proof of concept: |
| 14:09 |
dluch |
#link http://www.sandbox.lbcc.linnlibraries.org/Evergreen/docs/quickstarts/check_out.html |
| 14:10 |
dluch |
sandbergja: Can you lead us through a refresher on this topic? |
| 14:10 |
sandbergja |
Sure! I haven't really done much since last meeting on these |
| 14:10 |
sandbergja |
And I think you explained it really well, dluch! |
| 14:11 |
sandbergja |
The fundamental idea is to meet the needs of new Evergreen users who don't have much background with libraries, library jargon, ILSs, etc. |
| 14:11 |
sandbergja |
Like volunteers, student workers, etc. |
| 14:12 |
sandbergja |
So that they don't have to dig through the massive Evergreen manuals :-D |
| 14:12 |
sandbergja |
Even though we love those manuals |
| 14:12 |
dluch |
Which is awesome! Even though we do love them, lol |
| 14:12 |
dluch |
So, what are our next steps? |
| 14:13 |
dluch |
I also haven't done anything from last time, |
| 14:13 |
dluch |
So I'm going to make an official |
| 14:13 |
sandbergja |
I'd like to finish a video to go with that proof of concept link |
| 14:13 |
dluch |
#action Add ideas for very simple topics we can cover to the Quick Starts section of the wiki |
| 14:13 |
dluch |
Can I make an action item for you for that? |
| 14:13 |
sandbergja |
Yes, please do! |
| 14:14 |
dluch |
#action sandbergja will make a video to go with the proof of concept link |
| 14:14 |
sandbergja |
And then we can evaluate it all as a unit! |
| 14:14 |
dluch |
Sounds good! |
| 14:14 |
dluch |
Anything else we want to do now, or is that good for this month? |
| 14:15 |
sandbergja |
I don't have anything else to say on quick starts, but I'm very happy to hear anybody's feedback, either on IRC or by email |
| 14:16 |
dluch |
sandbergja++ |
| 14:16 |
Christineb |
sandbergja++ |
| 14:16 |
dluch |
#topic Old and Ongoing Business: Committees page updated |
| 14:16 |
|
Topic for #evergreen is now Old and Ongoing Business: Committees page updated (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:16 |
abneiman |
sandbergja++ |
| 14:16 |
dluch |
I didn't make it an action item last meeting (I forgot about those until later in the meeting, lol), but thank you to whoever updated the page! |
| 14:17 |
dluch |
#link https://evergreen-ils.org/communicate/committees/ |
| 14:17 |
|
cmal joined #evergreen |
| 14:17 |
dluch |
Any other old business I forgot about before moving on? |
| 14:18 |
dluch |
#topic New Business: Possible updates to terminology/style guide |
| 14:18 |
|
Topic for #evergreen is now New Business: Possible updates to terminology/style guide (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:18 |
dluch |
#info Background info at |
| 14:18 |
dluch |
#link https://webaim.org/discussion/mail_thread?thread=9306 |
| 14:18 |
dluch |
What are people's thoughts on this topic? |
| 14:19 |
sandbergja |
#link https://georgialibraries.markmail.org/thread/jztoghclirjd4k2f |
| 14:19 |
sandbergja |
there is the discussion we had on the email list |
| 14:20 |
dluch |
Oh, thanks! |
| 14:20 |
dluch |
Ignore my earlier link! |
| 14:21 |
sandbergja |
I thought that we had a good conversation on the mailing list! |
| 14:21 |
Bmagic |
#info Bmagic is Blake GH, MOBIUS |
| 14:21 |
sandbergja |
I don't know how we want to follow it up, though |
| 14:21 |
sandbergja |
FWIW, I think that "press" and "select" seem like better options than "click", since they are more inclusive of all the various ways people could use Evergreen |
| 14:22 |
abneiman |
Off the cuff, I like "select" (I'm not sure why Microsoft lady is so opposed to it?) and I agree that avoiding operated would be preferable |
| 14:22 |
Christineb |
I think it is a good idea for us to work towards this |
| 14:22 |
abneiman |
and yeah, I agree with the general goal of more accessibility-inclusive language |
| 14:22 |
Christineb |
+1 avoid operated |
| 14:22 |
sandbergja |
But I don't know that we need to do a massive find and replace this moment |
| 14:22 |
dluch |
I also like "select". And really don't like operated |
| 14:22 |
Bmagic |
select++ |
| 14:23 |
abneiman |
Perhaps we could update the style guide to suggest using "select" going forward, and the find-and-replace can be a separate thing |
| 14:23 |
Christineb |
I think that is a good idea |
| 14:23 |
remingtron |
I'd probably choose "press", rather than select |
| 14:23 |
dluch |
abneiman: I like that idea |
| 14:24 |
jihpringle |
is there a second term we like if there are multiple steps? |
| 14:24 |
Christineb |
to me "press" still sounds like a physical action |
| 14:24 |
dluch |
Does press still mean a physical thing, though |
| 14:24 |
dluch |
lol, yes |
| 14:24 |
Christineb |
:) |
| 14:24 |
Christineb |
select seems more generic |
| 14:25 |
sandbergja |
"press the button" or "press the link" sounds more idiomatic than "select the button" or "select the link" to me |
| 14:25 |
Bmagic |
sandbergja: the sandbox docs looks like antora pages |
| 14:25 |
jihpringle |
ie. Select the Actions menu and select Edit Due Date versus Select the Actions menu and choose/pick Edit Due Date ?? |
| 14:25 |
dluch |
jihpringle: like we select something and then have a different word for the next step that's not select? To avoid the repetition? |
| 14:25 |
jihpringle |
dluch: exactly |
| 14:26 |
sandbergja |
Bmagic: I should have just used antora! :-) |
| 14:26 |
dluch |
haha, yes, your example |
| 14:26 |
abneiman |
jihpringle: +1 to that, I'd go with "choose" I think |
| 14:26 |
dluch |
Or maybe, like, one word for if it's a menu and one for if it's a button? |
| 14:26 |
dluch |
Also +1 to choose |
| 14:28 |
sandbergja |
Also, for users with touchscreen devices, "pressing" a button would actually be a physical action |
| 14:28 |
Christineb |
select Acquistions -> choose Load MARC Order Records... what about form entry? |
| 14:28 |
Christineb |
complete the fields? |
| 14:29 |
dluch |
Okay, so how do we feel about slightly modifying abneiman's idea to update the style guide to use "select" and "choose" going forward? Then find-and-replace later? |
| 14:29 |
Christineb |
would you use "select the check box?" |
| 14:30 |
abneiman |
I typically use "enter" for forms -- "enter the required information" |
| 14:30 |
Christineb |
select the checkbox |
| 14:30 |
dluch |
Hmm. I like complete. It's...more complete than "fill in" or something |
| 14:30 |
abneiman |
also, since we're talking about it, here's the current style guide: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_style_guide#wording |
| 14:30 |
dluch |
Oh, enter is also good |
| 14:30 |
dluch |
Thanks, abneiman! |
| 14:31 |
Christineb |
Enter or Type a value into the text box - get rid of "Type" |
| 14:31 |
sandbergja |
Christineb: I like "check the checkbox" or "uncheck the checkbox", but I don't know about a more general "set the checkbox to the value you want" term |
| 14:31 |
dluch |
So we really already have several of those |
| 14:31 |
abneiman |
+1 to removing Type and +1 to using check/uncheck checkbox |
| 14:31 |
Christineb |
yeah it looks like just click and right click need to be replaced |
| 14:31 |
dluch |
+1 |
| 14:31 |
Christineb |
+1 |
| 14:32 |
jihpringle |
+1 |
| 14:32 |
abneiman |
so right click presents an interesting quandary. sandbergja do you have a sense of what might be a preferable term there? |
| 14:33 |
sandbergja |
I think right click can just stay right click |
| 14:34 |
sandbergja |
I don't think there's a fantastic alternative for right clicks for users who are using a phone or tablet |
| 14:35 |
dluch |
I was just doing a quick search to see if I could find anything other than right click, but couldn't |
| 14:35 |
abneiman |
sometimes it's long-click, but nowhere near universal |
| 14:35 |
abneiman |
(for mobile devices) |
| 14:35 |
dluch |
true |
| 14:35 |
sandbergja |
Or for keyboard-only users (there are some keyboard shortcuts that do similar things, but not consistently throughout Evergreen) |
| 14:36 |
jihpringle |
is there anywhere in Evergreen where right-clicking is the only way to access something? |
| 14:36 |
sandbergja |
So probably right click is the most accurate without over-promising |
| 14:36 |
sandbergja |
jihpringle: good question! |
| 14:37 |
abneiman |
jihpringle: in the web client, I would hope not - there were probably some in XUL |
| 14:37 |
dluch |
Yeah. I saw something that said a context menu was what you got when you right click, but I don't think that's a term anyone would get, lol. "open the context menu" |
| 14:37 |
|
khuckins joined #evergreen |
| 14:37 |
jihpringle |
I wonder if it would make sense to have an intro blurb that says for these common functions you can also access them by right-clicking/long-clicking etc. depending on your device and take it out of the specific instructions |
| 14:37 |
abneiman |
in the web client, right-click in grids is typically open the actions menu (which has its own access point at the top of the grid). Other right click things in the web client are browser tasks, like open in new tab. |
| 14:38 |
cmal |
In the MARC edit interface, there are field add/edit/delete menus that (afaik) are only accessed via right-clicking |
| 14:38 |
abneiman |
oh, good point cmal |
| 14:38 |
dluch |
Oh, yes, true |
| 14:39 |
sandbergja |
cmal: good point! |
| 14:39 |
abneiman |
cmal++ |
| 14:39 |
dluch |
cmal++ |
| 14:39 |
jihpringle |
is that how we want MARC Edit to continue working long term or should those menus be accessible in another way when MARC Edit it angularized? |
| 14:39 |
jihpringle |
(might be a questions for the cataloguing working group) |
| 14:40 |
jihpringle |
cmal++ |
| 14:40 |
abneiman |
jihpringle: I'm in favor of moving towards an accessible solution, and we can definitely put that on the CWG agenda for discussion next month |
| 14:40 |
dluch |
Good question, jihpringle. That does seem like a good question for the cataloging group. |
| 14:41 |
dluch |
Awesome. Okay, so summing up, it seems like we can... |
| 14:41 |
sandbergja |
FWIW, it seems like you can open those menus in the MARC record using the keyboard shortcut Shift+F10, but then you can't use the keyboard to choose anything from those menus |
| 14:41 |
abneiman |
I'll take an action item for bringing it up with CWG, since I'm on the CWG organizing committee |
| 14:41 |
sandbergja |
But that's more a bug than a documentation issue. :-) |
| 14:42 |
dluch |
#agree to removing "Type" from the style guide and change "Click" to "Select" |
| 14:43 |
dluch |
#action abneiman will add talking about MARC Edit, right-clicking, and accessibility with the CWG |
| 14:43 |
remingtron |
dluch: I feel like we hadn't quick settled on "select" vs. "press", but I missed some of the discussion |
| 14:43 |
remingtron |
hadn't *quite* settled |
| 14:44 |
dluch |
remingtron: it seemed like most people thought "press" was too indicative of a physical action. |
| 14:44 |
dluch |
But is there more discussion on that? |
| 14:45 |
remingtron |
I don't feel strongly about it, just wanted to make sure we were all happy with it, and I believe that now :) |
| 14:45 |
dluch |
Okay, great. :-) |
| 14:45 |
dluch |
I can take an action to update the style guide, unless someone else wants to? |
| 14:46 |
sandbergja |
dluch++ |
| 14:46 |
dluch |
#action dluch will update the style guide with the agree-upon changes |
| 14:46 |
dluch |
Okay, moving on |
| 14:46 |
dluch |
#topic New Business: Cataloging Working Group (CWG) and DIG Collaboration |
| 14:46 |
|
Topic for #evergreen is now New Business: Cataloging Working Group (CWG) and DIG Collaboration (Meeting topic: 2019-07-11 - Documentation Interest Group) |
| 14:47 |
dluch |
jweston contacted me about talking with CWG about DIG and how catalogers can be more involved |
| 14:47 |
dluch |
I spoke at their meeting on Tuesday and told them about DIG. |
| 14:47 |
dluch |
We also talked about specifically inviting them for our August meeting, since that would be more a working meeting. |
| 14:47 |
dluch |
And also putting together a special "training" session for them before that, about using IRC and some DIG basics. |
| 14:48 |
dluch |
Since IRC is how DIG meets, we thought catalogers who wanted to be more involved in docs should/could learn about how to use it |
| 14:48 |
dluch |
What do we think about this idea? |
| 14:49 |
remingtron |
sounds great |
| 14:49 |
jihpringle |
+1 |
| 14:49 |
abneiman |
+1 |
| 14:49 |
cmal |
+1 |
| 14:49 |
sandbergja |
+1 |
| 14:50 |
dluch |
I'm pretty excited about it! Catalogers will definitely have good insight on those docs. |
| 14:50 |
dluch |
Excellent! |
| 14:50 |
dluch |
Who is willing to help with a training session and DIG intro? |
| 14:51 |
abneiman |
I can help with that |
| 14:51 |
dluch |
jweston and I (and whoever else is interested) were going to correspond tomorrow, probably, to talk more details, but the session would probably be via conference call later in July |
| 14:51 |
dluch |
abneiman++ |
| 14:51 |
remingtron |
just a comment: I'd rather focus the catalogers on reviewing/writing content rather than AsciiDoc or other technical details. |
| 14:52 |
dluch |
remingtron that sounds like a good idea |
| 14:52 |
abneiman |
+1 remingtron |
| 14:52 |
abneiman |
let them be the workflow experts, we can asciidocifiy things later |
| 14:53 |
dluch |
+1 |
| 14:53 |
dluch |
#action abneiman and dluch will work with jweston on an IRC and DIG intro session for CWG later in July |
| 14:54 |
dluch |
#action August meeting will focus on cataloging docs and welcoming new CWG folks to DIG |
| 14:54 |
dluch |
Sound okay? |
| 14:54 |
sandbergja |
sounds excellent! |
| 14:54 |
remingtron |
yes |
| 14:54 |
sandbergja |
abneiman++ |
| 14:54 |
sandbergja |
dluch++ |
| 14:55 |
dluch |
Awesome! |
| 14:55 |
dluch |
Anyone have other DIG business they want to talk about today? |
| 14:57 |
dluch |
We are close to the hour mark, so no collaboration time this month (sorry), but great discussion today! |
| 14:57 |
dluch |
Next meeting will be August 1. Same bat time, same bat channel. Very brief meeting then, and mostly collaboration time. |
| 14:58 |
dluch |
Thanks for coming everyone! |
| 14:58 |
remingtron |
dluch++ #oldschool batman reference |
| 14:58 |
dluch |
:-D |
| 14:58 |
dluch |
#endmeeting |
| 14:58 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
| 14:58 |
pinesol |
Meeting ended Thu Jul 11 14:58:48 2019 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 14:58 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-07-11-14.01.html |
| 14:58 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-07-11-14.01.txt |
| 14:58 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-07-11-14.01.log.html |
| 14:59 |
abneiman |
dluch++ |
| 14:59 |
jihpringle |
dluch++ |
| 14:59 |
Christineb |
dluch++ |
| 15:02 |
sandbergja |
dluch++ |
| 15:04 |
|
mmorgan1 joined #evergreen |
| 15:25 |
Dyrcona |
JBoyer: So, about that segfault that I shared earlier.... I see an open-ils.auth.session.delete via websocket 1 second before the open-ils.pcrud.search.pgt call, and the trace is 1 lower than the trace on the pcrud call. They could be related? |
| 15:26 |
JBoyer |
Most likely, all of my examples were consecutive: session.retrieve, session.delete, pcrud.crash. |
| 15:26 |
JBoyer |
If you look up the login for that authtoken what's it's login_type? |
| 15:26 |
JBoyer |
(all of mine were temp) |
| 15:28 |
JBoyer |
Annoyingly, it doesn't look like you can just trigger it on demand by changing operator and watching the kettle come to a boil. :-/ |
| 15:29 |
JBoyer |
I wonder if there's an additional interaction with setTimeout() and Javascript timers being de-prioritized in the background or something along those lines. |
| 15:34 |
Dyrcona |
There's no login type. |
| 15:34 |
Dyrcona |
Not in the logs that I can find anyway. |
| 15:36 |
Dyrcona |
Gotta love how the successful login message shows up twice in the log. |
| 15:37 |
JBoyer |
It's a hassle tracking that part down. Once you have the thread trace from the login success message, then grep that trace out of the logs and you'll see the user id, org unit, and login type in an open-ils.auth_internal.user.validate call |
| 15:40 |
Dyrcona |
JBoyer++ "That's a bingo!....Is that how you say it?" |
| 15:41 |
Dyrcona |
login_type: temp |
| 15:45 |
|
seymour joined #evergreen |
| 16:16 |
|
jvwoolf left #evergreen |
| 16:19 |
|
nfBurton joined #evergreen |
| 16:19 |
|
khuckins joined #evergreen |
| 16:52 |
|
mmorgan joined #evergreen |
| 16:55 |
|
mmorgan2 joined #evergreen |
| 17:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 17:03 |
|
mmorgan left #evergreen |
| 22:35 |
|
sandbergja joined #evergreen |
| 22:47 |
|
sandbergja joined #evergreen |
