| Time |
Nick |
Message |
| 01:10 |
|
atlas__ joined #evergreen |
| 02:47 |
|
Terence joined #evergreen |
| 05:48 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 06:41 |
|
mtate joined #evergreen |
| 06:41 |
|
eeevil joined #evergreen |
| 06:42 |
|
Callender joined #evergreen |
| 06:42 |
|
phasefx joined #evergreen |
| 06:43 |
|
graced joined #evergreen |
| 06:52 |
|
b_bonner joined #evergreen |
| 06:52 |
|
mnsri_ joined #evergreen |
| 06:53 |
|
mtcarlson_away joined #evergreen |
| 07:53 |
|
collum joined #evergreen |
| 07:56 |
|
rjackson-isl joined #evergreen |
| 08:18 |
|
akilsdonk joined #evergreen |
| 08:19 |
|
mrpeters joined #evergreen |
| 08:33 |
|
kmlussier joined #evergreen |
| 08:34 |
|
Shae joined #evergreen |
| 08:38 |
|
tspindler joined #evergreen |
| 08:41 |
|
artunit joined #evergreen |
| 08:45 |
kmlussier |
g'morning |
| 08:46 |
|
sarabee joined #evergreen |
| 08:49 |
kmlussier |
jeffdavis++ #Overdrive API branch |
| 09:00 |
|
RoganH joined #evergreen |
| 09:02 |
|
jwoodard joined #evergreen |
| 09:03 |
|
ericar joined #evergreen |
| 09:29 |
|
artunit joined #evergreen |
| 09:33 |
|
yboston joined #evergreen |
| 10:19 |
|
dreuther joined #evergreen |
| 10:21 |
|
RBecker joined #evergreen |
| 10:21 |
Bmagic |
Is this a bug or a feature: Library A lends Library B an item. It gets checked out. B has long overdue settings. Patron is billed. Patron returns item. B has settings to void the long overdue bills but the opensrf logs show that it looks for A's settings to void the bill |
| 10:25 |
tsbere |
Bmagic: I would have to look, but either the item owning lib is being used or it was returned at library A. |
| 10:25 |
kmlussier |
Bmagic: IIRC, lost items (and therefore I expect long overdue items) go by the owning library's policies? |
| 10:26 |
Bmagic |
kmlussier: in that case it wouldnt have charged the long overdue fee because Library A doesn't have those settings |
| 10:26 |
Bmagic |
in the first place |
| 10:26 |
kmlussier |
ah, that's right. Then, no, I'm stumped. |
| 10:27 |
Bmagic |
it's either a bug with the action trigger or with the circulation code |
| 10:27 |
Bmagic |
the action trigger applied the bill and the circulation code is responsible for removing it |
| 10:28 |
Bmagic |
found the code from Circulate.pm my $circ_lib = (ref $self->copy->circ_lib |
| 10:28 |
Bmagic |
meaning it is getting the circ lib from the copy and not from the circulation |
| 10:30 |
|
atlas__ joined #evergreen |
| 10:32 |
Bmagic |
kmlussier: which library settings are supposed to be respected? Owning or circing? |
| 10:36 |
csharp |
PINES doesn't hit that issue since we have those settings set at the consortium level - if you can get your libraries to agree on a common policy, problem solved |
| 10:37 |
kmlussier |
Bmagic: My recollection is that the lost library settings used the circulation (not circing) library's settings. Since a lot of the long overdue behavior was based on how the system handles lost items, my assumption was that long overdue would be handled the same way, which seems to be the case. But I'm working from memory, not code, so take anything I say with a grain of salt. :) |
| 10:37 |
* csharp |
knows that's glib |
| 10:37 |
csharp |
let me look around, since it was our feature request |
| 10:39 |
csharp |
ous_proc_fee => 'circ.longoverdue_materials_processing_fee', |
| 10:39 |
csharp |
ous_void_od => 'circ.void_overdue_on_longoverdue', |
| 10:39 |
Bmagic |
csharp: ok right, it's supposed to be respecting the circ lib for both billing and voiding |
| 10:40 |
Bmagic |
I think I found a bug, because the code clearly shows it's getting the circ lib from the copy and not the circulation |
| 10:41 |
csharp |
it does appear to be using the copy's owning library (copy->call_number->owning_lib) |
| 10:41 |
Bmagic |
Circulate.pm line 3419 my $circ_lib = (ref $self->copy->circ_lib) |
| 10:41 |
csharp |
I'm looking at AssetCommon.pm |
| 10:41 |
csharp |
line er.... |
| 10:41 |
Bmagic |
you are looking at the code for billing, im looking at the code for voiding |
| 10:41 |
csharp |
694 |
| 10:41 |
csharp |
oh - ok |
| 10:42 |
csharp |
my $void_overdue = $U->ou_ancestor_setting_value( |
| 10:42 |
csharp |
$owning_lib, $args{ous_void_od}, $e) || 0; |
| 10:43 |
csharp |
so it checks whether to void or not based on the copy owning lib |
| 10:43 |
jeff |
copy circ lib |
| 10:43 |
Bmagic |
copy circ lib is what I am seeing |
| 10:43 |
csharp |
when processing longoverdue items? |
| 10:43 |
csharp |
ohhh |
| 10:44 |
csharp |
sorry - at checkin |
| 10:44 |
Bmagic |
which is wrong - it should be circ->circ_lib |
| 10:47 |
csharp |
so when being set to longoverdue, it grabs the owning lib's settings, but coming in, it grabs the copy circ lib's settings |
| 10:48 |
csharp |
for PINES, those are nearly always the same OU, so we probably would never notice the difference |
| 10:48 |
|
buzzy joined #evergreen |
| 10:48 |
csharp |
but Bmagic, you're saying that the circulation->circ_lib should be the one consulted for settings? I'm not sure that's what we would want |
| 10:55 |
Bmagic |
csharp: the action trigger is voiding overdue bills based on settings from the owning lib unless it was a precat, it's applying price of item based on owning lib. |
| 10:57 |
csharp |
also worth noting (as kmlussier aluded to) that longoverdue is in many ways copied and pasted from the "lost" code |
| 10:57 |
csharp |
some differences, but same basic process |
| 10:58 |
csharp |
so if we change lod, we would probably need to change lost too |
| 10:58 |
Bmagic |
The behavior that I just detected was: Patron billed based on circ_lib , and voided based on copy circ lib which the code doesnt support |
| 10:58 |
csharp |
but I'm sure our libraries are happy with the status quo |
| 10:58 |
Bmagic |
Patron billed based on action circulation circ lib not copy circ lib |
| 10:58 |
Bmagic |
could I have my Action Trigger setup wrong? |
| 10:59 |
csharp |
right - the billings are from the library where the circ happened |
| 10:59 |
Bmagic |
my AT is owned by Library B, with null "Processing Group Context Field" |
| 11:00 |
csharp |
whether it automatically voids on set to lost/longoverdue is a preference set for the copy circ lib/call number owning lib ("my item") |
| 11:00 |
csharp |
ah.. |
| 11:00 |
csharp |
you're running them per library |
| 11:00 |
csharp |
we run them at the PINES level |
| 11:01 |
Bmagic |
yes, the AT is at the system level for a system that Library B belongs to. The item belongs to Library A (no action trigger) |
| 11:01 |
csharp |
processing group context field is probably irrelevant here - that's for being able to group multiple A/T events for say, the same user so they don't get 15 separate notices for the 15 items that just got processed |
| 11:02 |
Bmagic |
I see |
| 11:02 |
Bmagic |
ok, then it doesn't make sense that this patron got a bill to begin with |
| 11:04 |
Bmagic |
I think I've got it. The action trigger finds everything that is overdue at Library B and sets them to long overdue, it doesnt care if the item was from another library. So the item is going to be marked long overdue no matter what. The paticulars about voiding overdues and such respect the item owner |
| 11:04 |
csharp |
yeah, longoverdue processes circs, so that makes sense |
| 11:05 |
csharp |
"circs that happened at my library" |
| 11:05 |
Bmagic |
So, it's not working the way we want it to. We need that Action trigger to only find circs by the AT owner AND the item owned by the AT owner |
| 11:06 |
Bmagic |
I am sure this is the same for lost |
| 11:07 |
Bmagic |
Does it make sense that the system would mark items long overdue on items owned by libraries that do not have settings for long overdue? |
| 11:10 |
|
atlas__ joined #evergreen |
| 11:12 |
csharp |
Bmagic: you may have hit a use case that wasn't considered when developing all that |
| 11:12 |
csharp |
however, creating a reactor that calls different/custom code is possible too |
| 11:13 |
csharp |
eeevil has been pushing for that for some time now |
| 11:13 |
csharp |
(people developing their own A/T reactors, etc.) |
| 11:13 |
|
dreuther joined #evergreen |
| 11:18 |
|
dreuther_ joined #evergreen |
| 11:21 |
|
vlewis joined #evergreen |
| 11:25 |
Bmagic |
Our solution could be to set a consortium default for voiding long overdue upon checkin |
| 11:26 |
|
vanya joined #evergreen |
| 11:26 |
Bmagic |
but I think that it's a bug, If the voiding of the fines and such respects the owning lib, then the action trigger should respect the item owning lib as well |
| 11:27 |
Bmagic |
Which means that the action trigger could apply a fine for a circulation that is not in it's scope because the item was lent |
| 11:38 |
tspindler |
we have been discussing an issue with the state 'lost' and the action trigger marked items lost, if we changed the name of that status to billed would it break anything or does the status have to be lost? |
| 11:39 |
kmlussier |
tspindler: Would that status also be used for items that are manually marked lost? |
| 11:39 |
tspindler |
kmlussier: we would probably create an additional status for that |
| 11:40 |
kmlussier |
tspindler: What about using the long overdue status for the "billed" features since there is already an a/t for that? |
| 11:40 |
tspindler |
i wasn't sure if the value in the name field "lost" is critical for the action trigger |
| 11:41 |
Bmagic |
tspindler: Changing the name has no affect, it's addressed by ID in the software |
| 11:41 |
tspindler |
kmlussier: we don't have that turned on but what would be the sequence? right now we have "mark items lost" action trigger and then the billing notices generated |
| 11:41 |
kmlussier |
tspindler: My understanding is that long overdue acts exactly as lost does, but it gives items a long overdue status instead of lost. |
| 11:41 |
tspindler |
Bmagic: thanks, my memory was wrong then because I thought there was some issue related to the name field |
| 11:42 |
kmlussier |
tspindler: But I was thinking it might be better to use that one, even if you changed the name, because then it would just be business as usual for those items you are manually marking as lost. |
| 11:42 |
Bmagic |
tspindler: I have recently been looking at this code and it's all addressed by the number not the name |
| 11:42 |
|
ldwhalen joined #evergreen |
| 11:50 |
tspindler |
thanks Bmagic |
| 11:50 |
* kmlussier |
waves to vanya |
| 11:50 |
Bmagic |
tspindler: np |
| 11:58 |
Bmagic |
Another question that Im not totally sure about. Does anyone know if the system will favor a title hold over a copy hold or visa versa? I understand that the holds are filled in the order received at the location of the item. |
| 11:59 |
csharp |
Bmagic: if it's a copy hold, only the targeted copy will fill the hold |
| 11:59 |
csharp |
we recommend that staff *only* place title holds unless they need a specific copy |
| 12:00 |
csharp |
our staff were using volume and copy holds in hopes of speeding things up (with the opposite effect in many cases) |
| 12:00 |
Bmagic |
csharp: I understand that, but who gets it first? Copy hold or title or it doesnt matter? |
| 12:01 |
csharp |
oh - I don't know off the top of my head |
| 12:01 |
csharp |
I've reviewed the code in detail before, but I don't remember |
| 12:01 |
Bmagic |
Example: 2 people have a hold on the system. One is for the title and one is on the copy. The exact copy is checked in that could fill either hold. Who gets it? |
| 12:02 |
csharp |
I think it would be the closest hold organizationally |
| 12:02 |
csharp |
i.e. as defined by the org proximity table |
| 12:03 |
Bmagic |
csharp: right, but if they were both in the same org |
| 12:03 |
Bmagic |
Doesnt it use the hold request date? |
| 12:07 |
|
jihpringle joined #evergreen |
| 12:18 |
|
AliceR joined #evergreen |
| 12:23 |
|
nhilton joined #evergreen |
| 12:45 |
jventuro |
Hi folks! Does anyone have any ideas about getting patron name to show up on the print out generated from the checkin screen? |
| 12:46 |
jventuro |
I tried %PATRON_FIRSTNAME% %PATRON_LASTNAME% under Line Item and I just get the code. |
| 12:50 |
tsbere |
That should work, though I dunno why you would want it in line item (that seems like a header/footer thing to me) |
| 12:50 |
tsbere |
Oh, wait, check *IN*? Probably no patron... |
| 12:52 |
tsbere |
jventuro: For more information, most of the %PATRON_whatever% aliases expect you to be in a patron context. Checkin isn't one, though there may be lineitem variants of those available. I just don't know what they are, if they exist. |
| 12:55 |
jventuro |
tsbere: Thanks. I thought that might be the case. I didn't see anything promising in the macros, but I'll keep digging. |
| 12:56 |
kmlussier |
gmcharlt: Given that the eg conference isn't guaranteed to get an Eventbrite sponsorship from year to year, do you see any issues with using something like https://wordpress.org/plugins/event-registration/ to handle conference registrations? |
| 12:58 |
gmcharlt |
kmlussier: no, assuming Conservancy doesn't specify an alternative; I'd also want enough advance warning to harden the website enough to handle ecommerce, even if it's mostly just passing stuff off to PayPal |
| 13:00 |
kmlussier |
gmcharlt: I'm chatting with Tony right now, and it sounds like they would be okay with it, but I'll keep them in the loop if we do it. |
| 13:00 |
gmcharlt |
great |
| 13:01 |
kmlussier |
gmcharlt: How much time is enough advanced warning? If I let you know after the next time the conference planning committee meets, would that be enough warning? |
| 13:01 |
gmcharlt |
kmlussier: yeah |
| 13:01 |
kmlussier |
gmcharlt: OK, thanks! |
| 13:04 |
|
julialima joined #evergreen |
| 13:11 |
|
sbrylander joined #evergreen |
| 13:30 |
phasefx |
gmcharlt: kmlussier: Evergreen FAQ's, are we looking to keep them on the wiki and just link to them more prominently? |
| 13:31 |
gmcharlt |
phasefx: I'd like them promoted to the main website |
| 13:31 |
phasefx |
so as a Page in wordpress? |
| 13:31 |
gmcharlt |
yeah |
| 13:31 |
phasefx |
sounds good |
| 13:31 |
gmcharlt |
thanks! |
| 13:31 |
phasefx |
do pages automatically get placed into the menu system? |
| 13:36 |
* phasefx |
will find out :) |
| 13:39 |
kmlussier |
phasefx: I don't think so. |
| 13:39 |
kmlussier |
I had to manually add one yesterday. |
| 13:40 |
kmlussier |
But I may have been doing things wrong. |
| 13:40 |
kmlussier |
phasefx: I don't know if you noticed, but we already have a menu entry for the FAQ, so I'm thinking the link would just need to be changed from the wiki FAQ to the new WP FAQ |
| 13:41 |
phasefx |
kmlussier: I did not notice, gracias |
| 13:42 |
|
dreuther joined #evergreen |
| 13:51 |
|
bbqben joined #evergreen |
| 13:54 |
|
buzzy joined #evergreen |
| 13:56 |
|
montgoc1 joined #evergreen |
| 13:57 |
bbqben |
Hi all - EOB meeting starting here in ~3 minutes. Cheers! |
| 13:59 |
|
abneiman joined #evergreen |
| 14:01 |
bbqben |
ok, here we go |
| 14:02 |
bbqben |
#startmeeting Evergreen Oversight Board Meeting, 16.10.14 |
| 14:02 |
pinesol_green |
Meeting started Thu Oct 16 14:02:07 2014 US/Eastern. The chair is bbqben. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:02 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 14:02 |
pinesol_green |
The meeting name has been set to 'evergreen_oversight_board_meeting__16_10_14' |
| 14:02 |
bbqben |
#topic introductions |
| 14:02 |
bbqben |
EOB members, please introduce yourself with #info |
| 14:02 |
RoganH |
#info RoganH = Rogan Hamby, SCLENDS |
| 14:02 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:02 |
montgoc1 |
#info montgoc1 = Chauncey Montgomery, Consortium of Ohio Libraries |
| 14:02 |
bbqben |
#info bbqben = Ben Hyman, BC Libraries Co-op |
| 14:02 |
yboston |
#info ysboston - Yamil Suarez - Berklee College of Music (EOB) |
| 14:03 |
abneiman |
#info abneiman - Andrea Buntz Neiman, Kent County (MD) Public Library |
| 14:03 |
bbqben |
hi all |
| 14:03 |
bbqben |
#topic Minutes / Actions from last meeting |
| 14:04 |
graced |
#info graced = Grace Dunbar, Equinox |
| 14:04 |
bbqben |
#info http://wiki.evergreen-ils.org/doku.php?id=governance:minutes:2014-9-18 |
| 14:05 |
bbqben |
looks like each of the actions is covered with agenda topics today. |
| 14:05 |
bbqben |
so, if no objections we'll move on |
| 14:05 |
bbqben |
hearing none... |
| 14:05 |
bbqben |
#topic Financial Report |
| 14:06 |
bbqben |
#info http://list.evergreen-ils.org/pipermail/eg-oversight-board/2014-October/000891.html |
| 14:06 |
bbqben |
gmcharlt ++ |
| 14:06 |
bbqben |
questions about finances? |
| 14:07 |
montgoc1 |
Thanks to Grace for the donation. |
| 14:07 |
csharp |
#info csharp = Chris Sharp, GPLS |
| 14:07 |
bbqben |
graced++ |
| 14:07 |
graced |
It's a worthy cause |
| 14:08 |
kmlussier |
graced++ |
| 14:08 |
RoganH |
graced++ |
| 14:08 |
bbqben |
ok, moving on then |
| 14:09 |
bbqben |
#topic Evergreen 2015 Conference Report |
| 14:09 |
bbqben |
buzzy - thanks for joining us today! |
| 14:09 |
buzzy |
no problem. thanks for having me! buzzy nielsen, hood river county library district (in the sage library system) |
| 14:09 |
kmlussier |
Welcom buzzy! |
| 14:10 |
bbqben |
what's new in "the hood"? |
| 14:10 |
buzzy |
the 2015 conference will be held may 13-16 at the hood river inn (http://hoodriverinn.com/) |
| 14:10 |
csharp |
bbqben++ |
| 14:10 |
buzzy |
yes, our area really looks like that |
| 14:10 |
csharp |
yay! |
| 14:10 |
buzzy |
the committee has started work, although if anyone else wants to join, we'd welcome the help |
| 14:11 |
bbqben |
buzzy++ |
| 14:11 |
buzzy |
i'm going to be sending the EOB a conference budget next week, and the venue agreement should begin finalization the following week with the SFC |
| 14:12 |
bbqben |
great to hear the planning is moving along |
| 14:12 |
buzzy |
we're excited to have everyone come out. hood river is a much smaller community than has hosted the conference in the past, but we believe people will nonetheless have a good time, and likely will want to stay afterward for some vacation time |
| 14:12 |
buzzy |
questions? |
| 14:13 |
bbqben |
buzzy - do you prefer Double Mountain or Full Sailing brewing? |
| 14:13 |
kmlussier |
No questions, but I just wanted to mention to the rest of the board that we should probably do the budget vote via e-mail once buzzy sends it so that the SFC can start working on the agreement ASAP. |
| 14:13 |
buzzy |
i feel like a bad columbia river gorge resident for saying this, but i like neither beer nor wine. |
| 14:14 |
buzzy |
however, we did have a craft distillery just open up: camp 1805. quite good |
| 14:14 |
kmlussier |
Sounds like the perfect place for a good pub crawl. :) |
| 14:14 |
buzzy |
definitely. we've also had several hard cideries open up in the last year |
| 14:15 |
bbqben |
ooh - craft distillery. Excellent. ...impressed with the number of microbrews in the region (now I'll stop being distracted) |
| 14:15 |
|
julialima joined #evergreen |
| 14:15 |
julialima |
hello evergreeners |
| 14:15 |
buzzy |
we love our alcohol in the pnw |
| 14:15 |
bbqben |
we'll watch for budget news from you. Other questions for buzzy? |
| 14:15 |
RoganH |
buzzy: I'm a big fan of card ciders so I'm definitely interested in that. :) |
| 14:15 |
kmlussier |
julialima: Hi! We're in the middle of a meeting right now, but if you stick around, we should be wrapping up in about 45 minutes. |
| 14:15 |
csharp |
buzzy++ |
| 14:16 |
graced |
buzzy++ thanks for the update! |
| 14:16 |
kmlussier |
buzzy++ |
| 14:16 |
bbqben |
buzzy++ look forward to hearing more from you in the coming months |
| 14:16 |
buzzy |
np. you'll be hearing from me next week |
| 14:17 |
bbqben |
ok, moving on |
| 14:17 |
bbqben |
#topic Evergreen 2.7 RM report |
| 14:17 |
bbqben |
but methinks "other ben" is AWOL |
| 14:18 |
yboston |
was Ben traveling this week? |
| 14:18 |
kmlussier |
yboston: No, I don't think he leaves until Friday. |
| 14:18 |
yboston |
oh |
| 14:18 |
bbqben |
#action supplemental EG2.7 RM report by email, if possible - bshum |
| 14:19 |
bbqben |
#topic SFC update (emergency fund) |
| 14:19 |
bbqben |
So, I emailed Karen S @ SFC on the 10th as follow up to the conversation that kmlussier and I had with her in August. No response yet, but I'll keep us posted |
| 14:20 |
bbqben |
hopefully we'll have something back to discuss for our next mtg |
| 14:21 |
bbqben |
ok, if no q's, let's move to yboston's update |
| 14:21 |
bbqben |
#topic Evergreen web FAQ development |
| 14:22 |
bbqben |
yamil - thanks for fleshing things out! |
| 14:22 |
yboston |
I sent to the board list me draft |
| 14:22 |
yboston |
http://list.evergreen-ils.org/pipermail/eg-oversight-board/2014-October/000893.html |
| 14:22 |
yboston |
*my |
| 14:22 |
yboston |
this is just a start, questiosn are not in any particular order |
| 14:23 |
montgoc1 |
Order looks logical to me. |
| 14:23 |
yboston |
feel free to bring up some comments or questions now, or reply to the thread |
| 14:23 |
kmlussier |
yboston: I think I could come up with some more questions to ask when hiring a vendor for development. |
| 14:23 |
yboston |
one next step to take is to put this draft on a wiki page so others can make cahnges |
| 14:23 |
* kmlussier |
could probably create an entire wiki page on that topic alone. :) |
| 14:24 |
yboston |
on the other hand, I don't want to make the FAQ too long |
| 14:24 |
yboston |
we could create a seperate docuemnt for a template of questions |
| 14:24 |
graced |
I cna also think of a few things to add... Our challenge will likely be to make it useful without being overwhelming. |
| 14:24 |
bbqben |
#action shift draft FAQ's to wiki - yboston |
| 14:24 |
kmlussier |
yboston: Don't worry. I could come up with a shortened list. |
| 14:24 |
yboston |
also, at some point I would like feedback from the community at large, speccially from vendors |
| 14:25 |
bbqben |
yboston++ a great start here, I think |
| 14:25 |
yboston |
graced: any suggestions from you? |
| 14:25 |
yboston |
(as a vendor) |
| 14:26 |
kmlussier |
yboston++ indeed! |
| 14:26 |
graced |
Gosh... yes, but I think you've got a great start |
| 14:26 |
graced |
yboston++ |
| 14:26 |
yboston |
muchas gracias |
| 14:27 |
bbqben |
#action all to hop in with expanded & shortened ideas for the FAQ |
| 14:27 |
csharp |
yboston++ |
| 14:27 |
bbqben |
but no sentence fragments or dangling participles |
| 14:27 |
montgoc1 |
yboston++ |
| 14:27 |
bbqben |
ok, moving on |
| 14:28 |
bbqben |
#topic code of conduct - procedures |
| 14:28 |
bbqben |
kmlussier - over to you |
| 14:29 |
kmlussier |
#link http://list.evergreen-ils.org/pipermail/eg-oversight-board/2014-October/000894.html |
| 14:29 |
kmlussier |
I would like to see if we can pull together some good procedures for handling code of conduct complaints before the next conference. |
| 14:30 |
* gmcharlt |
gives a hearty +1 to that |
| 14:30 |
kmlussier |
In addition to the link to the Geek Feminism wiki I shared in the e-mail, dbs just shared with me some procedures from another conference we might be able to use as a model. |
| 14:30 |
kmlussier |
https://github.com/python/pycon-code-of-conduct/ |
| 14:31 |
kmlussier |
My hope is that we never have to handle a complaint, but if we do, I would like to see that we have people on hand who know how to properly respond to it. |
| 14:31 |
* csharp |
agrees |
| 14:31 |
RoganH |
I'm in agreement. |
| 14:32 |
bbqben |
kmlussier thanks for the think on this. Certainly has implications for conference planning, I think (e.g. - securing a private space for incident debrief etc) |
| 14:32 |
RoganH |
I think it's nice to have an anti-harassment policy but we need to be prepared to follow through with it. And this is part of that. |
| 14:32 |
gmcharlt |
it also has consequences for the EOB itself, as the potential exists for issues to span the lifetime of a single conference |
| 14:33 |
gmcharlt |
span *past* the lifetime, I should say |
| 14:33 |
kmlussier |
bbqben: Yes, it does. I can follow through with buzzy to see if we have anything like that this year, but, in upcoming years, maybe it needs to be included in site requirements when doing the conference selection process. |
| 14:34 |
RoganH |
Even if we can't create ideal spaces this year, at least an awareness of the space needs puts in a better place. |
| 14:34 |
bbqben |
kmlussier++ |
| 14:34 |
kmlussier |
Anyone want to help me draft our procedures? |
| 14:34 |
abneiman |
kmlussier : I'm interested in this |
| 14:34 |
kmlussier |
abneiman++ Thanks! |
| 14:34 |
* gmcharlt |
is as well |
| 14:35 |
RoganH |
I'm willing. |
| 14:35 |
csharp |
kmlussier: I'm willing to help |
| 14:35 |
montgoc1 |
Me too. |
| 14:35 |
bbqben |
hot topic! |
| 14:35 |
RoganH |
Since you have plenty of offers I'll withdraw mine :) |
| 14:35 |
kmlussier |
Sounds like we have a committee! :) |
| 14:35 |
kmlussier |
RoganH: That's okay. I'm sure I'll have a chance to hit you up for something else. |
| 14:35 |
bbqben |
#action kmlussier et al to develop sagacious draft procedures asap |
| 14:37 |
bbqben |
one q re: budget - if we agree this is a project-wide element, would we cover, e.g. training costs at the Project level or the conference budget level? |
| 14:37 |
bbqben |
I don't think we need the answer, like now, but maybe back of mind as we build to "the Hood" |
| 14:38 |
kmlussier |
bbqben: I think it would be worth the expense. FWIW, I think the Ada Initiative offer for training by phone was at no cost. |
| 14:39 |
bbqben |
kmlussier - totally agree it would be worth the cost and additionally awesome that the Ada training is free |
| 14:40 |
bbqben |
any other thoughts / q's for kmlussier for now? |
| 14:40 |
abneiman |
Would be nice if someone in the community has counseling (or similar) background |
| 14:40 |
abneiman |
(to be involved in any potential response, that is) |
| 14:41 |
montgoc1 |
abneiman: good point. |
| 14:41 |
montgoc1 |
We could recruit on the listserv perhaps. |
| 14:42 |
kmlussier |
abneiman: After we get the procedures together, maybe we can put the question out to the community to see if anyone has that background who also is willing to help out. |
| 14:43 |
bbqben |
ok, sounds great. Thanks all for the volunteerism! |
| 14:43 |
bbqben |
Any new business or additional topics? |
| 14:43 |
kmlussier |
Where are we on the vendor listing policy? |
| 14:44 |
bshum |
#info bshum = Ben Shum, Bibliomation (late arrival) |
| 14:44 |
bbqben |
kmlussier I think we're at fleshing out the FAQ's first and foremost |
| 14:44 |
bbqben |
this was the element on which we achieved consensus. |
| 14:45 |
kmlussier |
OK, at some point I think some kind of clarification needs to be made since there is confusion over what the existing policy says. |
| 14:45 |
kmlussier |
I'm happy to put it off until the next meeting. |
| 14:46 |
csharp |
I'll make a motion |
| 14:47 |
csharp |
I move that we change the wording "Evergreen offering page" to "company website" |
| 14:47 |
kmlussier |
I'll second that motion. |
| 14:47 |
csharp |
so that the full sentence reads: Show support for the Evergreen community by adding a visible link on their company website to the Evergreen community web site at http://evergreen-ils.org |
| 14:48 |
bshum |
+1 |
| 14:48 |
|
julialima_ joined #evergreen |
| 14:48 |
bbqben |
any concerns about the proposed motion? |
| 14:49 |
kmlussier |
I went back to re-read the original discussion, and I believe that was the intent of the policy when it was originally voted. |
| 14:50 |
bbqben |
kmlussier - jives with my fading memory / recollection also |
| 14:50 |
csharp |
Slight wording variation to prevent "website" vs. "web site" awkwardness: Show support for the Evergreen community by adding a visible link on their company website to the Evergreen community site at http://evergreen-ils.org |
| 14:50 |
bbqben |
so, standby for fingers / vote, with csharp's amendment |
| 14:51 |
csharp |
vote now? |
| 14:51 |
csharp |
(sorry) |
| 14:51 |
bbqben |
#startvote Vote Show support for the Evergreen community by adding a visible link on their company website to the Evergreen community site at http://evergreen-ils.org? Yes, No, Abstain |
| 14:51 |
pinesol_green |
Begin voting on: Vote Show support for the Evergreen community by adding a visible link on their company website to the Evergreen community site at http://evergreen-ils.org? Valid vote options are Yes, No, Abstain. |
| 14:51 |
pinesol_green |
Vote using '#vote OPTION'. Only your last vote counts. |
| 14:52 |
csharp |
#vote Yes |
| 14:52 |
montgoc1 |
#vote Yes |
| 14:52 |
RoganH |
#vote yes |
| 14:52 |
graced |
#vote Yes |
| 14:52 |
yboston |
#vote yes |
| 14:52 |
kmlussier |
#vote yes |
| 14:52 |
bshum |
#vote yes |
| 14:52 |
bbqben |
#vote Yes |
| 14:52 |
abneiman |
#vote yes |
| 14:53 |
bbqben |
#endvote |
| 14:53 |
pinesol_green |
Voted on "Vote Show support for the Evergreen community by adding a visible link on their company website to the Evergreen community site at http://evergreen-ils.org?" Results are |
| 14:53 |
pinesol_green |
Yes (9): kmlussier, yboston, bbqben, graced, RoganH, montgoc1, csharp, bshum, abneiman |
| 14:53 |
* kmlussier |
can update the policy wiki page with the change. |
| 14:53 |
bbqben |
kmlussier++ |
| 14:54 |
bbqben |
any additional new business (bshum will provide his update via email)? |
| 14:55 |
bbqben |
if none, then I look forward to our 20.11.14 meeting |
| 14:55 |
bbqben |
going once .... |
| 14:56 |
bbqben |
#endmeeting |
| 14:56 |
pinesol_green |
Meeting ended Thu Oct 16 14:56:09 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 14:56 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-16-14.02.html |
| 14:56 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-16-14.02.txt |
| 14:56 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-16-14.02.log.html |
| 14:56 |
csharp |
bbqben++ |
| 14:56 |
abneiman |
bbqben++ later, all |
| 14:56 |
kmlussier |
bbqben++ |
| 14:56 |
montgoc1 |
bbqben++ |
| 14:56 |
graced |
bbqben++ |
| 14:57 |
julialima_ |
well now that the meeting has ended... hello again to everybody jaja |
| 14:57 |
yboston |
bbqben++ |
| 14:57 |
kmlussier |
julialima_: Hi! Welcome! |
| 14:58 |
bbqben |
julialima_ thanks for your patience. cheers! |
| 14:58 |
julialima_ |
:) |
| 14:58 |
phasefx |
gmcharlt: kmlussier: FAQ's are up. I tweaked the bit that talked about org units to not use the word "org units" ;) |
| 14:58 |
gmcharlt |
phasefx++ |
| 14:58 |
julialima_ |
I am participating for the OPW, for the UI project, I've almost finished my contribution... you can see it here: http://wiki.evergreen-ils.org/doku.php?id=opw:ui_suggest:julialima |
| 14:59 |
julialima_ |
but now i am a little lost |
| 14:59 |
julialima_ |
because i want to apply and I have to propose a project timeline and so on |
| 15:01 |
julialima_ |
in the Gnome OPW main page sais that i have to discuss it here |
| 15:02 |
kmlussier |
julialima_: Have you started to write up a timeline? |
| 15:04 |
julialima_ |
no i havent |
| 15:04 |
julialima_ |
i have been working on my contribution only |
| 15:05 |
julialima_ |
it is almoistg finished |
| 15:06 |
julialima_ |
and i have to provide futher information about the project i will be working on... the UI style guide project idea proposed in the opw evergreen main page |
| 15:11 |
kmlussier |
berick and graced might have some other ideas to share, but there are some things that come to mind in doing a timeline for the UI project. |
| 15:13 |
julialima_ |
I've just wrote to them |
| 15:13 |
kmlussier |
Since we're working on the web client project at the same time, it might be nice if the timeline somehow aligns with the timeline for that development project. So maybe some of the recommendations you identify in the style guide might be implemented in the client in one of the development sprints. |
| 15:14 |
kmlussier |
graced is probably the best person to talk to about the timeline for that project. |
| 15:14 |
julialima_ |
mmm do you mean the improvments I've proposed for my contrubtion... that would be great |
| 15:14 |
kmlussier |
But I think you would want to incorporate time for learning about the client, how it's used, getting user feedback. |
| 15:15 |
kmlussier |
julialima_: I'm thinking more along the lines of whatever comes out of the style guide. |
| 15:16 |
julialima_ |
aaah ok.. yes... I understand |
| 15:16 |
kmlussier |
And maybe outlining what would be the best way to get that feedback. |
| 15:16 |
julialima_ |
so the thing is to align whatever comes out of the UI style guide with the development team times |
| 15:17 |
julialima_ |
nice |
| 15:17 |
kmlussier |
julialima_: I personally think that would be nice. But I guess it depends on how the timing lines up. Either way, I would love to see anything coming out of a style guide is eventually implemented in the client. |
| 15:18 |
julialima_ |
:) |
| 15:18 |
kmlussier |
As far as your work to create the style guide, I guess I would recommend trying to split up the work into manageable chunks so that there is something you can show for your work every few weeks. |
| 15:19 |
julialima_ |
yes that's a great idea... so I can get quick feedback from the development team! |
| 15:20 |
dbwells |
julialima_: Just my two cents, but I wouldn't stress about the timeline too much. You have an excellent proposal, and the timeline probably won't make or break it. Anything reasonable with some sort of milestones (manageable chunks, as kmlussier said) will be fine. |
| 15:22 |
kmlussier |
julialima_: You might also want to just come up with a draft, even if it's broad, and run it by the project mentors or even by those of us in IRC. I tend to give better feedback when I have something to react to. :) |
| 15:22 |
kmlussier |
dbwells++ |
| 15:23 |
julialima_ |
mmm ok... the thing is I am a little confused right now... At the begining I believed that the project details like the timeline would be somehow provided by the mentors... I think now I understand a little better... I have to make a proposal of how I will develop the UI style guide... Is that correct? |
| 15:23 |
julialima_ |
that's why I was asking all this... @.@ |
| 15:26 |
kmlussier |
julialima_: Yes, exactly. The proposal is how you would develope the style guide, but if you had other ideas on what you wanted to do, I think that's something you could discuss with your mentors. |
| 15:27 |
kmlussier |
And the timeline is something that you can work with assistance/feedback from your mentors. |
| 15:28 |
kmlussier |
julialima_: Is that helpful? |
| 15:29 |
julialima_ |
yes... thank you so much |
| 15:29 |
julialima_ |
I will try to make contact with bill and grace |
| 15:29 |
julialima_ |
here in the IRC channel... if I cant find them I will wrote a mail to them |
| 15:30 |
julialima_ |
thanks again Kathy, you are awesome :P |
| 15:30 |
kmlussier |
julialima_: Thank you! There was a lot of positive feedback to your ideas when berick shared them at last week's developer meeting. :) |
| 15:32 |
julialima_ |
wow! .. that's great to hear that... I was a little scared, and I put the best of me on that contribution |
| 15:32 |
|
dreuther_ joined #evergreen |
| 15:41 |
phasefx |
yboston: I tweaked the vendor FAQ for "hosting" |
| 15:42 |
yboston |
phasefx: cool, forgot abouot hosting |
| 15:45 |
yboston |
phasefx: feel free to add questions that vendors would have for customers, I tried to think of what a vendor would want |
| 15:48 |
|
wsmoak joined #evergreen |
| 15:49 |
phasefx |
yboston: thanks man, I may be a bit bold with some more edits, but it's a wiki, so we can revert if needed :) |
| 16:08 |
|
sandbergja joined #evergreen |
| 16:11 |
gsams |
question on an oddity I found in the database just now. In the actor.usr_setting table, the values for opac.hold_notify seem odd. |
| 16:12 |
gsams |
I see some with colons in the text, and some with pipes |
| 16:12 |
gsams |
would this cause any problems, is there a specific way this should be appearing? |
| 16:13 |
gsams |
for example, I see "phone|sms" and "phone:sms" entries |
| 16:15 |
kmlussier |
phasefx++ #FAQ page |
| 16:35 |
|
dreuther joined #evergreen |
| 16:44 |
bshum |
gsams: I have both variants in my database as well. I'll just assume that it's just a slightly different way of expressing the same idea |
| 16:44 |
bshum |
gsams: Perhaps a pre-2.0 thing when the new patron editor came along |
| 16:45 |
bshum |
I'm not sure if there's any functional differences, or if one or the other is broken. |
| 16:45 |
bshum |
Or maybe it's one way of saving vs. another |
| 16:45 |
gsams |
bshum: that'll work for me, thanks for looking at it |
| 17:23 |
csharp |
gsams: bshum: I believe one "style" is from the opac and the other "style" is from the staff client (or if you ever had it, JSPAC) |
| 17:23 |
bshum |
csharp: I could see that too. |
| 17:24 |
csharp |
Terran and I ran into that when she created code for the KPAC to account for notification prefs |
| 17:30 |
bshum |
Aha, csharp++ |
| 17:35 |
gsams |
csharp: interesting, thanks for the insight there. |
| 17:35 |
gsams |
csharp++ |
| 17:35 |
gsams |
bshum++ |
| 17:40 |
Bmagic |
I have a hold question - A title has 6 copies, 5 copies at my library all checked out and 1 copy at another system that is available. All copies are age protected. I place a hold on the title and I get blocked "item is too new to transit this far". Why can't I put a hold on the title and wait in line for the copies at my library? |
| 17:46 |
|
dreuther_ joined #evergreen |
| 18:03 |
vanya |
Hi! Jason had asked me to add the awesome tags based UI option in the UI suggestions. Can anyone tell me how to make an entry in the wiki page ( I'm not being able to sign up) |
| 18:21 |
|
b_bonner_ joined #evergreen |
| 18:22 |
|
mrpeters1 joined #evergreen |
| 18:41 |
|
dreuther joined #evergreen |
| 19:00 |
|
nhilton_ joined #evergreen |
| 19:16 |
csharp |
Bmagic: I believe the "PLACE_UNFILLABLE_HOLD" perm allows a user to place a hold *anyway* on an bib with no eligible copies |
| 23:22 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 23:44 |
|
buzzy joined #evergreen |
