| Time |
Nick |
Message |
| 00:12 |
|
jamesrf joined #evergreen |
| 03:26 |
|
csharp joined #evergreen |
| 05:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 05:09 |
|
jamesrf joined #evergreen |
| 06:45 |
|
agoben joined #evergreen |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 07:54 |
|
Dyrcona joined #evergreen |
| 07:59 |
Dyrcona |
systemd-- |
| 08:04 |
JBoyer |
New adventures in silent failures? |
| 08:06 |
Dyrcona |
Failed to establish a new connection: [Errno -2] Name or service not known using systemd-resolved. |
| 08:06 |
Dyrcona |
That almost never used to happen. Happens all the time now, and web sites take longer to load because resolved is crap. |
| 08:07 |
Dyrcona |
And, that error's from the middle of a long spider run where it had been successfully connecting to the same site repeatedly. |
| 08:08 |
Dyrcona |
I thought resolved was supposed to cache this stuff? |
| 08:08 |
Dyrcona |
I think we should collectively declare the systemd experiment a failure and go back to upstart. |
| 08:11 |
Dyrcona |
I should bug it on Lp, but wait, there's already 3,150 other bug reports related to it. :) |
| 08:12 |
JBoyer |
That does sound especially weird, it rebuilt your resolv.conf randomly? I assumed that would be boot only. |
| 08:13 |
JBoyer |
I wouldn't mind seeing the back of cloud-init either. I spent 30+ mins last night trying to change network settings on a laptop "the right way" before giving up and just overriting /etc/netplan/50-... |
| 08:14 |
JBoyer |
(that file is one that starts with "Don't edit this file, changes won't be saved!" except I couldn't *make* the thing update it...) |
| 08:14 |
Dyrcona |
Yeahp. Linux is turning into Windows 98. |
| 08:17 |
Dyrcona |
No, I take that back. I think it's getting worse, somehow. |
| 08:59 |
|
sandbergja joined #evergreen |
| 09:22 |
|
aabbee joined #evergreen |
| 09:32 |
|
yboston joined #evergreen |
| 09:32 |
|
stephengwills joined #evergreen |
| 09:39 |
|
bos20k joined #evergreen |
| 10:14 |
Bmagic |
I've been part of conversations about Evergreen getting smarting about hold targeting regarding Geographic location. I just had an idea. What if We added a Longitude and Latitude column to actor.org_unit? And simply subtracted two branches Longitude and subtract their Latitude and arrive at a number. That number should basically represent the distance? |
| 10:15 |
Bmagic |
ABS( (a.longitude - b.longitude) + (a.latitude - b.latitude) ) = distance? |
| 10:16 |
Dyrcona |
Ah, the travelling salesman problem.... Good luck! |
| 10:16 |
Dyrcona |
Straight line distance <> road distance. |
| 10:16 |
Bmagic |
gotcha |
| 10:16 |
Dyrcona |
Though, it maybe a decent approximation. |
| 10:17 |
Bmagic |
that's what I was thinking |
| 10:17 |
gmcharlt |
YMMV in, say, Maryland |
| 10:17 |
aabbee |
abs? (a.long - b.long)**2 + (a.lat - b.lat)**2 https://en.wikipedia.org/wiki/Pythagorean_theorem ftw. or you could store "distance" as a weight of "drive time in minutes" |
| 10:17 |
Dyrcona |
It sounds like a decent idea. |
| 10:18 |
Dyrcona |
At MVLC we had configured hold weights or whatever to be based on the routes that the delivery company gave us. |
| 10:18 |
jeff |
or you could use a cost / routing metric, etc. think network routes or MX records. |
| 10:18 |
jeff |
but what problem are you trying to solve? |
| 10:18 |
Dyrcona |
This way, libraries were more likely to fill for the locations that came after them. |
| 10:18 |
jeff |
i suepect it's different for different organizations. |
| 10:18 |
gmcharlt |
there are other reasons to want to teach OUs their geographic coordinates, but I do think adding transit cost metrics would be a more general approach |
| 10:19 |
Dyrcona |
Another good reason to add coordinates: Showing a map from where you are to the library in the OPAC. I believe someone did that in BC. |
| 10:19 |
Bmagic |
we just heard from our courier that if we could teach the system to prioritize copies available in regions, it would be a major improvement. |
| 10:20 |
* Dyrcona |
is sadly drawing a blank on the name/handle...ldw? Liam? |
| 10:20 |
Dyrcona |
Yeah, it was Liam. |
| 10:20 |
Bmagic |
Liam - yes, I attended his presentation in 2016 |
| 10:21 |
Dyrcona |
Bmagic: It sounds like you need something smarter than just distance. If your courier has routes/regions, then you'll want to adjust proximity or something else to match that. |
| 10:21 |
Dyrcona |
It doesn't matter in Mass so much any more, since everything goes to one sorting facility before going anywhere else, now. |
| 10:24 |
Bmagic |
aabbee: thanks! Yes, that equation should be applied. a(squared) + b(squared) - I wasn't thinking in those terms but that makes more sense. And my 7th grade math teacher would be proud that I might be applying this in the real world! LOL. Queue the student complaints about "We'll never use this" |
| 10:24 |
Bmagic |
Queue/cue |
| 10:25 |
Dyrcona |
queue works for me...since I imagined it standing in a line behind the other complaints. :) |
| 10:25 |
Dyrcona |
"Take a number." |
| 10:25 |
Bmagic |
:) |
| 10:26 |
Dyrcona |
Bmagic: You can always try distance, but it might fall apart at the borders of 'regions' where two libraries are physically close, but on different schedules for the courier. |
| 10:26 |
Bmagic |
it's more about sorting facilities |
| 10:27 |
Bmagic |
if we can keep the items moving inside of a group of libraries served by the same sorting facility |
| 10:27 |
Dyrcona |
Right. Sound like you should get a copy of the routes and what goes where and adjust proximity accordingly. |
| 10:28 |
Dyrcona |
org unit lassos, if they [still] do anything, should help. |
| 10:28 |
Bmagic |
that's what we are going to do for sure |
| 10:28 |
jeff |
chrome issue from yesterday has been updated including link to possible related/duplicate bug: https://bugs.chromium.org/p/chromium/issues/detail?id=971368 and https://bugs.chromium.org/p/chromium/issues/detail?id=971641 |
| 10:30 |
jeff |
still not sure if there's any impact as long as you're running a point release that contains the code for bug 1797923 -- though again, we're also running with a loading="eager" element on the iframe (which i haven't yet tried without) |
| 10:30 |
pinesol |
Launchpad bug 1797923 in Evergreen 3.1 "Browser client iframe (catalog, etc.) loading page" [Medium,Fix released] https://launchpad.net/bugs/1797923 |
| 10:35 |
miker |
Bmagic: you may be able to do what you want with prox adjustments already. that lets you say things like "systems A and B are closer together". for each region, add a -0.5 to each of the cross product of all the systems in the region. plenty of rules, but if you maintain some external list it wouldn't be hard to maintain that automatically (esp if you don't have other adjustments and can just completely refresh the table as needed) |
| 10:39 |
Bmagic |
miker: right, I was aware of the prox adjustment but was trying to avoid it or at least make an attempt to make the system at least more* aware of proximity. For libraries and for Evergreen, it seems better to do it by hand but it's much more tedious and time consuming. The best way would be to bake a geomaps API in combination with courier sorting facilities addresses (for us probably). |
| 10:42 |
miker |
Bmagic: well, sure, geocoding would be good, but I think the problem that Dyrcona identified means the geolocation doesn't actually solve your problem. delivery regions aren't 1:1 with distance (phys location is just one input for them, and evergreen would never have all the info they have when defining a region) |
| 10:43 |
miker |
"they" being the delivery service |
| 10:43 |
rhamby |
yep, routes are often defined by means so cryptic that Terry Pratchett could have written novels around them |
| 10:47 |
|
yboston joined #evergreen |
| 10:49 |
jeff |
my favorite examples of distance calculations being naive and unhelpful are when retail web sites inform me that the next closest store to me is in Wisconsin. There is a rather great lake between there and here. |
| 10:49 |
abneiman |
rhamby: +1, would totally read that Pratchett book :) |
| 10:50 |
abneiman |
jeff: same, I live on the Eastern Shore of MD and I get recommendations for stores in Baltimore - the Chesapeake Bay is in the way - and for some reason never Delaware, which is actually closer to me |
| 10:50 |
gmcharlt |
and I would pay extra for a courier service that can actually use L-space |
| 10:50 |
abneiman |
gmcharlt++ |
| 10:50 |
jeff |
Green Bay, WI may be "closer" to me than Saginaw, MI as the crow files, but... |
| 10:51 |
jonadab |
So you're, like, in the Traverse City area? |
| 10:52 |
jonadab |
(It would actually make sense, if you were in the UP.) |
| 10:55 |
jonadab |
And yeah, delivery routes are designed around things someone outside the delivery organization can't know, like internal organizational structure. |
| 10:55 |
* miker |
thinks maybe a generalization in front the actual prox rule table would be useful... one entry of "Systems A, B, C, and D get hold priority for each other" generates all bidirectional rules as necessary; full ruleset rewrite when new general statement is recorded |
| 10:58 |
rhamby |
gmcharlt++ |
| 11:00 |
jeff |
jonadab: yes, Traverse City |
| 11:01 |
jeff |
jonadab: scrolling down through a "closest stores" frequently goes Green Bay, Saginaw, Kohler, Grand Rapids... |
| 11:01 |
jonadab |
Heh. |
| 11:01 |
jonadab |
I used to live about half an hour from Grand Rapids. In the late eighties. |
| 11:02 |
jonadab |
Those destinations are well dispersed. |
| 11:02 |
jeff |
(Kohler, WI being about a six hour drive, Grand Rapids, MI being about 2 to 2.5 hours) |
| 11:04 |
jonadab |
I mean, it could be worse. You could live in Montana, an hour's drive from the nearest grocery. |
| 11:06 |
* jeff |
nods |
| 11:07 |
jeff |
in most cases there's a local store for the retailer in question, i'm just often amused at the results not too far down the list. |
| 11:22 |
|
sandbergja joined #evergreen |
| 11:32 |
|
khuckins joined #evergreen |
| 11:36 |
|
jihpringle joined #evergreen |
| 12:17 |
|
jamesrf joined #evergreen |
| 12:17 |
|
cmalm joined #evergreen |
| 13:18 |
|
tlittle joined #evergreen |
| 13:35 |
JBoyer |
Bmagic, we do that kind of holds prox adjustement here; ask the courier for some kind of map or something that clearly shows their regions so you can tell who is where. |
| 13:35 |
Bmagic |
JBoyer: right on! We will most likely be exploring that |
| 13:35 |
JBoyer |
There's no point in doing much math, if the libraries are in the same region the added cost is 0, if they're a region away it doesn't matter if their on the border or the furthest end. |
| 13:36 |
Bmagic |
I was dreaming of Pythagorean Theorem |
| 13:36 |
* jeff |
overlays fractals on ZIP+4 maps |
| 13:37 |
* JBoyer |
can't un-see they're -> their, sigh.s |
| 13:37 |
jeff |
attach some red string, and we're fully prepared to explain things to all interested parties. they will be STOKED. |
| 13:37 |
JBoyer |
jeff++ |
| 13:39 |
Bmagic |
jeff++ |
| 13:39 |
Bmagic |
# red strings, lol |
| 13:41 |
jonadab |
JBoyer: https://www.smbc-comics.com/comics/1558189291-20190518%20%281%29.png |
| 13:42 |
JBoyer |
jonadab++ |
| 13:42 |
Bmagic |
jonadab++ # haha |
| 13:43 |
|
stephengwills joined #evergreen |
| 13:47 |
dluch |
FYI--the DIG meeting will be starting in 15 minutes :-) |
| 13:48 |
|
jefron joined #evergreen |
| 13:55 |
|
cmalm joined #evergreen |
| 14:00 |
dluch |
Okay, here we go! |
| 14:00 |
dluch |
#startmeeting 2019-06-06 - Documentation Interest Group |
| 14:00 |
pinesol |
Meeting started Thu Jun 6 14:00:11 2019 US/Eastern. The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:00 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:00 |
|
Topic for #evergreen is now (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:00 |
pinesol |
The meeting name has been set to '2019_06_06___documentation_interest_group' |
| 14:00 |
dluch |
The agenda can be found here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20190606-agenda |
| 14:00 |
dluch |
#topic Introductions |
| 14:00 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:00 |
dluch |
Please paste "#info <username> is <name>, <affiliation>" to identify who you are and what organization, if any, you represent. |
| 14:00 |
dluch |
#info dluch is Debbie Luchenbill, MOBIUS - DIG meeting facilitator |
| 14:01 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin College) |
| 14:01 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
| 14:01 |
abneiman |
#info abneiman, Andrea Buntz Neiman, Equinox |
| 14:01 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
| 14:01 |
|
jefron joined #evergreen |
| 14:02 |
cmalm |
#info cmal is Carissa Malmgren, Roanoke Public Library (Texas) |
| 14:02 |
remingtron |
cmalm: welcome! |
| 14:02 |
dluch |
cmalm: welcome! |
| 14:04 |
|
yboston joined #evergreen |
| 14:04 |
cmalm |
remingtron: thank you! |
| 14:04 |
cmalm |
dluch: thank you! |
| 14:04 |
dluch |
Thank you all for coming! |
| 14:05 |
dluch |
Anyone else, please feel free to introduce yourself as you come into the meeting |
| 14:05 |
dluch |
#topic Old Business: Conference wrap-up |
| 14:05 |
|
Topic for #evergreen is now Old Business: Conference wrap-up (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:05 |
dluch |
sandbergja: Thank you for leading DIG at the conference! |
| 14:05 |
dluch |
Minutes from that meeting are at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20190426-minutes |
| 14:05 |
dluch |
sandbergja++ |
| 14:05 |
sandbergja |
Happy to do it -- it was a good time. |
| 14:05 |
dluch |
sandbergja: Did you have anything you wanted to say about the DIG meeting at conference? |
| 14:06 |
dluch |
(else you wanted to say, lol) |
| 14:06 |
sandbergja |
I'm really interested in learning more about Antora -- Bmagic's presentation was really cool! |
| 14:07 |
sandbergja |
That's all I can think of at this time. :-) |
| 14:07 |
dluch |
Great, thanks! |
| 14:07 |
dluch |
Thanks, also, to everyone who came to the hackfest and especially to everyone who helped new folks get started and acclimated! I think we had 3 or 4 brand new people (?). |
| 14:07 |
dluch |
Anyone else? Comments, questions related to conference DIG stuff? |
| 14:07 |
remingtron |
hurray for brand new people! |
| 14:08 |
|
adurrence joined #evergreen |
| 14:08 |
dluch |
Yes! |
| 14:09 |
dluch |
#topic Documentation contributions and collaboration |
| 14:09 |
|
Topic for #evergreen is now Documentation contributions and collaboration (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:09 |
dluch |
#info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs |
| 14:09 |
dluch |
There are LOTS of documentation needs and several that have been identified as easy tasks for new folks. |
| 14:09 |
dluch |
Any other disucssion on documentation needs and/or the list? |
| 14:10 |
dluch |
We will be taking the latter part of this meeting to work on docs |
| 14:11 |
dluch |
#info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:digparticipants |
| 14:11 |
dluch |
We came up with these roles a few years ago, if I remember correctly, but I'm not sure we've ever had all of them filled. So if anyone would like to fill a particular role, please feel free to volunteer! |
| 14:11 |
dluch |
And is there anyone listed in a role they would like to pull back from? |
| 14:11 |
dluch |
Also, the Facilitator role includes coordinating training and I just wanted to mention that, while I'm perfectly happy to coordinate training for the hackfest (or otherwise) that we might want, I'll be tapping others to actually do the training. ;-) |
| 14:12 |
remingtron |
dluch: sounds good! the facilitating/coordinating is certainly a piece we've been lacking in DIG. |
| 14:13 |
dluch |
Oh, speaking of facilitator role, can someone with website updating privileges update the DIG listing on the committees page? https://evergreen-ils.org/communicate/committees/ |
| 14:14 |
sandbergja |
dluch: I can check to see if I have that permission |
| 14:14 |
dluch |
sandbergja: Thanks! |
| 14:14 |
dluch |
#topic Evergreen Quick Start documentation |
| 14:14 |
|
Topic for #evergreen is now Evergreen Quick Start documentation (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:15 |
abneiman |
sandbergja: I definitely have website perms if it turns out you don't |
| 14:15 |
dluch |
sandbergja: Did you add this to the agenda? Can you talk about this? |
| 14:15 |
dluch |
abneiman: Thank you! |
| 14:15 |
sandbergja |
Yes! That was me. |
| 14:15 |
dluch |
Take it away! |
| 14:15 |
sandbergja |
This is an idea that came up in the NW Evergreen User Symposium + the hackfest |
| 14:15 |
sandbergja |
We were talking about the documentation needs of folks like volunteers, student workers, and others who don't have much of a library background. |
| 14:16 |
sandbergja |
(and don't have much patience for huge manuals of documentation with lots of library concepts) |
| 14:16 |
sandbergja |
So we came up with the idea of providing quick starts |
| 14:16 |
sandbergja |
naming credits go to abneiman |
| 14:17 |
sandbergja |
The goal is to make a pair of 1 video + 1 one-page reference sheet, with jargon-free, local policy-free, non-customized instructions |
| 14:17 |
sandbergja |
To cover the most fundamental tasks in Evergreen, like check in, check out, attach a holding to a bib record, etc. |
| 14:17 |
sandbergja |
I've experimented a bit with making the one-pager in asciidoc, and came up with this: |
| 14:17 |
sandbergja |
#link http://www.sandbox.lbcc.linnlibraries.org/Evergreen/docs/quickstarts/check_out.html |
| 14:17 |
sandbergja |
But, uh, I was thinking that it would be worth it to consider technologies other than asciidoc too, like Google Docs or the wiki |
| 14:17 |
sandbergja |
Some pros and cons here: |
| 14:17 |
sandbergja |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:quickstarts |
| 14:17 |
sandbergja |
What do you all think? |
| 14:18 |
remingtron |
I think asciidoc is still a strong choice |
| 14:18 |
dluch |
I think that's an awesome idea! |
| 14:18 |
remingtron |
especially with the ability to edit and preview in GitHub |
| 14:18 |
remingtron |
and yes, I love the idea too |
| 14:19 |
abneiman |
yeah, agreed with asciidoc -- unless/until we wholesale switch to something else. |
| 14:19 |
remingtron |
I totally support having a different stylesheet if we think it would benefit the different audience |
| 14:19 |
abneiman |
Also, I love having the use case at the top of your demo doc sandbergja |
| 14:20 |
dluch |
Yes! The use case is a great feature! |
| 14:20 |
sandbergja |
Thanks! If you do print preview, the video disappears, and the link url appears, which I was pretty proud of :-D |
| 14:21 |
sandbergja |
But fitting it all on one page really depends on what browsers, fonts, settings you happen to have |
| 14:21 |
dluch |
sandbergja++ |
| 14:21 |
dluch |
So, sandbergja, how would you envision DIG adopting this idea? Add quick starts to the list of docs needs or keep it on a separate page, or...? |
| 14:22 |
sandbergja |
Good question! |
| 14:22 |
remingtron |
is the "one page" goal specifically about printing to a single sheet of paper? Or generally a "one screenful" idea? |
| 14:23 |
sandbergja |
I was thinking printing to one sheet of paper |
| 14:24 |
dluch |
I can see how keeping it to one sheet would be really helpful for those kinds of "casual" ILS users. And those who supervise/train them. |
| 14:24 |
remingtron |
maybe we could have a PDF version (semi-hand-crafted) for the actual printing |
| 14:25 |
remingtron |
since predictable printing from a browser seems hard. |
| 14:25 |
sandbergja |
agreed |
| 14:25 |
sandbergja |
I had some issues getting a2x and fop to do a one-pager |
| 14:26 |
sandbergja |
and finally realized I was in way over my head |
| 14:26 |
sandbergja |
So I think it would be helpful for somebody who is more familiar with those technologies to put together a working proof of concept |
| 14:27 |
dluch |
Lol. I don't even know what those are. |
| 14:28 |
|
alynn26_ joined #evergreen |
| 14:28 |
sandbergja |
they are the tools we use to convert asciidoc into PDFs currently |
| 14:28 |
dluch |
Oh, I just looked it up |
| 14:28 |
dluch |
gotcha |
| 14:28 |
sandbergja |
And fop seems to get really complicated really fast |
| 14:29 |
sandbergja |
...which was part of my thought in suggesting a really familiar tool like Google Docs |
| 14:31 |
remingtron |
could we make the single-page printing a secondary goal of the project? start with simple AsciiDoc files? |
| 14:32 |
dluch |
So, sandbergja, would you like someone else to try converting your sample page into a 1-page pdf? |
| 14:32 |
remingtron |
or does that remove too much of the value? |
| 14:32 |
dluch |
That seems like a good way to start, remingtron. |
| 14:33 |
sandbergja |
agreed, that seems like a good way to get the project off the ground |
| 14:33 |
sandbergja |
We'd also need to figure out the topics that should have a quickstart |
| 14:33 |
sandbergja |
but that can be a discussion for another time |
| 14:33 |
remingtron |
sandbergja: do you have ideas already that you could add to the "needs" wiki page? |
| 14:33 |
remingtron |
to get us started |
| 14:34 |
|
khuckins joined #evergreen |
| 14:34 |
dluch |
Yes! That seems like something we can all be thinking about for the next meeting, too. |
| 14:35 |
alynn26_ |
I say add it to the wiki. |
| 14:35 |
dluch |
I like the idea of keeping everything together on the "needs" wiki but do we need to worry about the page getting too long? |
| 14:36 |
sandbergja |
remingtron: just check in, check out, and adding holdings -- I'm sure there are others |
| 14:36 |
remingtron |
dluch: my only concern about length of that page is: Keep the "stuff for new contributors" at the top. |
| 14:37 |
remingtron |
I'm personally happy to swim through a long wiki page |
| 14:37 |
dluch |
remingtron: yes, good idea, so that's always uber-visible and easy to find |
| 14:38 |
dluch |
So, we can add a new section to the Needs wiki for Quick Starts and start adding things there as we think of them. Sound like a plan? |
| 14:38 |
dluch |
Do we need to make an action? We haven't made any this meeting, lol. |
| 14:38 |
remingtron |
dluch: you can give that action to me if you want, but I have to leave the meeting. See you all later! |
| 14:39 |
dluch |
Thanks, remingtron! Bye! |
| 14:39 |
dluch |
#action remingtron will create a new "Quick Starts" section to the Documentation Needs wiki and we will all add ideas there |
| 14:40 |
dluch |
Any other things we need to talk about related to this agenda item? |
| 14:40 |
dluch |
Thanks, sandbergja and the NW Evergreen User Symposium for this great idea! |
| 14:41 |
dluch |
#topic Other Business |
| 14:41 |
|
Topic for #evergreen is now Other Business (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:41 |
dluch |
Anyone have other DIG business they want to talk about today? |
| 14:42 |
dluch |
Okay, then... |
| 14:42 |
dluch |
#topic One on one and small group documentation collaboration |
| 14:42 |
|
Topic for #evergreen is now One on one and small group documentation collaboration (Meeting topic: 2019-06-06 - Documentation Interest Group) |
| 14:42 |
dluch |
We have about 20 minutes. What's everyone working on? |
| 14:43 |
abneiman |
I'm still planning to follow remington's suggestion to add a commit with index terms to this PR https://github.com/evergreen-library-system/Evergreen/pull/79 |
| 14:44 |
abneiman |
also, cmalm, if you have questions for any of us please feel free to ask :) |
| 14:45 |
dluch |
+1 |
| 14:45 |
dluch |
I need to go through the needs list and take some new things. |
| 14:45 |
sandbergja |
I think I'll try to write a script for a video for the check out quick start |
| 14:48 |
jihpringle |
sandbergja: we did a check out video with the basics for 3.1 - https://www.youtube.com/watch?v=e074WkZ8xBo |
| 14:49 |
sandbergja |
jihpringle++ |
| 14:49 |
sandbergja |
Thank you! |
| 14:49 |
jihpringle |
if it's helpful as a starting point you can find the script here - https://docs.google.com/document/d/1inzm9es731Ut6-LjvFyPdsbXTGIzx3WJec9fhRSglqo/edit?usp=sharing |
| 14:52 |
sandbergja |
it really is -- this is excellent |
| 14:52 |
jihpringle |
for our new videos we've been trying to ensure we include closed captioning so the scripts for all should be available through the transcripts (I'm also happy to share out the actual scripts if that's easier for copy/pasting/adapting) |
| 14:53 |
dluch |
jihpringle: That's fantastic! |
| 15:00 |
dluch |
We're at the hour mark, so I'm going to close the DIG Meeting. Thanks for coming and collaborating, everyone! |
| 15:00 |
dluch |
#endmeeting |
| 15:00 |
|
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 |
| 15:00 |
pinesol |
Meeting ended Thu Jun 6 15:00:33 2019 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:00 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-06-06-14.00.html |
| 15:00 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-06-06-14.00.txt |
| 15:00 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2019/evergreen.2019-06-06-14.00.log.html |
| 15:00 |
jihpringle |
dluch++ |
| 15:01 |
abneiman |
dluch++ |
| 15:02 |
Bmagic |
dluch++ |
| 15:02 |
remingtron |
dluch++ |
| 15:03 |
devted |
dluch++ |
| 15:04 |
sandbergja |
dluch++ |
| 16:02 |
|
stephengwills joined #evergreen |
| 16:02 |
|
stephengwills left #evergreen |
| 17:31 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 19:00 |
|
mrArcadeX joined #evergreen |
| 19:04 |
mrArcadeX |
Hello |
| 19:04 |
mrArcadeX |
I have an Evergreen question if anyone is available. |
| 19:06 |
jeff |
ask away, stick around, answers you may find. |
| 19:07 |
jeff |
irc can be pretty async -- i wouldn't worry about trying to find someone to answer before you even ask. |
| 19:07 |
mrArcadeX |
haha ok |
| 19:08 |
mrArcadeX |
I'm from Florence County Library System in SC and Evergreen was down for us today for a while; now we are not receiving normal updates to EnvisionWare but Evergreen seems to be fine now. |
| 19:09 |
mrArcadeX |
I spoke to EnvisionWare tech support and they said that our port my need to be reset on the Evergreen side. |
| 19:09 |
mrArcadeX |
*may |
| 19:10 |
jihpringle |
if you use SIP2 for authentication between Evergreen and Envisionware the SIP server may need to be restarted |
| 19:14 |
jihpringle |
might need to be done at your consortium level, depends on your set up |
| 19:17 |
mrArcadeX |
I'm thinking that it may need to be done at consortium level; our login credentials are in the Validating Authority and I can ping the address. The logs show us sending out requests but nothing being received (since Evergreen went down consortium wide today). |
| 19:55 |
|
sandbergja joined #evergreen |
| 20:31 |
|
yar joined #evergreen |
| 20:44 |
|
stephengwills joined #evergreen |
| 21:04 |
|
sandbergja joined #evergreen |
| 22:06 |
|
stephengwills joined #evergreen |
| 22:19 |
|
stephengwills joined #evergreen |
