| Time |
Nick |
Message |
| 00:26 |
|
b_bonner_ joined #evergreen |
| 00:26 |
|
chatley_ joined #evergreen |
| 00:26 |
|
dreuther_ joined #evergreen |
| 00:27 |
|
artunit_ joined #evergreen |
| 00:30 |
|
bradl_ joined #evergreen |
| 00:30 |
|
riot_ joined #evergreen |
| 00:31 |
|
dexap joined #evergreen |
| 00:35 |
|
mtj_- joined #evergreen |
| 00:35 |
|
mnsri joined #evergreen |
| 02:27 |
|
zerick joined #evergreen |
| 07:57 |
|
rjackson-isl joined #evergreen |
| 08:00 |
|
dcook__ joined #evergreen |
| 08:28 |
|
mrpeters joined #evergreen |
| 08:29 |
|
akilsdonk joined #evergreen |
| 08:42 |
|
mmorgan joined #evergreen |
| 08:49 |
|
collum joined #evergreen |
| 08:59 |
remingtron |
berick: minor conflict in css file when combining the two reports branches |
| 09:00 |
remingtron |
Open-ILS/web/reports/oils_rpt.css |
| 09:01 |
berick |
remingtron: not too surprised. if you like, i could create a combined branch for the two of them, since they are so tightly linked |
| 09:03 |
remingtron |
sure, that would be helpful. thanks! |
| 09:04 |
berick |
sure thing |
| 09:10 |
|
kmlussier joined #evergreen |
| 09:12 |
berick |
remingtron: working/user/berick/lp1332138-lp1329503-reports-combined |
| 09:12 |
berick |
i'll add a note to the LP's too |
| 09:12 |
remingtron |
berick++ #helping me test |
| 09:14 |
|
jwoodard joined #evergreen |
| 09:19 |
kmlussier |
Happy beta day! |
| 09:21 |
kmlussier |
Just a reminder that the following features need release notes - http://bit.ly/X4fGFH. I'll take care of the top one when it's ready to go. |
| 09:22 |
kmlussier |
And another reminder to fill out the bug squashing day poll. I hope to close it today. http://doodle.com/2dx9h3cccwbp84v4 |
| 09:22 |
* kmlussier |
is done issuing reminders. For now. |
| 09:24 |
kmlussier |
berick: On the reports branches, I was close to ready to sign off on the documentation one (just wanted to do some last-minute testing this morning), but was still finding issues on the other. I see you've merged them Any problem with me still signing off on the one? |
| 09:25 |
|
tater joined #evergreen |
| 09:28 |
berick |
kmlussier: no, that's fine. I can re-merge w/ signoff's (FYI remingtron) |
| 09:28 |
remingtron |
got it. thanks |
| 09:29 |
|
yboston joined #evergreen |
| 09:31 |
|
mdriscoll joined #evergreen |
| 09:36 |
remingtron |
yboston: error in ericar's doc, so online docs don't show her changes |
| 09:36 |
yboston |
darn |
| 09:36 |
remingtron |
ERROR: MARC_Fixed_Field.txt: line 1: [blockdef-listing] missing closing delimiter |
| 09:36 |
remingtron |
looks like a bad character at the beginning of that file |
| 09:37 |
remingtron |
something from copy/pasting from windows maybe? |
| 09:37 |
yboston |
I tried building all of her docs individually as part of the whole docuemntation. That process spits out a lot of errors, I must have missed it |
| 09:38 |
yboston |
I even created both HTML and epub versiosn of all the docs. Again, I must have missed it, or frgot to build that version |
| 09:38 |
yboston |
Would you like me to try to fix it? |
| 09:38 |
yboston |
or did you work on it already? |
| 09:39 |
remingtron |
I haven't done anything to it yet, so go ahead |
| 09:39 |
remingtron |
I think I saw other funny characters in some of her other docs too, I'll try to get you a list |
| 09:39 |
yboston |
OK |
| 09:40 |
remingtron |
bad apostrophes in D-subscription-ASCV.txt |
| 09:41 |
remingtron |
bad first character in tpac_meta_record_holds.txt |
| 09:41 |
remingtron |
bad first character in MARC_RAD_MVF_CRA.txt |
| 09:42 |
remingtron |
bad first character in physical_char_wizard.txt |
| 09:43 |
remingtron |
I think that's all |
| 09:46 |
yboston |
I will work on these |
| 09:47 |
remingtron |
yboston: thanks! |
| 09:47 |
dbs |
Sounds like we need a docs test build server maybe... |
| 09:48 |
yboston |
I have considered setting a test docs build server at Berklee, set to run its scripts mid day |
| 09:48 |
remingtron |
dbs: yes, that would be great. Robert is out of country all summer, any idea how/where else to set one up? |
| 09:48 |
yboston |
that way we can get a heads up on what will go wrong |
| 09:48 |
|
Dyrcona joined #evergreen |
| 09:51 |
dbs |
remingtron: might make sense to piggyback on the buildbot actually--just install the doc build prereqs on the build clients and then generate html / pdf / epub with an expected output of "OK" or similar |
| 09:52 |
dbs |
that wouldn't give us the whole enchilada that rsouilliere has going on but at least we could see build errors immediately |
| 09:52 |
remingtron |
dbs: definitely a good start |
| 09:53 |
remingtron |
yboston: did Robert give you the build scripts and all? |
| 09:53 |
yboston |
he has a github repository for them |
| 09:53 |
yboston |
looking it up now |
| 09:53 |
yboston |
https://github.com/rsoulliere/Evergreen_Documentation_Tools |
| 09:54 |
yboston |
I beleive these scripts are a little behind of what he uses right now, becuase I think he has to update the script to tell it the new release numbers |
| 09:55 |
yboston |
I have some other notes that he sent me a while ago that are missing from that repo (now that I am re-reading his notes) |
| 09:56 |
yboston |
Who should DIG collabrate with to set up a test docs build? |
| 10:00 |
yboston |
Dan I just sent you and remingtron a copy of the one email that Robert described a lot of his process |
| 10:03 |
dbs |
yboston: might make sense to put this out on the list, with some different possibilities (buildbot for basic builds; make targets for the docs in regular source; makefile.install target for doc build prereqs; a whole separate doc build server...)( |
| 10:03 |
dbs |
And see if anyone objects and/or is willing to tackle any of those pieces |
| 10:04 |
dbs |
yboston++ # thanks for forwarding |
| 10:04 |
dbs |
(and by "the list" I think open-ils-dev makes sense) |
| 10:06 |
remingtron |
yboston: thanks for sharing the info from Robert |
| 10:06 |
remingtron |
dbs: yboston: sounds like a good idea to see what the other devs think and try to move forward with something |
| 10:07 |
yboston |
I won't have time today to put together a letter to the dev ist buyt I will do it tomorrow or MOnday |
| 10:07 |
remingtron |
sounds great, thanks! |
| 10:07 |
remingtron |
yboston++ |
| 10:07 |
|
mtate joined #evergreen |
| 10:08 |
yboston |
remingtron: I will send you the draft to see what you think, like my idea of firing my scripts at something like 4 PM EST to get a chance to preview docs before the day is done |
| 10:13 |
|
RoganH joined #evergreen |
| 10:20 |
remingtron |
yboston: thanks |
| 10:26 |
|
RoganH joined #evergreen |
| 10:27 |
|
Shae joined #evergreen |
| 10:34 |
|
RoganH joined #evergreen |
| 10:37 |
jeff |
xz++ |
| 10:37 |
jeff |
2.9G MARC file compresses with bzip2 to 700M, with xz to 533M. |
| 10:37 |
yboston |
nice |
| 10:37 |
jeff |
(-9 to both, obvious trade-offs of memory and time, etc, etc) |
| 10:38 |
jcamins |
jeff: how much faster is bzip2 than xz, though? |
| 10:39 |
jeff |
jcamins: xz shows timing info by default when -v is used, and came out to: |
| 10:39 |
jeff |
100 % 532.1 MiB / 2,947.7 MiB = 0.181 821 KiB/s 1:01:18 |
| 10:39 |
jeff |
jcamins: bzip2 does not show timing information with -v, and i did not time it myself, so i don't know: |
| 10:39 |
jeff |
mrc: 4.215:1, 1.898 bits/byte, 76.28% saved, 3090908651 in, 733240838 out. |
| 10:40 |
jcamins |
That's too bad. I can't be bothered to compress such a large file to compare the compression speeds. |
| 10:40 |
jcamins |
Especially since there aren't enough outlets so I can't really plug my laptop in today. |
| 10:41 |
jeff |
jcamins: i'm a curious person, so i'm re-compressing the file with bzip2 using "time" to time it |
| 10:41 |
jcamins |
jeff++ |
| 10:41 |
jeff |
since that data was one of the things i was originally interested in as well. |
| 10:42 |
jeff |
when paying per gb/mo, time up front compressing can be time well spent. |
| 10:42 |
jcamins |
True. |
| 10:42 |
jcamins |
That's a shockingly massive marc file. How many records are in it? |
| 10:44 |
jeff |
it's a single marc record with one 856 tag for each wikipedia article (and each revision of each article) |
| 10:45 |
jeff |
(i am joking) |
| 10:45 |
jcamins |
lol |
| 10:47 |
yboston |
I wanted to quick feedback to see what the crowd would recommend for solving an issue I have. |
| 10:47 |
yboston |
We pay for Syndetics to provide album covers for us, but a lot of our older CD bibs do not have the UPC values that Syndetics needs to rpovide covers |
| 10:48 |
yboston |
if I have a table of item barcodes (library barcodes) and the corresponding UPC barcodes |
| 10:48 |
yboston |
is there a way to programatically add the appropirate MARC tag with the correct UPC value to each bib? |
| 10:49 |
yboston |
I can set up a query to match the item barcode to the bib, but not sure what options I have to add the proper UPC MARC tag, after I find the bib number |
| 10:53 |
jeff |
yboston: two options come to mind, neither in a "ready for immediate use" state, so i defer to others who might have ideas that you can use right away: you can use a custom DB plperl procedure to update bibs based on a database table of item -> upc, or you could use a perl script to read those bibs, parse and edit the marc, then write it out. |
| 10:53 |
jeff |
yboston: both are about the same, just different in implementation. |
| 10:55 |
dbs |
yboston: we have a need to do the same sort of thing for adding OCLC numbers after a batch reclamation process |
| 10:55 |
dbs |
It's on my list of to-dos, just not super high priority, but the plan was to go the plperl route |
| 10:55 |
yboston |
jeff: that really helps. I assumed that "a perl script to read those bibs, parse and edit the marc, then write it out." would work, but I was afraid there was a more obvious EG approach |
| 10:59 |
yboston |
dbs: thanks for chiming in, I am glad I am not the only one comtemplating something like this. I can ping you in a few months to see if you have looked at this problem again. |
| 10:59 |
yboston |
Also, I will probably write abotu it again on IRC or on the list as a plug away. The summer break is a great time for the studetns to fill up the item-> UPC table to get the ball running |
| 10:59 |
yboston |
s/as a plug/as I plug/ |
| 11:00 |
|
RoganH joined #evergreen |
| 11:07 |
jeff |
some day before physical media is dead, i dream of "scan item barcode, insert CD in drive, bib record is updated with musicbrainz ID/fingerprint/whatnot" |
| 11:09 |
dbs |
jeff: also, "take a picture of the cover with your cellphone when processing the item and have the cover automatically be associated with the catalogued item & added to a giant brain of Evergreen / musicbrainz services" |
| 11:10 |
pinesol_green |
[evergreen|Thomas Berezansky] LP#1302207 - Order AddedContent identifiers - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=76bb7b2> |
| 11:10 |
pinesol_green |
[evergreen|Jason Stephenson] LP#1302207 - Attempt to validate ISBNs in AddedContent.pm. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=cdda11a> |
| 11:11 |
dbs |
Always wanted to add write hooks for openlibrary for that purpose, wouldn't it be great to have openlibrary automatically get a new MARC record (if none exists) + cover from every opted-in Evergreen site? |
| 11:11 |
dbs |
*sigh* |
| 11:11 |
jeff |
dbs: yes |
| 11:11 |
jeff |
more co-operation / federation between libraries and services like musicbrainz/openlibrary |
| 11:11 |
dbs |
Hey, maybe musicbrainz / openlibrary types should be invited to the hackaway |
| 11:12 |
dbs |
(maybe a future one) |
| 11:13 |
jeff |
or a dedicated one |
| 11:18 |
bshum |
berick: I'm fixing up the jessie Makefile. Needs some light rebasing because we put in the Ubuntu Trusty stuff first and it shifted around some bits. |
| 11:18 |
bshum |
This is only intended to be initial support I guess, till Jessie is actually released. |
| 11:28 |
|
bmills joined #evergreen |
| 11:30 |
pinesol_green |
[evergreen|Bill Erickson] LP#1306019 Debian Jessie makefile.install target - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4af0f83> |
| 11:30 |
pinesol_green |
[evergreen|Bill Erickson] LP#1306019 move Business::Stripe to the 'force' list - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=dc70c30> |
| 11:30 |
bshum |
FYI for folks who might be curious |
| 11:30 |
bshum |
The beta deadline is today (I probably won't attempt cutting anything till tomorrow) |
| 11:32 |
bshum |
That said, there's been some discussion regarding the websockets work for OpenSRF and the web client preview for Evergreen and getting further review time on those. |
| 11:34 |
bshum |
As 2.7 RM, I am granting a special exception for this work and adding an additional milestone for beta2 (about 1-2 weeks from now) that is intended to include the web client preview. |
| 11:34 |
bshum |
If anything else comes up between now and then we'll re-evaluate things. |
| 11:35 |
bshum |
But for now, beta1 stands as firm freeze for new features unless otherwise brought up to my attention. |
| 11:36 |
jeff |
firm freeze as in "committed", and not just "targeted" -- correct? |
| 11:36 |
bshum |
That would be ideal yes. |
| 11:36 |
bshum |
If you have specific reservations about any features that are close, but needs a little more love, let me know today. |
| 11:36 |
bshum |
And I'll think it over. |
| 11:39 |
kmlussier |
Sounds reasonable to me. |
| 11:39 |
berick |
bshum++ # jessie -- yes, this is just to get it into the stream. it may have to change over time |
| 11:39 |
jeff |
bshum++ thanks! |
| 11:39 |
bshum |
berick: I already wonder what version of Apache is in Jessie. With Trusty, we found we had to disable some extra config, but I don't know if Jessie is the same way quite yet. |
| 11:40 |
bshum |
I'm writing an email to the list to describe the plan from here, but feel free to continue reviewing / signing off / pushing today :) |
| 11:40 |
* berick |
fires up his jessie VM to see |
| 11:40 |
dbs |
apache 2.4 according to https://packages.debian.org/jessie/apache2 |
| 11:40 |
berick |
dbs++ |
| 11:44 |
* eeevil |
curses his support for separating sipserver out... |
| 11:45 |
eeevil |
bshum: there are 2 commits at the top of http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/eg-sip2-support-multiplex-personality that are follow-ons to the nonce branch in support of some sipserver code |
| 11:45 |
bshum |
dbs++ |
| 11:45 |
bshum |
berick: In that case, with apache 2.4 in the mix, we may need to add some variant of e61a8085f9edabd97600b072c1a3ea41cd14265b for Jessie as well. |
| 11:45 |
pinesol_green |
[evergreen|Ben Shum] LP#1341013: Load apache mod CGI - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e61a808> |
| 11:46 |
gmcharlt |
bshum: note that the branch that eeevil pointed to is a no-op for the non-multiplex SIPServer (IOW, pushing it to EG now shouldn't break anything) |
| 11:47 |
eeevil |
bshum: They're transparent and (hopefully) non-controversial -- they don't change behavior, and they existed and been tested for nigh on a year. how would you like those pushed to your attention |
| 11:48 |
berick |
bshum: thanks for pointing that out. i wonder if that explains why apache segfaults for me on jessie ;) |
| 11:49 |
bshum |
eeevil: gmcharlt: Since it has both your sign-offs on it and has passed a week in wait, I'm fine with seeing it pushed to master on your review. I can do it after I send this email, but feel free to proceed as you need if nobody else steps up. |
| 11:50 |
bshum |
It looks fine to me. |
| 11:50 |
eeevil |
bshum: super. I'll do so |
| 11:51 |
eeevil |
now, I pushed the nonce patch to 2.5 and 2.6 as well as master, on the theory that it's a bug to cause a sip lockout for legitimate high-rate connection attempts |
| 11:51 |
eeevil |
we don't /have/ to push these there as well, but I'll ask leave here to do so |
| 11:52 |
eeevil |
so that 2.5/2.6 can benefit from multiplex /if they so desire/ at some later date |
| 11:52 |
bshum |
As an unrelated question I've always had... will we ever start specifying versions of SIPServer and what compatibility they have with Evergreen? |
| 11:53 |
bshum |
As is, it's more of a "use master" sort of situation with SIPServer right now, right? |
| 11:53 |
gmcharlt |
right |
| 11:53 |
eeevil |
well, that' it ... there are no versions :) |
| 11:54 |
eeevil |
as a motivator for that, perhaps we should reach out to the kohaians (gmcharlt: got your other hat?; jcamins: SUP!) about the state of sipserver v. internal, and collaborate on a first real version that we can both use |
| 11:54 |
gmcharlt |
speaking of which, the other day I decided to collect LOTS of opnions: http://www.perlmonks.org/?node_id=1095504 |
| 11:55 |
eeevil |
(related, but no, I've no tuits, the same would be good for QueryParser) |
| 11:58 |
eeevil |
gmcharlt: sweet. yet, no real direction from the monks, yet :( |
| 11:59 |
bshum |
Interesting reading. |
| 11:59 |
gmcharlt |
I nearly LOLed at the flat assertion "The library community has been a habit of putting modules in Biblio rather than 'Library', to deal with the ambiguity of that term." |
| 12:01 |
bshum |
eeevil: Given the uncertainty of SIPServer's capabilities depending on when people install it and what's available, seems good to me to safeguard 2.5 and 2.6 as well from potential problems. |
| 12:01 |
bshum |
eeevil++ |
| 12:01 |
* eeevil |
pushes ALL THE THINGS |
| 12:02 |
eeevil |
wheeh, done |
| 12:04 |
pinesol_green |
[evergreen|Mike Rylander] LP#1339190: support disconnection for SIP multiplex purposes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=3ffe114> |
| 12:04 |
pinesol_green |
[evergreen|Mike Rylander] LP#1339190: Have Evergreen save authtoken state to support IO::Multiplex mode - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=3798b73> |
| 12:04 |
dbs |
gmcharlt: well hey, our primary library server hostname is "biblio" because it's also bilingual (french / english) |
| 12:05 |
gmcharlt |
dbs: it's not "biblio", it's the implication that using that namespace is a "habit" |
| 12:06 |
bshum |
Every time someone writes or says "biblio" I end up gravitating that way. Sigh. :) |
| 12:06 |
|
RoganH joined #evergreen |
| 12:06 |
dbs |
gmcharlt: no, I get that. librarians are creatures... creatures of habit. |
| 12:06 |
dbs |
like nuns. |
| 12:07 |
gmcharlt |
... that puts the librarian wardrobe tumblr in a new light... |
| 12:07 |
gmcharlt |
;) |
| 12:29 |
dbs |
bshum: So I guess I should really get on that RDA 264 branch you put together, eh? |
| 12:30 |
bshum |
dbs: Well I think that'd be nice, but there's always 2.8 :) |
| 12:30 |
dbs |
And on the user/group UI branch too. |
| 12:30 |
* dbs |
has a few hours tonight and will hopefully be able to pull some of that together |
| 12:30 |
bshum |
Were you talking about https://bugs.launchpad.net/evergreen/+bug/868653 ? |
| 12:30 |
pinesol_green |
Launchpad bug 868653 in Evergreen "secondary permission groups (permission.usr_grp_map)" (affected: 3, heat: 20) [Wishlist,Triaged] |
| 12:31 |
bshum |
I was just reading it again and thinking to myself that if the feature is ready but the release note is pending, we could still move it in and add a note next week. |
| 12:31 |
bshum |
But that gets into slippery slope |
| 12:31 |
dbs |
bshum: yeah, testing + release note |
| 12:31 |
dbs |
that's what I was thinking |
| 12:34 |
jeff |
dbs++ |
| 12:34 |
bshum |
dbs++ |
| 12:55 |
bshum |
Interesting |
| 12:55 |
bshum |
berick: I'm finally reading up close - https://bugs.launchpad.net/evergreen/+bug/1292705 |
| 12:55 |
pinesol_green |
Launchpad bug 1292705 in Evergreen "IDL2js delivers lots of unneeded information, adding bulk." (affected: 1, heat: 6) [Wishlist,New] |
| 12:56 |
bshum |
What I'm doing right now is reading through stuff in 2.next that's marked "wishlist" and have pullrequest on them to see if they can be moved into review. |
| 12:56 |
bshum |
All the stuff already marked for beta1 that aren't fix committed look ready to review. |
| 12:59 |
berick |
bshum: thanks. the IDL2js stuff would be nice to have. |
| 13:00 |
berick |
i think it mostly just needs a few UIs from each general type (xul, old-school html, etc.) tested to ensure no breakage |
| 13:01 |
bshum |
Okay, I'll do some poking on one of my test servers later today. |
| 13:01 |
berick |
bshum++ |
| 13:04 |
dbs |
None of the junk is translation junk is it? (#alwaysparanoid) |
| 13:05 |
* jeff |
reads the "dangers of streaming across versions of glibc" thread on pgsql-general -- I like a good "why is this corrupt?" hunt. http://www.postgresql.org/message-id/BA6132ED-1F6B-4A0B-AC22-81278F5AB81E@tripadvisor.com |
| 13:06 |
berick |
dbs: IDL2js changes? no i18n "junk" removed |
| 13:21 |
remingtron |
berick: sorry, getting nowhere on the report features branch. System issues. |
| 13:22 |
berick |
remingtron: no worries. kmlussier is testing as well. may have another fix or two to push. |
| 13:22 |
berick |
i suggest testing elsewhere when yr system comes back |
| 13:22 |
berick |
at least for now |
| 13:23 |
|
vlewis joined #evergreen |
| 13:24 |
remingtron |
berick: when my system comes back? I'm not quite understanding. |
| 13:25 |
berick |
remingtron: i'm just refering your "system issues" comment. whenever that's resolved |
| 13:25 |
berick |
or did I misunderstand "system issues"? |
| 13:25 |
remingtron |
maybe, let me try again |
| 13:26 |
|
jihpringle joined #evergreen |
| 13:26 |
remingtron |
berick: my system is having strange issues, which has delayed my progress testing your bug |
| 13:27 |
remingtron |
berick: my main point is, I'll keep trying, but wanted to let you know not to count on my input |
| 13:27 |
berick |
gotcha, thanks. |
| 13:28 |
berick |
jfyi, i just pushed one fix and will probably push another soon |
| 13:29 |
remingtron |
berick: cool, thanks for update |
| 13:29 |
|
hbrennan joined #evergreen |
| 13:37 |
berick |
eeevil: tucking the "use Socket::Linux" line into the eval... is the goal to avoid requiring the module? |
| 13:37 |
berick |
http://git.evergreen-ils.org/?p=working/SIPServer.git;a=commitdiff;h=a8ca2fac6469852a4205ece58e5c0d1371658cf6 |
| 13:38 |
berick |
if so, i can modify it to use $module->use(stuff) so the compiler won't complain |
| 13:38 |
berick |
(when the mod's not present) |
| 13:39 |
eeevil |
berick: it was, and sure, ->use works for me |
| 13:40 |
berick |
k, thanks |
| 13:40 |
eeevil |
I seem to recall seeing lots of "that's deprecated!" warnings from that, but I lurve ->use() |
| 13:41 |
berick |
that does sound familiar |
| 13:41 |
berick |
the same style is *cough* used elsewhere, though, w/ no sign of complaint that I see. |
| 13:41 |
berick |
maybe a different invocation |
| 13:42 |
pinesol_green |
[evergreen|Yamil Suarez] Docs: Improved AsciiDoc formating for tpac_meta_record_holds.txt - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=31dfcab> |
| 13:44 |
jeff |
jcamins: regarding xz and bzip2 from earlier: bzip2 -v9 compressed the file in 6m7.762s -- so, significant speed difference to save that additional space. |
| 13:45 |
jeff |
2.9G -> 700M in ~6 minutes or to 533M in ~1 hour. |
| 13:46 |
jeff |
of course, other things might have been happening at that time that might have skewed those numbers. not a scientific test, etc. |
| 13:47 |
* jeff |
times decompression |
| 13:49 |
jeff |
bzcat to /dev/null: 2m18.181s |
| 13:50 |
yboston |
Heads up, the DIG monthly meeting will start at 2 Pm EST |
| 13:52 |
|
RoganH joined #evergreen |
| 13:52 |
jcamins |
jeff: yeah, that matches my recollection. |
| 13:53 |
jeff |
xzcat to /dev/null: 0m57.659s |
| 13:53 |
jcamins |
Iiiiinteresting. |
| 13:53 |
jeff |
so, with xz your upfront costs are memory and time when compressing, and you save more space and save more time when decompressing. |
| 13:54 |
|
Christineb joined #evergreen |
| 13:55 |
jeff |
in my experience, xz does well with MARC (sample size of one) and things like mbox archives, while bzip2 still does better on things like syslog output. |
| 13:58 |
|
mtate joined #evergreen |
| 13:58 |
pinesol_green |
[evergreen|Kathy Lussier] OpenSRF Services Update - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=578c080> |
| 14:00 |
yboston |
#startmeeting 2014-08-07 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting |
| 14:00 |
pinesol_green |
Meeting started Thu Aug 7 14:00:33 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_08_07___dig_monthly_meeting_evergreen_documentation_interest_group__dig__monthly_meeting' |
| 14:00 |
yboston |
The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20140807-agenda |
| 14:01 |
yboston |
#topic Introductions |
| 14:01 |
yboston |
Please feel free to start introducing yourselves... |
| 14:01 |
yboston |
#info 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 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:02 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative |
| 14:02 |
RoganH |
#info RoganH = Rogan Hamby, SCLENDS |
| 14:02 |
yboston |
btw, a fewminutes ago I updated the meeting agenda and pasted last meeting's agenda items for us to quickly review during this meeting |
| 14:03 |
yboston |
at this link http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20140807-agenda |
| 14:03 |
yboston |
#link http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20140807-agenda |
| 14:03 |
Christineb |
#info Christineb is Christine Burns, BC Libraries Cooperative |
| 14:04 |
yboston |
My timer went off, so I wil start |
| 14:04 |
yboston |
#topic old business - last meeting's action items |
| 14:05 |
yboston |
#info yboston is Yamil Suarez @ Berklee college of Music - DIG meeting facilitator |
| 14:05 |
yboston |
action: yboston will update general DIG to do list page with the work doen for 2.6 |
| 14:05 |
yboston |
I did some opdating, but I need to add info on the ESI controbutions |
| 14:06 |
yboston |
(sorry for spelling) |
| 14:06 |
kmlussier |
yboston: We know what you're sayind. |
| 14:06 |
yboston |
any comments on this old action item? |
| 14:06 |
remingtron |
are the ESI contribs all in master? |
| 14:06 |
yboston |
I put htem all in master |
| 14:07 |
yboston |
tpp |
| 14:07 |
yboston |
too |
| 14:07 |
yboston |
I have not finished fixing the issues in Erica's docs |
| 14:07 |
yboston |
just fixed one so far, where she used a curly apostrophe |
| 14:07 |
yboston |
still trying to fix all the other hidden characters |
| 14:07 |
yboston |
for the record... |
| 14:08 |
yboston |
I pushed a bunch of ESI docs yesterday |
| 14:08 |
yboston |
remingtron today noticed that the docs did not get built last night |
| 14:08 |
yboston |
because the new docs had some issues |
| 14:09 |
remingtron |
let me know if you need any help fixing those. I am available tomorrow |
| 14:09 |
yboston |
I will work on fixing the issues with those docs, and the concern is that until they are fixed the master and 2.6 docs will not be created tonight either |
| 14:10 |
yboston |
makes me want to automatically cache the previous day's good docs for when this happens |
| 14:10 |
remingtron |
I think the previous day's good docs stay live |
| 14:11 |
remingtron |
I don't think it produces broken docs or anything like that |
| 14:11 |
yboston |
I think the PDF's might not get made |
| 14:11 |
remingtron |
it just quits and says "never mind, I'll try again tomorrow" |
| 14:11 |
remingtron |
right, I think nothing new gets made, but it doesn't break the live docs, I believe |
| 14:11 |
yboston |
the PDF link gives a 404 right now |
| 14:11 |
yboston |
for 2.6 |
| 14:11 |
remingtron |
oh, not good |
| 14:12 |
remingtron |
however, the pdf is not very usable these days, so it's not a high priority to me. anyone else use it? |
| 14:12 |
yboston |
I thought you knew :( |
| 14:12 |
yboston |
You can do full text searches quite nicely on PDFs |
| 14:12 |
yboston |
that is one reason I look at it |
| 14:12 |
kmlussier |
remingtron: I never use it, but I generally don't like PDF. |
| 14:13 |
kmlussier |
remingtron: Why do you say it isn't very usable. Is it something about the way we create our docs? |
| 14:13 |
yboston |
the epub file look fine, not sure if it is new or not |
| 14:14 |
remingtron |
kmlussier: the pdf is hundreds of pages long, often screenshots are too large for the page |
| 14:14 |
remingtron |
it isn't terrible, so maybe it's plenty usable |
| 14:14 |
kmlussier |
remingtron: Good to know. I'll have to look at it sometime. |
| 14:15 |
kmlussier |
I wonder if we could split the PDF into different sections. Make it a little more manageable. |
| 14:15 |
yboston |
should we table that discussion (PDFs) for later or should we continue on it now? |
| 14:16 |
kmlussier |
yboston: Table it for later |
| 14:16 |
remingtron |
yeah, let's table it |
| 14:16 |
remingtron |
good call |
| 14:16 |
yboston |
should I make it an action item or do either of you want to just get back to us on it? |
| 14:16 |
remingtron |
kmlussier: important to you? or should we forget it till it comes up again? |
| 14:17 |
yboston |
we can make a long term goals list somewhere on the wiki? |
| 14:17 |
remingtron |
yboston: good idea |
| 14:17 |
remingtron |
I'll make that wiki page! |
| 14:17 |
kmlussier |
Sounds like a good long term goal. |
| 14:17 |
remingtron |
because I love wikis! |
| 14:17 |
yboston |
I would tie the issue of screenshot size to the DIG style guide |
| 14:17 |
kmlussier |
remingtron++ #wiki love |
| 14:17 |
yboston |
work |
| 14:18 |
yboston |
so I can assign the craetion of a long term goal wiki page to remingtron? |
| 14:18 |
remingtron |
yes |
| 14:19 |
yboston |
#action remingtron will create a DIG long term goals wiki page and will include ideas for improving PDFs |
| 14:19 |
yboston |
last thing I will say on the earlier topic is that ... |
| 14:19 |
yboston |
also, remingtron, dbs and I talked today on IRC about making plans to have a seperate server to build docs earlier in the day to catch build errors |
| 14:20 |
yboston |
of course this is another good long/short term goal |
| 14:20 |
yboston |
will move to the rest of the old action items, if that is OK |
| 14:21 |
remingtron |
great, thanks for keeping us on track |
| 14:21 |
yboston |
action: remingtron will check in on Elliot to see if he needs help with documenting "User Editor: “Update Expire Date” button " |
| 14:22 |
remingtron |
yup, I ended up doing it, basically just new screenshots and a little note |
| 14:22 |
remingtron |
it's in 2.6 and master now |
| 14:22 |
kmlussier |
remingtron++ |
| 14:22 |
yboston |
remingtron++ |
| 14:22 |
yboston |
anything else to add? comments/questions from anybody else? |
| 14:23 |
yboston |
moving on |
| 14:23 |
yboston |
action: yboston will move EDI entry from 2.6 DIG new features and put it in a new 2.7 DIG new features page; also email Jenifer to warn her |
| 14:24 |
yboston |
mostly done, but I don't think the email said I was moving the content, which I did |
| 14:24 |
kmlussier |
jihpringle: Is it really a new feature for 2.7 or is it documenting something that's always been there? |
| 14:24 |
jihpringle |
when I looked at EG it turns out it was documenting something that had always been there |
| 14:25 |
jihpringle |
it's done, I just haven't submitted it yet |
| 14:25 |
kmlussier |
Ah, ok. Thanks for the clarification. |
| 14:25 |
yboston |
lets us know if you need any help |
| 14:26 |
remingtron |
jihpringle: whenever you want to share it, just send the files or links to the email list and we can coach or help you through the process |
| 14:26 |
yboston |
anything else to add? comments/questions from anybody else? |
| 14:26 |
jihpringle |
will do, thanks and apologizes for the delay |
| 14:26 |
yboston |
no problem at all |
| 14:26 |
remingtron |
jihpringle: no worries, thanks for your work! |
| 14:26 |
remingtron |
jihpringle++ |
| 14:26 |
kmlussier |
jihpringle++ |
| 14:26 |
yboston |
action: yboston will help kbutler with her 2.6 task "Add granular settings for requiring staff initials for notes. " |
| 14:27 |
yboston |
I worked on this, but we are not done. |
| 14:27 |
yboston |
Thankfully, Kate contacted us today before I could get her to give us an update |
| 14:27 |
yboston |
"I will not be able to make the DIG meeting today. So, my report is that I haven't made any appreciable progress on the new piece of documentation I was working on. Our summer reading programs end this week so things should finally calm down enough for me to get on to it." |
| 14:28 |
yboston |
I will follow up with in the next few weeks |
| 14:28 |
remingtron |
do you know what is missing? |
| 14:28 |
remingtron |
her branch seems to have the release notes part |
| 14:28 |
yboston |
I think there might be a need |
| 14:29 |
yboston |
for a section that talks about the basics of the patron "messages" UI, for her to add a small note |
| 14:29 |
remingtron |
ok |
| 14:29 |
yboston |
I started searching to see if any documentation existed by doing a raw grep, but I never finsihed analyzing my results |
| 14:30 |
remingtron |
FYI, the docs has a google search now, which does pretty well at searching all version of the docs |
| 14:30 |
yboston |
I looked at it briefly today, and noticed something promising |
| 14:30 |
yboston |
remingtron: I keep forgetting to sue that nice feature, and your recommendations means a lot |
| 14:30 |
yboston |
#action yboston will help kbutler with her 2.6 task "Add granular settings for requiring staff initials for notes. " |
| 14:31 |
yboston |
will move on... |
| 14:31 |
yboston |
action: remingtron will reach out to Bill about what we can start documenting of the new browser staff client; also will experiment with setting up a Git collab brnach to work on |
| 14:31 |
yboston |
(btw, we are at the 30 minute mark) |
| 14:32 |
remingtron |
http://markmail.org/thread/7qhj665rk5vaag65 |
| 14:32 |
remingtron |
that's my message to the DIG email list |
| 14:33 |
yboston |
this could be a great way for DIG newcomers to help out, or at least get some practive |
| 14:33 |
yboston |
since you can just use a web browser, and not need to install software |
| 14:33 |
remingtron |
I agree! I'm looking for a volunteer to poke around Bill's test version of the web client and try editing a current doc to reflect the new web interface. |
| 14:34 |
remingtron |
https://bill-dev2.esilibrary.com/eg/staff/login?route_to=%2Feg%2Fstaff%2Fcirc%2Fpatron%2Fsearch |
| 14:34 |
yboston |
do we want to email folks on the general list to get them interested in helping? |
| 14:34 |
remingtron |
sure, I can do that |
| 14:34 |
yboston |
are there any folks right now watching this meeting that would like to help out? |
| 14:35 |
yboston |
you can contact any of us off the IRC channel if you prefer |
| 14:36 |
yboston |
how is this? action: remingtron will ask for volunteers to help with docuemnting the new browser staff client on the general EG list |
| 14:36 |
remingtron |
perfect |
| 14:36 |
yboston |
#action remingtron will ask for volunteers to help with documenting the new browser staff client on the general EG list |
| 14:37 |
yboston |
anything else to add? comments/questions from anybody else? |
| 14:37 |
yboston |
action: yboston add item to August DIG meeting agenda about following up on ligering 2.6 new features work |
| 14:37 |
yboston |
we have mostly addressed this already, I think? |
| 14:38 |
yboston |
last one... |
| 14:38 |
yboston |
action: yboston start a thread on DIG mailing list on targeting small older docuemntation tasks for the month of July; like working on 1 to 3 features from the 2.5 list between now and the next meeting? |
| 14:38 |
yboston |
I never got a chance to do this one, will push to next meeting or further if we thinkwe will be too busy with EG 2.7 work |
| 14:38 |
yboston |
thoughts? |
| 14:39 |
remingtron |
hard to tell yet, since 2.7 beta is today, we don't have release notes yet |
| 14:39 |
remingtron |
I'd say push it to next meeting for now |
| 14:40 |
yboston |
that is what I needed, hard to facilate a meeting and use my brain at same time :) |
| 14:40 |
remingtron |
understandable! |
| 14:40 |
yboston |
#action yboston start a thread on DIG mailing list on targeting small older docuemntation tasks for the month of August; like working on 1 to 3 features from the 2.5 list between now and the next meeting? |
| 14:40 |
yboston |
on to new business |
| 14:41 |
yboston |
#topic DIG needs to start looking at 2.7 new features |
| 14:41 |
yboston |
S skipped to this one, becuase of what remingtron just mentioned |
| 14:42 |
kmlussier |
I went through LP bugs last week to remind devs to add release notes where they were missing. |
| 14:42 |
kmlussier |
I was planning tomorrow to set up a wiki page similar to the ones from past releases to identify new features that need documentation. |
| 14:42 |
yboston |
so far I have been able to create release notes for two features that two developers worked on. was nice to work witht he devs |
| 14:43 |
yboston |
and getting so much better at git int he process |
| 14:43 |
remingtron |
yboston++ #working with devs |
| 14:43 |
remingtron |
kmlussier++ #making the feature list |
| 14:43 |
kmlussier |
IIRC, our goal this time is to try to get the docs done by the full release. Is that right? |
| 14:43 |
yboston |
kmlussier++ |
| 14:44 |
remingtron |
kmlussier: yes, if we can! |
| 14:44 |
remingtron |
and getting closer to our goal each release |
| 14:44 |
kmlussier |
Looking at the dev calendar, that's September 18. |
| 14:44 |
yboston |
kmlussier: that is what I understood, and we got somewhat close to 100% with 2.6 |
| 14:44 |
remingtron |
sooo....do we need a DIG hack-a-way before then? |
| 14:44 |
kmlussier |
remingtron: Might not be a bad idea. |
| 14:45 |
yboston |
I am open to it |
| 14:45 |
remingtron |
otherwise, I suggest more frequent DIG meetings |
| 14:45 |
kmlussier |
remingtron: Would those be working DIG meetings? |
| 14:45 |
remingtron |
(could be shorter, just progress updates and encouragement) |
| 14:45 |
kmlussier |
Ah, I see. That could work too. But I think the benefit of a DIG hack-a-way is that you set aside the time to work on docs. |
| 14:45 |
yboston |
should it be after the bug day (forgot name)? |
| 14:46 |
yboston |
bug squashing day? |
| 14:46 |
jihpringle |
I think so, some of those bugs may end up in 2.7 |
| 14:46 |
remingtron |
well, bugs won't usually affect the docs |
| 14:46 |
yboston |
let me clarify |
| 14:47 |
yboston |
some new fixes / fetures might not make it in until bug squashing day |
| 14:47 |
kmlussier |
For scheduling purposes, I think it would be easier to do it after Bug Squashing Day. Probably early September? |
| 14:47 |
yboston |
because the features needed testers |
| 14:47 |
kmlussier |
New features can't go into the release after today. |
| 14:48 |
yboston |
my bad, then just bug fixes |
| 14:48 |
yboston |
hard to keep this in my head in the heat of the moment |
| 14:49 |
yboston |
note the dev hack-a-way is the week of 22nd in September |
| 14:50 |
yboston |
to recap: we are debating when to have the DIG hack-way, timed to help us finish EG 2.7 |
| 14:50 |
|
tsbere joined #evergreen |
| 14:50 |
yboston |
and after today there is a freeze on new features making it into 2.7 |
| 14:51 |
kmlussier |
OK, so it looks like we need 2 action items here? One for me to identify 2.7 doc needs and another for someone to do a Doodle poll for a DIG hack-a-way? |
| 14:51 |
yboston |
my brain was slowly moving to that conclusion |
| 14:52 |
remingtron |
are any of you going to the developer hack-a-way? |
| 14:52 |
yboston |
I am |
| 14:52 |
remingtron |
I don't think I can make it |
| 14:52 |
remingtron |
wondered if it's a good or bad idea to have DIG hackaway the same day |
| 14:52 |
yboston |
how are these... action: kmlussier(and others) identify 2.7 doc needs and add to the 2.7 wiki page |
| 14:53 |
bshum |
Fwiw, this year, I voted towards making the Hack-A-Way after the expected release date for 2.7.0 so that we would avoid having developer interests affect 2.7's final outcome. |
| 14:53 |
bshum |
If you want docs ready for 2.7, then doing it earlier, like late August / early September seems like a better date range to me. |
| 14:53 |
remingtron |
+1 |
| 14:53 |
bshum |
Late August will give more time to stablize everything in 2.7 and get more test servers going for doc purposes too, I would assume. |
| 14:53 |
RoganH |
fwiw, as well, that was part of my goal for the scheduling the hack-a-way as well based on discussion at the conference |
| 14:54 |
|
Shae_ joined #evergreen |
| 14:54 |
kmlussier |
Sorry, it looks like I dropped out for a second. I prefer to keep dev and doc hack-a-ways separate. |
| 14:54 |
yboston |
#action kmlussier(and others) identify 2.7 doc needs and add to the 2.7 wiki page |
| 14:55 |
yboston |
I need to work on more dev work, and I can't help run DIG things at the same time |
| 14:55 |
yboston |
though I will gladly help with docs during the dev hack-a-way |
| 14:56 |
yboston |
who would liek to set up a poll and email the DIG list about scheduling the DIG dev hack-a-way? |
| 14:57 |
yboston |
and thanks to bshum and RoganH for their feednack |
| 14:57 |
yboston |
*feedback |
| 14:57 |
yboston |
(I am glad most of you have gotten emails from me and heard me speak when I am not in a hurry) |
| 14:57 |
kmlussier |
LOL. It's part of the medium. |
| 14:58 |
jihpringle |
I can set up the poll and email the list - are we agreed on sometime in first two weeks of September? |
| 14:59 |
yboston |
we might be able to use the thrid week of September too? |
| 15:00 |
yboston |
at least the early part of that third week if need be |
| 15:01 |
jihpringle |
k, I'll put out dates between Sept 3rd and Sept 17th |
| 15:01 |
yboston |
jihpringle: I can provide dates that I can host folks in our confrence room |
| 15:01 |
yboston |
though I expect most will work remotely |
| 15:01 |
jihpringle |
that's great |
| 15:01 |
kmlussier |
yboston: If there are dates that won't work for your conference room, I could probably find anyother place in MA that could host. |
| 15:02 |
yboston |
#action jihpringle will set up a doodle poll and email the DIG list to coordinate a DIG hack-a-way tageting EG 2.7 feaures before its officail release |
| 15:03 |
yboston |
#action yboston , kmlussier and others will send dates when they can host folks for the DIG hack-a-way |
| 15:03 |
jihpringle |
are libraries closed in the US on Patriot Day? (looking at the holidays on my calendar) |
| 15:03 |
yboston |
BTW, we are right past the one hour mark |
| 15:03 |
remingtron |
sorry, had a phone call, I'm back now |
| 15:03 |
kmlussier |
jihpringle: We're closed on Labor Day. First Monday of the month. |
| 15:03 |
* kmlussier |
doesn't know if it's the same day. |
| 15:03 |
jihpringle |
but not third Monday of Sept |
| 15:04 |
kmlussier |
No, the third Monday of the month isn't a holiday here. |
| 15:04 |
yboston |
For the record, Patriot Day (Sept 11) not to be confused witht the local New England holiday of "PatriotS Day," the day in April the run the Boston Marathon |
| 15:05 |
jihpringle |
thanks, Patriot's Day is what come up with I googled |
| 15:05 |
jihpringle |
just didn't want to offer a day most people woulnd't be available on |
| 15:05 |
yboston |
did we want to start wrapping up the meeting? any final comments or questions? |
| 15:06 |
remingtron |
jihpringle++ #making the poll |
| 15:06 |
yboston |
jihpringle+ |
| 15:06 |
yboston |
jihpringle++ |
| 15:06 |
yboston |
also |
| 15:06 |
yboston |
remingtron++ |
| 15:07 |
remingtron |
plus's all around! |
| 15:07 |
remingtron |
I forgot, we need cake to celebrate getting 2.6 documented! |
| 15:07 |
remingtron |
@dessert |
| 15:07 |
* pinesol_green |
grabs some Banana Puddin' for remingtron |
| 15:07 |
yboston |
since meeting remingtron at last year's dev hack-a-way, DIG has made a lot of progress |
| 15:07 |
remingtron |
since meeting yboston last year, life has been awesomer |
| 15:08 |
yboston |
thanks, too bad you can't make it this year, but we can figure out a way so that we can still collaborate |
| 15:08 |
* remingtron |
shares Banana Puddin' with everyone |
| 15:08 |
yboston |
besides high fives, any last thoughts? |
| 15:09 |
remingtron |
everybody watch the email list |
| 15:09 |
yboston |
OK ending the meeting |
| 15:09 |
remingtron |
and we'll get rolling on 2.7 |
| 15:09 |
remingtron |
yboston++ |
| 15:10 |
|
mllewellyn joined #evergreen |
| 15:10 |
yboston |
#endmeeting |
| 15:10 |
pinesol_green |
Meeting ended Thu Aug 7 15:10:07 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/evergreen/2014/evergreen.2014-08-07-14.00.html |
| 15:10 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-08-07-14.00.txt |
| 15:10 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-08-07-14.00.log.html |
| 15:10 |
yboston |
jihpringle: thanks for your help witht he poll, and I am exited that we are in essence following your idea to have a topic oriented DIG hack-a-way |
| 15:11 |
bshum |
jihpringle++ |
| 15:11 |
bshum |
yboston++ |
| 15:11 |
bshum |
remingtron++ |
| 15:11 |
jeff |
@quote search parties |
| 15:11 |
pinesol_green |
jeff: 1 found: #46: "<_bott_> I am not a cataloger, but I speak..." |
| 15:11 |
jeff |
@quote get 46 |
| 15:11 |
pinesol_green |
jeff: Quote #46: "<_bott_> I am not a cataloger, but I speak enough MARC to be fun at parties" (added by gmcharlt at 11:43 AM, March 15, 2013) |
| 15:12 |
|
Christineb left #evergreen |
| 15:15 |
jihpringle |
yboston: glad to help :) |
| 15:36 |
_bott_ |
I often wonder how IRC history will portray that comment... |
| 15:39 |
yboston |
remingtron, kmlussier: Heads up, I might be traveling out of state in the first week of September and might not be able to host a DIG hack-a-way or facilitate the September DIG meeting (if we have one) |
| 15:39 |
remingtron |
yboston: thanks for the warning |
| 15:43 |
kmlussier |
berick: Is the latest reports code in your working branch? |
| 15:44 |
berick |
kmlussier: in the combined branch, yes |
| 15:44 |
berick |
user/berick/lp1332138-lp1329503-reports-combined |
| 15:46 |
remingtron |
berick: not sure if you spotted this bug yet |
| 15:46 |
remingtron |
Reload the page, edit any report, both "Run as soon as possible" and time selector checkboxes are checked |
| 15:46 |
remingtron |
after some usage, that problem goes away, but seems try on a fresh reload of that screen |
| 15:46 |
remingtron |
seems *true* |
| 15:47 |
remingtron |
that's all I've done for testing, now have to leave early. sorry can't sign off today. |
| 15:47 |
berick |
remingtron: hm, thanks, i'll look at that |
| 15:48 |
* remingtron |
heads out |
| 15:49 |
kmlussier |
berick: Yeah, I can confirm that behavior too. |
| 15:49 |
berick |
thanks kmlussier |
| 15:52 |
* kmlussier |
runs out for a conference call. |
| 16:25 |
yboston |
quick question, I am trying to fix some docs that are causing an error when creating the EG docs. |
| 16:26 |
yboston |
The scripts say something to the effect of "bad first character in" and when seen in the Git web front end I see "\feff" as the first character |
| 16:26 |
yboston |
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=blob;f=docs/admin/MARC_RAD_MVF_CRA.txt;h=f0a678255c8ed04dabf5d6d3bbfeb886b9764d17;hb=bd48faa094db48331ab46c9d1454f966184dc7c8 |
| 16:26 |
yboston |
I know "\feff" it is related to UTF-8 encoding, but still figuring out how to remove it or make the error go away |
| 16:34 |
bshum |
Hmm |
| 16:34 |
bshum |
Well, using nano as my editor on my laptop, I was able to remove the leading character I think. |
| 16:34 |
bshum |
I imagine you could do that on a macbook |
| 16:34 |
yboston |
remingtron: if you are around, what asciidoc command di dyou use to get those error messages about the "bad first character"? |
| 16:36 |
yboston |
bshum: nano might have worked for me too |
| 16:36 |
yboston |
vim and textmate/bbedit (on OS x) did not allow me to erase the leading char |
| 16:38 |
RoganH |
yboston: I use nano as my text editor on my mac, it's fairly straight forward to install |
| 16:39 |
RoganH |
yboston++ as well for using bbedit, my favorite gui editor on the mac |
| 16:39 |
yboston |
did not realize there was a gui for mac, I use nano on the os x command line on occasion |
| 16:39 |
RoganH |
yboston: I was referring to command line, I think I misunderstood what you said. |
| 16:40 |
yboston |
looks like nano is not very utf-8 aware so it left the space blank. VIM and others hide the special chars |
| 16:40 |
yboston |
apparebtly |
| 16:40 |
yboston |
*apparently |
| 16:54 |
kmlussier |
I can't recall how I've used those characters in the past. I use Notepad++ (when I'm not using VIM) and had to enable a setting to not add those character. I can't remember if I was able to delete them there. |
| 17:00 |
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 |
|
kmlussier left #evergreen |
| 17:03 |
bshum |
So as far as 2.7 beta freeze goes, I think anything that is signed off tonight will get committed later this evening or tomorrow morning. |
| 17:03 |
bshum |
I'll give at least till midnight for our west coast friends. ;) |
| 17:07 |
|
mdriscoll left #evergreen |
| 17:07 |
bshum |
Calling 0888 and 0889 for LP 1270289 |
| 17:07 |
pinesol_green |
Launchpad bug 1270289 in Evergreen "Backordered items have line item status of cancelled" (affected: 9, heat: 44) [Undecided,Confirmed] https://launchpad.net/bugs/1270289 |
| 17:11 |
jeff |
Good news, everyone! Freenode got back to me about my request for an increase in the number of allowed connections to Freenode from the conference hotel wifi! |
| 17:12 |
jeff |
You know, the conference that ended a few months ago? |
| 17:12 |
bshum |
Haha |
| 17:12 |
bshum |
:D |
| 17:12 |
jeff |
reply starts out ``Due to time constraints within freenode staff it seems that there are many idle requests for increased connection limits.'' |
| 17:13 |
pinesol_green |
Showing latest 5 of 11 commits to Evergreen... |
| 17:13 |
pinesol_green |
[evergreen|Bill Erickson] LP#1270289 Release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e9199f2> |
| 17:13 |
pinesol_green |
[evergreen|Bill Erickson] LP#1270289 sort ACQ cancel reason selectors - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6861a31> |
| 17:13 |
pinesol_green |
[evergreen|Bill Erickson] LP#1270289 support canceling delayed copies - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=df206ed> |
| 17:13 |
pinesol_green |
[evergreen|Bill Erickson] LP#1270289 remove redundant lineitem cancel display - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=2e7dd0e> |
| 17:13 |
pinesol_green |
[evergreen|Ben Shum] LP#1270289 - stamping upgrade scripts for acq cancel display - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9496603> |
| 17:13 |
jeff |
explains that they're closing all but the most recent, with the understanding that in most cases events are over, things didn't need tweaking, or things were handled outside of the ticket system. |
| 17:13 |
jeff |
closes with " If you still need special configuration then please reply to this email saying so and the ticket will automatically reopened. If you could form an orderly queue sorted by urgency it would be appreciated." |
| 17:14 |
|
mmorgan left #evergreen |
| 17:15 |
bshum |
dbs: If you have time tonight while you're playing with 264, yboston added six more RDA bibs to his branch on LP 1308768 |
| 17:15 |
pinesol_green |
Launchpad bug 1308768 in Evergreen "add sample RDA records to test data set" (affected: 1, heat: 6) [Wishlist,Confirmed] https://launchpad.net/bugs/1308768 |
| 17:16 |
bshum |
You did some magic on his first offering but my regular expression fu is weak :( |
| 17:16 |
bshum |
If you can convert those over and add them to also be loadable, I think it'd be great to push that all up to master so that the test dataset has good 264 sample data. |
| 17:18 |
bshum |
Oh you know, I just realized he has them as marcxml too |
| 17:18 |
* bshum |
will play with it if he gets more time later. |
| 17:18 |
bshum |
yboston++ |
| 17:20 |
bshum |
dbs: Actually looking at your marcxml I'm not sure the < and > are all in the right places. |
| 17:22 |
bshum |
<record>leader> ... etc. I think it's missing the leading < for much of the tagging. |
| 17:38 |
dbs |
bshum: my marcxml? |
| 17:39 |
dbs |
oh, http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=42578aef2117e917cccc67432cde855cc915c97e |
| 17:39 |
dbs |
yeah, that looks broken. |
| 17:41 |
pinesol_green |
[evergreen|Mike Rylander] LP#1351355: Switch to XLSX format for Excel report output - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e19d29a> |
| 17:41 |
pinesol_green |
[evergreen|Ben Shum] LP#1351355: Use libexcel-writer-xlsx-perl package for Ubuntu Trusty - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=af29ca4> |
| 17:41 |
pinesol_green |
[evergreen|Ben Shum] LP#1351355: Add release note on change to XLSX format for Excel report output - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=50c39d8> |
| 17:43 |
yboston |
bshum: I am about to push a single docs fix commit, I know git can handle it, but I wanted to give you a heads up |
| 17:43 |
bshum |
yboston: I would do a quick rebase before you push since master has just drifted a bit |
| 17:44 |
yboston |
technically, I am cherry picking a commit into master and 2.6 |
| 17:44 |
bshum |
Ah okay then |
| 17:44 |
bshum |
Go right ahead |
| 17:44 |
bshum |
I'll hold off pushing anything else for a moment :) |
| 17:46 |
yboston |
done |
| 17:46 |
yboston |
on master |
| 17:46 |
yboston |
will be cherry picking into 2.6, which should not matter to you right now(?) |
| 17:47 |
bshum |
Correct, thanks yboston |
| 17:48 |
yboston |
I am finally getting this stuff :) |
| 17:49 |
yboston |
my deadlien is to see if the PDF for 2.6 get built tonight, ebcuase it was not last night because of errors I hoped I fixed |
| 17:49 |
pinesol_green |
[evergreen|Yamil Suarez] Docs: various AsciiDoc formatting fixes for docs - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=07e00d0> |
| 18:15 |
bshum |
dbs++ |
| 18:35 |
bshum |
tsbere: Tested https://bugs.launchpad.net/evergreen/+bug/1347805 using some of the sample contentcafe codes we talked about and I got errors trying to save stuff to memcache. |
| 18:35 |
pinesol_green |
Launchpad bug 1347805 in Evergreen "Content Cafe module should use an XML lookup method" (affected: 2, heat: 10) [Wishlist,Confirmed] |
| 18:35 |
bshum |
Could not store in memcache server repeated a bunch of times |
| 18:35 |
bshum |
And then the facets didn't show up, etc. |
| 18:36 |
bshum |
Marking as incomplete pending further tests |
| 18:43 |
pinesol_green |
[evergreen|Bill Erickson] LP#1351317 ACQ fund selector filters cont. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=71241c7> |
| 18:43 |
pinesol_green |
[evergreen|Thomas Berezansky] LP#1246745: Remove OK message from SIP2 messages - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=916c095> |
| 18:43 |
pinesol_green |
[evergreen|Thomas Berezansky] LP#1347793: Teach TPac to load AC by Bib ID - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=331983c> |
| 18:43 |
pinesol_green |
[evergreen|Thomas Berezansky] LP#1347793: TPAC added content by ID release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=5f0433a> |
| 18:43 |
pinesol_green |
[evergreen|Bill Erickson] LP#1292705 trim unneeded fields from IDL2js - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4f1074a> |
| 18:45 |
dbs |
bshum: per https://bugs.launchpad.net/evergreen/+bug/1304462/comments/24 RDA264 stuff just needs one signoff (on my fixed-up commit for the RDA record load) |
| 18:45 |
pinesol_green |
Launchpad bug 1304462 in Evergreen "Add 264 tag values to Record Summary" (affected: 3, heat: 20) [Wishlist,Confirmed] |
| 18:45 |
bshum |
dbs: Excellent! I'll try that out right after dinner. |
| 18:45 |
* dbs |
needs to scoot, might not be able to test the user group editor UI sadly |
| 18:46 |
dbs |
"arias for bass" is a good record to test with. Also a good argument for making the "added contributor entries" only show the first 3 or so with a little CSS "click to show 'em all" thingy |
| 18:46 |
bshum |
Cool, I'll look at that one. |
| 18:46 |
bshum |
Thanks dbs! Appreciate your looking at it. |
| 18:47 |
dbs |
I appreciate your many contributions to the branch and to the 2.7 release! |
| 19:48 |
|
kmlussier joined #evergreen |
| 20:09 |
bshum |
yboston++ dbs++ # pushing 264 stuff to master |
| 20:12 |
pinesol_green |
Showing latest 5 of 8 commits to Evergreen... |
| 20:12 |
pinesol_green |
[evergreen|Jason Stephenson] LP#1304462: Add additional RDA information to TTOPAC record summary. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9d2b231> |
| 20:12 |
pinesol_green |
[evergreen|Dan Scott] LP#1304462: Add schema.org copyrightYear, manufacturer for RDA 264 fields - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=fc4619d> |
| 20:12 |
pinesol_green |
[evergreen|Ben Shum] LP#1304462: Stop using combined pubinfo for search results - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=76bd5e3> |
| 20:12 |
pinesol_green |
[evergreen|Ben Shum] LP#1304462: Use other 264 types in search results if publisher is not available - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=771cf4c> |
| 20:12 |
pinesol_green |
[evergreen|Yamil Suarez] LP#1304462: Release notes about expanded RDA tag 264 support - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d83387f> |
| 20:15 |
kmlussier |
dbs++ |
| 20:35 |
bshum |
kmlussier++ berick++ # I'll push on the reports stuff |
| 20:36 |
berick |
bshum: i have one last patch, if you haven't pushed yet.. |
| 20:37 |
bshum |
I have not |
| 20:37 |
berick |
to handle at least some (maybe all) of the run-time issues |
| 20:37 |
* berick |
goes to push |
| 20:37 |
eeevil |
it was oddly fun to dig back into the reports code... |
| 20:37 |
bshum |
If you'd like to push it up, that'd be fine too. You hae kmlussier's signoff |
| 20:38 |
berick |
bshum: no, this is brand new |
| 20:38 |
berick |
no sign off |
| 20:38 |
bshum |
I was about to go test the TPAC view/edit copy links stuff |
| 20:38 |
bshum |
Ah, alright, let me know when to grab and where |
| 20:44 |
* bshum |
twiddles his thumbs waiting for staff clients to build. |
| 20:44 |
berick |
bshum: pushed to the tip of user/berick/lp1332138-lp1329503-reports-combined |
| 20:45 |
bshum |
berick: Cool, I'll grab that too when I put together the next test server build. |
| 20:45 |
berick |
bshum:++ |
| 20:45 |
berick |
er, bshum++ |
| 20:45 |
bshum |
berick++ |
| 20:46 |
berick |
eeevil: agreed re: reports. it was oddly fun. i forgot how much was going on in there. |
| 20:46 |
eeevil |
there's a bit in there |
| 21:50 |
* jeff |
gets home and looks in |
| 21:50 |
jeff |
good evening. |
| 21:50 |
bshum |
About to push a bunch more things through |
| 21:50 |
bshum |
My internet is slowly dying it seems |
| 21:50 |
bshum |
But my test server lives! |
| 21:51 |
* bshum |
waves at jeff |
| 21:54 |
pinesol_green |
Showing latest 5 of 16 commits to Evergreen... |
| 21:54 |
pinesol_green |
[evergreen|Bill Erickson] LP#1329503 report editing additional repairs - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8ad52e5> |
| 21:54 |
pinesol_green |
[evergreen|Bill Erickson] LP#1329503 propagate 'in list' values for editing - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=2f2859c> |
| 21:54 |
pinesol_green |
[evergreen|Bill Erickson] LP#1329503 avoid run now + later combined schedule - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=de72876> |
| 21:54 |
pinesol_green |
[evergreen|Thomas Berezansky] Update ContentCafe Added Content Module - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=164c7e7> |
| 21:54 |
pinesol_green |
[evergreen|James Fournie] Add multiple permission groups editor to user registration form - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ef04f72> |
| 21:58 |
pinesol_green |
[evergreen|Jennifer Pringle] Secondary Permissions Documentation and Screenshots. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=b3f203b> |
| 21:59 |
jeff |
bshum: have you given much thought to bug 1347774 and its scope for 2.7? do you feel that it's already beyond 2.7? |
| 21:59 |
pinesol_green |
Launchpad bug 1347774 in Evergreen "Backend logic has leaked into the TPAC (and friends)" (affected: 2, heat: 12) [Wishlist,New] https://launchpad.net/bugs/1347774 |
| 21:59 |
jeff |
it was one of the first uncommitted things in the targeted-for-2.7-beta1 that caught my eye just now |
| 22:00 |
bshum |
jeff: I thought about it a little, but I haven't had a chance to actually look over the code yet. |
| 22:00 |
jeff |
grr. launchpad, stop timing out. :P |
| 22:04 |
bshum |
jeff: Since the bug hadn't been tagged with pullrequest yet, I guess I was focused on other LP ones that were tagged as done. |
| 22:04 |
bshum |
I wasn't sure if there was still ongoing work / discussions |
| 22:04 |
bshum |
It sounded like it was still work in progress |
| 22:06 |
jeff |
yeah. it's not pullrequest-ready, and it's pretty far-reaching. i am a big fan of the concepts it embodies, but it might be post-2.7. |
| 22:08 |
bshum |
Could make a good early candidate for 2.8 cycle |
| 22:08 |
bshum |
Something to work on during the hackaway |
| 22:31 |
* dbs |
starts to dig into user/group ui |
| 22:31 |
bshum |
dbs: I pushed it by accident, sort of |
| 22:31 |
bshum |
dbs: It got stuck at the tail end of a big branch I was testing on a test server |
| 22:32 |
bshum |
But I didn't realize that there may have been an issue with it. |
| 22:32 |
bshum |
I'm getting an error when trying to access the patron editor |
| 22:32 |
bshum |
TypeError: patron.isnew is not a function |
| 22:32 |
bshum |
Comes up different places |
| 22:32 |
bshum |
But basically it stalls out the editor |
| 22:32 |
bshum |
I was about to try undoing or fixing it |
| 22:32 |
bshum |
But my internet is being uncooperative with me. |
| 22:33 |
* dbs |
will dig |
| 22:37 |
dbs |
huh. lots of uses of patron.isnew() before jeffdavis' last commit |
| 22:37 |
bshum |
Yeah it's not related |
| 22:37 |
bshum |
Might be something else |
| 22:37 |
bshum |
I'm trying to see where it leads back to |
| 22:37 |
bshum |
Maybe it's the IDL2JS change? |
| 22:37 |
dbs |
maybe. hmm |
| 22:38 |
dbs |
2.7 requires updated opensrf as well now, right? |
| 22:38 |
bshum |
Err, I don't know |
| 22:38 |
bshum |
I've been using master OpenSRF for awhile. |
| 22:38 |
dbs |
or is that only for the backend logic leaking? |
| 22:38 |
bshum |
Nothing has changed in OpenSRF for awhile. |
| 22:38 |
bshum |
3 months or so |
| 22:39 |
dbs |
Yeah, I'm running latest master. No issue there. And websockets stuff hasn't been committed yet |
| 22:39 |
bshum |
No, that was delayed |
| 22:39 |
* dbs |
goes back to focusing on Dojo 1.3 |
| 22:40 |
jeff |
if you're getting patron.isnew() failures, you probably don't have a valid patron object. |
| 22:41 |
* bshum |
supposes the quick way to know for sure it was the secondary perm group is to revert it and go back a step on his test server. |
| 22:41 |
* dbs |
still needs to get his test server running latest EG master to reproduce said error... working on it |
| 22:44 |
dbs |
bshum: did you run the ever-popular autogen? :) |
| 22:45 |
bshum |
dbs: Yes I did. |
| 22:46 |
bshum |
But I'll try it again right after I open up my client to test reverting it |
| 22:47 |
bshum |
If my internet cooperates... |
| 22:47 |
bshum |
Hmm, interesting |
| 22:48 |
bshum |
revert did nothing |
| 22:49 |
bshum |
I think it was the IDL2JS thing now. |
| 22:49 |
* bshum |
pokes at that next. |
| 22:55 |
bshum |
Yep |
| 22:55 |
bshum |
reverting the IDL2JS changes fixes it |
| 22:55 |
dbs |
bshum: yeah, I suspect so too. Because that patron.isnew(1) line immediately follows "patron = new au();" |
| 22:55 |
dbs |
aha |
| 22:56 |
bshum |
http://git.evergreen-ils.org/?p=Evergreen.git;a=blobdiff;f=Open-ILS/xsl/fm_IDL2js.xsl;h=ecc374fad54c1dcd0d0884cde1068d88af143e53;hp=1a857bf1bae13246710a78e88fb39593aec51f19;hb=4f1074aec9e57b0df2cfd6b371e2517929cda090;hpb=5f0433a9c68164377c262f65ed67a7a538b28585 |
| 22:56 |
pinesol_green |
[evergreen|Bill Erickson] LP#1292705 trim unneeded fields from IDL2js - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4f1074a> |
| 22:56 |
pinesol_green |
[evergreen|Thomas Berezansky] LP#1347793: TPAC added content by ID release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=5f0433a> |
| 22:56 |
bshum |
I saw that "isnew" is there |
| 22:56 |
bshum |
As one of the fields that's been poked a bit. |
| 22:56 |
bshum |
Maybe we need some of those fields more than we thought. |
| 22:58 |
bshum |
Well, secondary groups seems to work okay |
| 22:58 |
bshum |
:D |
| 22:58 |
dbs |
wild and crazy thought was that maybe "patron = new au();" now needs to be "patron = new fieldmapper.au();" |
| 22:58 |
bshum |
Hmm |
| 22:58 |
* dbs |
goes to test |
| 22:59 |
dbs |
nope, patron.isnew(1) still fails. |
| 23:02 |
dbs |
wow I hate the million-character-long lines in fm_IDL2js.xsl, they make it really hard to see the changes in the diff :( |
| 23:02 |
bshum |
They are a bit rough. |
| 23:15 |
dbs |
oh hey, p no longer gets incremented. |
| 23:17 |
dbs |
BINGO. |
| 23:18 |
bshum |
dbs++ # troubleshooting |
| 23:23 |
dbs |
tacked a branch onto https://bugs.launchpad.net/evergreen/+bug/1292705/comments/4 |
| 23:23 |
pinesol_green |
Launchpad bug 1292705 in Evergreen "IDL2js delivers lots of unneeded information, adding bulk." (affected: 1, heat: 6) [Wishlist,Fix committed] |
| 23:27 |
dbs |
jeffdavis++ # Nice, simple UI. Sweet. |
| 23:27 |
* bshum |
tests |
| 23:28 |
bshum |
It lives! |
| 23:28 |
dbs |
And I got to add a set of braces to a for loop, which always makes me happy :) |
| 23:29 |
dbs |
No more evergreen hacking for me tonight. bshum++ |
| 23:29 |
bshum |
I think this is a good place to rest. |
| 23:29 |
bshum |
dbs++ # thanks for swooping in to save the day |
| 23:30 |
bshum |
I'll push this fix and then call it myself. |
| 23:34 |
pinesol_green |
[evergreen|Dan Scott] LP#1292705 Fix broken is*() methods in fm_IDL2js.xsl - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9986607> |
