Evergreen ILS Website

IRC log for #evergreen, 2014-10-01

| 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:02 buzzy joined #evergreen
00:24 cherri_ joined #evergreen
00:41 cherri_ joined #evergreen
00:58 DPearl1 joined #evergreen
04:12 RBecker joined #evergreen
05:11 vanya joined #evergreen
05:31 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
05:38 mceraso joined #evergreen
07:56 shruti joined #evergreen
08:00 remingtron joined #evergreen
08:06 akilsdonk joined #evergreen
08:06 ericar joined #evergreen
08:38 mrpeters joined #evergreen
08:42 tspindler joined #evergreen
08:43 mmorgan joined #evergreen
09:25 mllewellyn joined #evergreen
09:43 phasefx joined #evergreen
09:44 Callender joined #evergreen
09:44 eeevil joined #evergreen
09:44 mtate joined #evergreen
09:46 graced joined #evergreen
09:56 yboston joined #evergreen
09:59 kmlussier joined #evergreen
10:09 jwoodard joined #evergreen
10:09 kmlussier yboston: When we set the academic meeting date, I don't think I realized it was right after the DIG meeting time. : \
10:10 yboston I did not realize it until two weeks ago, but at least I will not be facilitating that meeting :)
10:10 kmlussier yboston: Yes, but you will need to strict about sticking to the DIG meeting run time.
10:12 yboston I try to be in every meeting, and alwasy warn people when we hit the hour mark. I made note that I really had to be strict this time
10:12 jeff this might be seen as "not a bad problem to have" :-)
10:12 yboston jeff++
10:12 kmlussier jeff++
10:14 kmlussier I used to have that problem when running web team meetings right before the EOB meetings. But I have to say I wasn't too distressed when gmcharlt moved the web team meeting day and I didn't have to do the back-to-back meetings anymore.
10:18 remingtron yboston: just a warning, I'm changing the github workflow instructions
10:18 remingtron and I'm working on Josh's pull req #23
10:24 mmorgan1 joined #evergreen
10:28 Dyrcona joined #evergreen
10:32 yboston remingtron++
10:34 frank___ but is there a command I have to run to could update the pull list? or automatically show the holds?
10:38 pinesol_green [evergreen|Josh Stompro] Docs: Change all internal links to correct format - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ca8cb47>
10:39 kmlussier frank___: What exactly is happening on your end? Is the holds pull list not showing any titles? Or is it a problem where somebody has placed a hold on a title you thing should be displaying, but isn't there?
10:40 kmlussier remingtron / yboston: I'm spending the week doing some web client testing and was planning to do some documentation at the same time. Do you think it would be worthwhilt to have a wiki page where we track what people are working on in the web client?
10:41 yboston kmlussier: yes
10:41 frank___ kmlussier: yes, actually is the second, there are titles thad got placed hold and they doesn´t appear
10:42 kmlussier frank___: My first guess is that, for some reason, the copies at that library are not eligible to fill that hold.
10:46 DPearl frank___: Let me know what you come up with. I have seen cases where the hold targeter wouldn't pick a copy at the pickup lib even though there were no restrictions on the copy, from what I could see.
10:47 csharp frank___: how often do you run your hold targeter process?
10:49 kmlussier Doesn't the hold get targeted at the time you place it, provided that the copy is available at that time?
10:51 csharp kmlussier: the hold selects a potential copy, yes, but I think the targeter cron is what updates the table that maps hold requests with potential copies
10:51 * csharp is open to being corrected on that
10:52 berick the hold is targeted at hold placement time
10:52 frank___ what is the targeter cron I have to run?*
10:52 berick the nightly (or whatever) targeter re-targets holds that were not captured
10:52 csharp berick: ah - thanks
10:53 mmorgan1 frank___: there are lots of places to check that make items not holdable.
10:54 mmorgan1 Item's status, item's holdable flag, Copy Location's holdabiility …
10:54 mmorgan1 age hold protection, hold policies …
10:54 csharp frank___: our cron line is: '0,15,30,45 * * * * . /etc/profile && /openils/bin/hold_targeter.pl /openils/conf/opensrf_core.xml' - ours runs every 15 mins
10:55 csharp hold stalling too
10:57 kmlussier That would be a good FAQ. All the places to check to see why a hold may not be targeting.
10:57 csharp yep
10:58 mmorgan1 I think there may be a couple more, too…
10:58 kmlussier berick: Since you're around, did you have a minimum resolution in mind when you were working on the web client?
10:58 csharp lots o' moving parts, for sure
10:59 kmlussier Screen resolution, that is. As opposed to New Years resolutions.
11:03 * berick hits the gym
11:03 kmlussier berick: Those resolutions never last. :)
11:07 berick kmlussier: i generally tried to keep my screen in the 1200x800 range for most devevelopment.  since we're using the "medium" bootstrap grid, it breaks into the mobile view around 992px
11:07 berick some of the existing html pages don't work so well at 1200x800, though, as others have pointed out.
11:07 kmlussier berick: OK, thanks! That's helpful.
11:09 kmlussier I just wanted a benchmark to know when something should be reported as a display problem and when it's a problem with the resolution that's being used.
11:10 berick cool.  there's nothing official w/ 1200x800, it just seemed like a reasonable baseline.
11:11 kmlussier It might be nice to have something official to help guide people. That's not on you, of course, but maybe a topic for a future dev meeting.
11:12 kmlussier Speaking of which, our last IRC dev meeting was July 28.
11:17 sandbergja joined #evergreen
11:21 bshum And don't forget about checking to make sure the library is actually open.  Like hours of operation and closed dates.
11:21 bshum If the library isn't open, then nothing will show on the pull list.
11:22 collum joined #evergreen
11:25 vlewis joined #evergreen
11:26 StephenGWills joined #evergreen
11:58 stephsamson joined #evergreen
12:00 * kmlussier wonders if anyone would be interested in taking over the scheduling of dev meetings.
12:01 kmlussier It doesn't take a lot of time, but I've got a lot of other community stuff that's been clamoring for my attention.
12:08 nhilton joined #evergreen
12:12 StomproJ joined #evergreen
12:12 tsbere_ joined #evergreen
12:13 nhilton_ joined #evergreen
12:14 kmlussier1 joined #evergreen
12:16 mnsri- joined #evergreen
12:17 dexap joined #evergreen
12:17 dexap joined #evergreen
12:45 berick kmlussier: i can take over for a bit.  for this month, were you thinking next week?
12:45 jeff berick++
12:45 jeff kmlussier++
12:46 kmlussier berick: Yes. At one time, my plan had been to hold it the week before the point releases were scheduled, not that I ever really followed that plan. :)
12:46 kmlussier berick++
12:46 berick kmlussier: ok
12:46 kmlussier berick: Thanks!
12:48 berick kmlussier: remind me.. what times do you usually offer?
12:49 kmlussier I usually do 1, 2, and 3 Eastern.
12:49 berick thanks
12:52 Dyrcona joined #evergreen
13:05 jihpringle joined #evergreen
13:08 shruti joined #evergreen
13:26 vanya joined #evergreen
13:39 RoganH joined #evergreen
13:52 nhilton joined #evergreen
14:10 berick joined #evergreen
14:18 stompro remingtron: Thanks for working on my pull request.  Let me know if you have any feedback for me.
14:32 remingtron stompro: You're welcome. And thank you for the pull requests!
14:32 remingtron stompro++
14:35 vanya Hello. I was working on Bug #1203734, and I was wondering if someone could tell me if the archived data is stored anywhere in the database.
14:35 pinesol_green Launchpad bug 1203734 in Evergreen 2.6 ""Last Few Circulations" total circulation count does not include aged circulations" (affected: 2, heat: 10) [Medium,Confirmed] https://launchpad.net/bugs/1203734
14:38 kmlussier vanya: It looks like there may already be a fix in the works for that one.
14:39 vanya kmlussier : Oh. I'm sorry- I just saw the solution given by Chris. My bad.
14:39 kmlussier But it may have shown up with the bitesize bugs because it doesn't have a pullrequest.
14:39 kmlussier Or, not, it does have one.
14:41 vanya Yes, it showed up in the bitesize bug list.
14:41 vanya No worries :) I'll continue the bug hunt. :D
14:45 snigdha26 joined #evergreen
14:45 vanya Wait- I think there is a milestone set. What does that mean?
14:51 kmlussier vanya: The milestones are something that are usually set after code is ready to be reviewed. It's saying that the fix might be ready for that particular release of Evergreen. However, those milestones are often changed if the code isn't reviewed and merged by the time that release happens.
14:54 vanya So what exactly is the status for this bug? Should I be working on it?
14:55 kmlussier vanya: No, if there is a pullrequest, then there is code waiting to be reviewed.
14:55 kmlussier vanya: Try this link - http://bit.ly/Zsjz8F
14:55 kmlussier It should retrieve the bitesize bugs that don't have a pullrequest tag.
14:55 kmlussier I'll update the link on the OPW page. Sorry about that.
14:55 eby_ joined #evergreen
14:56 vanya No problem. Thank you :)
14:58 kmlussier Hmmm...is it safe to assume this bug is no longer a problem? bug 1026315
14:58 pinesol_green Launchpad bug 1026315 in Evergreen "Staff Client - Installation text" (affected: 2, heat: 10) [Undecided,Triaged] https://launchpad.net/bugs/1026315
14:58 ericar_ joined #evergreen
15:07 nhilton_ joined #evergreen
15:07 kmlussier Nope. It's not safe to assume. :)
15:09 remingtron yboston: kmlussier: jpringle's EDI doc update was pushed in Sept. Seem reasonable to backport to 2.6 (and 2.5)?
15:09 * kmlussier looks.
15:15 kmlussier remingtron: Yes
15:17 jihpringle remingtron: the EDI info will be accurate for 2.6 and 2.5
15:18 remingtron jihpringle: kmlussier: thanks!
15:31 remingtron kmlussier: yboston: could one of you close pullreq #23 on github? And if you know how, could you add me to the organization?
15:33 kmlussier remingtron / yboston: I closed it
15:33 kmlussier remingtron: I don't think I can add you. gmcharlt added me.
15:33 kmlussier remingtron: Never mind. I see how to do it I think.
15:34 kmlussier remingtron: what's your user name?
15:36 remingtron kmlussier: remocrevo
15:37 remingtron (sadly, remingtron was taken!)
15:37 kmlussier remingtron: Good thing I asked. I almost sent the invitation to the other remingtron. :)
15:38 vanya joined #evergreen
15:39 remingtron kmlussier: thank you! I promise to use my github powers for DIG only. :)
15:40 pinesol_green [evergreen|Dan Scott] Whitespace and non-weird emdash in docs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=432346b>
15:41 kmlussier remingtron: Heh. I never made such promises.
15:42 * kmlussier now turns her attention to wreaking havoc on the Evergreen github repository.
15:46 Dyrcona joined #evergreen
15:49 buzzy joined #evergreen
15:58 Dyrcona joined #evergreen
16:11 _bott_1 left #evergreen
16:24 mrpeters anyone try Win10 and Evergreen yet :P
16:24 mrpeters Was going to tinker tonight and see how the staff client runs
16:24 mrpeters (fine, i'm sure)
16:25 bshum mrpeters: I didn't know it was called Win10 till this morning.  So, no, not yet.  :)
16:25 bshum For me anyways
16:25 mrpeters what ive seen so far, looks good.  i would consider upgrading from 7 when its done haha, windows 8 was a bust from the get go for me
16:30 tspindler left #evergreen
16:31 bshum mrpeters: Yes, we'll be curious to see what you find out then :)
16:31 bshum Hopefully nothing too crazy.  At least buy us time to get more of the web client built out.
16:40 * dbs is weird, likes Windows 8.1 when he has to use it. works just like GNOME 3 (hit "windows" key, start typing program name, <enter>, boom, you're running the program)
16:42 bshum ... I never thought of it that way, but that totally makes sense...
16:44 mrpeters i think 8.1 would rock, with normal start menu
16:44 mrpeters and i dont want to use a 3rd party hack to get that
16:44 mrpeters so, i feel like i should at least participate in this "Technical Preview" so Win 10 comes out better!
16:45 kmlussier You can't do that in Windows 7?
16:53 jeff s/in Windows 7/on television/ ?
17:04 kmlussier left #evergreen
17:14 mmorgan left #evergreen
17:22 gsams joined #evergreen
17:56 jwoodard joined #evergreen
18:04 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
20:46 artunit joined #evergreen
20:54 gmcharlt joined #evergreen
21:09 gmcharlt joined #evergreen
21:12 gmcharlt joined #evergreen
21:52 RBecker joined #evergreen
22:06 shruti joined #evergreen
22:30 stephsamson joined #evergreen
23:16 gmcharlt joined #evergreen

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