Evergreen ILS Website

IRC log for #evergreen, 2019-10-10

| 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
00:36 sandbergja joined #evergreen
00:53 jeff_ joined #evergreen
06:50 agoben joined #evergreen
07:05 rjackson_isl joined #evergreen
07:21 rfrasur joined #evergreen
08:23 bos20k joined #evergreen
08:41 mmorgan joined #evergreen
08:49 bos20k_ joined #evergreen
08:54 bos20k joined #evergreen
08:56 Dyrcona joined #evergreen
09:04 mmorgan left #evergreen
09:15 collum joined #evergreen
09:32 aabbee joined #evergreen
09:38 remingtron joined #evergreen
09:40 jvwoolf joined #evergreen
09:56 mmorgan joined #evergreen
10:14 sandbergja joined #evergreen
10:33 Dyrcona Has anyone tried Z39.50 with Evergreen 3.4.0?
10:33 Dyrcona I just did and got storage and search errors.
10:37 Dyrcona Eh, nope. Configuration issue. Needed to change - to CONS in the default config.
10:37 Dyrcona It's working, now.
10:41 mmorgan left #evergreen
11:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
12:04 sandbergja joined #evergreen
12:05 jihpringle joined #evergreen
12:23 Bmagic berick: what's wrong with ES 7xx?
12:25 berick Bmagic: the Perl API only goes to v6 at the moment.  It won't work with v7 because of a small change in the index definition syntax
12:25 Bmagic oh dang!
12:25 Bmagic I didn't notice that
12:25 * berick is watching the perl site for new releases
12:47 collum joined #evergreen
12:52 sandbergja_ joined #evergreen
12:58 collum_ joined #evergreen
13:01 collum_ joined #evergreen
13:12 khuckins joined #evergreen
13:30 dluch_ Reminder -- the DIG meeting begins in 30 minutes
14:00 dluch Time for DIG!
14:00 dluch #startmeeting 2019-10-10 - Documentation Interest Group Meeting
14:00 pinesol Meeting started Thu Oct 10 14:00:16 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-10-10 - Documentation Interest Group Meeting)
14:00 pinesol The meeting name has been set to '2019_10_10___documentatio​n_interest_group_meeting'
14:00 dluch #topic Agenda
14:00 Topic for #evergreen is now Agenda (Meeting topic: 2019-10-10 - Documentation Interest Group Meeting)
14:00 dluch #info The agenda can be found here:  https://wiki.evergreen-ils.org/doku.php?id=​evergreen-docs:dig_meetings:20191010-agenda
14:00 dluch Welcome everyone!  Today's meeting will be primarily collaboration and working on documentation.
14:00 dluch #topic Introductions
14:00 Topic for #evergreen is now Introductions (Meeting topic: 2019-10-10 - Documentation Interest Group Meeting)
14:00 bjwillis joined #evergreen
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
14:02 jweston #info jweston is Jennifer Weston, Equinox
14:02 bjwillis #info bjwillis is Beth Willis, NOBLE
14:02 stephengwills #info stephengwills is himself with Maine Balsam Libraries
14:04 dluch Thank you all for coming! It appears we are a small but mighty group today.  If you join in later, feel free to introduce yourself when you arrive.
14:05 dluch #topic Helpful Information: Documentation contributions and collaboration
14:05 Topic for #evergreen is now Helpful Information: Documentation contributions and collaboration (Meeting topic: 2019-10-10 - Documentation Interest Group Meeting)
14:05 dluch #info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php​?id=evergreen-docs:documentation_needs
14:05 dluch #info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.p​hp?id=evergreen-docs:digparticipants
14:05 dluch That's all just FYI.
14:05 dluch #topic Business
14:05 Topic for #evergreen is now Business (Meeting topic: 2019-10-10 - Documentation Interest Group Meeting)
14:05 dluch #info Update on Documentation server move
14:06 dluch I'm not sure either of them are here, but...
14:06 dluch rsoulliere and/or gmcharlt, where are we with this?
14:06 gmcharlt dluch: stalled, though I hope to make more progress during the hack-a-way
14:07 dluch gmcharlt: Excellent, thanks for the update!
14:07 dluch gmcharlt++
14:07 dluch #info We will catch up on other action items and business at the November meeting
14:07 dluch That said, is there anything pressing anyone needs to bring up?
14:08 dluch Alrighty, then
14:09 dluch #topic Collaboration time
14:09 Topic for #evergreen is now Collaboration time (Meeting topic: 2019-10-10 - Documentation Interest Group Meeting)
14:10 dluch We would generally have the rest of our meeting time to work on documentation.  Since there's only four of us...does everyone have something they were planning to work on today?  Or should we just end the meeting super-early?
14:10 jweston quick question from me - I would like to add missing settings to the Library Settings Overview tables (in Chapter 68) but I do not yet do ascii, what's the best way to share my updates?
14:10 stephengwills I have been tasked with fixing notifications that are not working for balsam.
14:11 abneiman dluch: comment from peanut gallery - docs twitter chat yesterday was archived here if anyone wants to check it out: https://twitter.com/i/moments/1181986368832131082
14:11 jweston abneiman++
14:12 abneiman (I'm in a training, sorry for missing meeting)
14:12 dluch jweston: Please send it as an attachment to the documentation list.  Make sure to include any screen shots you want put in as separate images.  Also indicate where, exactly, in the documentation you want your piece(s) added
14:12 dluch abneiman: Thank you!!
14:12 dluch abneiman++
14:12 jweston dluch++ will do
14:12 abneiman also, jweston I can give you an ascii crash course at some point if you want
14:12 abneiman jweston++ # docs adds
14:12 jweston abneiman: ++ would love that
14:13 abneiman ...acutally I guess it would make sense to do a community crash course on asciidoc
14:13 abneiman dluch: will you please give me an action item to look into doing that?
14:13 dluch stephengwills: You're doing documentation on fixing notifications?  Is there anything we can help with or any questions you have?
14:13 bjwillis yes, that would be great!
14:13 dluch abneiman: Yes!  Thank you for that!
14:14 abneiman dluch++ thanks
14:14 stephengwills Ive really just started but I’m sure I’ll have questions.
14:14 jweston +1 to community crash course on asciidoc
14:14 * abneiman vanishes again
14:14 stephengwills I just broadcast into IRC as necessary, correct?
14:14 stephengwills le poof!
14:14 dluch #action abneiman will look into a community crash course on ascii
14:15 dluch stephengwills: Yep.  Right now during the DIG meeting, we can talk about docs questions, but if you need help with the actual fixing, just broadcast into IRC after the meeting
14:15 stephengwills generally I just use BBEdit on my mac to generate first drafts.  perhaps the asciidoc course will have happened befor I need it.
14:16 dluch Yes!
14:16 stephengwills and I’ve blocked out time tomorrow morning to work on it but if we just about done I’ll start going after it right now.
14:17 dluch Any other questions folks have?  Documentation you're planning to work on?  If you'd like extra accountability, I can make an action item to show up in the minutes, but it's not necessary.
14:17 dluch If not, I'm thinking we can just end early?
14:18 stephengwills one question
14:18 stephengwills i’m looking at https://wiki.evergreen-ils.org/doku.php​?id=evergreen-docs:documentation_needs
14:18 bjwillis I have a basic question.  What is the best way to update existing documentation?  Do I need access to the most current adoc?
14:19 stephengwills and the section that talks about undocumented needs from the releases
14:19 stephengwills those would NOT be in launchpad, correct?  how to I note that I’m working on them?
14:20 stephengwills i.e. 3-day courtosy notices via SMS
14:20 stephengwills sp, sorry
14:21 dluch We will accept updates in just about any form you want to submit them!  If you're comfortable with github, you can do edits there on a branch and then make a pull request.  If you'd rather do them in Notepad or Word, or whatever, that's fine, too, and just email to the documentation listserv, as I mentioned to jweston earlier.
14:21 remingtron stephengwills: you can put your name next to the item on the wiki page
14:21 dluch stephengwills: Most of them are not in launchpad, unless there's a bug link attached somewhere on the line
14:21 remingtron stephengwills: do you have a wiki account?
14:21 dluch Yep, what remingtron said, lol
14:22 stephengwills I must have one somewhere.  it was in my top dresser drawer last week.
14:22 dluch If you don't have a wiki account, you can request one.  Or you can just let me know and I can add your name next to the item you're working on.
14:22 stephengwills ok thanks
14:23 dluch stephengwills: Yay for knocking out undocumented needs!
14:24 jweston stephengwills: I just added your name to 3 Day Courtesy Notice by SMS
14:24 dluch Anything else?
14:24 stephengwills ok, thanks
14:24 dluch jweston++
14:24 dluch stephengwills++
14:25 stephengwills and I just got a PW reset link to te wiki so I’ll be up to speed again shortly.
14:25 jweston stephengwills ++
14:25 dluch Great!
14:25 dluch Okay, I'm going to call the meeting, then.  Feel free to use the rest of this hour to work on documentation, though, if you need the set-aside time!
14:25 dluch Next meeting will be November 7.  Same bat time, same bat channel.  Business meeting first then collaboration time.
14:26 dluch Thanks for coming!
14:26 jweston dluch:++ thanks for leading!
14:26 dluch #endmeeting
14:26 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:26 pinesol Meeting ended Thu Oct 10 14:26:16 2019 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:26 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-10-10-14.00.html
14:26 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-10-10-14.00.txt
14:26 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2019/evergreen.2019-10-10-14.00.log.html
14:26 dluch :-)
14:26 stephengwills Holy efficiency
14:27 dluch LOL
14:31 nfBurton joined #evergreen
14:39 troy__ is there a way to prevent holds being modified to another pickup location?
15:05 Dyrcona troy__: Remove the UPDATE_HOLD permission from staff, assuming that it is actually being used.
15:06 troy__ ahh overlooked that. it's actually patrons through our custom interface. that will prob prevent them from freezing too then eh?
15:06 troy__ might just implement a custom solution around this
15:07 troy__ thanks for the help Dyrcona :)
15:08 Dyrcona troy__: Yes, I think you'll have to do something local.  There's no way in stock Evergreen to prevention changing the pickup location on a hold, other than preventing updates entirely.
15:10 jeff troy__: mostly out of curiosity... what's your use case?
15:16 troy__ we have oversize items that are too big to easily move between branches all the time
15:16 troy__ like mega chess that takes up 4 16lb bags
15:16 troy__ so we're trying to relegate items to only our main location
15:17 Dyrcona troy__: You have hold matrix matchpoints that only allow them for pickup at the main branch?
15:17 troy__ yea
15:17 troy__ but patrons can still modify. don't want to prevent them from cancelling / freezing, though
15:18 troy__ thought of a friend end solution with our harvested data to limit cases
15:23 Dyrcona Well, the update holds code could be made to respect holds matrix and other rules, but that might slow things down too much.
15:23 Dyrcona And, it would require a bit of new code.
15:25 troy__ yea for sure. wouldn't worry about it. pretty marginal use case here and we can get around it with minimal dev
15:29 gsams__ joined #evergreen
15:29 Dyrcona Not so sure the use case is marginal. Lots of places have things that are only available for pickup at one location. That said, there may sometimes be other items that could still fill the hold.
15:29 cmalm_ joined #evergreen
15:29 * jeff nods
15:29 jeff we have similar needs, which is partly why I was wondering.
15:30 jeff we also have externally managed holds which don't support changing pickup location.
15:32 troy__ happy to talk about how we're handling things whenever. our setup is is a little different. hoping to get our php evg api opened up fairly soon
15:32 * jeff nods
15:32 jeff (nod re: your env)
15:43 cmalm joined #evergreen
15:45 gsams joined #evergreen
16:10 mmorgan joined #evergreen
16:26 khuckins joined #evergreen
16:28 jvwoolf left #evergreen
17:06 mmorgan left #evergreen
17:28 khuckins joined #evergreen
17:45 JBoyer_ joined #evergreen
19:04 cmalm joined #evergreen
19:29 StomproJosh joined #evergreen
20:14 sandbergja joined #evergreen
23:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
23:40 sandbergja joined #evergreen

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