Evergreen ILS Website

IRC log for #evergreen, 2019-07-18

| 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
04:28 book` joined #evergreen
05:08 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:13 agoben joined #evergreen
07:33 bos20k joined #evergreen
07:56 Dyrcona joined #evergreen
09:26 yboston joined #evergreen
09:37 cowens joined #evergreen
09:37 cowens left #evergreen
09:38 stephengwills joined #evergreen
09:41 cowens76 joined #evergreen
09:41 cowens76 left #evergreen
09:52 cowens joined #evergreen
10:11 sandbergja joined #evergreen
10:18 khuckins joined #evergreen
11:12 Christineb joined #evergreen
11:42 gmcharlt bug 1777207 now has a pullrequest that I'm backing
11:42 pinesol Launchpad bug 1777207 in Evergreen 3.2 "Web Client - Check In List Refreshes After Every Scan and Gets Progressively Slower" [Medium,Confirmed] https://launchpad.net/bugs/1777207
11:46 jvwoolf joined #evergreen
11:59 sandbergja_ joined #evergreen
12:02 cowens joined #evergreen
12:05 Dyrcona hmm.... I should be able to proxy port 7632 to websockets on a different locally, so that it is totally transparent to our current users.
12:05 Dyrcona should be "...on a different port locally..."
12:06 Dyrcona I'll test that this afternoon before I send an email. If that works, it could save us some headache.
12:17 collum joined #evergreen
12:41 pinesol [evergreen|Galen Charlton] LP#1777207: have eg-grid generate DOM nodes only for visible columns - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a84b6ae>
12:41 pinesol [evergreen|Galen Charlton] LP#1777207: teach egGrid how to prepend rows more efficiently - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1da6a8e>
12:54 Dyrcona After thinking about it, I've decided not to even bother. I'll change the port when we start using a proxy. It's better for the long run.
12:56 Dyrcona All right, I'm going to test it out of curiosity.
12:59 pinesol [evergreen|Dan Wells] LP#1823367 Tone down org unit row coloring - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=0ef978c>
12:59 pinesol [evergreen|Dan Wells] LP#1823367 De-encapsulate holdings grid styles to fix row highlighting - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a60fcd0>
12:59 pinesol [evergreen|Dan Wells] LP#1823367 Add place to collect style guidelines - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=d424f00>
12:59 pinesol [evergreen|Dan Wells] LP#1823367 Make search bar area neutral - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=bf132ad>
13:03 Dyrcona Oh, nice. haproxy doesn't start, but systemd won't say why not.
13:04 Dyrcona OK. That's better.... Something else was listening on one of the ports.
13:07 Dyrcona Eh, no... Doesn't seem to work.
13:10 Dyrcona That's even better....
13:11 Dyrcona Except it isn't... :(
13:13 Dyrcona It's going to take more effort than I want to put into it right now.
13:15 Dyrcona If I change the websocket port is it necessary to do the npm steps for the webstaff client, again?
13:16 bshum Dyrcona: It's part of the compile I think , to use a different websocket port
13:17 Dyrcona bshum: I'm trying it now. All I did before was reinstall OpenSRF with the websocket port changed. I figured it loaded opensrf_ws.js and just used that, but if it gets compiled in, then, maybe I need to rebuild the npm stuff, too.
13:21 Dyrcona I'm also using a simple form of the proxy configuration by adding an additional port to the configuration. I should probably make a separate section, but this *should* work.
13:34 Dyrcona Well, that doesn't work, either. I'll just give up and say we have to change the port with the proxy. I'm not going to waste my day figuring this out, when I'd rather not do it in the first place. I was just looking to see if it would be easy to set up the proxy without disrupting our users too much.
13:36 yboston joined #evergreen
13:40 tlittle joined #evergreen
13:48 kip joined #evergreen
13:53 Dyrcona And, maybe, my test vm is hosed for some other reason. :(
13:53 Dyrcona 'Cause it doesn't work after reverting the changes.
13:54 agoben The Evergreen Project Board/EOB meeting should be starting in about 5 minutes.
14:00 agoben #startmeeting EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.​php?id=governance:minutes:2019-07-18
14:00 pinesol Meeting started Thu Jul 18 14:00:24 2019 US/Eastern.  The chair is agoben. 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: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:00 pinesol The meeting name has been set to 'eob_meeting_for_2019_07_18__agenda_h​ttps___wiki_evergreen_ils_org_doku_ph​p_id_governance_minutes_2019_07_18'
14:00 agoben #topic Roll Call
14:00 agoben Use the #info command to provide name and affiliation
14:00 agoben #info agoben = Anna Goben, Evergreen Indiana
14:00 Topic for #evergreen is now Roll Call (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:01 JBoyer #info JBoyer = Jason Boyer, IN State Library / Evergeren Indiana
14:01 gmcharlt #info gmcharlt = Galen Charlton, Equinox
14:01 cowens #info cowens = Chris Owens, Blanchester PL/COOL
14:01 tlittle #info tlittle = Tiffany Little, PINES
14:02 jvwoolf #info jvwoolf is Jessica Woolford, Bibliomation
14:02 agoben csharp is on vacation.  Haven't heard from anyone else about being out.
14:02 agoben Welcome back, Jessica!
14:02 jvwoolf Thanks :)
14:03 agoben Looks like that may be everyone that's here today.  We do still have a quorum though!
14:03 agoben #topic Approval of Minutes
14:03 Topic for #evergreen is now Approval of Minutes (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:04 agoben #info Minutes from 2019-06-20 meeting: http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-06-20-14.00.html
14:04 agoben Corrections, updates, suggestions?
14:05 agoben #startvote Accept minutes from 2019-06-20? yes, no
14:05 pinesol Begin voting on: Accept minutes from 2019-06-20? Valid vote options are yes, no.
14:05 pinesol Vote using '#vote OPTION'. Only your last vote counts.
14:05 gmcharlt #vote yes
14:05 JBoyer #vote yes
14:05 tlittle #vote yes
14:05 agoben #vote yes
14:05 cowens #vote yes
14:05 jvwoolf #vote yes
14:05 agoben #endvote
14:05 pinesol Voted on "Accept minutes from 2019-06-20?" Results are
14:05 pinesol yes (6): JBoyer, agoben, cowens, tlittle, gmcharlt, jvwoolf
14:05 agoben #topic Chair Report
14:05 Topic for #evergreen is now Chair Report (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:05 agoben The hospital donation went off very smoothly end of last month, so we're close to closing out the expenses from the 2019 conference.
14:05 agoben I've sent everything I have over to Dilly.  He's on vacation this week, so hopefully will hear back once he returns as to what our next steps are.  There was draft of the 1023 that was fairly close to completion, so we should be able to wrap up pretty quickly to submit.  We need to submit all of our paperwork by the end of the year to ensure we meet the deadlines.  Sooner would be better if the paperwork is in good enough shape.
14:06 agoben #info All COI forms sent to lawyer; awaiting his return to office for next steps with 1023.
14:06 agoben Any questions?
14:07 agoben Seems to be quiet, so moving on...
14:07 agoben #topic Treasurer's Financial Report
14:07 Topic for #evergreen is now Treasurer's Financial Report (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:08 gmcharlt #info There have been no changes to our ledger with SFC since the June Board meeting
14:08 agoben I did query MOBIUS about our standing there.  We owed just under $9,500 as of the end of last month for their services. Do we want to request a formal invoice and clear that up or hold off for a while?  I would be in favor of paying it down even if we can't pay it off yet.
14:09 gmcharlt we have cash on hand to pay the entire amount, but that doesn't take into account any initial 2020 conference expenses we need to deal with
14:09 agoben Thoughts?
14:09 gmcharlt and I would prefer that we have a formal invoice, and am happy to request one
14:09 agoben Which is why I was wondering about paying an installment against the balance
14:09 tlittle I'd agree with paying some of it now and requesting a formal invoice
14:09 cowens +1
14:09 JBoyer If MOBIUS is ok with waiting I'd suggest paying at most half now, possibly only a third.
14:09 jvwoolf +1
14:10 JBoyer +1 to an invoice too
14:10 agoben So, to recap, the plan is to request an invoice for half of the amount we owe for immediate payment?
14:11 gmcharlt well, we'd want a statement backing the entire amount regardless
14:12 agoben True, that would need to accompany the invoice, regardless of the amount addressed initially.
14:12 tlittle Are they providing us with regular statements anyway, or do we need to specially request them?
14:12 agoben I think we have to request them
14:12 tlittle Gotcha
14:12 gmcharlt yeah, I have access to the project's QuickBooks instances and can request financial statements whenever, but that's different from an accounting of services provided
14:12 agoben If we were caught up, they might be able to put us into rotation with regular statements though.
14:13 agoben ++
14:13 agoben gmcharlt, would you please pursue that?
14:13 gmcharlt yes
14:14 gmcharlt #action gmcharlt will request an invoice for services rendered from MOBIUS and arrange a payment plan
14:14 agoben gmcharlt++
14:14 agoben #topic SFC Updates
14:14 Topic for #evergreen is now SFC Updates (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:14 agoben I know there's nothing financially, but anything else to note?
14:15 agoben Didn't think so, but wanted to ask!
14:15 agoben #topic SFC Updates
14:15 Topic for #evergreen is now SFC Updates (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:15 agoben whoops
14:16 agoben #topic Release Manager (3.3)
14:16 Topic for #evergreen is now Release Manager (3.3) (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:16 agoben dbwells?  anything to note?
14:16 dbwells Nothing in particular, thanks
14:16 agoben Thanks!
14:17 agoben #topic Release Manager (3.4)
14:17 Topic for #evergreen is now Release Manager (3.4) (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:17 agoben gmcharlt?
14:17 gmcharlt #info Next Feedback Fest is 29 July through 2 August
14:17 gmcharlt particular projects of notes
14:18 gmcharlt - some work on performance improvements that should make its way into 3.1, 3.2., and 3.3 shortly
14:18 gmcharlt - active work to produce a new Bootstrap OPAC skin that should offer some nice mobile improvements
14:18 gmcharlt - and ongoing work on the Angular staff interfaces
14:19 agoben Sounds interesting!  Thanks!
14:19 agoben Toddling along then to the conferences:
14:19 agoben #topic 2019 Conference Committee
14:19 Topic for #evergreen is now 2019 Conference Committee (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:19 agoben Anyone have any remaining follow-up?
14:20 tlittle Terran wasn't able to attend today, but she says to pass along that she has nothing to report there
14:20 tlittle So...pass along nothing :)
14:20 agoben Thanks, tlittle!
14:20 agoben #topic 2020 Conference Committee
14:20 Topic for #evergreen is now 2020 Conference Committee (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:21 agoben Anything on 2020 then?
14:21 tlittle Nothing to report there either; no movement since last month's meeting
14:21 agoben Thanks!
14:21 agoben #topic Outreach Committee
14:21 Topic for #evergreen is now Outreach Committee (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:21 agoben rhamby?
14:21 rhamby It has been a quiet month for the outreach committee.  We have a rough draft of our first interviews with community members that will go on Youtube soon. It has been a quiet month for the outreach committee.  We have a rough draft of our first interviews with community members that will go on Youtube soon.  We also got a press release out for new releases. It has been a quiet month for the outreach committee.  We have a rough draft of our first
14:21 rhamby interviews with community members that will go on Youtube soon.  We also got a press release out for new releases.  We also got a press release out for new releases.
14:22 rhamby open to any questions, comments, will dodge tomatoes, etc....
14:22 agoben Busy month for it being quiet!
14:22 rhamby I think my fingers double pasted there :)
14:22 agoben Thanks to you and the committee for all the work!
14:23 agoben I got these out of order, so apologies:
14:23 agoben #topic Site Selection Committee
14:23 Topic for #evergreen is now Site Selection Committee (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:23 agoben csharp is heading this effort up, so we'll look for an update next month.
14:23 agoben #topic Unfinished Business
14:23 Topic for #evergreen is now Unfinished Business (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:24 gmcharlt as far as the financial policy subcommittee work is concerned, I'm ready to get moving on it
14:24 agoben At the last meeting we approved putting together a subcommittee to draft a financial policy for the Project.  gmcharlt was nominated to lead it, but wasn't here to defend himself.
14:24 agoben Awesome!
14:25 agoben I'm willing to assist as much as I can, and csharp also indicated interest.  Anyone else want to officially join?
14:25 tlittle I would like to
14:25 agoben Ok, then,
14:25 agoben #info The subcommittee to develop a financial policy for the Evergreen Project is comprised of: gmcharlt, agoben, tlittle, and csharp
14:25 gmcharlt great
14:26 gmcharlt I suggest of giving ourselves a deadline of the September board meeting to report back with a proposal
14:26 jvwoolf gmcharlt++ agoben++ tlittle++ csharp++
14:26 agoben agreed
14:26 tlittle +1
14:27 agoben #action The subcommittee will present a proposed policy at the September 2019 meeting.
14:27 JBoyer gmcharlt++ agoben++ tlittle++ csharp++
14:27 agoben Any further discussion before the subcommittee whisks that away for a bit?
14:28 agoben ok, then, on to New Business:
14:28 agoben #topic New Business: PINES' accessibility audit
14:28 Topic for #evergreen is now New Business: PINES' accessibility audit (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:28 agoben #info PINES commissioned an accessibility audit of the web client to identify areas which need attention to bring the client up to WCAG 2.0/2.1 standards.
14:28 agoben #info The study was released to the board here: http://list.evergreen-ils.org/pipe​rmail/board/2019-July/000009.html
14:29 agoben Do we wish to take any action or make any recommendation at this time or postpone while the audit is reviewed?
14:30 BAMkubasa joined #evergreen
14:30 JBoyer I'm not sure what action we would take today, but passing along the recommendations to those currently working on the bootstrap OPAC update would be good.
14:31 agoben Is that vendor led or a multi-entity project?
14:32 gmcharlt it's arising from a staff member at the Niagara Falls Public Library
14:32 gmcharlt but would inherently become multi-entity when it becomes ready for review
14:32 agoben Sure, just wasn't sure where to start if we wanted to pass it along.
14:32 gmcharlt I note that the accessbility report reflects testing of the web staff client
14:33 tlittle I asked the auditors if it was okay to widely share the results, and they said yes. So maybe it would be beneficial to release to the dev mailing list, as guidelines for future dev work that accounts for accessibility needs?
14:33 gmcharlt and of course the Angular work may effectdetails
14:33 agoben tlittle++
14:33 JBoyer I thought it covered some of both, if it's just the client there's little point sending it to the dev list *and* Chris.
14:33 gmcharlt I think it is worthwhile to share it with the dev mailing list, and also put it somewhere on the wiki or website if GPLS is amenable to that
14:34 tlittle I'm fine with that
14:35 agoben tlittle, since PINES solicited the study, would you be willing to take lead on getting that document shared?
14:35 gmcharlt I'm not seeing OPAC on the list of URLs tested, FWIW
14:35 tlittle Sure, I can do that
14:35 cowens joined #evergreen
14:35 tlittle I'm pretty sure it was purely for the client, IIRC
14:35 tlittle We did an accessibility audit several years ago that was for the OPAC, I believe
14:36 agoben #action tlittle will share accessibility study results with dev list and post on the evergreen wiki.
14:36 JBoyer Oops. Should have looked more than T-5 mins before the meeting.
14:36 gmcharlt but to make a broader point, sharing documents may raise bit more awareness, but is not a plan for making improvements
14:37 tlittle What about opening each as a LP bug?
14:37 agoben With the audit just being released, I would suggest that the time to start making plans is now.
14:37 gmcharlt now, there's been a fair amount of recent work on a11y coding, and sandbergja_ in particularly deserves a shoutout for that
14:37 agoben Yes, sandbergja_ has been very present with that!
14:37 gmcharlt I agree that opening individual LPs for the specific issues noted would be helpful
14:38 tlittle Thank you--"issues" was the word on the tip of my tongue!
14:38 JBoyer referencing the study in each bug may hopefully prevent them being marked as duplicates of each other also.
14:39 tlittle Since that kind of ties into having the study accessible on the wiki/web somewhere, I can open the bug reports
14:39 tlittle I can include those in the email to the dev list
14:39 agoben tlittle++  for allllllll the bug writing ahead
14:39 tlittle :D
14:40 JBoyer tlittle++
14:40 jvwoolf tlittle++
14:40 agoben I don't have any other entries for the agenda today.  Did anyone else have something they wanted to discuss?
14:40 jvwoolf I just want to make sure someone else is receiving invoices from the attorney's office
14:41 jvwoolf I had some in my inbox while I was out. I can forward them if not.
14:41 gmcharlt I'm not sure I'm getting them; could you forward to me?
14:41 agoben I'm not.  Please forwaard to me too.
14:41 agoben Hopefully we aren't too far in arrears there too.
14:42 jvwoolf gmchartl: agoben: I will forward to you both and let them know you should receive them going forward
14:42 agoben jvwoolf++
14:42 agoben #info Our next meeting will be on August 15, 2019.
14:42 gmcharlt jvwoolf: thanks!
14:43 agoben Seeing no other comments...
14:43 agoben #endmeeting
14:43 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:43 pinesol Meeting ended Thu Jul 18 14:43:16 2019 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:43 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-07-18-14.00.html
14:43 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2019/evergreen.2019-07-18-14.00.txt
14:43 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2019/evergreen.2019-07-18-14.00.log.html
14:43 agoben Thanks everyone!
14:43 tlittle agoben++
14:43 JBoyer agoben++
14:43 cowens agoben++
14:43 jvwoolf agoben++
14:44 BAMkubasa if you join IRC during a meeting, is there a way to tell there's a meeting going on?
14:44 BAMkubasa I saw the #endmeeting and assumed one was going on, but just from the targeted conversation
14:45 miker BAMkubasa: the channel topic notes it indirectly, for instance: New Business: PINES' accessibility audit (Meeting topic: EOB meeting for 2019-07-18, agenda:https://wiki.evergreen-ils.org/doku.p​hp?id=governance:minutes:2019-07-18)
14:46 BAMkubasa miker, ahh, I missed that at the top due to scrolling
14:46 dbs Perhaps we could use the audit as the basis of another check when reviewing branches
14:47 dbs e.g. "Does this touch the user interface? If so, does it meet WCAG 2.x requirements?"
14:53 cowens left #evergreen
14:53 dbs oh wait it's already there, in some form, at https://wiki.evergreen-ils.org/doku.​php?id=dev:signoff_review_checklist - could be beefed up to be more specific though
14:54 Dyrcona Does this look familiar to anyone: GET https://jasontest.cwmars.org/IDL2js?locale=en-US net::ERR_ABORTED 500 (Internal Server Error)
14:54 Dyrcona I get that as soon as I open the web staff client, and no you can't access that host without a VPN and special DNS/host file.
14:55 Dyrcona The apache logs just have the 500 error about why the 500 .
14:55 Dyrcona and nothing about why....
14:57 Dyrcona When I try logging in, I get a flash of the header for the workstation page, get redirected back to the login page, with that error again and one about not having an authtoken. I'm pretty sure I have not typoed  my password a dozen times in a row.
15:03 dbs Dyrcona: i'm rusty but - memcached config in apache maybe?
15:03 dbs hey dbwells were you ever able to get auth_proxy working for the web staff client? can't seem to find a bug in launchpad about it
15:04 Dyrcona dbs: That must be it.
15:04 Dyrcona I thought I had that fixed and hadn't copied the config file since.
15:05 dbs I've been bitten by it many times
15:06 dbwells dbs: If that was on my radar, it must have fallen off.  Sorry for that.  We use the built in auth for staff accounts, so it hasn't been an issue for us.
15:08 dbs dbwells: it was probably something that only came up in IRC, no worries
15:11 sandbergja joined #evergreen
15:13 sandbergja dbs: re checking accessibility before merging PRs, I've also been wondering if we can add some automated accessibility tests to our test suite
15:14 sandbergja I've been meaning to experiment with this: https://github.com/angular/pr​otractor-accessibility-plugin
15:15 sandbergja (not that automated tools can catch all a11y errors, but they can help so much with things like unlabeled inputs)
15:16 Dyrcona While that was broken, xmllint says it can't parse /openils/var/web/reports/fm_IDL.xml, but /openils/conf/fm_IDL.xml is fine.
15:16 Dyrcona autogen.sh doesn't help.
15:17 Dyrcona Replacing one with the other resolves it.
15:18 BAMkubasa question: in the action.circulation table, what exactly does xact_finish mean, especially for transactions that didn't result in a normal on time return? I’m trying to run some numbers for circulation events where a book was checked out to someone from another system and it ended up lost, missing or overdue.
15:19 Dyrcona xact_finish means the item is checked in, all bills have paid, etc.
15:19 Dyrcona Specifically, it's the time that the transaction was finished.
15:20 BAMkubasa ok, if an item is renewed, does that initial transaction have an xact_finish, but the renewal transaction could still be unfinished?
15:20 jeff yes.
15:21 Dyrcona As for my problem, I think installing the fr_CA translations hosed my reports IDL at some point.
15:21 jeff if the item was renewed before any billings were added to the circulation transaction, the circulation would have xact_finish set at pretty much the same time as checkin_time.
15:22 BAMkubasa awesome, thanks
15:22 jeff if the first circ was renewed late, and the second circ was returned on time, and then later the bills on the first circ were paid, the first circ's xact_finish would be later than the second circ's xact_finish.
15:23 khuckins joined #evergreen
15:25 jeff and a circ that was backdated will have an xact_finish after the checkin_time, even if that circ had no billings.
15:25 jeff (in that case, xact_finish will generally match checkin_scan_time)
15:27 pastebot "BAMkubasa" at 168.25.130.30 pasted "items were checked out by users from another system and now in problem status" (18 lines) at http://paste.evergreen-ils.org/10036
15:28 BAMkubasa jeff, if you're interested, I pasted the query, as I have it built now
15:33 jeff BAMkubasa: one observation is that you seem to be basing things off of a copy's current status, which may be completely unrelated to the circulation in question.
15:34 jeff (a copy that was checked out by a user in a different system, returned, then checked out and lost by a user in the owning lib system -- the first circulation will show up in this query simply by nature of the circ's xact_start being between the given date range.
15:34 jeff )
15:37 BAMkubasa yeah, trying to figure out a way to figure out the final dispensation of the transaction. as I was building it and bringing in that current status, I was seeing Checked Out, On Holds Self, etc. which told me it eventually showed up. Open to other ideas
15:37 BAMkubasa In our big resource sharing environment, I'm trying to figure out how often things fall apart
15:39 BAMkubasa going back to your bracketed comment, removing things that have a checkin date would get rid of those cases?
15:42 jeff there are various classes of "bad" you may or may not care about. unreturned items won't have a checkin_time, but items returned and found to be damaged will usually have a checkin_time.
15:43 jeff BAMkubasa: do you want to see only "cross-system" circulations where there is an outstanding balance?
15:44 Dyrcona BTW, that proxy thing I was trying before the meeting. It works. My problems were all related to a hosed IDL because I installed fr_CA when confirming a bug for someone a few weeks ago.
15:44 BAMkubasa I want to see cross system circulations where the item was lost, is missing, or is long overdue, maybe damaged
15:45 yboston joined #evergreen
15:47 dbs Sacre blue! (fm_IDL.xml)
15:48 jeff BAMkubasa: for us, a copy status of Missing is usually set when we expect to find the item on the shelf and don't. We usually don't attribute that to the patron/library who had the item last.
15:48 bshum fm_IDL.xml makes me sad every time I hear about it and i18n :(
15:53 BAMkubasa jeff true, good point
15:53 dbs yeah, dyrcona I don't think xmllint will ever be able to parse a prepped-for-translation fm_IDL.xml, because it will be missing the XML entity definitions
15:53 Dyrcona dbs: Well, I found that replacing the translated IDL with the non-translated one fixed my issue.
15:54 Dyrcona Something else may have been wrong with it.
15:54 dbs the XMLENT apache module resolves those at run time, but you'll only have a complete set of XML entity definitions if you do the make install step after prepping the desired localizations, iirc
15:54 Dyrcona I'm doing a fresh build after git clean -xfd to test.
15:55 Dyrcona dbs: Yeah, I followed the correct steps once, when verifying the bug, but I had forgotten about having done it.
15:55 dbs yeah, all the unilingual sites just do that (cp /openils/conf/fm_IDL.xml /openils/var/web/reports/fm_IDL.xml) :/
15:55 dbs but it works! which is always a good thing
15:56 dbs maybe at some point in the future the IDL translation stuff could be replaced by something more intelligent and we could get rid of the XMLENT hack. but so many tuits required.
15:56 Dyrcona I just want to make sure it works after a git clean, without any extra steps.
15:56 Dyrcona Yeah....
15:57 bshum dbs: For said future:  https://bugs.launchpad.net/evergreen/+bug/1686832
15:57 pinesol Launchpad bug 1686832 in Evergreen "fieldmapper changes break with translations" [Medium,Triaged]
15:57 dbs bshum++
15:58 * bshum hasn't done anything on that since reporting it in 2017 other than updating the template file every time
15:58 bshum But I didn't think of folks who have localized fieldmapper entries custom to their install
15:58 bshum For that it's basically undocumented if they mix in i18n to it
15:59 Dyrcona Yeah, we have custom IDL entries, so that's the main problem.
15:59 Dyrcona And the git clean fixed it.
15:59 dbs yay
15:59 Dyrcona So, I can proxy websockets over port 7682, too!
16:00 dbs sweet
16:00 * dbs waits an inordinate amount of time for an actor.usr_delete call to finish - this batch must include someone who was a cataloguer
16:01 dbs I imagine the avalanche of triggers spawned by "UPDATE asset.copy SET editor = dest_usr WHERE editor = src_usr" is driving the database crazy
16:03 jeff how's ingest.reingest.force_on_same_marc look? :-)
16:03 dbs good point jeff!
16:04 dbs FALSE thankfully
16:04 jeff phew.
16:04 jeff :-)
16:10 jvwoolf left #evergreen
16:11 gsams I recently was requested to undo a deletion of a record, and it is still showing up as deleted to folks regardless of what they do.
16:12 gsams I've reingested, they've refreshed, relogged, restarted their computer, I can pull the record up and it doesn't show as deleted, but I can't find it in a search.
16:12 gsams It is active, and deleted is false in the database.
16:14 dbs mmm, something to do with the asset.opac_visible_copies (or whatever the replacement for that was?)
16:15 dbs https://bugs.launchpad.net/evergreen/+bug/1831803 refers to the replacement, maybe that's a lead?
16:15 jeff was the record deleted via means other than the staff client?
16:15 pinesol Launchpad bug 1831803 in Evergreen "asset.opac_visible_copies is unused and should be removed" [Low,New]
16:16 gsams it was deleted from the marc edit screen in the staff client.
16:18 jeff and was it undeleted from the staff client?
16:19 dbs ah so the MARC record is not even visible in the staff client search results? hmm. And the search isn't cached? (add "-blahblah" or something)
16:20 gsams jeff: it was undeleted through the database directly
16:20 jeff recent versions of Evergreen adjust the MARC leader (LDR/05) on deleted records (and on undeleting them). I don't recall if ingest pays attention to that or not.
16:21 jeff that's something that could be easily overlooked if you undeleted by setting active=true, deleted=false at the db level.
16:23 gsams jeff: I believe that is it, I hadn't run into that before
16:23 dbs jeff++
16:24 jeff I'm not surprised that the LDR/05 value may need updating, but I doubt that's your entire issue.
16:25 jeff there was the venerable old bug 1091885 and mention of metabib.record_attr_vector_list needing to be regenerated in bug 1802156
16:25 pinesol Launchpad bug 1091885 in Evergreen "Reingest bib needs to deal with missing metabib.record_attr entries" [Medium,Fix released] https://launchpad.net/bugs/1091885
16:25 pinesol Launchpad bug 1802156 in Evergreen "Undeleting bibs does not null merged_to column" [Undecided,New] https://launchpad.net/bugs/1802156
16:25 gsams It does appear in search again
16:26 jeff oh, good deal!
16:26 gsams but shows up as deleted for the staff member still
16:26 jeff that sounds like bug 1768122
16:26 pinesol Launchpad bug 1768122 in Evergreen "webclient: undelete is subject to weird possibly caching-related issues" [Undecided,New] https://launchpad.net/bugs/1768122
16:27 jeff ...which is a bit of a head scratcher on first/second read
16:30 jeff gsams: what version of Evergreen?
16:33 dbs And the actor.usr_delete() is done, in less than 30 minutes!
16:34 khuckins joined #evergreen
16:34 dbs Only 37780 more users to go. Hopefully not too many of them were cataloguers
16:42 gsams jeff: 3.2.3 and it does appear to be working properly now after some browser clearing.
16:51 yboston joined #evergreen
16:57 sandbergja joined #evergreen
17:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
17:04 gsams jeff++
17:48 stephengwills left #evergreen
21:16 stephengwills joined #evergreen
23:07 sandbergja joined #evergreen
23:34 sandbergja joined #evergreen

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