Evergreen ILS Website

IRC log for #evergreen, 2014-05-19

| 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:41 zerick joined #evergreen
05:04 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
05:09 _bott_ joined #evergreen
05:46 john3213 joined #evergreen
05:51 john3213 left #evergreen
07:29 csharp dbs: oooh reveal.js is nice!
07:29 jcamins dbs: thanks!
07:40 rjackson-isl joined #evergreen
07:51 collum joined #evergreen
07:55 jboyer-laptaupe joined #evergreen
07:59 collum joined #evergreen
08:05 akilsdonk joined #evergreen
08:06 akilsdonk_ joined #evergreen
08:31 timf joined #evergreen
08:31 book` joined #evergreen
08:39 Dyrcona joined #evergreen
08:40 mmorgan joined #evergreen
08:42 Shae joined #evergreen
08:49 kmlussier joined #evergreen
08:54 kbeswick joined #evergreen
08:57 pinesol_green [evergreen|Galen Charlton] LP#1320048: correctly display closures in the closed dates editor - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=6d747f9>
08:57 pinesol_green [evergreen|Galen Charlton] LP#1320048: remove last use of Date.W3CDTF() from closed dates editor - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=1990e6f>
08:57 pinesol_green [evergreen|Galen Charlton] LP#1320048: remove the Date.W3CDTF() JavaScript module - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=148449c>
09:00 dac joined #evergreen
09:02 Dyrcona So, while cherry-picking gmcharlt's fix into rel_2_6 this morning, I noticed that commit ba0e6c0b09d763e1fef0685c03aa169e4d6562d7 was in master, but not in rel_2_6.
09:02 pinesol_green [evergreen|Ben Shum] Documentation for adding OpenSearch to Firefox - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ba0e6c0>
09:02 Dyrcona I think it should be, but though I'd ask here so someone from DIG can chime in.
09:03 kmlussier Yes, it should be.
09:03 kmlussier Sometimes we forget to backport the doc commits. I know I've done it a couple of times.
09:03 Dyrcona OK. That's good enough for me.
09:04 Dyrcona And, done!
09:04 kmlussier Dyrcona++
09:05 Dyrcona Ah, shucks. 'Tweren't nuthin'.
09:06 Dyrcona gmcharlt++ # For the fast turnaround on a Saturday.
09:10 mrpeters joined #evergreen
09:33 yboston joined #evergreen
09:45 pastebot "mrpeters" at 64.57.241.14 pasted "Grocery billing that won't show in client, eventual server failure" (45 lines) at http://paste.evergreen-ils.org/32
09:46 mrpeters ^^ totally stumped on this.   seems to be all of the needed pieces in place, logs aren't throwing me much in the way of errors when that network failure appears
09:55 mrpeters fwiw, running request open-ils.actor open-ils.actor.user.fines.summary.authoritative in srfsh for that patron id returns data, just all 0.0 values however
09:58 tsbere mrpeters: Does money.materialized_billable_xact_summary have a row for that?
10:00 mrpeters it does, but its 0.0 total paid, 0.0 total owed for some reason
10:00 pastebot "mrpeters" at 64.57.241.14 pasted "materialized_billable_xact_summary" (15 lines) at http://paste.evergreen-ils.org/33
10:21 mrpeters woo!  thank you 0174.schema.money.nulls-in-mmbxs-fix.sql!
10:21 mrpeters and jeff++
10:21 mrpeters http://irc.evergreen-ils.org/evergreen/2013-10-25 helped a ton!
10:32 jeff good!
10:32 jeff logs++
10:32 mrpeters heck yeah
10:32 mrpeters i dont know what caused this, which is a bummer, but im glad to at least fix it so they can go live
10:59 pastebot "gsams" at 64.57.241.14 pasted "ccvm wild query since this morning" (2 lines) at http://paste.evergreen-ils.org/34
11:00 gsams I'm seeing a weird query that started up this morning, I'm not entirely sure why this is happening though
11:01 gsams we turned on a virtual host and added a few staff working locations and suddenly this query started flying every few minutes, up to about 10 times every time
11:03 tsbere gsams: I would not be surprised if this is the catalog trying to translate labels without the database-side changes that provide the IDs
11:04 vlewis joined #evergreen
11:10 gsams tsbere: odd.  Wasn't an issue before turning a new member on apparently (as far as I can find anyway) and everything appears to be running swimmingly otherwise...
11:11 tsbere gsams: The "10 times every time" would possibly correspond to search result pages
11:12 jeff gsams: compare evergreen perl libs and templates on the new server with existing servers, see if you have a difference?
11:12 gsams jeff: same server, unfortunately.
11:12 gsams tsbere: I think I might know what it is now...  Though it shouldn't be...
11:13 Dyrcona gsams: You said something about a VM.
11:14 gsams Dyrcona: Virtual host, same machine multiple subdomains
11:14 Dyrcona gsams: Ah, got it.
11:14 jeff ah. an apache virtual host. got it.
11:15 tsbere and since the "look up the translations" is based in the templates it could be the templates are too new for the db
11:17 gsams tsbere: I think you are right about that, thanks for pointing me in the right direction I appreciate it.
11:17 gsams tsbere++
11:17 gsams jeff++
11:17 gsams Dyrcona++
11:21 gsams tsbere: you were indeed correct.  Thanks again.
11:22 tsbere gsams: No problem. For note, if I recall correctly the database changes at the time were not disruptive to anything else if you wanted to apply them.
11:25 * bshum chants, "upgrade, upgrade, UPGRADE!"
11:25 bshum :D
11:25 gsams bshum: soon^TM
11:26 gsams I'm ready for an upgrade though, really really ready
11:28 pastebot "Dyrcona" at 64.57.241.14 pasted "Bmagic: Modified pingest.pl I mentionedin private chat." (161 lines) at http://paste.evergreen-ils.org/35
11:37 pmurray_away joined #evergreen
11:43 pmurray joined #evergreen
12:01 hbrennan joined #evergreen
12:17 kmlussier joined #evergreen
12:41 kmlussier @marc 240
12:41 pinesol_green kmlussier: The uniform title for an item when the bibliographic description is entered under a main entry field that contains a personal (field 100), corporate (110), or meeting (111) name. [a,d,f,g,h,k,l,m,n,o,p,r,s,6,8]
12:57 Dyrcona @giveup
12:57 pinesol_green Dyrcona: <shaggy>We're, like, doomed.</shaggy>
12:57 Dyrcona Perfect!
12:58 * Dyrcona pats pinesol_green on the head.
12:58 gsams working as intended
12:59 Dyrcona It was a most apropos dunno.
13:21 * kmlussier needs to pick up a sick child from school and will be missing the developers meeting today.
13:21 * bshum is feeling sick and probably won't be around either.
13:22 kmlussier left #evergreen
13:23 akilsdonk joined #evergreen
13:23 jeff looks like it may be a short meeting.
13:25 gsams having trouble with sip server.  Setup new logins for our setup, entered users into Evergreen through staff client as well.  getting 940
13:25 Dyrcona Just move it to tomorrow.
13:28 tsbere gsams: Did you ensure the passwords are correct in the SIP XML config, and restart SIP to read the new config?
13:28 gsams yes, still getting 940
13:29 gsams There seems to be some gremlins in our system since we turned the new library on
13:30 tsbere gsams: Did you double-check that the passwords in the SIP XML config are the ones provided to Evergreen *and* the clients are using the correct passwords?
13:30 * tsbere points out that this has been an issue for him in the past on his dev machine, mis-typing the password in one of the three spots and not noticing
13:31 mllewellyn joined #evergreen
13:32 gsams tsbere: unfortunately yes again, I double checked that first, using the password from the xml file and copying it into Evergreen and then into a telnet sip session
13:32 gsams I also tested a few of the other credentials that I have and they all pass except for the new ones.
13:32 tsbere gsams: Did you ensure the permissions are properly set on the new accounts in Evergreen?
13:33 gsams tsbere: yes, they have the same permission group and permissions as other working sip users
13:33 tsbere gsams: Do your other sip users have secondary groups that the new ones may have had overlooked?
13:34 Dyrcona gsams: Did you restart the SIPServer software after adding the new accounts in oils_sip.xml?
13:34 gsams Dyrcona: yes, a few times just to be sure
13:35 Dyrcona OK, just checking the obvious.
13:36 gsams Dyrcona: not a problem, I was hoping it was something obvious too.
13:36 gsams tsbere: I'm not sure if they have secondary groups or not honestly.
13:37 jcamins I have a suggestion of something else obvious. Did you check to make sure that you're connecting to the correct machine?
13:38 jcamins I've definitely had moments of panic where the new login isn't working... only to realize that I'm logging into a test server.
13:38 tsbere gsams: Perhaps run this for old vs new? If old doesn't return anything don't worry about the new.   SELECT pugm.grp FROM permission.usr_grp_map pugm JOIN actor.usr au ON pugm.usr = au.id WHERE au.usrname = 'some username';
13:39 gsams jcamins: yeah, I've got that part correct as well
13:39 gsams tsbere: nothing was returned for old users
13:39 jcamins Darn. That was the only useful suggestion I had.
13:39 jcamins Well, potentially useful.
13:39 gsams jcamins: I'm there with you honestly.  I did the equivalent of turning it off and on again.
13:39 tsbere gsams: For added fun, along the lines of "correct server", are you editing the correct xml file? I have sometimes edited the wrong one on accident and bashed my head against it for a while before realizing "oh, wait, this is reading this other copy..."
13:41 gsams tsbere: the sip file I pointed to when I restarted was the one that I've edited, so yes.
13:41 gsams Though that would have been exactly like me
13:41 gsams I've done that a lot with Evergreen honestly
13:42 tsbere gsams: At this point, without a copy of some of the files, or access to the server(s), I am not sure I have other ideas.
13:43 gsams tsbere: I was afraid we had hit that point.
13:43 gsams thanks for all the help though, I'll keep cracking at it
13:45 tsbere gsams: Well, from a debugging point of view, logs at warning level will tell you if the problem is a bad user, bad password, or some other more serious issue. Some of the more serious ones will come up as errors instead of warnings. Look for those entries?
13:46 csharp gsams: tailing the osrfsys.log will probably provide clues too
13:46 tsbere (at info level it will tell you success)
13:46 csharp ah - I see tsbere was already suggesting that ;-)
13:46 tsbere csharp: I disagree with your statement
13:47 tsbere csharp: As far as I know, having double-checked just now, osrfsys.log will only help if it gets past the first few login steps. SIPServer logs to syslog by default.
13:50 csharp ah - well, in our log setup, the SIPServer logs to osrfsys.<hour>.log, so I was making a bad assumption
13:51 * tsbere actually avoided mentioning anything beyond "logs" due to differing log setups
13:51 tsbere I figure gsams would know what log to look at better than I would
13:51 RoganH joined #evergreen
13:51 pastebot "gsams" at 64.57.241.14 pasted "SIP server syslog info" (14 lines) at http://paste.evergreen-ils.org/36
13:52 gsams this is what is present in logs, it says unknown login as the reason
13:52 tsbere gsams: The username provided was not known in the XML file, it appears
13:52 DPearl joined #evergreen
13:53 gsams tsbere: that sounds like I am editing the incorrect file.  but I know I'm pointing to the one that I edited...
13:53 tsbere gsams: I would check everything, right down to case differences, in the username in the file vs what is being provided then. And make sure you don't accidentally have things commented out.
13:54 tsbere gsams: Oh, and check the XML tags for that matter. If the attributes aren't correct it won't yell at you, but it also won't work...
13:57 * csharp waves magic wand to standardize everyone's log setups so we can effectively troubleshoot
13:57 gsams csharp: I would welcome logging standardization.  I have the hardest time remembering where to look for certain things.
13:58 gsams and our system appears to be setup oddly
13:58 gsams so I find logs in like 4 different locations, instead of all in one general area
13:59 gsams of course, that may be the process of switching from old to new through the years and some stuff is still kicking around when it shouldn't be or something
13:59 gsams I don't know
13:59 gsams we are having issues with permissions as well regarding a single ou
13:59 gsams the new one
14:00 gsams none of the permissions are functioning correctly for them
14:00 tsbere gsams: I would check the work ous and what depth they are assigned on the permissions issue
14:01 gsams tsbere: at this point I've hit the wall on that.  I can assign a user from one ou to a permission group(new user versus new user) and it will work for them at their location, but the same setup does not work for the new ou at their location.
14:02 tsbere gsams: Again, work ous. If they are not assigned a *lot* of permissions don't work right.
14:02 csharp gsams: for the logging issue, you can put this file in /etc/rsyslog.d/ and restart rsyslog, then make sure apache, postgres, and opensrf are all set up to use syslog (and the correct facility code - e.g. LOCAL0)
14:02 csharp http://git.evergreen-ils.org/?p=Evergreen.git;a=b​lob;f=Open-ILS/examples/evergreen-rsyslog.conf;h=​ba25cea727c4aadead5635197f86040392c5ecf2;hb=HEAD
14:03 gsams csharp: you are a log generation hero.
14:03 gsams csharp++
14:03 csharp then your logs will be in /var/log/evergreen/YYYY/MM/DD and be divided by hour of day for each service
14:03 csharp gsams: happy to assist!
14:04 csharp gsams: you may have to create /var/log/evergreen and/or tinker with its ownership
14:05 remingtron dev meeting today?
14:05 gsams tsbere: yeah, the work ous are all set properly that is what is the wierdest part.  The workstations are setup with the correct ou, their accounts have the correct working ou, and yet they are still unable to do just about anything
14:05 gsams I'd say driving me insane, but it's such a short walk at this point
14:06 tsbere gsams: Hmmm....perhaps your ous are a little wonky.
14:06 DPearl remingtron: I thought so
14:07 gsams tsbere: that sounds about right
14:07 jeff #startmeeting 2014-05-19 - Developer Meeting
14:07 pinesol_green Meeting started Mon May 19 14:07:31 2014 US/Eastern.  The chair is jeff. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:07 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:07 pinesol_green The meeting name has been set to '2014_05_19___developer_meeting'
14:07 jeff #topic Introductions
14:07 jeff #info jeff is Jeff Godin, Traverse Area District Library (TADL)
14:08 Dyrcona #info Dyrcona is Jason Stephenson, MVLC
14:08 tsbere #info tsbere is Thomas Berezansky, MVLC
14:08 DPearl #info DPearl is Dan Pearl, C/W MARS
14:08 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:09 eeevil #info eeevil is Mike Rylander, Equinox
14:09 jeff #link http://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2014-05-19 Agenda
14:09 jeff (forgot to link that first!)
14:09 csharp #info csharp is Chris Sharp, GPLS (mostly absent today, but will read the logs)
14:09 phasefx #info phasefx is Jason Etheridge, Equinox
14:09 RoganH #info RoganH is Rogan Hamby, SCLENDS
14:10 jeff #topic #topic Past Action Items
14:10 jeff #action bshum to summarize bug tracking based on feedback from developers
14:10 gmcharlt #info gmcharlt is Galen Charlton, Equinox
14:11 jeff #info bshum reports this is done-ish
14:11 Dyrcona I don't believe bshum is her.
14:11 Dyrcona here
14:11 jeff #link http://wiki.evergreen-ils.org/d​oku.php?id=dev:bug_wrangler:faq Evergreen Bug Wrangler FAQ
14:12 jeff Dyrcona: *nod* -- bshum and kmlussier were unexpectedly unable to participate in today's meeting
14:12 jeff Any questions about the bug wrangler faq, etc -- see bshum, or ask on the list. :-)
14:12 jeff #action jeff to review OpenSRF bug 1109301 for consideration, may solicit the review of others as well
14:12 pinesol_green Launchpad bug 1109301 in OpenSRF "New submission for a client library in php for openSRF" (affected: 1, heat: 8) [Wishlist,Triaged] https://launchpad.net/bugs/1109301 - Assigned to Jeff Godin (jgodin)
14:13 jeff #info Reviewing (barely), haven't sought feedback/review from others yet. If you're interested, let me know here (now, later) or on the bug.
14:13 jeff #info jeff to call for RM 2.7 vote on open-ils-dev within the next few days
14:13 berick #info berick Bill Erickson, ESI
14:13 jeff #info Call for RM vote (and actual vote) Done! Congrats to Ben Shum, 2.7 RM. :-)
14:14 jeff bshum++
14:14 Dyrcona I made my thoughts known on that bug, IIRC.
14:14 jeff Dyrcona++ yes, thanks!
14:15 remingtron jeff: did we skip the action item about eeevil's baseline schema thing?
14:15 jeff remingtron: I did! Thanks for the catch!
14:15 jeff #action eeevil After 2.6.0 is cut, eeevil to publish detailed plan about freezing baseline schemas between EG releases and using deprecates/supersedes in database upgrade scripts. This will go on the mailing list and the thread should structure further discussion of pros and cons of eeevil's plan.
14:15 jeff eeevil: anything to report?
14:16 eeevil jeff: just that I've still got to do that :)
14:16 jeff #info pending
14:16 jeff #topic Release info - OpenSRF
14:17 gmcharlt #info gmcharlt is now thinking mid-summer for an OpenSRF 2.4.0
14:17 jeff gmcharlt: same likely new features as previously mentioned?
14:17 gmcharlt more testers for bericks web sockets patches would be great
14:17 gmcharlt jeff: yes
14:18 jeff #info OpenSRF rel_2_3 branch maintenance-only, focus is on 2.4.0 for mid summer 2014: web sockets, CORS, removal of deprecated osrf_ctl.sh, improvements for recent Perl versions and stricter C compiler settings
14:18 jeff #info More testers for WebSockets branch would be great
14:18 jeff #topic Release info - Evergreen
14:19 jeff #info Evergreen 2.4.7 released May 8, final planned release in 2.4 series
14:20 jeff #info Evergreen 2.5.4 released April 23
14:20 jeff #info Evergreen 2.6.0 released April 15
14:20 jeff eeevil++ 2.4
14:21 jeff dbwells++ 2.5
14:21 jeff dbwells++ 2.6
14:21 jeff eeevil: any parting words for 2.4? :-)
14:21 eeevil Evergreen is dead; long live Evergreen!
14:21 jeff dbwells: anything of note regarding 2.5 and 2.6 planned releases?
14:21 gmcharlt eeevil++
14:21 remingtron #info dbwells says 2.6.1 will probably be released this week
14:21 jeff dbwells++ remingtron++
14:22 jeff #topic New Business
14:22 jeff #topic Brief Discussion abour Release Notes
14:23 jeff There's a bit in the agenda regarding this, and having read it before the meeting it looks good, reasonable, and makes sense.
14:24 berick agreed
14:24 jeff I like the idea of DOCS_NEXT, and the clear distinction between what goes into release notes and what becomes documentation.
14:25 jeff DIG++ kmlussier++ remingtron++ yboston++
14:25 jeff anyone I'm missing there that should get credit? :)
14:25 remingtron I think that's the main crew for this blurb
14:26 remingtron #info developers can send any feedback to the DIG email list
14:27 jeff good deal. I don't think DOCS_NEXT exists yet -- is someone going to take care of creating that, and possibly putting the summary contained on the agenda into more prominent place... either in the repo or on the wiki or...
14:27 remingtron I can work on that with dbwells before 2.next gets too far
14:27 remingtron (and/or with the other DIG folks)
14:29 jeff # topic Feedback for New Features Under Development
14:29 jeff er
14:29 jeff #topic Feedback for New Features Under Development
14:30 jeff This is intended for discussion of (as it says on the tin) new features under development. First come, first discussed.
14:33 jeff I'll give a few minutes for anyone to start discussion of new features in development, or alternately any other New Business -- then I think we'll adjourn.
14:37 berick maybe not the right context, but RoganH, what's the latest on the hackaway?
14:37 RoganH Right now I've had one tentative offer to host.  I can't say where but myself and the person offering both are concerned about the distance for many attendees.
14:38 RoganH So, I hope I get more offers.  I know one or two others are discussing at their organizations offering but aren't ready to say "we want to" yet.
14:38 jeff RoganH: For anyone interested in hosting, can you re-iterate the requirements and expectations for a hackaway host?
14:38 RoganH Sure.
14:39 RoganH It's a low key event so we look for help arranging lodging though participants pay themselves.
14:39 RoganH We need a meeting space with good power and wifi and the chairs can't be too painful.
14:39 RoganH Providing caffeine is a bonus.
14:40 RoganH Those are really all we need.  We avoid fancy hotels and expensive venues looking to focus on giving the devs time to work together.
14:40 jeff Thanks for the recap.
14:40 RoganH We generally have 10 - 20 attendees so it's not huge.
14:40 afterl joined #evergreen
14:40 jeff Anyone with anything else for the meeting?
14:41 jeff #endmeeting
14:41 pinesol_green Meeting ended Mon May 19 14:41:46 2014 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:41 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-05-19-14.07.html
14:41 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-05-19-14.07.txt
14:41 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2014/evergreen.2014-05-19-14.07.log.html
14:41 jeff Thanks, all!
14:41 remingtron jeff++ #saving the day
14:41 berick thanks jeff
14:42 RoganH jeff++
14:42 Dyrcona jeff++
14:42 DPearl jeff++
14:43 jeff And I'd encourage anyone with new features to discuss / provide feedback on to make use of IRC and/or the mailing list(s) also. As I understand it, the in-meeting agenda slot for this is a new experiment, but probably shouldn't be considered the only venue for such discussions.
14:47 kmlussier joined #evergreen
14:49 kmlussier Darn! Didn't make it home in time to catch any of the meeting.
14:49 kmlussier jeff++
14:54 jeff kmlussier++ thanks for trying! i hope sick child feels better soon. :-)
14:54 * csharp uses 'script' to record SQL upgrade output in a similar manner to what gmcharlt suggests to Jesse (though output redirection is probably a better approach)
14:54 csharp more graceful anyway
14:55 gmcharlt we could probably spend a good half hour coming up with different ways of doing it
14:55 * csharp weeps over bug 1207533
14:55 pinesol_green Launchpad bug 1207533 in Evergreen 2.5 "Triggered event log times out for large-data sites" (affected: 13, heat: 70) [Medium,Confirmed] https://launchpad.net/bugs/1207533
14:56 csharp I kicked off the query like 4 to 5 minutes ago
14:58 Bmagic Does anyone out there have some statistics on the preformace of their DB when running a full bib reingest? In testing I am measuring something like 22,500 bibs per hour. Does that sound right?
14:59 csharp Bmagic: I didn't record stats before... I know that it took most of 24 hours last time I did one (1.7 million bibs)
15:00 Bmagic csharp: that is 70,800 bibs per hour
15:01 Bmagic csharp: I might be able to get up to that speed when I use my raw real production machine, so perhaps I am on track
15:03 csharp Bmagic: a lot of that probably depends on your DB machine and how it's physically and logically configured
15:04 Bmagic When running a bib reingest one bib at a time on a loop, is there a problem running the DB live? Will it have an impact on the functionality of the system. Not speed of course, but functionality I mean. In other words: Are there underlying functionality required as a result of the reingest before the system can be used?
15:04 csharp our performance got far better once we had our data directory on a separate RAID array
15:04 csharp Bmagic: it slows things down in my experience, yeah, but no functionality problems in my experience
15:05 * csharp too many 'in my experience' clauses there :-/
15:06 * csharp runs off to pick up child from school
15:06 Dyrcona Bmagic: I usually do my parallel ingests at night after our libraries have closed.
15:06 Bmagic Dyrcona: csharp: Thanks for the tips!
15:07 csharp oh yeah - I was forgetting about parallel reingest
15:07 csharp Dyrcona++
15:08 Dyrcona Bmagic: If you do the ingest via a massive update of all your bib records, it will affect your system in negative ways.
15:09 Dyrcona By that I mean something like 'update biblio.record_entry set marc = marc...'
15:09 Dyrcona After setting the internal flags, etc.
15:09 Bmagic Dyrcona: I have changed my query to reflect your script's method. I like it better because it's less work for the DB as far as I can tell
15:09 Dyrcona Using my parallel ingest script is much safer in that you're only locking a handful of records at a time.
15:10 Dyrcona Bmagic++
15:10 Dyrcona I also like going through the records in reverse id order to get the newer records first.
15:11 Bmagic I like that too Dyrcona++
15:35 ktomita Dyrcona: Can you point me to your parallel ingest scripts you are talking about?
15:36 Dyrcona ktomita: Here's the "official" one: http://git.mvlcstaff.org/?p=jason/evergreen​_utilities.git;a=blob;f=scripts/pingest.pl;​h=2b43e9a45b20e10325217f86579002b5c0e14315;​hb=cc9a96dc734997946c8027d41c9252a545dc05a8
15:37 Dyrcona Here's a modified version that I recently used for the 2.6.0 upgrade: http://paste.evergreen-ils.org/35
15:37 Dyrcona BTW, that git repo contains some other useful scripts.
15:38 ktomita Dyrcona: thank you.  I will check them out. Dyrcona++
15:39 Dyrcona http://git.mvlcstaff.org/ has some more useful and/or interesting repos of Evergreen-related things.
15:43 remingtron kmlussier: I'm reviewing bugs for 2.6.1 and wondered if you've tested this: https://bugs.launchpad.net/evergreen/+bug/1078593
15:43 pinesol_green Launchpad bug 1078593 in Evergreen 2.6 "serials: deleting an issuance does not update the basic summary statement" (affected: 3, heat: 18) [Medium,Triaged]
15:44 kmlussier remingtron: Not yet. I was just talking to Dyrcona about that one. He's going to add it to his dev server this week. I'll test it as soon as it's been loaded.
15:45 remingtron kmlussier: okay thanks
15:46 remingtron kmlussier: not sure if you have influence over that timeline, but dbwells mentioned he might cut 2.6.1 on wednesday
15:46 Dyrcona I have a meeting in the morning and may be expected to attend another meeting in the afternoon.
15:46 Dyrcona meetings--
15:51 collum|2 joined #evergreen
15:52 geoffsams joined #evergreen
15:56 phasefx tsbere: question for you, would you expect for the staff client's embedded OPAC to escape out of oils://remote/ back to https://hostname/ solely based on an Apache RewriteRule that tacks on a physical_loc query param?
15:56 phasefx this happens when I click on the Basic Search link
15:58 tsbere phasefx: It is possible that could happen. I personally prefer setting the relevant ENV var, which a rewriterule can be used to accomplish as well...
15:58 phasefx tsbere: thanks, I didn't know setting that as ENV var was an option; will try
16:00 rangi can i get a quick sanity check from the evergreeners?
16:00 phasefx rangi: shoot
16:00 rangi http://ils.foss4lib.org/  im about to send an email about this
16:00 mmorgan left #evergreen
16:01 rangi http://paste.koha-community.org/6
16:01 rangi too harsh?
16:01 bradl rangi: only if we get more of those pineapple chocolate things :)
16:01 rangi heh
16:01 bradl I CAN'T STOP THINKING ABOUT THEM
16:01 kmlussier rangi: Looks good to me.
16:02 bradl rangi++ #agree with the directness of that message
16:02 rangi bradl: https://www.youtube.com/watch?v=q800G-x8qA0
16:03 rangi http://kiwicornerdairy.com/
16:03 * kmlussier might add a similar comment to the bottom of the FB post.
16:03 kmlussier rangi++
16:03 rangi thanks kmlussier and bradl ill hit send
16:04 Jimmy__ joined #evergreen
16:05 rangi heh i cant, because there is some kind of invisible captcha
16:05 Dyrcona rangi: +1 on the message.
16:06 Dyrcona rangi++ # just becasue
16:06 rangi The answer you entered for the CAPTCHA was not correct.
16:06 rangi thats because a/ i cant see one, and b/ there is no box to enter it in anyway
16:07 Dyrcona oops.
16:07 jcamins rangi: I've been noticing that a lot, too.
16:08 remingtron rangi: sounds like it's time for some firebug hacking
16:08 jcamins It's like website operators don't expect anyone to use Noscript + RP.
16:08 Dyrcona Only bots can fill in the captcha, or real hackers!
16:09 remingtron or, as happened to me recently, there might be a checkbox somewhere which enables the captcha
16:09 remingtron "Check this box to prove you are a human, then fill in this crazy captcha too...."
16:09 bradl rangi: I should have known the real purpose of your trip here was for New Zealand foodstuff propoganda. "The first taste is free.
16:09 rangi heh
16:10 kmlussier @dessert add pineapple chocolate things from New Zealand
16:10 pinesol_green kmlussier: Error: You must be registered to use this command. If you are already registered, you must either identify (using the identify command) or add a hostmask matching your current hostmask (using the "hostmask add" command).
16:10 kmlussier Bah!
16:11 kmlussier @dessert add pineapple chocolate things from New Zealand
16:11 pinesol_green kmlussier: The operation succeeded.  Dessert #26 added.
16:11 kmlussier @dessert 26 bradl
16:11 * pinesol_green grabs some pineapple chocolate things from New Zealand for bradl
16:11 bradl thanks! I didn't even have to pay the $30 shipping!
16:13 Dyrcona bradl: sweetas, bro!
16:20 * kmlussier made the mistake of actually reading the feature comparison.
16:20 rangi yeah dont do that
16:21 kmlussier I have a hard time believing Evergreen does this - http://ils.foss4lib.org/features/general/aut​omatic-processing-serials-cease-publication - when we don't have a thing called check-in records.
16:21 rangi its flawed in a few ways, 1 is that it started with evergreen features and then went to see if they were in koha
16:22 rangi which means things like start ratings which have been there since about 3.4 i think, dont show
16:22 * kmlussier thinks "check-in records" are a feature of a proprietary vendor.
16:22 rangi that could also be true
16:23 collum|2 Sure.  Now I'm inclined to read it.  (train wreck theory)
16:23 rangi heh sorry :)
16:24 csharp rangi++
16:24 rangi http://ils.foss4lib.org/fea​tures/search/fuzzy-matching
16:24 rangi yeah .. that doesn't actually work in Koha
16:24 csharp I guess that site might go the way of RSCEL, which also suffered from stale data from not enough caretaking
16:25 csharp though it sounds like there's a lot of inaccurate info as well, which is worse
16:26 rangi mostly i have a philosophical problem
16:26 rangi of pitching koha vs evergreen
16:26 rangi id rather say "I don't care what ILS you use, as long as it's not proprietary :)"
16:30 Dyrcona rangi: I tell people to do their homework and pick what works for them.
16:31 gmcharlt and nothing like trying them out of a while first
16:32 csharp jcamins++
16:32 gmcharlt *for a while
16:32 rangi yep
16:33 rangi instead of doing a 335 question RFT ....
16:33 * rangi may be trying to fill one of those in now
16:34 * Dyrcona wonders how the Buddhist Library in Sydney is getting along in their migration.
16:34 Dyrcona They obviously didn't pick me. :)
16:36 Dyrcona kmlussier: The code branch is ready: 23 branches merged with only 1 simple conflict (and I expected that one).
16:36 Dyrcona It's not installed yet, though.
16:37 kmlussier Dyrcona: Thanks!
16:37 Dyrcona Still waiting on the database reload.
16:37 Dyrcona I'll build a new vm and load the new branch in the morning.
16:42 Dyrcona Am I remembering correctly that the by_heading_and_thesaurus index is no longer needed in 2.6.0? Probably a question for eeevil
16:45 Dyrcona Oh. Never mind. I found out.
16:45 Dyrcona They get dropped and recreated in 0875
16:47 Dyrcona And, now it looks our database fixup script for after a dump may need to do something different.
16:50 afterl left #evergreen
17:06 mrpeters left #evergreen
17:07 gsams tsbere++ #for walking me all the way through a SIPServer issue
17:40 Dyrcona joined #evergreen
17:44 Dyrcona Ah, cool.
17:44 Dyrcona Turns out that we don't need post restore database fix script because of the changes made to how those indexes work.
18:08 rangi bradl: i could sell the nz landscape too https://www.youtube.com/watch?v=6D-A6CL3Pv8
18:16 Dyrcona rangi: Next thing you know, I'll be knocking on your door. ;)
18:16 rangi we have a spare bed :)
18:16 Dyrcona :)
18:33 * Dyrcona is not having much luck with python-vm-builder this evening.
18:40 Dyrcona Hopefully, third time is the charm.
18:47 RBecker joined #evergreen
18:49 Dyrcona Nice. vm-builder is making images that don't boot, again.
18:50 Dyrcona I never should have updated the VM host....
19:09 Dyrcona Fourth time was the charm.
19:10 kmlussier @bartender Dyrcona
19:10 * pinesol_green fills a pint glass with Moosehead Lager, and sends it sliding down the bar to Dyrcona (http://beeradvocate.com/beer/profile/379/1053/)
19:10 Dyrcona Heh.
19:11 kmlussier I'm guessing you need it if you're still working this late at night.
19:11 Dyrcona For some reason, I had to manually delete the qcow2 image file before it worked.
19:11 Dyrcona I'm setting it up for you for tomorrow.
19:17 hbrennan Since when did we get a bartender?! Yahoo!
19:18 hbrennan ^ So excited that sentence didn't come out right
19:21 kmlussier @swill hbrennan
19:21 * pinesol_green grabs a can of Sparks Light and sends it sliding down the bar to hbrennan
19:21 hbrennan Haha
19:21 hbrennan I'm in college again!
19:22 kmlussier hbrennan: We got both of those at the same time we got coffee and tea.
19:22 hbrennan kmlussier: Awesome!
19:22 kmlussier bshum++ #Giving us IRC toys to play with.
19:25 Dyrcona I think I'll take a break and finish this after dinner.
19:30 kmlussier @swill
19:30 * pinesol_green grabs a forty of Hurricane and sends it sliding down the bar to kmlussier
19:31 * Dyrcona wonders if the bartender has anything that will go well with curried chicken.
19:31 Dyrcona @bartender
19:31 * pinesol_green fills a pint glass with White Rascal, and sends it sliding down the bar to Dyrcona (http://beeradvocate.com/beer/profile/30/9689/)
19:32 kmlussier Dyrcona: The label on that beer is a quite scary.
19:39 bshum kmlussier: They're borrowed from the #code4lib bot. Except for dessert. That's ours :D
19:39 kmlussier I know. I was just looking at some of the other supybot plugins. I think we need wine too.
19:45 bradl rangi: I'm pretty sure I saw the mines of Moria! ;)
19:54 Marii_Valen joined #evergreen
19:54 Marii_Valen left #evergreen
20:17 kmlussier left #evergreen
20:22 kmlussier joined #evergreen
20:46 gsams joined #evergreen
22:03 mtcarlson_away joined #evergreen

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