Evergreen ILS Website

IRC log for #evergreen, 2013-10-16

| 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
01:30 dbwells_ joined #evergreen
01:30 [1]remingtron joined #evergreen
01:53 Mark__T joined #evergreen
01:55 dbwells joined #evergreen
01:55 remingtron joined #evergreen
01:58 dbwells_ joined #evergreen
01:58 [1]remingtron joined #evergreen
02:18 stevenyvr2 joined #evergreen
02:18 stevenyvr2 left #evergreen
07:28 jboyer-isl joined #evergreen
07:34 rjackson-isl joined #evergreen
07:52 collum joined #evergreen
08:14 akilsdonk joined #evergreen
08:36 kbeswick joined #evergreen
08:55 mmorgan joined #evergreen
08:59 mrpeters joined #evergreen
09:41 kbeswick joined #evergreen
09:49 phasefx2 joined #evergreen
09:49 mllewellyn joined #evergreen
09:52 yboston joined #evergreen
10:02 rfrasur joined #evergreen
10:11 kmlussier joined #evergreen
10:13 dbwells kmlussier: I pushed my combined release notes file to master last night.  You can see it here, and also read in the commit message about the state of things: http://git.evergreen-ils.org/?p=Evergreen.git;a=c​ommit;h=8866470bf0c79e39324917f89523fefb2cf9a4fa
10:13 pinesol_green [evergreen|Dan Wells] Initial compilation of release notes for 2.5 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8866470>
10:14 dbwells kmlussier: I was focused mostly on the html generated output, so the text itself could still use some general cleanup, especially extra whitespace.  Also, the generated version is live: http://evergreen-ils.org/documentat​ion/previews/RELEASE_NOTES_2_5.html
10:15 kmlussier dbwells: Thanks! I think I'll have time today to try to tackle that file and clean things up a bit.
10:17 jeff dbwells++
10:18 dbwells kmlussier: As soon as you are comfortable doing so, please do delete the stuff in the RELEASE_NOTES_NEXT folder, or let me know and I can do it.  I didn't want to jump the gun on that, but also don't want those files to linger, since we might accidentally get some parallel edits.
10:22 kmlussier dbwells: OK, I'll do that.
10:27 dbwells kmlussier: thank you!  Also, if there is anything about this process which you think didn't go the way it should, please let me know.  It wasn't totally clear which parts of the release notes process I was supposed to handle, so I am sorry if I went out of bounds at all.
10:30 dbs s/let me know/document this part of the release process on the wiki/ ?
10:33 kmlussier dbwells/dbs: Yes, I think documenting it would be good. I'll give the process some thought. 2.4 was the first release that we had that script to generate the release notes, but by the time eeevil had done it, we were almost done with the process of refining the release notes. So I would say this is the first release where we've fully used that script to generate the release notes.
10:35 dbwells That sounds like a good plan.  The stated idea on the wiki the release-notes-writer is "now a community effort" certainly lends itself to fuzziness, but in the end, maybe that's good enough :)
10:35 rfrasur berick++
10:35 kmlussier dbwells: Which wiki page is that one?
10:35 kmlussier s/one/on
10:36 dbwells kmlussier: http://www.open-ils.org/dokuwiki/doku.​php?id=dev:evergreen:release_checklist
10:36 dbwells some parts are obviously out of date.
10:37 dbwells Not sure if there is a better one.
10:38 dbwells kmlussier: Also, I did some manipulating of the release notes by hand, but having done it now a couple times, I know a good bit of it could be automated into the builder script.
10:39 rfrasur jcamins: thank you for the article.  The topic is something that I've been trying to figure out how to conceptualize.  This helps that a lot.
10:39 kmlussier dbwells: Thanks! Release notes writing is indeed a community effort now, but I would say there still need to be one or two people who need to verify that everything made it in and review the notes for clarity, typos, etc.
10:44 dbs Maybe see if there's a DIG volunteer to step up as release notes (or docs?) coordinator for the next release? Shoulder to shoulder with the release manager?
10:44 * kmlussier is the DIG release coordinator. :)
10:44 sylvar joined #evergreen
10:45 dbs kmlussier++ # sorry!
10:47 sylvar I'm seeing references to a "windowssetup.nsi" and my brain keeps wanting to insist that it must be .msi (Microsoft installer). What's up with that?
10:47 jeff nullsoft installer image.
10:48 jeff technically, NSIS, Nullsoft Scriptable Install System
10:48 sylvar jeff++ # Evergreen: It really whips the camel's ass.
10:48 kmlussier On another topic, is there a way to configure which statuses are included when the "limit to available" checkbox is selected? I thought there was something in config.tt2, but I'm not seeing anything.
10:48 sylvar Llama?
10:48 sylvar Eh, I forget.
10:49 jeff and i shouldn't have said "image" above. the nsi file is the NSIS script.
10:49 jeff sylvar: Llama
10:49 * sylvar resists the urge to /topic it.
10:49 rfrasur kmlussier++ #she who does many things
10:49 dbs kmlussier: I guess the DIG roles are listed on a DIG wiki page. I wonder if it would make sense to have a "Release X.X in a nutshell" page that listed the release manager, docs coordinator, QA lead, i18n lead, link to the roadmap, dates, etc...
10:49 jeff sylvar: probably best.
10:50 jeff +1 to roles for a release being documented in a handy place
10:50 kmlussier dbs: It looks like the release checklist page dbwells linked to above was supposed to do that. But, as he mentioned, it's a bit outdated.
10:51 dbs kmlussier: in times past, the concept of availability often ended up being hardcoded, despite having some database-level configuration bits
10:51 kmlussier But, you're right. The DIG release coordinator role has mostly been codified in the DIG side of things and not so much in places like the release checklist.
10:51 dbs Not sure if it's still "AND status IN (1,3,7)" in the important bits anymore...
10:52 rfrasur has there been talk in the past about when a patron's email bounces automatically invalidating that email address and making a note/alert on their account?
10:53 rfrasur jboyer-isl:^have you heard of such a thing in EI? or further abroad?
10:53 kmlussier Darn! I was hoping there was an easy way to add some local statuses there.
10:54 * dbs is guilty of having created the release checklist page in the past, and intended it to be a generic process-oriented thing, vs. a "release status / who do we lynch?" page that names names and arguably serves a separate role :)
10:55 jeff rfrasur: we're likely to start doing that on a wider scale soon.
10:55 jboyer-isl rfrasur: I'm not sure there's currently a way to do that. Parsing email logs is like a nerd's version of Dirty Jobs; no one wants to do it.
10:56 rfrasur jeff++ #yay...that shall be my happy for today
10:56 rfrasur jboyer-isl: I don't want to deal with them anymore...hence the desire for an automatic process :D
10:56 jboyer-isl rfrasur,jeff: though I've been wrong before. Jeff, is "we" tadl, or is there a project in Eg that I'm woefully out of date about?
10:56 * rfrasur has nearly gotten to the point of using the f word
10:57 jboyer-isl Friends of the Library? ;)
10:57 rfrasur yes....friends of the library....another topic altogether.
10:57 jeff jboyer-isl: i should have clarified. the "we" above was tadl, and we'd like to do it in a way that would be useful to all.
10:57 dbs asset.opac_ou_record_copy_count has 0,7,12 hard-coded
10:57 rfrasur that also inspires another f word at times
10:57 jeff but of course everyone's mail infrastructure is different. :-)
10:58 dbs cp_available_by_circ_lib_idx just has 0,7 in the index WHERE clause
10:58 * rfrasur thinks that people that think IE is the internet shouldn't be allowed to use email.
10:58 jboyer-isl jeff: that sounds like a big help (especially since I think there's a valid? field for email now?). Looking forward to hearing how it goes. :)
10:59 rfrasur jboyer-isl: there is a valid field now...which has been added into our workflow and is very helpful...but it's still clunky
10:59 jeff jboyer-isl: not a valid field for email, but an api call (and UI button) to invalidate. the invalidate process clears the email from the user and makes note of it in a standing penalty, so that staff can see "we HAD an email for you, but it was marked invalid, can we get an updated address?", etc.
10:59 RoganH joined #evergreen
11:00 rfrasur jeff: that's EXACTLY what I was thinking would be nice.
11:00 jboyer-isl Oh. It's been too long since I've seen the patron reg screen. Getting a little too high in my ivory tower over here. :/
11:00 dbs ah, query_parser_fts takes an array of statuses, so that's good
11:00 jeff i'm cleaning up our patron records by removing e-mail addresses that are syntactically invalid, putting in a very forgiving-but-useful regex for the user registration form, and then we'll be moving on to invalidating addresses that bounce.
11:01 rfrasur jboyer-isl: please look with favor upon us, the mere plebians.
11:01 jeff rfrasur: the Invalidate button should be in your user editor now, and should do roughly what i described. the only missing part is the making it more automatic, so that a human doesn't need to hit the Invalidate button.
11:02 jeff dbs: COPY_BAD_STATUS at checkin time has a hardcoded list of statuses, I think.
11:02 rfrasur It is.  We use it.  It's just the "automatic" that I'm pining for.
11:02 jeff dbs: though that's not exactly in-scope for your "what is considered available" quest at hand. Sorry. :-)
11:02 jboyer-isl update actor.usr set email = null;
11:02 jboyer-isl No more invalide emails!
11:02 jeff rfrasur: got it. just making sure you were aware of and using what was there already -- and that it did what I expected.
11:03 rfrasur Yup :D
11:24 kbutler joined #evergreen
11:30 kmlussier joined #evergreen
11:45 mrpeters left #evergreen
12:06 dbs oh, and in staged_fts() in O:A:Storage:Publisher:metabib.pm, statuses = (0,7,12) for the "available" filter
12:06 rfrasur dbwells++
12:07 dbs also in query_parser_fts() in the same module
12:08 dbs I guess the least we could do would be to adjust the index on asset.copy to include 12
12:11 kmlussier dbs: Yes, I agree it would make sense to keep them consistent. The issue we have here is that there are locally-created statuses they would like to see included in the "Limit to Available," so that's not something that could be easily handled by a global change to the code.
12:12 kmlussier Is 12 Reserves?
12:12 kmlussier nm. I answered my own question.
12:12 dbs kmlussier: I completely understand
12:21 smyers_ joined #evergreen
12:32 ktomita-phone joined #evergreen
13:04 rfrasur kmlussier: I'm putting together something for EI about the MVF development program and am trying to gather together as much information as possible.  If libraries were to commit funds, would they just mail checks to MassLNC?  Will this need to be rebid after the 30 days? (after today?)
13:16 sylvar So I'm guessing that the effects of changing Evergreen/Open-ILS/examples/permacrud.xsd from <xs:attribute name="permsission" type="xs:string"/> to <xs:attribute name="permission" type="xs:string"/> would be positive.
13:16 sylvar (s/permsission/permission/)
13:21 dbs sylvar: sure. have you run xmllint against the default fm_IDL.xml with the schema recently?
13:22 sylvar dbs: no, I haven't; I'm just supervising aspell as it goes through... well, ultimately master, I guess.
13:22 dbs sylvar: don't worry, nobody else has either. *ba dump SHHH*
13:23 dbs "xmllint --noout --schema fm_IDL.xsd fm_IDL.xml" for those following along at home
13:24 sylvar dbs: *snort* I'm not actually using EG. Just volunteering to supervise a spellcheck (not fully copyediting, just "oh, that's an abbreviation for container::call_number_bucket_type... okay aspell, you can learn 'ccnbt').
13:32 csharp @who fails to validate?
13:32 pinesol_green csharp: Mr. Spock: Something fascinating just happened.
13:42 kbeswick joined #evergreen
13:47 bzl joined #evergreen
13:55 Bmagic joined #evergreen
13:57 fparks_ joined #evergreen
13:59 sylvar I'm trying not to change *code* while spellchecking, but I think oils_sql.c:4464 may have a logically significant typo. There are 15 occurrences of 'selfield' and only 1 occurrence, in that line, of 'elfield'. scottmk, you committed http://git.evergreen-ils.org/?p=Ev​ergreen.git;a=commitdiff;h=b822a2b​acf811932a57474ce9fe5f5765706c9cf -- should I change that to 'selfield'?
13:59 pinesol_green [evergreen|scottmk] Pedantic changes for const-correctness: - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b822a2b>
13:59 sylvar ah, scottmk no here
14:01 sylvar will file separate bug
14:01 dbs sylvar: luckily it's in an "#if 0" block, but yeah, should be fixed.
14:02 stevenyvr2 joined #evergreen
14:02 kbeswick_ joined #evergreen
14:04 sylvar dbs++
14:05 sylvar I feel vaguely bad that I've added both "thingy" and "thingie" to my custom dictionary.
14:06 rfrasur sylvar: don't feel even vaguely bad about that.
14:07 gmcharlt sylvar: as long you resist the temptation to add "thingamabob"...
14:07 gmcharlt ;)
14:07 bzl you hve to watch your step with these librarians
14:08 * rfrasur agrees with bzl - we're a treacherous bunch
14:13 jeff rumor/legend had it that the local newspaper's early computer system had an "add" function for its spell check but nobody knew how to "remove". one summer intern didn't understand the correct usage of the system and ended up adding most common typos, and their spell check became useless.
14:13 jeff i keep meaning to ask someone over there how much truth there was to that tale. :-)
14:14 rfrasur there should never be an add w/o a remove...unless it's NEVER a person doing the adding.
14:14 dbs "Every time I hit Add another red wiggly line goes away, that's progress!"
14:15 rfrasur dbs++
14:15 gmcharlt jeff: that reminds me of one of my hobby-horses -- the evils of automatically generating authority records
14:16 kmlussier dbs++
14:16 gmcharlt (or at least, not checking them after they're generated)
14:16 jeff authority by majority.
14:19 jcamins gmcharlt: automatically generating authority records is a great idea! Even better an idea would be to use a script intended to work with an existing authority file.
14:19 jcamins To generate the authorities.
14:20 gmcharlt jcamins: what I'm objecting to is functionality that takes bib records and generates authority records from their headings without reference to anything else such as an external authority database
14:20 gmcharlt among other things, a good way to enshrine typos
14:20 jcamins gmcharlt: my tongue was firmly in my cheek.
14:20 gmcharlt jcamins: ah, sorry -- missed that :)
14:20 jcamins I would agree with you that it is an extraordinarily bad idea.
14:20 jboyer-isl King, Steve 19XX - ?
14:21 gmcharlt jboyer-isl: Bachman, Steve...
14:21 jboyer-isl Hah, yes.
14:21 jcamins In the Koha world a surprising number of people think that the link_bibs_to_authorities script should be used for generating new authorities.
14:31 bzl i'm a noob, trying to load the gutenberg catalog.marc file
14:32 rfrasur the whole thing?
14:32 bzl should i be following the docs in Evergreen/docs/initial_setup/migrating your data?
14:32 bzl the whole thing
14:32 rfrasur I dunno about the docs...and good luck.
14:33 bzl i'm just looking for sample data to load
14:34 rfrasur gotcha.  I honestly can't help with that part.  and I'm not sure how many people are in here...but also at kohacon so w/ split attentions
14:35 * rfrasur is a mere library administrator...not systems admin.
14:36 dbs bzl: sample data is loaded when you run eg_db_config.pl with one or more flags
14:37 bshum With 2.4+
14:37 dbs bzl: for example, --load-all-sample
14:37 dbs bshum: good point!
14:38 bzl so if i already went through the install process, i can run that script again as stated in the README?
14:39 bzl lets find out
14:39 dbs bzl: yep, if you use the --create-schema flag it blows away the existing database
14:39 dbs (fair warning: all data will be lost!)
14:41 kmlussier dbs: Before I commit my changes to the release notes, should we be saying anything about schema.org in the release notes?
14:42 dbs kmlussier: I can always add something, right?
14:42 * kmlussier nods.
14:48 bshum remingtron++
14:53 kbeswick joined #evergreen
14:53 ktomita_ joined #evergreen
14:59 fparks joined #evergreen
15:01 phasefx thingamajig
15:12 csharp @quote random
15:12 pinesol_green csharp: Quote #24: "<denials> when git doesn't kill you, it makes you smarter" (added by gmcharlt at 03:58 PM, May 03, 2012)
15:22 jeffdavis http://pastebin.com/RtPdhiC5 <- anyone seen this sort of error before?
15:22 jeffdavis the function that "does not exist" does indeed exist, and search_path appears to be set correctly
15:26 jeffdavis ah, wait, no it wasn't - server is configured to use an unexpected postgres role which does not have correct search_path
15:26 jeff bingo.
15:26 jeffdavis This is the great thing about IRC. As soon as you ask a question publicly, you figure out the answer for yourself. ;)
15:27 jeff jeffdavis: *quack*
15:27 rfrasur kmlussier: are you available to read something?
15:27 csharp jeffdavis+++
15:27 csharp jeffdavis++
15:27 jeffdavis jeff: "but this can't possibly be a duck!"
15:28 sylvar congrats jeff, you qualify for http://www.nerdmeritbadges.com/products/rubberduck
15:29 csharp jeffdavis: sometimes just starting to type the question, then going - "wait a minute... did I consider X?
15:29 csharp is enough
15:29 * csharp is typo happy and needs to stop :-/
15:29 * rfrasur needs to stop working...an hour ago
15:30 sylvar (my favorite nerd merit badge is http://www.flickr.com/photos/sylvar/tags/bitcoin because I bought it when 1BTC < 7USD)
15:52 jeff sylvar: nice. rather an expensive badge now.
16:15 bzl allright, next, i'm trying to log into the linux staff client on the server machine, i get a few 'dojo not defined errors' and some other js related errors when i log in
16:15 bzl is dojo 1.3.3 still what is being used with current release?
16:16 bzl evergreen.git, not 2.4
16:17 sylvar "fourty_two" atque "anscestor_depth" sicut "recuring" delendae fuerant. Not today, though.
16:20 phasefx bzl: dojo 1.3.3, yes
16:50 mrpeters joined #evergreen
16:50 mrpeters left #evergreen
16:59 mmorgan left #evergreen
17:14 pinesol_green [evergreen|Kathy Lussier] Release notes cleanup - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7e785f3>
17:15 bshum Ugh, running 0836 is gonna take forever... just realized it's adding columns for the auditor tables.  :(
17:18 jeff upgrades a perfect times to archive auditor tables, no? ;-)
17:18 tsbere I didn't think *adding* columns was a long term process...unless they have defaults, anyway.
17:19 bshum I just miss things just finishing in seconds :D
18:05 bzl okay, on login to the staff client "dojo is not defined" "js2JSON is not defined" "perm_ex is not defined"
18:05 bzl it can't find dojo?
18:06 senator bzl: what xulrunner version are you using?
18:07 * senator tries to remember the various problems that can lead to that series of errors from the staff client
18:07 bzl 10
18:07 bzl do I need 14?
18:08 senator i think so
18:08 senator we basically jumped from 1.9.2.x to 14 IIRC, and i think most people haven't tried anything in between
18:09 bzl hmm, i seem to get the same error
18:09 bzl i think i will wipe everthing and see if i can recreate it
18:11 bshum joined #evergreen
18:15 smyers_ joined #evergreen
19:46 smyers_ joined #evergreen
20:41 DPearl joined #evergreen
21:09 stevenyvr2 joined #evergreen
21:10 stevenyvr2 left #evergreen
21:30 stevenyvr2 joined #evergreen
23:43 shadowspar joined #evergreen
23:45 jeff oh hey, this AuthorizeReporting.pm perl module I wrote a few years ago still works.
23:45 jeff (yay)

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