| Time |
Nick |
Message |
| 02:17 |
|
DPearl joined #evergreen |
| 04:53 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 07:59 |
|
collum joined #evergreen |
| 08:06 |
|
julialima_ joined #evergreen |
| 08:27 |
|
mrpeters joined #evergreen |
| 08:38 |
|
ericar joined #evergreen |
| 08:54 |
|
Shae joined #evergreen |
| 09:00 |
kmlussier |
Good morning #evergreen |
| 09:01 |
maryj |
Good morning, kmlussier! |
| 09:01 |
julialima_ |
Good morning, kmlussier! |
| 09:34 |
|
mllewellyn joined #evergreen |
| 09:38 |
eeevil |
kmlussier: every time you say that I hear you yelling into an old-school mic, a la Robin Williams in Good Morning Vietnam :) |
| 09:38 |
|
yboston joined #evergreen |
| 09:38 |
kmlussier |
eeevil: Good! That's what I want you to hear. :) |
| 09:39 |
kmlussier |
Good mooooorning #evergreen! |
| 09:39 |
maryj |
I didn't have that image before of kmlussier, but I do now! :D |
| 09:39 |
eeevil |
kmlussier++ |
| 09:39 |
maryj |
kmlussier++ |
| 09:40 |
jeff |
we now need to give kmlussier a mic and some amplification at a morning coffee at the next conference. |
| 09:40 |
eeevil |
jeff: I'll inform Buzzy ;) |
| 09:40 |
jeff |
or just arrange for the hotel to customize their stock wakeup call audio. |
| 09:40 |
* kmlussier |
prefers to be loud in IRC |
| 09:41 |
jeff |
that would be an interesting service for a hotel to offer its conference clients... custom wakeup calls that include summary of the day's events or something... |
| 09:41 |
jeff |
</tangent> |
| 09:51 |
mrpeters |
I'm building a report to show all of the monetary transactions for a given staff username on a given day. I've got it working great with Cash Transactions, and am prepared to add Check Transactions next. My concern is ending up with empty rows where the username/workstation/etc. may match, but not the payment type. Will nullability allow me to use all of the views (cash, check, credit, etc.) in the "Payments" reporter source and prevent empty rows |
| 09:52 |
tsbere |
jeff: I know of at least one conference where the conference group offered their own wakeup calls, though those generally went to cell phones instead of to the room phones. |
| 09:54 |
mrpeters |
hey can we have the next Evergreen conference in Cuba!? I hear we can do that now :P |
| 09:54 |
mrpeters |
I could use a few cigars! |
| 09:54 |
tsbere |
mrpeters: I am not as well versed in some of that, but I do know that not all transactions are guaranteed to have a staff user and workstation. Credit card via OPAC won't have a workstation, nor will SIP2 payments, and I don't know what username is used for recording the latter. |
| 09:55 |
mrpeters |
tsbere: actually, that is ok in this case |
| 09:55 |
mrpeters |
we're only concerned about payments that happen with a staff member involved |
| 09:55 |
mrpeters |
its for auditing cash drawer. each staff member has their own and nobody else ever uses it. |
| 09:56 |
mrpeters |
so i filter on date, and staff username that accepted the payment (along with the workstation name) and it's working quite nicely. I was just hoping to avoid seperate reports for Cash, Check, and Credit |
| 09:56 |
mrpeters |
and figured this was a good opportunity to try to understand what nullability can do for me better |
| 09:57 |
tsbere |
mrpeters: Hmmm....gimme a sec to check something |
| 09:57 |
mrpeters |
no rush at all tsbere |
| 09:58 |
tsbere |
mrpeters: Looks to me like you want to start over with the reporter table of "Payments: Desk" |
| 09:59 |
tsbere |
which combines all the desk payment types into one view |
| 10:00 |
mrpeters |
ah, interesting. i had been using Payments: All |
| 10:00 |
mrpeters |
Which I *think* may still be OK, since we filter on an accepting staff username |
| 10:00 |
tsbere |
The "All" would include types without a cash drawer indicator, which it seems you care less about... |
| 10:04 |
mrpeters |
Agreed. I think it would be a performance gain to use Payment: Desk |
| 10:05 |
tsbere |
mrpeters: The cash drawer is also available from the "Desk" one directly. Which I think may be the workstation ID you want anyway... |
| 10:05 |
mrpeters |
right on |
| 10:05 |
mrpeters |
im going to do some experimenting |
| 10:08 |
eeevil |
mrpeters: money.bnm_desk_payment is the level at which we add the cash_drawer field, so reporting on that is what you want if you care about the cash drawer specifically. money.bnm_payment (a level above) adds the accepting_user |
| 10:08 |
mrpeters |
yeah, i remembered brick and mortar being defined as "actual transactions inside a library" from long ago |
| 10:09 |
mrpeters |
and we do care about the accepting_usr so Payments: Brick-and-Mortar may be the way to go. |
| 10:10 |
tsbere |
mrpeters: bnm_desk_payment is below bnm_payment, so both have accepting_usr |
| 10:10 |
mrpeters |
ah, ok |
| 10:11 |
* tsbere |
believes *neither* is available from the reporter normally, though, but instead views that include the actual underlying payment type are |
| 10:11 |
mrpeters |
I still think im going to have issues since I'm using "Cash Payment Detail", "Check Payment Detail", etc. I'll end up with multiple columns for accepting user (3x) and 3 columns for several other things too. |
| 10:11 |
tsbere |
mrpeters: Accepting user should be available from the "Payments: Desk" source directly. |
| 10:12 |
mrpeters |
The optimal goal would be a report that lists all of the payments taken in by an accepting_usr as the base filter, along with the date, and then display the transaction id, payment type, accepting_usr, accepting_ws_name, timestamp of payment, and the amount collected. |
| 10:13 |
mrpeters |
but since these are broken down in to cash, check, CC, etc. detail im not sure that is possible with the currently available sources |
| 10:13 |
tsbere |
All of that should be accessible from the Payments: Desk source without going into details |
| 10:13 |
mrpeters |
thinking ahead...this could become a basis for getting the cash report (pretty old interface in the staff client) in the web client |
| 10:14 |
mrpeters |
you think it's all available under Payments: Desk > Billable Transaction? |
| 10:15 |
eeevil |
tsbere: it's avaialbe from the "all sources" submenu, if nothing else |
| 10:15 |
tsbere |
mrpeters: Payments: Desk has a direct link to the accepting user and cash_drawer as well as the amount, payment type, and timestamp. And the billable transaction is a link too, now that I look. |
| 10:15 |
tsbere |
eeevil: Allow me to clarify: As far as I can tell, the *IDL itself* does not directly refer to the bnm_payment or bnm_desk_payment, but only to the views that add the payment type in. |
| 10:16 |
mrpeters |
alright, awesome. i may just not have been digging down far enough. thanks guys! eeevil++ tsbere++ |
| 10:16 |
tsbere |
mrpeters: Actually, I think you were digging down *too far* - You don't need links for most of the pieces you want at all. ;) |
| 10:17 |
|
rjackson-isl joined #evergreen |
| 10:23 |
kmlussier |
bug 1403907 is interesting. |
| 10:23 |
pinesol_green |
Launchpad bug 1403907 in Evergreen "E-resources not included in ver 2.7.1 Group formats and editions search" (affected: 1, heat: 6) [Medium,Confirmed] https://launchpad.net/bugs/1403907 |
| 10:24 |
kmlussier |
If you look at http://catalog.mvlc.org/eg/opac/results?query=omnivore%27s+dilemma&qtype=keyword&fi%3Asearch_format=&locg=1&sort=&modifier=metabib , you don't see any e-book icons, but the title for result 6 has [electronic resource] in the title. |
| 10:25 |
kmlussier |
And when you click through to the next screen, none of the titles retrieved say [electronic resource] |
| 10:26 |
* tsbere |
wouldn't be surprised if the issue is a lack of copies or something, but isn't looking into that today ;) |
| 10:27 |
mrpeters |
this is working beautifully, thanks tsbere and eeevil |
| 10:27 |
mrpeters |
you are right, i was digging too far |
| 10:35 |
eeevil |
tsbere: I believe that's correct (copies not there). that may have been an intentional change, I'm not sure OTTOMH |
| 10:36 |
eeevil |
kmlussier (or csharp ... Elaine's bug): is it only on 2.7.1? |
| 10:37 |
kmlussier |
eeevil: I don't know. NOBLE's training server is on 2.7.1 and MVLC is 2.7.1ish, so I don't have a good base for comparison. |
| 10:37 |
eeevil |
ah, thanks |
| 10:38 |
* kmlussier |
notes there is different behavior between NOBLE and MVLC's catalog. |
| 10:38 |
dbs |
Oh right, and our cataloguers have been adding fake copies to eresource records since the Unicorn days, so our experience won't count either |
| 10:38 |
kmlussier |
NOBLE's catalog did show the e-resource icon on the initial search results page. I didn't see those icons in the MVLC catalog. |
| 10:39 |
kmlussier |
It could have been the examples I was using. |
| 10:39 |
|
mmorgan joined #evergreen |
| 11:04 |
kmlussier |
eeevil: I don't know what version Sitka is on, but the e-resource issue with metarecord search seems to be happening there too. |
| 11:05 |
kmlussier |
I know there is a way you can see what version a site is using, but I always forget what URL to use. |
| 11:05 |
eeevil |
kmlussier: well, they're not an a version, strictly speaking: http://catalogue.bclibrary.ca/gateway?service=open-ils.actor&method=opensrf.open-ils.system.ils_version&param= |
| 11:06 |
kmlussier |
Ah. I've seen that here before. :) |
| 11:16 |
|
mmorgan1 joined #evergreen |
| 11:19 |
|
jwoodard joined #evergreen |
| 11:33 |
|
vxbush joined #evergreen |
| 11:35 |
|
bmills joined #evergreen |
| 11:42 |
* dbs |
had some discussions with Eric Miller from Zepheira around Libhub.org and linked data, and he was wondering if the Evergreen community would consider me an okay point person to talk with about linked data / library resource discoverability |
| 11:42 |
bshum |
dbs: Eh, only "okay" Dan. |
| 11:43 |
dbs |
I mention this because I doubt that anyone would object, but want to give dev-oriented / EOB-oriented folks the ability to think about it |
| 11:45 |
bshum |
dbs: +1 :) |
| 11:45 |
bshum |
And dbs++ |
| 11:50 |
|
mmorgan1 joined #evergreen |
| 11:51 |
dbs |
well thanks :) |
| 11:51 |
|
vlewis joined #evergreen |
| 11:51 |
kmlussier |
Anyone else want to volunteer to be the spokesperson on linked data? Bueller? Bueller? |
| 11:52 |
dbs |
kmlussier: gmcharlt would be a candidate |
| 11:52 |
* gmcharlt |
perks up and reads scrollback |
| 11:52 |
kmlussier |
dbs: I think you're a fine choice. :) |
| 11:52 |
|
rjackson-isl joined #evergreen |
| 11:52 |
kmlussier |
dbs++ |
| 11:53 |
dbs |
but I think the idea is that Eric wants to pull together a very small team of people from various projects (including proprietary ones) to think about future steps we can take for realz |
| 11:53 |
* gmcharlt |
is entirely happen for dbs to do it |
| 11:53 |
gmcharlt |
dbs++ |
| 11:53 |
gmcharlt |
but I'm also /very/ interested in the discussion |
| 11:53 |
kmlussier |
dbs: That sounds like a great plan! |
| 11:53 |
kmlussier |
Can 2 people from Evergreen be involved? |
| 11:53 |
* dbs |
isn't even sure anything will happen but will try to ensure that Koha and VuFind and the like have the ability to participate if something does happen... |
| 11:54 |
dbs |
kmlussier: I'm not sure anything will even happen! If I hear anything more (this dates back a few weeks), then I'll share more |
| 11:56 |
kmlussier |
dbs: Well, I hope do hope something happens. It would be great if everyone could collaborate on this so that everone doesn't go off in their own directions. |
| 11:56 |
dbs |
kmlussier: yeah, that's our hope |
| 11:57 |
dbs |
!I suspect part of Eric's goal in having Evergreen there would be to shame some of the proprietary vendors |
| 11:57 |
dbs |
!I don't think this makes things off the record anymore but it makes me laugh anyway |
| 11:57 |
bshum |
Heh |
| 11:57 |
bshum |
Yeah it's [off] now |
| 11:57 |
gmcharlt |
! [off] |
| 11:58 |
phasefx |
[oof] |
| 11:59 |
kmlussier |
bshum: You should make [oof] work for those of us who constantly have problems with typos. |
| 12:00 |
gmcharlt |
"oof" - the sound one makes when hit by a truth to sensitive to make public? |
| 12:00 |
kmlussier |
Not that I'm in the habit of using the [off] command. If I don't want somethingto show up in the logs, I don't make a habit of saying it in public channels. |
| 12:02 |
|
sandbergja joined #evergreen |
| 12:10 |
* bshum |
finds the new getfedora.org website very friendly looking. |
| 12:12 |
Bmagic |
I have a question about staff client javascript AutoFieldWidget.js. When they are loaded on the page, it appears that they are loaded async, I have poked around in the code and I am altering the contents of one of the dropdowns. My new code only works if there is a lag introduced |
| 12:13 |
Bmagic |
I need new openils.User().getPermOrgList to get done before the code calls new openils.PermaCrud().search and I can't seem to make it wait |
| 12:14 |
* dbs |
knee-jerks "callbacks?" but hasn't looked at that code in eons |
| 12:14 |
|
rjackson-isl joined #evergreen |
| 12:14 |
Bmagic |
dbs: that sounds promising |
| 12:15 |
|
jihpringle joined #evergreen |
| 12:17 |
Bmagic |
dbs: or maybe nest the functions? |
| 12:21 |
jeff |
nest the functions, chain the callbacks, just don't cross the streams. |
| 12:22 |
bshum |
"Excuse me, Egon, you said crossing the streams was bad." |
| 12:23 |
* dbs |
was pretty sure Dojo offered the ability to make calls either async or sync but again, haven't looked at the dojo.openils stuff forever |
| 12:27 |
|
bmills joined #evergreen |
| 12:29 |
* dbs |
blames all of the Dojo widgets that get loaded for no reason for https://devlaurentian.concat.ca/eg/opac/record/787108 (now that we've disabled autosuggest, we really only need the core DOM-manipulation stuff for a few things) |
| 12:29 |
dbs |
But of course I could be mistaken :) |
| 12:32 |
berick |
dbs: agreed, if autosuggest is disabled, you really shouldn't need openils_dojo.js |
| 12:35 |
bshum |
There's only three things that enable dojo in the past I thought: autosuggest, google books, and.... hmm, Novelist |
| 12:35 |
bshum |
But then we enabled it always cause of the copy location search in advanced search. |
| 12:36 |
bshum |
Or you guys are talking even more granular and specific bits of dojo here and there |
| 12:38 |
berick |
bshum: we're talking about loading dojo.js, but not loading all of the dijits and stuff included in openils_dojo.js |
| 12:38 |
bshum |
Aha |
| 12:38 |
berick |
since the tpac only uses dijits for autosuggest (TTBOMK) |
| 12:39 |
phasefx |
the shelving location field in advanced search needs dojo |
| 12:39 |
phasefx |
oh, that was said |
| 12:40 |
dbs |
yeah, dojosrf and openils.cgi |
| 13:00 |
|
RoganH joined #evergreen |
| 13:09 |
jeff |
transit list hates it when it runs into many deleted copies (that are in transit) |
| 13:16 |
|
Dyrcona joined #evergreen |
| 13:30 |
|
bbqben joined #evergreen |
| 13:53 |
|
montgoc1 joined #evergreen |
| 13:57 |
|
keynote2k joined #evergreen |
| 13:57 |
|
abneiman joined #evergreen |
| 14:01 |
bbqben |
Hi all - JFYI that the EOB meeting starts here in a few minutes. Cheers |
| 14:03 |
bbqben |
#startmeeting Evergreen Oversight Board Meeting, 20.12.14 |
| 14:03 |
pinesol_green |
Meeting started Thu Dec 18 14:03:58 2014 US/Eastern. The chair is bbqben. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:03 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 14:03 |
pinesol_green |
The meeting name has been set to 'evergreen_oversight_board_meeting__20_12_14' |
| 14:04 |
bbqben |
#topic introductions |
| 14:04 |
bbqben |
EOB members, please introduce yourself with #info |
| 14:04 |
bshum |
#info bshum = Ben Shum, Bibliomation |
| 14:04 |
RoganH |
#info RoganH = Rogan Hamby, SCLENDS |
| 14:04 |
yboston |
#info ysboston - Yamil Suarez - Berklee College of Music (EOB) |
| 14:04 |
bbqben |
#info bbqben = Ben Hyman, BC Libraries Co-op |
| 14:04 |
montgoc1 |
#info montgoc1 = Chauncey Montgomery, Consortium of Ohio Libraries |
| 14:04 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:05 |
abneiman |
#info abneiman Andrea Buntz Neiman, Kent County Public Library |
| 14:05 |
bbqben |
Hi everyone! csharp sends his regrets |
| 14:05 |
bbqben |
#topic Minutes / Actions from last meeting |
| 14:06 |
bbqben |
#info http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-11-20-14.01.html |
| 14:06 |
bbqben |
and it looks like we'll cover the actions in our agenda |
| 14:06 |
bbqben |
so moving on... |
| 14:06 |
bbqben |
#topic Financial Report |
| 14:06 |
bbqben |
bshum ++ |
| 14:07 |
bbqben |
#info http://list.evergreen-ils.org/pipermail/eg-oversight-board/2014-December/000931.html |
| 14:07 |
bshum |
Indeed, the kind folks over at Conservancy got me all squared away and I've learned the basics of getting info out of the books. |
| 14:07 |
bbqben |
thanks to bshum for gaining access to the ledger and mind melding with gmcharlt |
| 14:07 |
kmlussier |
bshum++ |
| 14:08 |
gmcharlt |
(graced is returning from an errand and should be joining shortly, BTW) |
| 14:08 |
bbqben |
great - any questions about the finances today? |
| 14:08 |
bbqben |
ok moving on then |
| 14:09 |
bbqben |
#topic Evergreen Conference Report |
| 14:09 |
bbqben |
looks like Buzzy's not here. |
| 14:10 |
kmlussier |
I can report that keynote2k received an agreement from the hotel just this week. |
| 14:10 |
kmlussier |
We'll need the agreement sign before we can start the registration process. |
| 14:11 |
kmlussier |
I think buzzy was planning to send an update out to the community shortly. |
| 14:11 |
keynote2k |
Hi, all. I plan to the review the agreement this afternoon. Kmlussier: I'll let you and buzzy know if I see any red flags |
| 14:11 |
* keynote2k |
goes back to lurk mode |
| 14:11 |
kmlussier |
Sorry, I don't have any other updates other than the issues that came up in the e-mail keynote2k sent out to the Board earlier. |
| 14:11 |
bbqben |
kmlussier++ |
| 14:11 |
kmlussier |
Thanks keynote2k! |
| 14:12 |
bbqben |
good to see some momentum building here... |
| 14:12 |
bbqben |
anxious to see sponsorship package and registration up and out asap in 2015 |
| 14:12 |
kmlussier |
bbqben: Should we take some time to discuss the issues with the wordpress plugin now or defer it to later? |
| 14:13 |
bbqben |
now works for me... |
| 14:14 |
bbqben |
#topic conference registration platform |
| 14:14 |
kmlussier |
OK, I personally would like to move forward with the WordPress plug-in to handle registrations. I know it's know there are some gray areas with licensing with WordPress plugins, but I think it's a better solution than the Eventbrite ones. |
| 14:15 |
kmlussier |
The question is if you all feel comfortable using it or if you think the concerns keynote2k are too much of a red flag. |
| 14:16 |
kmlussier |
Ideally, I would have found a fully-GPL'ed WordPress plugin that handled our needs, but each of the ones I investigated were missing certain features that I thought were important to our registration process. |
| 14:17 |
RoganH |
I don't have an objection to using a commercial plugin if the license is clearly legal. |
| 14:17 |
RoganH |
I'm not sure what you mean by grey area here. |
| 14:17 |
bshum |
I like working solutions. |
| 14:17 |
bbqben |
I understand the desire to integrate around WordPress - as a community we've focused energy here |
| 14:18 |
kmlussier |
RoganH: I was specifically referring to the issues keynote2k raised in his e-mail to the Board. |
| 14:18 |
bbqben |
I did raise an alternative FLOSS solution (but not WordPress in https://pkp.sfu.ca/ocs/ ...but cycles are very tight this year |
| 14:19 |
kmlussier |
For those who don't know, keynote2k is Tony Sebro, the attorney for the Software Freedom Conservancy. He came today in case anyone has any questions about the licensing. |
| 14:20 |
kmlussier |
bbqben: My only concern with that is the time factor. I have 2 more days before I'm on vacation for the rest of the year. But it doesn't mean others couldn't give it a thorough look-through if they have the tuits. |
| 14:20 |
yboston |
kmlussier: thanks |
| 14:21 |
yboston |
I would rther go back to Eventbrite, because I hate to rush into a brand new system that will handle credit card information |
| 14:21 |
kmlussier |
The plug-in integrates with PayPal. |
| 14:21 |
* keynote2k |
reads the backlog. |
| 14:21 |
kmlussier |
yboston: Unless you're referring to the software bbqben was linking to? |
| 14:21 |
yboston |
I meant both of them, but mostly Ben's |
| 14:22 |
montgoc1 |
I agree with yboston. Due to time constraints, etc., would it be easier just to use what we have an investigate other options for the future? |
| 14:22 |
yboston |
though I appreciate the fact that the first one relies on PayPal |
| 14:22 |
bbqben |
The jist: EventBrite=proprietary, but a known entity, and possibly gratis vs Events Manager Pro, integrating with WordPress, but possibly representing a GPLv2 violation |
| 14:22 |
kmlussier |
In the past, Eventbrite has waived its fees, but my understanding is that's not a sure thing anymore. |
| 14:22 |
abneiman |
Agreed with yboston; also time is starting to become a factor here so I'd be inclined to go with what we can get up & running faster. |
| 14:22 |
kmlussier |
They charge 2.5% plus .99 per transaction, which is about $1,000? |
| 14:23 |
keynote2k |
Like kmlussier said, I'm here to answer any questions you may have. I should note, though, that I don't view the Events Mgr Pro's licensing issues as a gray area, per se. Either it's GPLv2-compliant, or it isn't -- and if it's compliant, it's on the edge. We'd need more time to vet it thoroughly |
| 14:23 |
RoganH |
Eventbrite has always been willing to waive charges for me, even for small events. |
| 14:23 |
montgoc1 |
If they are willing to waive, I'd go with Eventbrite. |
| 14:23 |
kmlussier |
I've been working with the plug-in for a few weeks to evaluate it. Time is not a factor with that particular solution. |
| 14:23 |
montgoc1 |
But license is? |
| 14:23 |
kmlussier |
montgoc1: Yes |
| 14:23 |
RoganH |
I'm in favor of using Eventbite if there's a question about GPL compatibility. I am curious what part of the GPL it might be violating though. |
| 14:23 |
keynote2k |
As for Eventbrite: we're working on whether they'll waive the fees for 2015; I haven't heard back yet |
| 14:24 |
graced |
#info graced is Grace Dunbar (better late than never) |
| 14:24 |
yboston |
good to know that on the techinical side kmlussier has been testing the first solution |
| 14:24 |
kmlussier |
keynote2k: But in the past, you have indicated it's less likely than it has been previously, right? |
| 14:24 |
yboston |
but I think we need tme for the license vetting |
| 14:24 |
* gmcharlt |
would like to point out that the investigation of the event plugin is not something that was being undertaken lightly; my understanding is that there has been significant uncertainty about whether EventBrite would waive this year |
| 14:24 |
abneiman |
kmlussier: sorry, I meant more time on the analysis, not deployment. |
| 14:25 |
keynote2k |
RoganH: the GPL compliance analysis will depend in part on how the pro add-on connects to the base plug-in. The license status of the base plug-in is confusing as well |
| 14:26 |
montgoc1 |
How long until we can licensing stuff figured out and how does that impact the timeline? |
| 14:26 |
kmlussier |
abneiman: gotcha |
| 14:26 |
yboston |
montgoc1: +1 |
| 14:26 |
RoganH |
keynote2k: gotcha so the shared calls and data structures part of the traditional gpl interpretation |
| 14:26 |
keynote2k |
re: Eventbrite: Yes, I had previously placed the odds at being lower than in years past. But my contact didn't mention any low odds when I reached out to her this time around. |
| 14:27 |
keynote2k |
(This was not the tune she was singing a year ago) So, I can't really handicap it at this point until I hear back. |
| 14:28 |
keynote2k |
montgoc1: in terms of timeline: ideally, 1-2 weeks. But compliance investigations are messy, unfortunately: sometimes, pulling on one thread unravels something else. |
| 14:28 |
kmlussier |
I think I'm hearing people prefer to stick with Eventbrite. Although I would be interested in hearing the results of the analysis, if it takes longer than a week, I'm really concerned about timeline. |
| 14:28 |
bbqben |
keynote2k in practical terms, what is the risk to the EG project if at the end of your analysis the gpl isn't being respected? |
| 14:28 |
kmlussier |
We have people who want to register for the conference before the end of their fiscal year, which is soon. |
| 14:28 |
bbqben |
(and we choose to go with wordpress integration over EventBrite) |
| 14:30 |
kmlussier |
I think that's been my question. What is the risk? My understanding is these types of add-ons aren't unusual in the WordPress community. |
| 14:30 |
RoganH |
They're down right common. |
| 14:32 |
yboston |
also; what if the analysis come back as being on the "bleeding edge" as it is currently suspected. I can see that to some in our board that would be good enough, but perhaps not to the conservancy |
| 14:32 |
keynote2k |
bbqben, kmlussier: I'm reluctant to discuss risk associated with using this particular solution in a public channel. But, as a general matter, a GPL'ed project would risk damage to its reputation |
| 14:32 |
kmlussier |
yboston: I think that decision should rest in the hands of the community, not the conservancy. |
| 14:33 |
yboston |
kmlussier: that makes sense |
| 14:33 |
graced |
kmlussier: I agree |
| 14:33 |
bbqben |
keynote2k: appreciate this perspective.... |
| 14:33 |
bbqben |
For this group, I suppose we weigh the reputation associated with using an imperfect proprietary solution against an imperfect GPL'ed version |
| 14:35 |
bbqben |
hearing kmlussier and concern re: time getting away, I see a couple of approaches here |
| 14:36 |
bbqben |
Approach 1: give it to the end of the week to hear back from EventBrite (& possibly keynote2k re: analysis of Event Manager Pro) re: gratis or not & GPL compliance or not, then call a vote |
| 14:36 |
bbqben |
Approach 2: call a vote now. |
| 14:36 |
bbqben |
Thoughts? |
| 14:36 |
montgoc1 |
Approach 1 for me. |
| 14:36 |
kmlussier |
End of week is end of tomorrow? |
| 14:37 |
RoganH |
If end of the week means tomorrow I'm for #1. |
| 14:37 |
montgoc1 |
Ah yes. |
| 14:37 |
bbqben |
kmlussier: yep - day end tomorrow |
| 14:37 |
montgoc1 |
Time flies. |
| 14:37 |
graced |
I can wait until tomorrow for a vote |
| 14:37 |
abneiman |
Same as Rogan, if this means tomorrow +1 |
| 14:37 |
kmlussier |
OK, that's fine with me. That gives me all of Monday to implement whatever solution we go with. |
| 14:37 |
keynote2k |
I might have an answer from Eventbrite by tomorrow (not sure), but I won't have much to add on the compliance anlaysis by then |
| 14:37 |
bshum |
How long would it take to setup EventBrite (regardless of whether fees are waved or not)? |
| 14:38 |
bshum |
*waived, whatever. |
| 14:38 |
keynote2k |
1 more day is a lot shorter than 1-2 additional weeks |
| 14:38 |
bbqben |
keynote2k: fair enough, thanks |
| 14:38 |
kmlussier |
bshum: I could do either one in the same amount of time. It will be Monday one way or another because I don't really have another choice. |
| 14:38 |
graced |
I am concerned, like kmlussier, that we will lose substantial conference goers if they can register under this FY - (by the end of the month). |
| 14:38 |
kmlussier |
And if the agreement with the venue isn't signed, I'll place it in the hands of somebody else to pull the trigger when we are allowed. |
| 14:38 |
graced |
So I don't think we can wait 2 weeks for an answer |
| 14:39 |
bbqben |
thanks everyone |
| 14:39 |
bbqben |
#action bbqben call a vote at 1600 Pacific on 19.12.14 re: registration platform for EG2015 |
| 14:39 |
abneiman |
I also agree with this concern about people needing to register before 12/31 for their own budgetary reasons. |
| 14:39 |
kmlussier |
Thanks keynote2k for answering questions! |
| 14:40 |
bbqben |
keynote2k++ |
| 14:40 |
keynote2k |
Glad to help. If you have any other questions, let me know |
| 14:40 |
montgoc1 |
keynote2k++ |
| 14:40 |
bbqben |
ok, moving on |
| 14:40 |
* keynote2k |
is signing of |
| 14:40 |
keynote2k |
f |
| 14:40 |
|
keynote2k left #evergreen |
| 14:40 |
bbqben |
#topic Evergreen 2.8 Release Manager's Report |
| 14:40 |
bbqben |
#info Latest from the dev list: http://libmail.georgialibraries.org/pipermail/open-ils-dev/2014-December/009764.html |
| 14:41 |
bbqben |
berick: you around and available? |
| 14:41 |
bbqben |
er, the latest from the dev list isn't actually the latest - sorry |
| 14:42 |
berick |
bbqben: i am |
| 14:42 |
berick |
but have not prepared anything in particular |
| 14:42 |
berick |
we're just hashing out the details of schedule now |
| 14:42 |
bbqben |
berick: sorry to put you on the spot. |
| 14:43 |
berick |
no problem |
| 14:43 |
bbqben |
berick: was just thinking that the countdown to this release is a bit like the enjoyment you get from an advent beer pack ;) |
| 14:44 |
bbqben |
any q's for berick or shall we see where things get for the January meeting? |
| 14:44 |
kmlussier |
bbqben: advent beer pack? Is that a real thing? |
| 14:44 |
berick |
bbqben: hah, i'll do my best to help us live up to that ;) |
| 14:45 |
bbqben |
kmlussier: this is the one I've been enjoying: http://www.snowcasecalendar.com/ |
| 14:45 |
bbqben |
but enough if that :) |
| 14:45 |
bbqben |
#topic SFC update (Emergency Fund) |
| 14:46 |
bbqben |
Heard back 2 days ago from Karen Sandler at SFC re: additional questions that Kathy and I had re: what role the SFC could play/at what cost WRT pooling of funds... |
| 14:47 |
bbqben |
Next steps - I'll summarize some of the notes and likely survey this group on a couple of topics, after double checking out Terms of Reference |
| 14:47 |
bbqben |
Expect to hear from me in January on this. Any questions/concerns? |
| 14:48 |
bshum |
bbqben++ # sounds like a plan |
| 14:48 |
bbqben |
#action bbqben summarize SFC feedback & survey board on relevant topics |
| 14:48 |
bbqben |
#topic Evergreen web FAQ development |
| 14:50 |
bbqben |
yboston - you able to provide an update? |
| 14:50 |
yboston |
I do not have anything to add at this point |
| 14:50 |
yboston |
no new updates have been made to the FAQ |
| 14:51 |
yboston |
I was thinking of removeing the "draft" label at this point |
| 14:51 |
bbqben |
yboston - ambitious ;) |
| 14:51 |
kmlussier |
+1 |
| 14:51 |
bbqben |
+1 |
| 14:51 |
bshum |
+1 |
| 14:51 |
montgoc1 |
+1 |
| 14:52 |
RoganH |
+1 |
| 14:52 |
kmlussier |
It's so nice when we can all come to agreement this easily. :) |
| 14:52 |
yboston |
DONE |
| 14:52 |
bbqben |
#action yboston will press into production the revised vendor FAQ's |
| 14:53 |
bbqben |
yboston++ |
| 14:53 |
bbqben |
and a belated berick++ |
| 14:53 |
yboston |
berick++ |
| 14:53 |
bbqben |
#topic Code of Conduct - Procedures |
| 14:53 |
kmlussier |
I'll need to defer my update until the next meeting. |
| 14:53 |
kmlussier |
Since I haven't done anything on it. |
| 14:54 |
kmlussier |
At this point, I think the call for volunteers should go out after the New Year. |
| 14:54 |
bbqben |
kmlussier: sounds good and timing should work as we build to EG2015 |
| 14:54 |
kmlussier |
Because we've reached the point of the year when people stop paying attention to e-mail. |
| 14:55 |
bbqben |
true, that. Moving on... |
| 14:55 |
bbqben |
#topic new business |
| 14:55 |
bbqben |
anyone? going once... |
| 14:56 |
bbqben |
...going twice (& final) |
| 14:56 |
bbqben |
#topic happy holidays everyone! |
| 14:57 |
bbqben |
Do watch for an email from me tomorrow re: voting on registration platform. 1600 Pacific should be considered a time estimate only for this |
| 14:57 |
graced |
Happy holidays, everyone! |
| 14:57 |
bbqben |
#endmeeting |
| 14:57 |
pinesol_green |
Meeting ended Thu Dec 18 14:57:54 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 14:57 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-12-18-14.03.html |
| 14:57 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-12-18-14.03.txt |
| 14:57 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-12-18-14.03.log.html |
| 14:58 |
kmlussier |
Happy holidays! |
| 14:58 |
kmlussier |
bbqben++ |
| 14:58 |
graced |
bbqben++ |
| 14:58 |
yboston |
bbqben++ |
| 14:58 |
yboston |
happy holidays |
| 14:58 |
montgoc1 |
bbqben++ |
| 14:58 |
montgoc1 |
Have a jolly time y'all. |
| 15:20 |
* kmlussier |
the code from bug 1403967 on a sandbox so that one of the catalogers here can look at it. |
| 15:20 |
pinesol_green |
Launchpad bug 1403967 in Evergreen "Display 'subject heading thesaurus' value in Manage Authorities results" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1403967 |
| 16:02 |
|
vxbush left #evergreen |
| 16:39 |
|
julialima_ left #evergreen |
| 16:44 |
|
bshum joined #evergreen |
| 16:50 |
yboston |
berick: question about your code that provides authority overlays in Vandelay, if you have a moment |
| 16:51 |
berick |
yboston: i do, indeed |
| 16:51 |
|
nhilton joined #evergreen |
| 16:51 |
yboston |
I looked over your code, but I am not sure I can answer this short question |
| 16:52 |
yboston |
are you adding any new defaults to the UI/feture of "record display attributes" for auths? |
| 16:52 |
yboston |
I actually have not loaded your code yet, but an older 2.7.0 VM I see that there is only one entry for auths |
| 16:52 |
|
mrpeters left #evergreen |
| 16:53 |
berick |
yboston: no, i didn't add any new attrs for this code |
| 16:54 |
yboston |
not that I understand how overlays work for bibs or auths, wondering if some new values for auths would be a nice thing to have |
| 16:56 |
yboston |
I can't seem to be able to add new "record display attributes" for auths from the XUL UI either, but that is a diferent matter |
| 16:57 |
berick |
huh |
| 16:58 |
berick |
i wonder if no one's ever tested it, since vandelay has such limited auth support. i found other authority record bugs in vandelay. |
| 16:58 |
yboston |
tested what, the "record display attributes" or importing authorities? |
| 16:58 |
yboston |
we import authorities through Vabdelay daily |
| 16:59 |
yboston |
*Vandelay |
| 16:59 |
berick |
yboston: since the matching is based on MARC tags or normalized headings, new attributes are not required. however, not havingin any attrs, certainly limits the utility of the UI. |
| 16:59 |
berick |
the display attributes |
| 17:00 |
berick |
yboston: if you have suggestions on a set of default attrs, I'd be happy to help integrate them |
| 17:00 |
berick |
as a new LP ticket |
| 17:00 |
yboston |
that is what I suspected you woudl ask |
| 17:00 |
berick |
;) |
| 17:00 |
berick |
<-- predictable |
| 17:01 |
yboston |
I will run it by the catalogers here |
| 17:02 |
yboston |
and to be clear, I see two things |
| 17:03 |
yboston |
1) new defaults are needed (and I will help sugest some) 2) there might be a bug with addign new ones from the XUL UI (more testing needed to confirm) |
| 17:04 |
berick |
cool, that's how I understood it |
| 17:04 |
yboston |
great, just checking |
| 17:04 |
yboston |
BTW, I am trying to learn how to do bib overlays before I tackle testing the auth overlays |
| 17:11 |
|
mmorgan left #evergreen |
| 17:54 |
|
dcook joined #evergreen |
| 17:58 |
|
vlewis_ joined #evergreen |
| 17:59 |
|
artunit_ joined #evergreen |
| 18:06 |
|
dcook joined #evergreen |
| 18:07 |
|
dcook__ joined #evergreen |
| 20:46 |
jeff |
@praise documentation |
| 20:46 |
* pinesol_green |
the upgrade came off brilliantly, and it's all because of documentation |
| 20:46 |
jeff |
documentation++ |
| 20:46 |
|
bmills joined #evergreen |
