Evergreen ILS Website

IRC log for #evergreen, 2014-05-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
05:18 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
07:16 csharp @later tell bmills check out the action.find_hold_matrix_matchpoint function - it takes the pickup lib ID, the request lib ID, the copy ID, the user's ID, and the requestor's ID and will return the IDs of the matching hold rules and the one chosen (usage: SELECT action.find_hold_matrix_matchpoint(pickup_ou.id, request_ou.id, copy.id, user.id, requestor.id);)
07:16 pinesol_green csharp: The operation succeeded.
07:18 kmlussier joined #evergreen
07:19 kmlussier @coffee
07:19 * pinesol_green brews and pours a cup of Ethiopia Konga Co-op Yirgacheffe, and sends it sliding down the bar to kmlussier
07:20 * kmlussier thinks it's funny that bshum left me an @later asking me to check my @later messages. :)
07:22 csharp @later [someone] check your laters!
07:22 pinesol_green csharp: You probably want hard-boiled eggs.
07:23 csharp @later tell [someone] check your laters!
07:23 pinesol_green The operation succeeded.
07:23 kmlussier csharp: So will that message go to any random person?
07:23 csharp kmlussier: yep ;-)
07:23 csharp or a specific random person, that is
07:23 csharp dunno who
07:24 csharp @someone
07:24 pinesol_green tater
07:24 csharp pinesol_green: poetically correct
07:24 pinesol_green csharp: You probably want hard-boiled eggs.
07:24 pinesol_green csharp: I am only a bot, please don't think I'm intelligent :)
07:27 * kmlussier runs off to meetings for the day.
07:27 kmlussier left #evergreen
07:43 tater lol
08:02 collum joined #evergreen
08:02 mdriscoll1 joined #evergreen
08:19 ericar joined #evergreen
08:21 akilsdonk joined #evergreen
08:46 mmorgan joined #evergreen
09:01 dluch joined #evergreen
09:05 rjackson-isl joined #evergreen
09:05 Shae joined #evergreen
09:09 timf joined #evergreen
09:12 14WACPMLM joined #evergreen
09:12 timf joined #evergreen
09:19 mrpeters joined #evergreen
09:28 * tsbere apparently did not get the "check your laters!" later
09:29 tsbere assuming that there isn't a later for [someone] instead of it having replaced that in the command, anyway
09:31 bshum Oh, it picked somebody
09:34 bshum I just peeked under the hood to find out where the later was added for that one and it exists.
09:40 bshum Hmm, postgres hibernator extension?
09:40 bshum http://gurjeet.singh.im/blog/2014/04/30/postgres​-hibernator-reduce-planned-database-down-times/
09:40 bshum Sounds intriguing.
09:43 tsbere And of course only available for 9.3+
09:43 tsbere <_<
09:44 bshum Yeah I just got to that part of the README
09:44 bshum I'm giving serious thought towards using 9.3 for our nextgen DB server in a couple weeks.
09:44 yboston joined #evergreen
09:47 bshum It's hard to test all the parts of Evergreen with 9.3 but so far nothing too crazy jumping out at me in the test servers we're practicing on.
09:48 bshum Also, it being the default in Ubuntu 14.04,  maybe I'm just being lazy. :D
09:57 denishpatel joined #evergreen
10:00 bshum yboston: For DIG, I took a tiny thing and tried my hand at making a short asciidoc snippet (with pictures) in http://git.evergreen-ils.org/?p=work​ing/Evergreen.git;a=shortlog;h=refs/​heads/user/bshum/docs-for-opensearch with an example of how to add OpenSearch to Firefox.  If you have time later, I'd like to check with you on how to test how it looks and whether I screwed up a lot :)
10:01 yboston I am off to a meeting, I will ping you when I am done, and thanks!
10:11 remingtron bshum: if you have asciidoc installed on your machine, you can test the conversion to html with something like:
10:11 remingtron asciidoc -a data-uri -a icons -a toc -d book -o OUTPUT_FILE
10:12 remingtron oops, you also need your asciidoc file on the end :)
10:12 bshum remingtron: Ah, the extra flags are helpful.  I just did a basic conversion test, which failed to find all the images I embedded probably cause of the path I was using.
10:12 remingtron yeah, I usually have a problem with the image path too, but your syntax looks fine for those
10:22 jbfink joined #evergreen
10:29 montgoc1 joined #evergreen
10:38 remingtron bshum: screenshots #3 and #4 are pretty wide. Could you shrink your screen a bit and do them again? Maybe <900px wide?
10:39 bshum remingtron: I can probably do that.
10:40 bshum Unrelated, the Firefox 29 look is throwing me off cause now it really looks like Chrome too :)
10:41 jcamins bshum: yeah, it's bizarre.
10:42 * jeff raises an eyebrow
10:42 jcamins (the FF and Chrome thing)
10:43 jeff oh, do you mean how desktop firefox now uses the same style tab chrome as mobile firefox has?
10:43 jcamins jeff: probably. It's the exact same interface as Google Chrome, too, though.
10:44 jcamins Since I just switched back to FF from Chrome a few days ago, I keep on thinking I'm in the wrong browser and accidentally quitting FF.
10:44 jeff "exact" might be a bit of a stretch, but I'll agree that the tab chrome in firefox and in chrome is now more similar than in the past. :-)
10:45 jcamins jeff: okay, maybe not "exact," but it's pretty darn close.
10:46 bshum remingtron: Wow, less than 900px wide is quite small.
10:47 * bshum already hates the look of the catalog at that resolution :)
10:47 denishpatel left #evergreen
10:48 remingtron bshum: hm, guess it doesn't have to be that small
10:49 remingtron whatever looks reasonable, while trying to be small. how's that?
10:49 bshum It's okay, I'm just wondering if maybe we should establish a general guideline for screenshot size maybe.
10:49 bshum And that should probably factor somewhat into development decisions about what we strive towards.
10:49 bshum :D
10:50 remingtron yeah, 900px was my first attempt, based on the docs PDF display, which nobody should use because it's terribly large and slow.
10:50 remingtron so...we should choose a different width that seems reasonable on modern screens.
10:52 bshum For the purpose of what I was trying to illustrate (that there are results and how the dropdown works), it's not a big deal to go smaller width.  It just starts looking really different as you go.
10:55 remingtron yeah, and we want people to recognize the screen as looking like theirs, so choose whatever is reasonable
10:56 jeff keep in mind also that a screen shot can be a portion of the screen. sometimes i prefer that.
10:57 jeff (you might already be doing that)
11:05 * dbs likes how the FF tab outlines disappear when you're not hovering over them
11:20 pinesol_green [evergreen|Hekman Library Technology Team] Docs 2.6: Lost Item Billing Min/Max Price Settings - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7b759a4>
11:23 jeff interesting author there.
11:23 jbfink joined #evergreen
11:25 asimon joined #evergreen
11:25 dbs Yeah. I guess doc commits in the github workflow won't follow the "include Launchpad number in commit summary" recommendation
11:27 jeff if we want to require launchpad bug number for docs commits, whoever is pushing them to git.evergreen-ils.org should rebase/rewrite as needed so that they do.
11:28 jeff but i was more concerned with the role account listed as author. i don't know if that's Dan or Remington, for example.
11:28 asimon Searching the TPAC by item barcode number is case-sensitive.  Has anyone modified the TPAC to change this?
11:28 jeff (and sorry, dbwells and remingtron if it seems we're nitpicking at a useful doc commit!)
11:29 jeff asimon: i have not, and suspect that the change would need to be somewhere other than at the TPAC level, unless you know that "your" barcodes are always upper or lower case, or follow a specific pattern, in which case you could modify the input value with javascript included in a tpac template, or could transform the input value at the Perl layer tpac handler.
11:30 akilsdonk joined #evergreen
11:30 yboston bshum: do you still need feedback from we? I saw that you got some feedback from remingtron already
11:31 yboston bshum & remingtron : do we want to make additions to the DIG style guide regarding screenshots?
11:31 yboston http://evergreen-ils.org/dokuwiki/doku​.php?id=evergreen-docs:dig_style_guide
11:38 asimon jeff: TY.  JavaScript could certainly change the input to upper case or lower case.  I was just wondering if there was another way already implemented somewhere.
11:42 jwoodard joined #evergreen
11:48 bshum dbs: Never too late to just use github for the whole thing and convert all our LP to Github issues with linking over there :D
11:48 bshum yboston: I'm going to poke at screenshots when I have a bit more time.  I'm getting pulled into meetings and such.  Might not make the DIG one :\
12:16 jihpringle joined #evergreen
12:19 kbutler joined #evergreen
12:42 remingtron dbs: jeff: I'll add LP# and checking authorship to the GitHub workflow. Thanks for comments.
12:44 jeff remingtron++
12:45 ericar joined #evergreen
13:00 rfrasur joined #evergreen
13:03 hbrennan joined #evergreen
13:07 RoganH joined #evergreen
13:12 remingtron For any devs interested: http://evergreen-ils.org/dokuwiki/doku​.php?id=evergreen-docs:github-workflow
13:19 RoganH remingtron +1
13:20 finnx joined #evergreen
13:23 rfrasur_ joined #evergreen
13:32 akilsdonk joined #evergreen
13:32 rfrasur joined #evergreen
13:51 remingtron Documentation Interest Group meeting starting in about 10 minutes, all are welcome.
13:51 * rfrasur awaits.
13:53 jbfink joined #evergreen
13:54 * rfrasur awaits while writing out thank you tags for teacher appreciation week gifties from the library.
13:57 rsoulliere joined #evergreen
14:00 yboston #startmeeting 2014-05-01 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting.
14:00 pinesol_green Meeting started Thu May  1 14:00:37 2014 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 '2014_05_01___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_20140501-agenda
14:00 yboston #topic Introductions
14:00 yboston Please feel free to start introducing yourselves...
14:01 * yboston is Yamil Suarez @ Berklee college of Music - DIG meeting facilitator
14:01 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:01 remingtron (note, if  you use #info, then it shows up better in the MeetBot minutes)
14:01 yboston #info yboston is Yamil Suarez @ Berklee college of Music - DIG meeting facilitator
14:01 RoganH left #evergreen
14:02 kbutler #info kbutler is Kate Butler, Rodgers Library (Hudson, NH)
14:02 rsoulliere #info /me is Robert Soulliere, Mohawk College
14:02 jihpringle #info jihpringle is Jennifer Pringle, Sitka Support (BC Libraries Cooperative)
14:02 rfrasur #info rfrasur is Ruth Frasur, Hagerstown Library (Evergreen Indiana)
14:02 hbrennan #info Holly Brennan, Homer Public Library, Alaska
14:03 rsoulliere #info rsoulliere is Robert Soulliere, Mohawk College 2nd try ;-)
14:04 yboston as we wait for everyone to introduce themselves, should we start talking about the EG 2.6 release notes?
14:04 yboston or another topic?
14:04 remingtron maybe we should start with coordinator reports, since we haven't done that in a while
14:05 yboston OK
14:06 yboston who would like to go first?
14:06 rsoulliere I have a couple of items.
14:06 rsoulliere #topic Conversion Coordinator Report
14:06 yboston go ahead
14:06 rsoulliere #info Evergreen Documentation for 2.6 is up and available now and pulling for the rel_2_6 branch.
14:07 rsoulliere #info Note that the documentation processing is a bit finicky and asciidoc errors may hold back processing of pages you have edited. They may also prevent the PDF file from being produced.  Testing asciidoc syntax before pushing is recommended.
14:07 rsoulliere #info I sent out a question to the mailing list regarding retiring "Evergreen in Action" on Lulu?
14:07 rsoulliere #link http://list.georgialibraries.org/pipermail/o​pen-ils-documentation/2014-April/001645.html
14:08 rsoulliere Any suggestions?
14:08 remingtron do we have access to the purchase history?
14:09 kbutler Given that it's out of date, it seems logical to take it down. But will/should/does anyone want to update it?
14:09 Meme joined #evergreen
14:11 rsoulliere The software freedom conservancy group was managing the financial details of sales.
14:11 remingtron yeah, since 2.3 is no longer supported, I think we should take it down
14:11 yboston I agree, since I would eb a fraid of somone paying for something that is out of date.
14:11 rsoulliere Yeah, that what I was thinking.
14:11 yboston without realizing it
14:12 remingtron rsoulliere: do you have the ability to remove it from Lulu?
14:12 rsoulliere Yes, I can "retire" it so it it no longer available.
14:12 yboston BTW, if we want we can try a mini vote with those that are hear (using +1 or -1), but I think the consensus is pretty clear
14:13 rfrasur +1
14:13 remingtron do we need to ask the authors and/or oversight board folks?
14:13 yboston also, the content will continue to be available for free under FLOSS manuals(?)
14:14 yboston remingtron: to be nice and to establish precedent
14:14 rsoulliere yboston: exactly, and the free electronic versions will still be available from other sources for those needing a copy for sentimental reasons.
14:15 yboston but since this version is quite old and the risk of someone paying for something without realizing that is out of date, makes me want to act immediatly
14:15 kbutler +1
14:15 jihpringle +1
14:15 yboston a quick heads up to the authors shoudl not take long.
14:16 remingtron yboston: yeah, for good measure.
14:16 yboston so we might need a volunteer to pull the Lulu content and to contact the authors
14:16 remingtron dbs: are you around? quick question about removing EG in Action book from lulu
14:16 yboston I mean two seperate volunteers
14:16 yboston BTW, rsoulliere can you take care of removing it from Lulu by yourself?
14:17 rsoulliere Yes, I can and will remove it.
14:18 yboston BTW, is it definitive that all of the content from it has already been put in the main docs? I thought there were chinks missing. (this could be simple task for DIG newcomers to verify.)
14:18 yboston sorry, that shoudl say "chunks"
14:19 remingtron yboston: Sounds like a good ToDo task for the list: http://evergreen-ils.org/dokuwiki​/doku.php?id=evergreen-docs:todo
14:20 remingtron I think we should at least email the authors and EG oversight board folks and give a few days for them to respond before we remove the book from lulu.
14:21 yboston remingtron: I am updating that wiki page now
14:21 rsoulliere OK, I will wait until I get the official thumbs up.
14:21 remingtron rsoulliere: you want to email people then?
14:22 rsoulliere I can email the authors... What is the process for the Oversight Board... Anyone here on that board?
14:22 yboston I am on the board
14:22 rsoulliere yboston: could you get the OK from them?
14:22 yboston There is a mailing list, and anyone can subscribe to it
14:23 yboston I will talk to them, again perhaps just to set good precedents
14:24 remingtron Yeah, we have the power to act, but it's good to communicate with all who may care
14:24 yboston #action yboston will ask the EG oversight board if they mind that the book EIA is pulled fromt he Lulu account
14:24 rsoulliere OK, that is all I had in my report.
14:24 yboston #action rsoulliere will email the authors of EIA to ask if they mind that the book EIA is pulled fromt he Lulu account
14:25 yboston thanks rsoulliere
14:25 yboston rsoulliere++
14:25 remingtron rsoulliere++
14:26 yboston the other report woudl normally be kathy, but I don't think she is here now
14:26 remingtron yeah, I don't see her on the channel right now
14:26 yboston should we switch to the release notes or something else?
14:27 remingtron sure, this could be a quick vote, unless people have feedback
14:27 remingtron here's my email proposal
14:28 remingtron http://markmail.org/message/apb55ar3pooih4ql
14:29 remingtron I'd like to present this at the next Dev meeting for developer feedback
14:29 remingtron what does everyone think?
14:30 yboston I think it is a fine idea, though not sure how often there will be developer time to get extra documentation this way
14:31 yboston but I think having a place to place draft documentation would be good, before having to worry exactly where ti should fit
14:31 remingtron we've already had a few devs submit longer docs as release notes
14:31 yboston good to know
14:31 remingtron not sure how often it would be useful, but could at least clarify some confusion I've heard
14:31 yboston good to know again
14:32 rsoulliere +1
14:32 jihpringle I think having the definitions of normal docs vs. release notes is helpful
14:32 yboston it could be a good place for DIG and developers to collaborate on stuff
14:32 yboston at least new features
14:33 remingtron any other thoughts?
14:34 rsoulliere For draft documentation, you could upload an asciidoc file without linking to it in the  root.txt file. Perhaps file name could be prefixed with "draft"? Then it could be reviewed without being processed.
14:34 remingtron rsoulliere: good idea
14:35 yboston though it makes me think if there are already some asciidoc files lingering out there that have never been linked?
14:35 remingtron I guess it could also be added to a branch like other development
14:35 yboston kinda like using a sperate folder at first
14:36 yboston just realized we did not start a new Meetbot  "topic"
14:36 yboston #topic remingtron proposal for release notes
14:36 yboston BTW, for those that arrived after the start of this meeting, here is the agenda and a link to todays IRC log to catch up with us
14:37 yboston http://evergreen-ils.org/dokuwiki/doku.php?i​d=evergreen-docs:dig_meeting_20140501-agenda
14:37 yboston http://irc.evergreen-ils.org/evergreen/2014-05-01
14:37 yboston any other suggestions? should we vote on the proposal?
14:38 * rfrasur needs to run.
14:38 yboston of course the developers also have to approve it
14:38 rsoulliere remintron: right, branching is better. Having floating draft doc files could really bloat the repositories.
14:39 remingtron okay, let's vote on whether I take this to the next dev meeting
14:39 yboston OK
14:39 yboston +1
14:39 rsoulliere +1
14:39 jihpringle +1
14:40 remingtron cool, I'll add it to the dev meeting agenda
14:40 yboston excelent
14:40 yboston shall we talk about the EG 2.6 todos?
14:40 yboston or something else. note that we have 20 minutes untilt he hour mark
14:41 remingtron yeah, let's jump to 2.6 progress reports
14:42 yboston Here is the list http://evergreen-ils.org/dokuwiki/d​oku.php?id=evergreen-docs:2.6_needs
14:42 remingtron jihpringle: kbutler: how's it going with your chosen tasks?
14:42 remingtron any pitfalls you need help getting past?
14:43 kbutler I am not done yet, but hopefully tomorrow I have time to work on it (and finish up.)
14:44 ericar joined #evergreen
14:44 jihpringle I have partial documentation but still need to put in the screenshots - I'm hoping to have time to do them early next week
14:44 remingtron ericar: Just in time, we're talking about EG 2.6 task progress
14:45 remingtron jihpringle: kbutler: great, feel free to ask the list for help if you need anything, or when you finish, and we can push it into master
14:45 jihpringle will do
14:46 remingtron Looks like 3 tasks have been completed and pushed to master already, that's great!
14:46 yboston BTW, I just finsihed yesterday, and I almost forgot to backport to the 2.6 branch. Thankfully I ran into the email remingtron sent out recently reminding us of the backporting
14:46 kbutler definitely
14:47 remingtron yboston: yes, thanks for the reminder again, I have to backport mine still.
14:47 yboston this was a great trial run of the complete workflow
14:48 remingtron ericar: any updates on ESI's docs for 2.6?
14:48 ericar they are complete and just need to be committed to the repository.
14:49 remingtron great! ericar++
14:50 yboston ericar++
14:50 yboston BTW, should those that are "done" sign up for the still unassigned 2.6 items OR team up to help/collaborate with those that have not fisnished yet?
14:50 yboston also, I was looking over the release notes, and their might be up to three unassigned doc needs that need to be listed for 2.6
14:50 remingtron yboston: feel free to add things to the 2.6 todo list wiki page
14:51 yboston for example, the disabling of auto suggest and the deprecation of 'classic_current_circ'
14:51 yboston OK
14:52 remingtron I can commit to another task to complete by next month's DIG meeting
14:52 yboston so can I
14:52 remingtron anyone else want to commit to a 2.6 feature task?
14:53 remingtron or does anyone have questions about this process?
14:53 yboston or find a partner to commit to a 2.6 feature task?
14:53 remingtron right, I'm willing to partner with anyone
14:53 yboston me too
14:54 remingtron hbrennan: I don't want to pick on you, just wondering if you have any thoughts or questions you'd like to share?
14:55 krvmga joined #evergreen
14:55 yboston #action yboston will add more missign features from the 2.6 release ntoes that need documentation
14:56 hbrennan remington: Being honest, I'm just lurking, at best. I was startled when my browser just started flashing :)
14:56 remingtron hbrennan: no problem, lurkers are welcome. :)
14:56 krvmga is this a good time to add a little note?
14:57 remingtron krvmga: sure! docs related, right?
14:57 hbrennan remington: Being at the circ desk isn't making it easy to keep up
14:57 hbrennan remingtron I mean
14:57 remingtron hbrennan: those patrons are important folks
14:57 krvmga i've put up nearly three dozen patron-centric documents at http://www.cwmars.org/content/using-online-catalog
14:58 krvmga everyone should feel free to steal whatever is useful to them
14:58 krvmga i'll be putting up more in the next week
14:58 jihpringle krvmga++
14:59 yboston krvmga++
14:59 yboston BTW, one suggestion is to check-in on the DIG list two weeks from now, and then see what was finsished by then, to see if we can declare victory over 2.6 so we can shoot for either 2.7 features and older faetures to document for next meeting
14:59 jbfink joined #evergreen
14:59 remingtron krvmga++
14:59 krvmga the docs at cwmars are for 2.4 but they will all be updated and added to when we go to 2.5 at the beginning of June
15:00 krvmga the patron docs, that is
15:00 remingtron yboston: good idea, I can email a 2.6 progress report to the list in two weeks
15:00 yboston do you want to add a meetbot action item or should I?
15:00 remingtron krvmga: thanks for sharing your work
15:01 krvmga yw :)
15:01 remingtron yboston: go ahead and add the action, I think it only works for the person running the mtg
15:01 yboston as a test, give it a shot
15:02 yboston start with #action
15:02 remingtron #action remingtron will send a 2.6 docs progress report to the DIG list in two weeks
15:03 yboston I think that should work, but Iw ill make a dup action to be safe
15:03 yboston #action remingtron will send a 2.6 docs progress report to the DIG list in two weeks
15:03 remingtron yboston: thanks
15:04 kmlussier joined #evergreen
15:04 yboston we are slightly past the hour mark. any more pressing topics or questions?
15:04 remingtron one quick idea for future consideration
15:04 yboston BTW, if we follow the current meeting schedule, the next meeting would be June 5th
15:04 yboston go ahead
15:05 remingtron #idea I think we should consider planning a DIG hack-away for after 2.7 beta is ready but before 2.7 is officially released
15:05 yboston sure, but I can't remember when that would roghly fall on, like around September?
15:06 remingtron yeah, around then
15:06 remingtron is anyone present vaguely interested?
15:06 yboston I am interested
15:06 remingtron it would mostly mean doing some focused Docs work to help get 2.7 docs finished on time
15:06 kmlussier I'm interested (sorry I'm late.)
15:07 yboston though we have to watch out not to conflict with the dev hack-a-way
15:07 yboston in case some want to attend both
15:07 remingtron may or may not mean being physically at the same location
15:07 yboston absolutely
15:07 jihpringle bshum's schedule has 2.7 beta being released Aug 7th and then the RC Sept 4th
15:07 jihpringle as his general timeline
15:07 remingtron okay, we can discuss that more later, just wanted to plant the idea
15:07 yboston no problem
15:08 yboston anything else from anybody else, even lurkers :)
15:08 * krvmga makes scratching sounds on the wall.
15:08 krvmga rats in the walls
15:09 yboston going once?
15:09 yboston going twice?
15:09 krvmga yboston++
15:10 yboston #endmeeting
15:10 pinesol_green Meeting ended Thu May  1 15:10:02 2014 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:10 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-05-01-14.00.html
15:10 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-05-01-14.00.txt
15:10 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2014/evergreen.2014-05-01-14.00.log.html
15:10 yboston sold
15:10 remingtron yboston++
15:10 jihpringle yboston++
15:10 rsoulliere yboston++
15:12 krvmga following up on the conversation we were having here yesterday about "lost" and "missing". if an "lost" item is set to its default values will it still be visible in the staff client "Search Catalog" or, if its not visible in the public OPAC, is it also not visible in the staff client "Search Catalog"?
15:14 krvmga default value of "Lost"  is not opac_visible
15:14 krvmga currently, in cwmars, it is visible in the opac
15:15 jihpringle in Sitka when staff change an item to be opac invisible it still show up in the staff client catalogue and I believe it is the same for our opac invisible statuses
15:16 krvmga excuse my fumble fingers: an = a; its = it's
15:16 * kmlussier 's understanding is the same as jihpringle's.
15:16 krvmga lovely. brilliant. in fact, couldn't be better. thx!
15:19 eeevil jihpringle and kmlussier understand correctly. a staff search ignores status visibility (and item-specific visibility, and others)
15:20 krvmga this has all just made my day!
15:21 krvmga jihpringle++
15:21 krvmga kmlussier++
15:21 krvmga eeevil++
15:44 Dyrcona joined #evergreen
15:44 Dyrcona left #evergreen
15:45 gsams joined #evergreen
15:56 gsams joined #evergreen
16:05 bshum Hmm
16:05 bshum Overdrive API general list question
16:06 bshum Maybe I should point out that 2.6 is done, so if anyone is working on things they should bring it up for consideration on 2.7 :)
16:06 * bshum stares intently in jeff's direction :)
16:06 akilsdonk joined #evergreen
16:07 jeff hey, not MY fault they refused me access to the APIs until it was well past the point of my having time to muck with it!
16:07 * jeff ducs
16:07 jeff er
16:07 * jeff ducks
16:07 jeff <quack>
16:08 bshum Hehe, jeff++ # for being awesome
16:08 bshum *generally awesome
16:08 jeff thanks for the clarification!
16:09 bshum And I know, I'm just heckling you
16:31 kmlussier yboston, remingtron: Just catching up on some DIG meeting business. There is still a lot of material from the book that never made it into the official docs. But that content can be retrieved from the floss manuals site if needed.
16:32 kmlussier yboston, remingtron: As one of the authors, I'm okay with taking the Lulu book down. I'm not sure that the EOB needs to be consulted.
16:33 kmlussier Seems like a decision DIG should be able to make on its own.
16:33 yboston kmlussier: I thought of letting the board know because it was theoretically a source of revenue
16:34 remingtron I agree with yboston
16:35 kmlussier yboston: Sure, and they definitely needed to be consulted when setting up pricing. But, looking at merchandising as an example, the EOB didn't need to be consulted for every item put up for sale, and I'm guessing won't be consutled for taking them down.
16:35 remingtron kmlussier: that's a good point
16:35 remingtron I guess DIG feels more removed from EOB than the merch team
16:36 yboston kmlussier: I agree, I did not see it as requiring the boards permisson, but I wanted to be thorough
16:36 kmlussier I just worry about getting to EOB getting too involved in day-to-day comunity management decisions, but maybe that's the broader discussion to have with the Board. :)
16:36 remingtron so I wasn't clear on what authority we have
16:36 gmcharlt kmlussier: I'm with you on that concern
16:37 remingtron maybe we should present it to EOB as "information" rather than asking for approval?
16:37 kmlussier +1
16:37 yboston in my opinion, we have plenty of authority on matters of documentation. if the Lulu account had nothing to do with revenue, I would not alert the board
16:37 remingtron yboston: I agree
16:38 yboston so was the board contatced when the lulu account was created? are there any outstanding monies?
16:39 kmlussier yboston: Yes, the EOB needed to be involved when setting it up, IIRC, because they needed to authorize selling the Board and also needed to set something up with the SFC to make sure the money went into the right account.
16:39 kmlussier But I think it's in DIG's purview to decide when content is outdated and should be taken down.
16:40 yboston kmlussier: I agree, my plan was just to give the board a heads up because of the revenue aspect of it
16:41 kmlussier yboston: Sure, I think a heads up is fine.
16:41 remingtron yboston: I agree
16:41 remingtron kmlussier: thanks for your perspective
16:41 bshum kmlussier++ # agree with your wise suggestions :D
16:48 mdriscoll1 left #evergreen
16:50 jventuro Hey folks.  Does anyone know how to get text to align in the center in a receipt template?
16:50 hbrennan yes'um
16:50 hbrennan <center>
16:51 hbrennan before the text, and </center> and the end
16:51 jventuro Well, that was too simple.
16:51 jventuro Thank you!
16:51 jventuro hbrennan++
16:51 bshum hbrennan++
16:51 hbrennan yep, basic HTML!
16:51 kmlussier @praise hbrennan
16:51 * pinesol_green hbrennan can run a report without assistance
16:52 hbrennan Haha, that is a lie
16:52 bshum jventuro++ # asking questions in IRC :)
16:52 kmlussier jventuro++ indeed
16:52 jventuro It only took me 4 years :)
16:52 hbrennan I have our address header set up to center. Looks so nice that way
16:52 kmlussier Yes, but now that you asked that first question, watch out. You'll be sending @dessert commands to pinesol_green in no time.
16:53 bshum kmlussier++ # for giving us @dessert
16:53 bshum :D
16:53 kmlussier Speaking of which...
16:53 kmlussier @dessert
16:53 * pinesol_green grabs a slice of Cherry Pie and sends it sliding down the dessert bar to kmlussier
16:53 hbrennan It's always Cherry Pie
16:53 * kmlussier doesn't really like cherry pie.
16:53 jventuro Mmm dessert
16:53 hbrennan it takes 5 tries to get something chocolate
16:54 * kmlussier tests hbrennan's theory.
16:54 kmlussier @dessert hbrennan
16:54 * pinesol_green grabs a slice of Pecan Pie and sends it sliding down the dessert bar to hbrennan
16:54 montgoc1 a la mode?
16:54 kmlussier @dessert jventuro
16:54 * pinesol_green grabs a slice of Strawberry Rhubarb Pie and sends it sliding down the dessert bar to jventuro
16:54 kmlussier Lots of pie today.
16:54 bshum @dessert
16:54 kmlussier @dessert bshum
16:54 * pinesol_green grabs a slice of Chocolate Lava Cake and sends it sliding down the dessert bar to bshum
16:54 * pinesol_green grabs a slice of Cherry Pie and sends it sliding down the dessert bar to bshum
16:54 bshum :D
16:54 kmlussier Fourth try! :D
16:54 hbrennan haha
16:55 kmlussier Today must be slice today. No scoops or batches.
16:55 gmcharlt @dessert
16:55 * pinesol_green grabs a slice of Carrot Cake and sends it sliding down the dessert bar to gmcharlt
16:55 bshum Indeed.
16:55 bshum We need to rewrite the plugin so that it uses a database.  Then we can have people add their own desserts :)
16:56 kmlussier I agree. How do I do that?
16:56 * kmlussier thinks @dessert will be her one memorable contribution to the community.
16:56 bshum I'm not sure yet.  But I imagine it's something we can learn by looking at some of the other plugins.
16:56 hbrennan jventuro: Phasefx did a great receipt template talk at the conference. Slides are here: http://evergreen-ils.org/wp-content/u​ploads/2014/04/eg_14_receipt-talk.pdf
16:57 kmlussier Well, I suppose parts can be considered a memorable contribution.
16:57 * kmlussier pokes bshum.
16:57 bshum Sure, memorable.
16:57 bshum We'll go with that.
16:57 kmlussier parts++
16:57 kmlussier @karma parts
16:57 pinesol_green kmlussier: Karma for "parts" has been increased 7 times and decreased 14 times for a total karma of -7.
16:58 bshum Hey, think of it this way, I haven't said parts-- in a few weeks.  Oh wait...... :D
16:59 gmcharlt kmlussier: your first programming exercise may be telling the bot to ignore certain karama decrements from bshum ;)
16:59 kmlussier Ooh! I can do that?
17:01 bshum Hehe
17:01 gmcharlt assuming bshum doesn't lock it away ;)
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:01 gmcharlt though seriously, there would be worse things than the bot to use an an example/testbed for introductory programming tutorials
17:01 kmlussier That's the problem. bshum has too much power.
17:03 bshum Oh, really, can we not make them gray bibs again?  bug 1084753 discussion makes me queasy
17:03 pinesol_green Launchpad bug 1084753 in Evergreen "tpac: bib records without copies are not easily identifiable in the staff client" (affected: 2, heat: 12) [Wishlist,Triaged] https://launchpad.net/bugs/1084753
17:03 * bshum adds to his list of customizations he'll have to apply locally
17:04 gmcharlt bshum: just the grey in particular?  seems pretty clear that some visual indication of deleted record status is desired by a number of folks
17:05 bshum gmcharlt: I'm not opposed to that, though we'd probably never include deleted bibs in our searches for anyone.  But yeah, the colorization approach undertaken before was a bit unwelcome.  But perhaps we're just special in having ALOT of unattached bibs in our cluttered DB.
17:08 kmlussier Looks like we can cross some items off that list.
17:08 bshum Indeed.
17:08 kmlussier metarecord holds, ability to increase/decrease font size.
17:08 kmlussier OpenSearch too, right?
17:08 bshum Yep.
17:09 * kmlussier will update the page.
17:09 * kmlussier wonders if she should delete that "Pending Features" section.
17:09 kmlussier If they haven't been done already, I'm guessing they really aren't pending.
17:12 kmlussier Rewrites from JSPAC to TPAC to preserve old links going to new interfaces. That's been done, right?
17:12 mmorgan left #evergreen
17:13 gmcharlt yes
17:13 kmlussier Did we get rid of fixed widths? As part of the mobile-friendly catalog work?
17:14 bshum Uh, hmm
17:14 bshum A lot of them were changed
17:14 bshum I'm not 100% sure of whether we've dealt with all of the places yet.
17:15 bshum But I think it's much better now.
17:15 bshum At the very least, the bug linked in the sub bullet is marked "fix released"
17:15 bshum So there is that :)
17:17 kmlussier I'm somewhat surprised we still haven't dealt with password strength yet.
17:18 bshum Guess it wasn't enough of a blocker :\
17:18 * bshum stares intently at jeff again.
17:18 kmlussier Poor jeff. Always on the other side of bshum's stares.
17:27 ningalls joined #evergreen
17:29 gsams joined #evergreen
17:37 pinesol_green [evergreen|Kathy Lussier] Fix for docs on library information pages - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=34c2878>
17:59 kmlussier1 joined #evergreen
18:08 gsams joined #evergreen
18:45 kmlussier joined #evergreen
18:54 gsams joined #evergreen
19:08 gsams joined #evergreen
19:32 gsams joined #evergreen
19:54 kmlussier @dessert bshum
19:54 * pinesol_green grabs a slice of Chocolate Lava Cake and sends it sliding down the dessert bar to bshum
19:59 gsams joined #evergreen
20:16 geoffsams joined #evergreen
22:23 n2006 joined #evergreen
22:29 n2006 left #evergreen
22:59 bshum :D
23:00 bshum @dessert add Mint Chocolate Ice Cream
23:00 pinesol_green bshum: The operation succeeded.  Dessert #3 added.
23:00 bshum @dessert
23:00 * pinesol_green grabs chocolate chip cookies and sends it sliding down the dessert bar to bshum
23:00 bshum @dessert [someone]
23:00 * pinesol_green grabs Mint Chocolate Ice Cream and sends it sliding down the dessert bar to dbwells
23:01 bshum @dessert search
23:01 pinesol_green bshum: 3 found: #1: "chocolate chip cookies", #2: "chocolate pudding", and #3: "Mint Chocolate Ice Cream"
23:03 bshum @dessert 2
23:03 * pinesol_green finds chocolate pudding and offers this tasty treat to bshum
23:03 bshum Hehe
23:03 bshum Okay, so much for being productive tonight.
23:11 bshum @dessert get 1
23:11 pinesol_green bshum: Dessert #1: "Chocolate Chip Cookies" (added by bshum at 10:08 PM, May 01, 2014)
23:11 bshum @later tell kmlussier Mission accomplished.
23:11 pinesol_green bshum: The operation succeeded.

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