Evergreen ILS Website

IRC log for #evergreen, 2020-02-06

| 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:23 abowling1 joined #evergreen
00:38 sandbergja joined #evergreen
07:07 rjackson_isl joined #evergreen
07:24 collum joined #evergreen
07:51 rfrasur joined #evergreen
08:15 Dyrcona joined #evergreen
08:18 yboston joined #evergreen
08:21 rfrasur_ joined #evergreen
08:26 rjackson_isl joined #evergreen
08:38 mmorgan joined #evergreen
08:48 rfrasur joined #evergreen
08:50 rfrasur_ joined #evergreen
08:52 rjackson_isl joined #evergreen
08:55 rfrasur joined #evergreen
08:59 mantis1 joined #evergreen
09:01 mmorgan1 joined #evergreen
09:02 rfrasur_ joined #evergreen
09:02 kip joined #evergreen
09:34 Dyrcona berick | csharp: If you have any thoughts on bug 1858448, they would be appreciated.
09:34 pinesol Launchpad bug 1858448 in Evergreen 3.4 "Aged Payment (and Billing) Table Breaks Cash Report and Removes Relevant Payment Tracking Abilities" [High,Confirmed] https://launchpad.net/bugs/1858448
09:59 StomproJosh joined #evergreen
10:16 jvwoolf joined #evergreen
10:30 sandbergja joined #evergreen
10:30 Bmagic I've got a few bib records that won't save. Upon clicking save the browser console spews tons of errors ""me.controlSet(...) is undefined"" forever until the page is reloaded. Comparing that to a bib that does save, I found that those errors appear upon page load but do not appear after saving....
10:32 Bmagic acctually, correction, those errors are spewing forever upon page load and never stop for the troubled bibs. Whereas on non-troubled bibs: those errors appear but do not go on forever.
10:36 mmorgan joined #evergreen
10:36 berick Dyrcona: commented.  I'm happy to help on that one.
10:46 Bmagic it's a different error in Chrome: TypeError: Cannot read property 'bib_fields' of undefined
10:58 Bmagic hmmmm, it seems that updating the 001 to agree with the BIB ID resolved it....
11:17 Dyrcona Bmagic: I think there's a related LP bug for the editor changing the 001. Do you have the flag cat.bib.use_id_for_tcn set?
11:17 Dyrcona berick++
11:18 Bmagic Dyrcona: that flag is set to true
11:19 Bmagic so that's it - if the 001 doesn't agree with the BIB ID AND that flag is set true - this error happens
11:19 Bmagic I believe that setting used to be false which would explain how the bib exists in the first place
11:20 Dyrcona Bmagic: Maybe. It's supposed to replace the 001 with the bib id and move the original 001 to an 035 on import.
11:20 Dyrcona You can try setting it back to false to see if that helps.
11:21 Dyrcona BTW, bug 1859191 indicates that the web staff client MARC editor ignores that flag.
11:21 pinesol Launchpad bug 1859191 in Evergreen "Editing and saving MARC record changes the TCN value" [High,Confirmed] https://launchpad.net/bugs/1859191
11:21 Bmagic Dyrcona++
11:23 Dyrcona Too many moving parts--
11:23 Dyrcona :)
11:37 Dyrcona So, I added two new languages to the language filters and reingested the item_lang record attribrutes, but search is not pulling up records for those languages.
11:37 Dyrcona Specifically, I've got a record with two 041$a on for eng and for per. This record comes up if I limit the search to eng, but not if I limit the search to per (Persian).
11:39 Dyrcona I also added Armenian, and it doesn't appear to be working. I added Hebrew last year, and that seems to be working OK.
11:40 Dyrcona I'll try the metabib.reingest_record_attributes again, but in the meantime if anyone has any ideas....
12:17 sandbergja Dyrcona: just to check, does the item_lang entry in Administration>Server Administration>Record Attribute Definitions include 041$a?
12:17 sandbergja That should have been added with multilingual search in 3.1
12:17 Dyrcona sandbergja: I don't use the Administration interface. The crad enty in the database does.
12:18 sandbergja :-( that was my only idea
12:19 Dyrcona tag = 041 sf_list = abdefgm
12:19 Dyrcona I think the ingest blew up silently, so I'm trying again.
12:25 Dyrcona Maybe I should try something less ham-fisted? https://pastebin.com/UBwMTX7Q
12:39 khuckins joined #evergreen
12:47 jihpringle joined #evergreen
12:48 Dyrcona And, now, I'm being asked to expand the number of 041 subfields used.
13:01 dluch Friendly reminder that the DIG meeting will begin in 1 hour
13:27 sandbergja Christineb: Just saw that you are the community spotlight!  Very well deserved!
13:28 sandbergja Christineb++
13:28 Christineb sandbergja - Thank you!!! :)
13:56 dluch 5 minutes to the DIG meeting!
14:00 dluch #startmeeting 2020-02-06 - Documentation Interest Group Meeting
14:00 pinesol Meeting started Thu Feb  6 14:00:26 2020 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: 2020-02-06 - Documentation Interest Group Meeting)
14:00 pinesol The meeting name has been set to '2020_02_06___documentatio​n_interest_group_meeting'
14:00 dluch #topic Agenda
14:00 Topic for #evergreen is now Agenda (Meeting topic: 2020-02-06 - 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:20200206-agenda
14:00 dluch Welcome everyone!  Today's meeting will be primarily collaboration and working on documentation.
14:01 dluch #topic Introductions
14:01 Topic for #evergreen is now Introductions (Meeting topic: 2020-02-06 - Documentation Interest Group Meeting)
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:01 sandbergja #info sandbergja is Jane Sandberg, Linn-Benton Community College
14:01 cmalm #info cmalm is Carissa Malmgren, Roanoke Public Library
14:02 rfrasur_ #info rfrasur is Ruth Frasur, Indiana State Library/Evergreen Indiana/ECDI
14:04 dluch Small group today. Thank you for coming! If you join in later, feel free to introduce yourself when you arrive.
14:04 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
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: 2020-02-06 - 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 We are going to do a couple of quick business items, but let's try to get through them fairly quickly...
14:05 dluch #topic Business
14:05 Topic for #evergreen is now Business (Meeting topic: 2020-02-06 - Documentation Interest Group Meeting)
14:05 dluch #info Update on Documentation server move
14:06 dluch gmcharlt: (or anyone) Where are we with this?
14:07 dluch Well, we'll just circle back around to this topic next month!
14:07 dluch #info Quick update on Antora progress
14:07 dluch remingtron and bmagic: Where are we with Antora nav progress?
14:08 remingtron dluch: let me check...
14:08 Bmagic It's not "done" but remingtron has gone through several of the "modules"
14:08 Bmagic has it been a month already?
14:08 remingtron Bmagic: my thoughts exactly
14:08 dluch It has, lol!
14:09 dluch How about we come back to this in more detail for the March meeting?
14:09 remingtron We still need to figure out how to do the topic manuals in Antora
14:09 remingtron dluch: sounds good
14:09 dluch Great.  Thanks for all your work on this!
14:09 dluch remingtron++
14:10 dluch bmagic++
14:10 dluch #info We will catch up on other action items at business at the March meeting
14:10 dluch #info Anythihng else pressing?
14:10 sandbergja I am wondering about if we can get antora into 3.5
14:10 Bmagic sandbergja: any feedback from your folks? I seem to remember you were asking people
14:10 Bmagic I see the feedback on the LP bug
14:11 sandbergja Bmagic: they liked it!  The main feedback was about the navs
14:11 Bmagic bug 1848524
14:11 pinesol Launchpad bug 1848524 in Evergreen "wishlist: Antora-ize docs " [Undecided,New] https://launchpad.net/bugs/1848524
14:11 remingtron sandbergja: we'll need a new docs server from gmcharlt before we can publish them
14:12 dluch sandbergja: thanks for getting the feedback from your folks!
14:12 sandbergja I am worried about us having to maintain both the Antora branch and the main repo for too long
14:12 Bmagic sandbergja++ # fur sur
14:12 khuckins joined #evergreen
14:12 sandbergja I suspect that we will end up with content missing from both
14:12 remingtron sandbergja: that's a good concern
14:12 dluch sandbergja++ and sandbergja's people++
14:12 sandbergja We could probably host antora on docs-testing for a while
14:12 sandbergja ??
14:13 Bmagic works for me
14:13 remingtron sounds ok
14:13 dluch That sounds good.
14:13 dluch What's necessary for that?
14:13 sandbergja dluch: great question!
14:14 sandbergja I can explore that as my project for the rest of the meeting. :-)
14:14 sandbergja especially if remingtron and Bmagic are around to bounce questions off of
14:14 sandbergja :-)
14:15 dluch sandbergja++
14:15 Bmagic :)
14:15 dluch Should we also add an action item for next time or no?
14:15 remingtron sandbergja: I'll be around, though Bmagic has handled all the install stuff so far
14:15 sandbergja yay!
14:16 sandbergja Hmmmm... I remember the cutoff for 3.5 features being before the next DIG meeting
14:16 dluch Oh, that's probably true
14:16 Bmagic awwww, no 3.5 then?
14:16 Bmagic maybe if we begged
14:17 dluch Well, work on it may have to be done in between meetings
14:17 Bmagic I'm not sure it needs to be included in the release in order to put it up
14:17 Bmagic Taking advantage of the "versioning" in antora would be nice though
14:18 dluch Feb. 26 was what berick said was feature freeze
14:19 dluch Well, let's see what sandbergja figures out today, then go from there
14:19 Bmagic with that date in mind - what if we all set aside some time on our calendars to meet up and finish it up...
14:19 sandbergja What needs to be finished at this point?
14:19 Bmagic are all of the sections done?
14:19 sandbergja And does it seem like we have enough consensus that antora is a direction that we want to move to?
14:21 Bmagic sandbergja: that was the impression I got at the hack-a-way
14:21 dluch I believe so.  When we have talked about it at previous meetings, everyone seems pretty happy with it, other than some of the nav stuff
14:22 Bmagic but that said - I think we can drop it. LOL
14:22 dluch Okay, lol.  moving on... (and you can keep talking about it in collaboration time, if you want)
14:22 dluch Today's meeting is mainly for collaboration time, so let's move on to that!
14:23 dluch #topic Collaboration time
14:23 Topic for #evergreen is now Collaboration time (Meeting topic: 2020-02-06 - Documentation Interest Group Meeting)
14:23 dluch What is everyone planning to work on today?  Please let us know here, and feel free to talk and work with each other.  If you'd like extra accountability, I can make an action item to show up in the minutes, but it's not necessary.
14:24 Bmagic remingtron sandbergja dluch - These modules have been touched: opac, development, admin_initial_setup, cataloging, shared, acquisitions
14:25 remingtron the remaining modules should be easy
14:25 dluch bmagic: thanks.  And what's still left?
14:25 remingtron I tried to tackle the harder more complex ones
14:25 dluch remingtron++
14:26 Bmagic which leaves admin/ api/ appendix/ installation/ local_admin/ reports/ serials/ using_staff_client/ sys_admin/
14:26 Bmagic I think*
14:28 remingtron I think local_admin and sys_admin are both empty
14:28 remingtron just placeholders for the nav files
14:30 Bmagic that's good
14:31 Bmagic I'll nab reports
14:32 dluch Unrelated to all that, but just as an fyi (and for accountability)... I've had a bunch of balls in the air, so haven't done much documenting, but I should have a little more time soon.  So I will look over our needs list and pick at least two things to do before the next meeting.
14:34 jvwoolf joined #evergreen
14:36 Bmagic oh and circulation still needs done
14:44 Bmagic remingtron: did you deal with "indexterm:[bla bla bla]" - whilst reviewing?
14:45 remingtron Bmagic: hm, doesn't sounds familiar
14:45 Bmagic Not sure - leave it?
14:46 remingtron I think that's real AsciiDoc, so I'd vote leave it, unless it causes a problem
14:46 * rfrasur_ is "listening and learning", btw.
14:47 * Bmagic loves rfrasur_
14:47 * rfrasur_ also loves Bmagic
14:50 dluch rfrasur++
14:59 dluch We are at time.  Thanks for all the great work, everyone!  Feel free to keep going after the meeting!
14:59 dluch The next meeting will be March 5. Same time, same place. Regular business meeting first then collaboration time (if there's time).
14:59 dluch Please continue using the email list for questions and other things that come up in between meetings.
14:59 dluch And/or Launchpad
15:00 dluch Thanks for coming!
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 Feb  6 15:00:14 2020 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:00 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2020/evergreen.2020-02-06-14.00.html
15:00 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2020/evergreen.2020-02-06-14.00.txt
15:00 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2020/evergreen.2020-02-06-14.00.log.html
15:00 remingtron dluch++ #thanks for keeping us on track!
15:01 dluch :-)
15:05 mmorgan1 joined #evergreen
15:05 Bmagic remingtron sandbergja: reports commit pushed
15:06 remingtron Bmagic++ #fast as lightning!
15:06 Bmagic Lightning might be slightly faster :)
15:09 Bmagic results: http://antora.mobiusconsortium.org/prod​/docs/latest/reports/introduction.html
15:17 rfrasur_ That looks really awesome.
15:18 Bmagic you're really awesome
15:18 * rfrasur_ laughs
15:19 rfrasur_ Not really, but I'm alright.  But the Antora stuff really is, and it's interesting to see how it might be used for local documentation in the future along with the general Evergreen docs.
15:19 berick :)
15:20 Bmagic Clicking around on that site - I'm realizing that we might only have two sections left: circulation and serials
15:21 Bmagic the search is my favorite
15:22 Bmagic "Using the Browser Staff Client" still needs it's sub pages headers upgraded
16:00 mantis1 left #evergreen
16:11 Bmagic what does it mean when the gateway.log shows this: Session cache for thread 0.xxxxxxxxxxxxxxxxxxx does not match request
16:12 Bmagic That's the only error I can see that might be related to why I cannot add a permission to a permission group using the staff client (web client but dojo within)
16:56 jvwoolf left #evergreen
17:05 mmorgan joined #evergreen
17:07 jihpringle joined #evergreen
17:07 mmorgan left #evergreen
17:15 jeffdavis Anyone have experience with something like this: EZProxy authenticates against Evergreen (via cgi script or whatever); Evergreen uses auth_proxy to authenticate with LDAP? Any reason why that wouldn't work?
17:16 jeffdavis doesn't need to be EZProxy, just that general kind of scenario where EG is an auth provider but is itself using authentication proxy
17:16 jeffdavis it feels wrong but I don't see an obvious reason why it shouldn't work (assuming the EZProxy piece is auth_proxy aware)
17:18 jeff our cgi+ticket method may or may not be auth-aware. I think it's just making OpenSRF calls via the gateway.
17:24 jeffdavis seems like the C auth methods aren't auth_proxy aware, but using open-ils.auth_proxy.login in that scenario seems like it should work
17:25 jeffdavis albeit inefficient
17:26 jeff heh, meant to say "may or may not be auth_proxy-aware". not being auth-aware would be amusing.
17:26 jeffdavis ezproxy access for all!
17:39 JBoyer Bmagic: that error sounds similar to what happens if you have nginx in front of apache and the apache config still has the RemoteIP stuff commented out. That does cause problems with the dojo interfaces.
17:39 Bmagic hmmm, didn't check that
17:39 Bmagic those lines are commented out
17:40 Bmagic sorry, not commented out (uncommented)
18:23 sandbergja joined #evergreen
18:26 remingtron joined #evergreen
19:01 cmalm_ joined #evergreen
20:44 sandbergja joined #evergreen
21:54 sandbergja joined #evergreen

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