Evergreen ILS Website

IRC log for #evergreen, 2015-02-05

| 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:16 BigRig_ joined #evergreen
00:47 abowling joined #evergreen
06:42 Callender_ joined #evergreen
07:15 sarabee joined #evergreen
07:16 eeevil joined #evergreen
07:24 bshum Stompro++ # docs generated for upgrade instructions for 2.7 based on your changes.
07:24 bshum I have linked to them on the main downloads page now.
07:25 bshum Thanks for your efforts :)
07:25 bshum For fun reference: http://docs.evergreen-ils.org/2.7/_​upgrading_the_evergreen_server.html
07:34 rjackson_isl joined #evergreen
07:44 graced joined #evergreen
08:05 ericar joined #evergreen
08:08 jboyer-isl berick, bshum: Some Indiana folks will also be around Saturday evening in case there are sights that need seeing, food that needs eating, etc.
08:09 Dyrcona joined #evergreen
08:11 Dyrcona1 joined #evergreen
08:13 bshum jboyer-isl: Yay! :)
08:28 mrpeters joined #evergreen
08:38 jwoodard joined #evergreen
08:41 Shae joined #evergreen
08:51 julialima_ joined #evergreen
08:55 maryj joined #evergreen
09:04 mmorgan joined #evergreen
09:07 jeff popular holdshelf aliases (that have snuck past the patron-side filter preventing duplicates): https://gist.github.com/jeff/6318b9a5a84d26b9e7b9
09:08 bshum Heh
09:09 bshum jeff: How did those slip past?
09:11 jeff bshum: staff-side patron editor has no checks for duplicate holdshelf alias. We didn't put effort into closing that loophole.
09:11 bshum Ahh.
09:11 jeff bshum: So at least one of each group is staff or asked staff to set their alias to that value.
09:11 sarabee joined #evergreen
09:12 jeff looking, the duplicate catwoman is a test/training account's alias.
09:12 eeevil joined #evergreen
09:18 mmorgan jeff: speaking of popular - what are you looking at to get the "most popular" titles on your stats page? Circs? Holds? A combination?
09:36 jeff mmorgan: i think i owe you an email regarding that, too!
09:37 jeff mmorgan: but for those "top ten" lists, we're currently factoring in circs within the last 30 days. we are not presently using holds or hold:copy ratio or anything else.
09:41 mmorgan jeff: Okay, thanks! Also, wondering where you're getting the "title" from since it has proper case.
09:44 jeff Just a naive transform at display time -- the title and author are coming from reporter.materialized_simple_record and the abstract from the first 520$a that we find in metabib.real_full_rec (we're on 2.5 at present)
09:45 jeff we're also pulling the "date" from the 260$c, which explains why so many lack a date.
09:45 jeff and the abstract is a normalized value, so it looks... well, normalized.
09:45 jeff room for improvement there.
09:46 * csharp returns from three consecutive sick days
09:47 csharp @who is THE DOCTOR?
09:47 pinesol_green Dyrcona is THE DOCTOR.
09:47 Dyrcona Got that right.
09:47 Dyrcona ;)
09:47 * csharp cues Dr. Who them
09:47 csharp e
09:47 Dyrcona "You may be a doctor, but I am THE Doctor."
09:48 * jeff takes an illogical and completely imaginary step back from csharp
09:48 Dyrcona May the 4th be with you.
09:49 jeff oh man.
09:49 jeff so we have been deploying Intel NUC computers. Nice units.
09:49 jeff The box that they come in has a gimmick.
09:49 bshum jeff: I love those things.
09:49 bshum The box is awesome!
09:49 bshum And super annoying to show everyone
09:49 jeff bshum: if they had one with ECC RAM, I'd be even happier, but... I digress.
09:50 jeff So the box contains a light-activated sound gadget that plays the Intel chime/ding/whatever.
09:51 jeff csharp's comment about cueing the Doctor Who theme made me think of placing similar (or re-purposed) light-activated devices under books on the holdshelf that correspond to the patron's alias.
09:51 bshum Hehe
09:51 Dyrcona So each patron gets a different theme?
09:52 jeff well, a small handful (even 2-3) on the shelf at a given time.
09:53 berick bshum: jboyer-isl: good to know.  i'm going to try to stick around
09:53 bshum More the merrier :)
09:53 berick eeevil: got a page on webby doing the double pcrud commit I can look at?
09:54 eeevil berick: sure https://webby.evergreencatalog.com​/eg/staff/cat/catalog/record/4010 ... watch the console and hit the save button at the bottom
09:55 berick eeevil: it drops me into the catalog view.  not seeing a save button.  are you in a different view?
09:56 eeevil berick: ha. sorry. yes,  the "marc edit" view
09:56 berick ah, k, thanks
09:57 eeevil I'm actively poking at context menus ATM, so there could be some instability, but the double-commit is always there
09:59 * csharp likes jeff's idea and connects it with bshum's desire to replace EG sounds with Super Mario sounds
10:00 * bshum wonders how library staff would react to suddenly hearing Mario sounds in the client.
10:01 berick eeevil: is this what you're seeing?  http://pastie.org/9889102
10:02 gdunbar joined #evergreen
10:02 eeevil berick: yes. on on the server I see two calls to transaction.commit immediately following each other
10:02 eeevil going to the same pcrud process
10:02 eeevil from the same client, obv
10:03 berick hm, ok..
10:03 eeevil it's like the xactClose promise is being called twice
10:04 yboston joined #evergreen
10:04 eeevil pcrud.js is completely unchanged (now... I was messing with it last night)
10:11 berick eeevil: ok, was able to reproduce locally
10:11 * berick pokes
10:12 eeevil berick: I suspect, but haven't tested, that it happens with every pcrud CUD call
10:31 dreuther joined #evergreen
10:34 dMiller_ joined #evergreen
10:36 berick eeevil: found it.  good stuff
10:36 berick http://git.evergreen-ils.org/?p=work​ing/OpenSRF.git;a=commitdiff;h=1b25f​487c0acdfa000becbccac6943e24bc0ca77
10:36 berick i'll open an LP
10:37 berick this code path (per-tab connections) got much less testing than the global WS connection code, which had to be disabled, because chrome started acting funky with global connections
10:37 berick will have to revisit that..
10:42 mrpeters joined #evergreen
10:46 berick https://bugs.launchpad.net/opensrf/+bug/1418613
10:46 pinesol_green Launchpad bug 1418613 in OpenSRF "Per-tab websocket JS connections can re-send messages" (affected: 1, heat: 6) [Undecided,New]
11:01 bshum berick: I'm adjusting that entry if I can so that it points at OpenSRF 2.4.1
11:01 bshum Since 2.4.0 was already released last month
11:02 berick bshum: gracias
11:04 bshum All set.
11:04 bshum Thanks berick.
11:08 eeevil berick: ah ... I imagine those "some cases" are when we send an opensrf message without a payload, a la DISCONNECT
11:08 eeevil because guess what else is /not/ getting to the server (hint: it's the DISCONNECT message)
11:08 berick eeevil: exactly...
11:14 Dyrcona That's bad.
11:14 Dyrcona ;)
11:16 eeevil Dyrcona: if you thought you had hanging opensrf sessions before... ;)
11:19 * csharp release his new album: The Hanging OpenSRF Sessions
11:19 csharp bleh s/release/releases/
11:19 * csharp is typo-ridden today
11:20 csharp @eightball are jokes funnier without typos?
11:20 pinesol_green csharp: You know the answer better than I.
11:24 mrpeters joined #evergreen
11:30 Dyrcona heh
11:31 Dyrcona csharp: The Hanging OpenSRF Sessions sounds more like an album title.
11:31 Dyrcona OOf.
11:31 * Dyrcona is dumb.
11:31 Dyrcona I was thinking of it as a band name, sorry.
11:32 mrpeters1 joined #evergreen
11:32 Dyrcona That's what happens when I pay more attention to work than to IRC. :)
11:45 graced joined #evergreen
11:55 csharp Dyrcona: ;-)
11:56 * Dyrcona has chicken curry for lunch, but with Nutella in the sauce.
12:00 csharp ewww
12:00 * csharp hasn't jumped on the nutella bandwagon yet ;-)
12:00 Dyrcona It actually tastes pretty good.
12:00 Dyrcona I don't usually consume much Nutella.
12:01 Dyrcona I got a taste before I decided to take it.
12:04 Dyrcona If you like spicy, you would probably like this dish.
12:09 bshum gmcharlt: Sorry I'll fix up 2.7.3 too and create a 2.7.4 for everyone.
12:09 bshum Old, old bug.  Back from my 2.0 days :(
12:10 gmcharlt bshum: ah, great - thanks for catching that!
12:11 bshum gmcharlt: I'm not sure if dbwells has cut 2.6.6.  He might not have yet and it could still get tested and applied there.  But more than likely I expect we'll keep that lock-step on bug fixes in general.
12:11 bshum gmcharlt++ # poking at ancient bugs
12:12 gmcharlt bshum: that's fine - that bug gets hit rarely enough, I think, that testing doesn't need to be super-rushed
12:12 gmcharlt our_customers++ # running into ancient bugs and KEEPING THEM ALIVE
12:13 bshum Reported by Ben Shum on 2011-12-15, zomg :(
12:13 * bshum can't believe how long it's been :\
12:14 bshum Stompro++ # helping to announce new release on list with helpful notes and links!
12:15 kmlussier Any git admins available who might be able to a recent request made for access to the working repository? :)
12:15 kmlussier Recent being about 30 minutes ago.
12:15 bshum 30 minutes?!  The slackers...
12:15 bshum :D
12:15 kmlussier I was hoping to try pushing the branch while I'm sitting at her desk.
12:16 * kmlussier is learning how to use Git Gui today, which is fun.
12:16 gmcharlt kmlussier: one minute
12:16 kmlussier gmcharlt++ Thanks!
12:18 gmcharlt kmlussier: and tis done, and I've responded to cmorgan
12:19 kmlussier gmcharlt: Thank you Galen!
12:20 Stompro bshum,  I'm happy to do that in the future also.  I sent a note to the web team list about possibly doing the same thing for the web site blog.
12:32 kbutler joined #evergreen
12:32 kmlussier bshum: You're familiar with Git Gui, right?
12:32 * tsbere is somewhat familiar with Git Gui
12:32 bshum kmlussier: Somewhat familiar, sure.
12:33 Dyrcona Gui? What is Gui? :P
12:33 kmlussier bshum: We're having a hard time figuring out how to push to the working repository. There doesn't seem to be a way to specify which directory you're pushing to.
12:34 bshum kmlussier: Yeah that can be weird.
12:34 kmlussier bshum: Do you remember how to do it?
12:34 bshum I think Meliss and I found that the best way to get around that was to name our local branches appropriately.
12:34 bshum Then push.
12:34 bshum So my local branch had to be named user/bshum/branch_name
12:34 bshum In order for it to accept it on the remote's end of things
12:34 kmlussier Ah! I see. We'll try that.
12:34 bshum I think there's a way to manually specify the name, but it ended up being more hasslesome
12:34 bshum So we just skipped that
12:35 bshum And stuck to giving good names for our local branches
12:35 * tsbere seems to recall having figured something about that out.....but can't remember what now >_>
12:39 kmlussier Hooray! We got it.
12:39 kmlussier bshum++
12:40 kmlussier One last question. Is there a way to set the remote url that we want to push to for the working repository? We had to type the entire URL in when pushing the branch.
12:40 sandbergja joined #evergreen
12:42 tsbere kmlussier: Did you add the remote on the "Remote" menu?
12:43 buzzy joined #evergreen
12:43 kmlussier tsbere: We did, but we added git://git.evergreen-ils.org/working/Evergreen.git as the URL, and that's not the URL we push to.
12:44 kmlussier Do we need to add a separate remote just for pushing changes?
12:44 tsbere kmlussier: So add the push SSH URL instead? It works for both read and write.
12:44 kmlussier tsbere: OK, we'll try that.
12:44 tsbere kmlussier: The git:// urls are mainly for "you don't plan on writing back" - If you can write the SSH ones work the same way anyway.
12:52 dbs Wow. I found people actively using bookbags!
12:52 dbs Unfortunately they're using it to work around our "Don't allow hold placement on items that are available / on the shelf" policy.
12:54 finnx joined #evergreen
12:56 finnx left #evergreen
12:59 nhilton joined #evergreen
13:00 finnx1 joined #evergreen
13:00 finnx1 joined #evergreen
13:03 tsbere dbs: I am having trouble determining how that works around the issue in question.
13:03 tsbere dbs: Then again, we have people that use holds for things that I personally feel are better suited to bookbags....
13:05 dbs tsbere: We don't show the "Place a hold" button for items in the catalogue that have available copies.
13:06 tsbere dbs: So what, are they adding to the bookbag because the bookbag lets you try to place a hold anyway?
13:19 mrpeters joined #evergreen
13:24 dbs tsbere: yep, exactly (sorry for the delay, real life person came by)
13:24 dbs Not only lets you try to place a hold, but successfully places it.
13:25 tsbere dbs: You know, I think that is less of an abuse than "suspended holds as a reading history" >_> Problematic for you, granted, but less of an abuse.
13:26 tsbere dbs: And isn't there an option somewhere that makes "item is on the shelf" throw an error at hold placement time?
13:27 kmlussier @love grep
13:27 pinesol_green kmlussier: The operation succeeded.  kmlussier loves grep.
13:32 dbs I can take away the "Place holds on items in this list" option, but then someone is going to start using raw GET requests
13:33 bshum Darn kids :)
13:33 dbs There's a "throw ugly error when patron tries to renew an item that has a hold on it" thing
13:33 dbs Ultimately I feel like we're trying to bar enthusiastic patrons from using our library resources, but that's a policy issue.
13:34 akilsdonk joined #evergreen
13:34 jihpringle joined #evergreen
13:42 tsbere dbs: Looks like it is 100% inside of TPac, but circ.holds.hold_has_copy_at.block should apply to bookbag placement as well? Not 100% sure what your overall situation is, though. (Won't help either way right now if they drop straight into making direct hits against the gateway/translator)
13:44 * tsbere glares at the pile of spam that just hit his mailing list moderation queues, then goes and runs the batch discard script he wrote for moderating spam into oblivion anyway
13:46 dbs tsbere++ # that looks promising!
13:50 rsoulliere joined #evergreen
13:51 dbs tsbere++ # That did the trick. Fantastic
13:52 tsbere dbs: Saves you the trouble of annoying people by removing buttons that were there previously. Added bonus of it telling them why it failed too. :D
13:52 dbs and it's only existed since 2011!
13:56 yboston heads up the DIG monthly meeting is starting at 2 Pm EST
14:00 yboston #startmeeting 2015-02-05 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting.
14:00 pinesol_green Meeting started Thu Feb  5 14:00:37 2015 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00 pinesol_green The meeting name has been set to '2015_02_05___dig_monthly_meeting_evergreen_docu​mentation_interest_group__dig__monthly_meeting_'
14:00 yboston The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?i​d=evergreen-docs:dig_meeting_20150205-agenda
14:01 yboston #topic Introductions
14:01 yboston Please feel free to start introducing yourselves...
14:01 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:01 yboston #info yboston is Yamil Suarez @ Berklee College of Music - DIG meeting facilitator
14:01 kbutler #info kbutler is Kate Butler at Rodgers Memorial Library (Hudson, NH)
14:02 bshum #info bshum is Ben Shum, Bibliomation
14:02 rsoulliere #info rsoulliere is Robert Soulliere, Mohawk College
14:03 phasefx #info phasefx is Jason Etheridge, ESI
14:04 yboston My timer is done, ready to start
14:04 yboston any reports from content coordinators?
14:05 rsoulliere Nothing from me this time.
14:05 yboston OK
14:05 yboston Previous Action items...
14:06 yboston #topic yboston will contact krvmga to check in on his 2.7 docs work
14:06 yboston I forgot to reach out to krvmga; will push forward for next meeting
14:06 yboston #action yboston will contact krvmga to check in on his 2.7 docs work
14:07 yboston #topic kmlussier will complete the marc stream importer work and check on the status of the RDA docs
14:07 kmlussier Sorry. I wasn't paying attention.
14:07 kmlussier #info kmlussier is Kathy Lussier MassLNC
14:08 yboston did you want to postpone for next meeting?
14:08 kmlussier I was supposed to get the notes I have to Jane Sandberg so that she could work on the docs.
14:08 kmlussier Unfortunately, I forgot about my action item. I'll try to pull them together for Jane this afternoon.
14:09 kmlussier yboston: So, yes, in answer to your question, postpone to the next meeting.
14:10 yboston same wording?
14:10 kmlussier Sure
14:10 yboston #action kmlussier will complete the marc stream importer work and check on the status of the RDA docs
14:10 yboston #topic yboston will follow up with gmcharlt and Robert about provisioning a VM for DIG
14:11 yboston right before the start of our last meeting on December 4, 2014  I sent out an email to Galen and others to psuh this forward, but I did not hear back.
14:11 yboston right before this meeting I sent another email to try to push this forward
14:12 yboston I will postpone again this action item
14:12 yboston #action yboston will follow up with gmcharlt and Robert about provisioning a VM for DIG
14:12 yboston #topic remingtron will set up doodle to set up a meeting on IRC in Janaury 2015 to discuss re-organizing the EG docs
14:12 remingtron I have stalled on the docs re-org, mostly because of focusing on web client docs, but I'd like your feedback
14:13 remingtron should we pause web client work and work on re-org for a while, since webclient will take a while to progress?
14:13 remingtron (web client *may* take a while)
14:13 remingtron or press on with web client work?
14:14 yboston good question
14:14 remingtron And keep in mind that we want to shift focus to 2.8 when beta is released
14:14 remingtron (though I think that's a fairly small list of new features this time)
14:14 kmlussier remingtron: Do you recall if there was still work to be done on the circulation web client docs?
14:15 remingtron my perspective is just the wiki, which seems to have a lot more to do
14:16 yboston I did not finsih everything in "Circulation - Patron Record"
14:16 remingtron #link http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:webclient
14:16 yboston I also suspect, some features that were missing when I wrote the docs might have been ported over, so it would be useful for me to review again
14:16 remingtron ah, but now I see some comments that some items aren't in the web client yet, etc.
14:17 kmlussier Does it need to be either/or? To be honest, docs organization is not my strong suit. But I see there are still some areas I could work on for the web client.
14:18 kmlussier Whereas others may prefer to work on the reorganization.
14:19 remingtron sure, people can certainly do what they are most interested in
14:19 remingtron and if anyone doesn't know where to start, they can work on web client stuff
14:19 remingtron but I'll plan to shift focus to the reorganization project
14:20 yboston I am not sure on what to focus if we should only choose one. BTW, do we want to also put down a time in the near future to work on one or both do of these topics. Like an hour long IRC meeting or re-org were we can talk about different approaches?
14:22 remingtron where's that wiki page with suggestions from the OPW candidate?
14:23 remingtron maybe it was just an email
14:23 yboston I am trying to find it
14:24 remingtron #link http://markmail.org/thread/kjddts4zod2uwbe6
14:25 remingtron anyway, yes, I guess it is still worth a meeting to discuss reorganization approaches
14:25 remingtron I'll send a doodle
14:26 yboston How is this… "remingtron will set up doodle to set up a meeting on IRC in February 2015 to discuss re-organizing the EG docs"?
14:27 remingtron perfect
14:27 yboston #action remingtron will set up doodle to set up a meeting on IRC in February 2015 to discuss re-organizing the EG docs
14:28 yboston no more previous action items
14:28 yboston should we talk about the web client docs?
14:28 remingtron sure, I have a question
14:29 remingtron does anyone know where development progress is at? mainly, are they ready for using launchpad yet for filing bugs?
14:29 yboston go ahead
14:29 remingtron maybe that's a question for graced ?
14:29 gsams joined #evergreen
14:30 phasefx I think we're pretty close; I can have a better answer tomorrow
14:30 kmlussier I know there is a lot of bug fixing going on in https://bugs.launchpad.net/evergreen/+bug/1402797
14:30 pinesol_green Launchpad bug 1402797 in Evergreen "Browser client sprint1 miscellaneous repairs" (affected: 1, heat: 8) [Undecided,New]
14:31 phasefx and here, http://git.evergreen-ils.org/?p=working/Everg​reen.git;a=shortlog;h=refs/heads/collab/miker​/web-client-sprint1-bug-fixing-rebased-collab
14:32 remingtron phasefx: thanks, we'd love to hear when you have an update
14:33 yboston I think there are still some web cleint docs hat have to be added to master
14:33 phasefx remingtron: no problem.  we need to be more proactive with updates
14:33 yboston I need to review some DIG related emails I have pilled up since the ned of last year
14:34 yboston I beleive there are a couple of web clients submissions through the DIG list there that need to be added
14:34 remingtron yboston: I think you're right. let's work together to get those into master
14:35 yboston specially to avoid the both of us working on the same content
14:35 gsams joined #evergreen
14:35 remingtron but let's still not push into 2.7 branch until we're ready to use launchpad for web client bugs
14:35 yboston I can set up a time to reach out to you early next week or even tomorrow to coordinate
14:35 remingtron great
14:36 yboston anything else web client related? or we can shift to another topic?
14:37 yboston (we are barely past the 30 minute mark)
14:37 remingtron sure, press on
14:38 yboston #topic Decide best presentation of web client install instructions
14:38 yboston See draft by bshum:
14:38 yboston #link http://evergreen-ils.org/~bshum/Ever​green-README.html#_optional_extra_st​eps_for_browser_based_staff_client
14:39 yboston remingtron: did you add this or was it bshum?
14:41 yboston I can move on to something else. I was just going downt he list
14:41 remingtron I think I did, but probably asked bshum first
14:41 remingtron basically, he wrote the instructions draft, and he wants some feedback
14:42 remingtron maybe he/we should ask the general and dev lists for help on that
14:42 yboston ats ome point I need to build a new test server to try out the web client, I can give him some feedback at that point
14:43 yboston I can put an action item to reach out to him to see if this has been included in master, and if others have been able to run his intructions
14:43 yboston they look fine to me, bu I have nos tested them yet
14:43 bshum It has not been added up to master yet.
14:43 bshum Sorry, stepped away a sec there.
14:44 bshum I'll work on it with more devs in the coming weeks.
14:44 yboston I can reach out to you when I am ready to build a new VM to test the web client, to make sure I use the latest version
14:45 yboston is there a git branch that has these instructions?
14:45 bshum yboston: I haven't put all the changes into a git branch yet.  That's also on my to-do list I think.
14:45 yboston no worries
14:46 yboston I can move on, but want suggestions on what action item if any we should leave for next meeting for this?
14:46 yboston (or we can continue on this topic too)
14:47 remingtron maybe action item to revisit state of those install docs.
14:47 yboston another topic to cover is the next release
14:48 yboston #action all check in on state of latest web cleint docs from bshum or others
14:50 yboston let me take a moment to look up the milestone dates for EG 2.8
14:50 yboston Friday, February 20th is the 2.8 beta cut off date
14:51 yboston the EG 2.8 beta release is scheduled for Wednesday, February 25th
14:51 graced joined #evergreen
14:52 yboston when woud we want to focus on the docs for the new features?
14:52 yboston I ca't rmemebr what we have done in the past?
14:52 kmlussier I would say we should start as soon after the beta release as possible.
14:52 remingtron after the 25th beta should be "feature stable"
14:52 remingtron kmlussier: yes, I agree
14:53 kmlussier Also, I don't know if I'm going to be able to use the MassLNC server as a community server for doc work this time around.
14:53 yboston Also, the projected release for EG 2.8 is Monday, March 9th. Though these dates coudl slip a bit, understandably so
14:54 yboston remingtron: the 25th make sense
14:54 remingtron should we try to have a day (or half day) hack-fest to focus on 2.8 features, or only use a wiki page to track progress?
14:54 kmlussier hack-fests are very effective for me. Otherwise, I tend to let tasks slip. But maybe I'm the only one with that problem.
14:55 yboston Ihack-fest for me too, I have that problem
14:55 remingtron okay, I'm in too
14:56 remingtron maybe on a Friday?
14:56 yboston sure
14:56 remingtron March 27, April 6, April 13?
14:56 yboston any volunteers to run a doodle poll targetting after February 25th?
14:57 remingtron whoa, sorry, I'm a month off!
14:57 remingtron Feb 27, March 6, March 13
14:57 kmlussier Feb 27 is bad for me. The other dates look fine.
14:57 yboston we may be able to try just on the mailing list, I wonder if some potential volunteers are scared off by doodle?
14:58 remingtron hmm, let's try a combo of the list and doodle
14:58 remingtron I'll do it
14:58 remingtron and I suggest I wait on the reorganization meeting until after 2.8 docs are finished. thoughts?
14:59 kmlussier They're scared off by Doodle, but please write in AsciiDoc? :)
14:59 remingtron or I guess it makes sense to sqeeze in the reorg meeting now, before beta
14:59 remingtron nevermind, I'll do both doodles
14:59 yboston #action remingtron will set up a doodle poll and ask on the DIG list to set up a time for a DIG 2.8 hackfest
15:00 remingtron kmlussier: double standard, eh?
15:00 yboston kmlussier: point taken
15:01 yboston we are slightly past the one hour mark
15:01 yboston shoudl we stop now, or
15:01 remingtron I think we've covered everything
15:01 yboston is there one more topic or quick question we woudl like to cover?
15:02 remingtron kmlussier: are you able to make the wiki page for 2.8 features again?
15:03 kmlussier Yes, I can.
15:03 kmlussier Sorry, I was pulled into another discussion.
15:03 * gmcharlt jumps in to mention that I intend to provision the doc testing server next week
15:03 gmcharlt sorry for hte delay
15:03 kmlussier gmcharlt++
15:04 yboston no problem, you have a lot on your olate
15:04 yboston *plate
15:04 remingtron gmcharlt++
15:04 yboston I laughed when I realized this nice reply on code4lib list was from you, as another example of your omnipresence
15:04 yboston OK, I will end the meeting
15:05 yboston #endmeeting
15:05 pinesol_green Meeting ended Thu Feb  5 15:05:12 2015 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:05 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-02-05-14.00.html
15:05 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2015/evergreen.2015-02-05-14.00.txt
15:05 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2015/evergreen.2015-02-05-14.00.log.html
15:05 remingtron yboston++
15:06 kmlussier yboston++
15:07 kbutler yboston++
15:14 kmlussier bshum / gmcharlt: I'm curious. Is there a reason why we don't include "Powered by WordPress" in our footer?
15:14 gmcharlt kmlussier: theme default, I assume
15:14 bshum kmlussier: What gmcharlt said
15:15 kmlussier OK. That's a shame.
15:20 kmlussier Would there be any objection to my trying to add it back into one of the footer widgets? I would like seeing it there, for the same reason I like seeing "Powered by Evergreen" in our library catalogs.
15:21 kmlussier Oh, wait. The footer widgets are for those blocks that are a little higher than the footer, aren't they?
15:23 bshum kmlussier: Right, those widgets are just above it.
15:23 bshum And it doesn't handle things like links.
15:23 bshum At least, it didn't work for the text block where the other stuff lives now.
15:23 Dyrcona1 joined #evergreen
15:40 kmlussier eeevil / goood: I may have asked this question before, but I don't recall the answer. Is bug 1251394 ready for testing or does it still need work?
15:40 pinesol_green Launchpad bug 1251394 in Evergreen "Metabib Display Fields" (affected: 3, heat: 16) [Wishlist,Triaged] https://launchpad.net/bugs/1251394 - Assigned to Mike Rylander (mrylander)
15:45 eeevil kmlussier:  it's just the backend components, but I think they work. nothing knows how to use them yet, though
15:46 kmlussier eeevil: Ah, ok. So if we wanted something to be able to use them, it still needs work.
15:46 eeevil we'd talked about making use of the browse_entry table to limit db size growth. that would probably be a minor change, but a change nonetheless
15:48 eeevil since they're field_safe, any client can grab the data given a bib ID ... just a matter of  committing and then doing so :)
16:27 rjackson_isl_ joined #evergreen
16:39 julialima_ left #evergreen
16:59 mrpeters left #evergreen
17:01 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:31 chick joined #evergreen
18:07 ningalls joined #evergreen
19:19 graced joined #evergreen
20:06 nhilton joined #evergreen
23:00 eeevil joined #evergreen
23:11 Sato joined #evergreen

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