| Time |
Nick |
Message |
| 01:04 |
|
mnsri joined #evergreen |
| 01:25 |
|
mnsri joined #evergreen |
| 02:39 |
jeff |
hrm. in 2.5 i'm seeing bibs with located URIs appear in the staff client probably due to the nature of them being "no copies attached anywhere" bibs. |
| 03:13 |
|
DPearl joined #evergreen |
| 03:49 |
|
DPearl joined #evergreen |
| 04:03 |
bshum |
jeff: 2.5 before or after fix for https://bugs.launchpad.net/evergreen/+bug/925776 went in? |
| 04:03 |
pinesol_green |
Launchpad bug 925776 in Evergreen "located URIs appear in staff client OPAC searches regardless of $9's" (affected: 8, heat: 46) [Medium,Fix committed] |
| 04:04 |
bshum |
That was backported to rel_2_5 but maybe it isn't fully fixed or something.... |
| 04:56 |
|
DPearl1 joined #evergreen |
| 07:14 |
|
sarabee joined #evergreen |
| 07:23 |
jeff |
bshum: likely 2.5 before that fix. i was going to dig this morning into the recent 856-related bugs. thanks! |
| 07:23 |
* jeff |
is at work early |
| 07:32 |
|
wsmoak joined #evergreen |
| 07:32 |
|
wsmoak joined #evergreen |
| 07:44 |
|
collum joined #evergreen |
| 07:57 |
|
jboyer_isl joined #evergreen |
| 07:59 |
|
rjackson-isl joined #evergreen |
| 08:17 |
|
akilsdonk joined #evergreen |
| 08:21 |
|
DonB joined #evergreen |
| 08:24 |
|
DonB left #evergreen |
| 08:28 |
|
Shae joined #evergreen |
| 08:34 |
|
DonB joined #evergreen |
| 08:40 |
|
Dyrcona joined #evergreen |
| 08:43 |
|
mdriscoll joined #evergreen |
| 08:48 |
|
mrpeters joined #evergreen |
| 08:48 |
|
tspindler joined #evergreen |
| 08:48 |
|
mmorgan joined #evergreen |
| 08:52 |
|
ericar joined #evergreen |
| 08:52 |
|
ericar left #evergreen |
| 08:54 |
|
Dyrcona joined #evergreen |
| 08:58 |
|
DPearl left #evergreen |
| 09:08 |
Dyrcona |
bshum++ |
| 09:09 |
Dyrcona |
I'm guessing it was he who updated the 2.7 series milestones while I was looking at it for my report to the executive committee next week. |
| 09:09 |
Dyrcona |
Does this mean that beta 1 is being released today? |
| 09:15 |
csharp |
@eightball Are betas gonna... beta? |
| 09:15 |
pinesol_green |
csharp: Obviously. |
| 09:16 |
berick |
heh |
| 09:21 |
|
DPearl joined #evergreen |
| 09:21 |
csharp |
wow - SSDs, where have you been all my (Evergreen-administering) life? |
| 09:22 |
csharp |
based on my initial tests, our upgrades will cease to need multiple day-long downtimes |
| 09:24 |
bradl |
ssd++ |
| 09:25 |
bradl |
csharp: what's your setup? /me gets a coke and a moonpie and sits in the rocking chair, awaiting |
| 09:25 |
csharp |
heh |
| 09:26 |
csharp |
we have 3 Dell R815s with 512 GB RAM and 4 480 GB SLC SSDs in RAID5 (I think) |
| 09:27 |
csharp |
with a 4th identical server for prototyping and testing |
| 09:27 |
|
kmlussier joined #evergreen |
| 09:27 |
csharp |
oh, and 64 cores |
| 09:28 |
csharp |
it's really kind of crazy |
| 09:28 |
bradl |
hmm, even with RAID-5, which is probably one of the worst I/O performant schemes |
| 09:28 |
csharp |
it may be another scheme - awitter set it up |
| 09:29 |
bradl |
well, that's awesome |
| 09:29 |
csharp |
it's seriously smokin' |
| 09:31 |
bradl |
we've been getting Dells lately, too, and have been happy with them |
| 09:31 |
csharp |
yeah - doing the same type of thing with HP was cost-prohibitive for us |
| 09:31 |
kmlussier |
G'morning! |
| 09:31 |
bradl |
yeah, we also found HPs to be a good bit higher. Funny. |
| 09:32 |
csharp |
that and their "no firmware updates without a contract BS" have left a bad taste in my mouth |
| 09:32 |
bradl |
oh yeah |
| 09:33 |
csharp |
s/BS"/" BS/ |
| 09:34 |
bradl |
haha |
| 09:35 |
csharp |
:-) |
| 09:37 |
|
yboston joined #evergreen |
| 09:40 |
eeevil |
csharp: either placement works -- a modifier to their concept of "contract" seems as fair as a statement of opinion on the situation as a whole ;) |
| 09:42 |
csharp |
eeevil++ |
| 09:43 |
* dbs |
assumes the RAID config is really RAID10 |
| 09:44 |
dbs |
The big question is: is the hardware setup still costing less than the equivalent legacy proprietary software would require? |
| 09:45 |
csharp |
dbs: absolutely in our case |
| 09:45 |
bradl |
I suspect with the falling cost of hardware, the ratio is probably even better today |
| 09:46 |
csharp |
I don't have numbers from the old days, but I still think we haven't spent more since 2005 on PINES hardware than they did on the single S**SI server |
| 09:48 |
|
mllewellyn joined #evergreen |
| 09:48 |
dbs |
Excellent. It would be cool to see a follow-up article for the tenth anniversary |
| 09:48 |
dbs |
(where "article" == "blog post") :) |
| 10:07 |
|
mdriscoll joined #evergreen |
| 10:09 |
bshum |
csharp: As you explore I'll be curious to see what tuning choices you make in postgresql.conf |
| 10:09 |
bshum |
I'm not 100% satisfied that I haven't missed something critical yet. |
| 10:09 |
csharp |
bshum: sure thing - if you have advice from your experience so far, please let me know ;-) |
| 10:10 |
bshum |
csharp: I've been reading about adjusting random_page_cost lower. |
| 10:13 |
|
mmorgan joined #evergreen |
| 10:28 |
bshum |
As I work on the upgrade script for 2.7-beta I am uncertain but I think that it's not really intended for them to process alpha to beta right? Just build script from 2.6 to 2.7? |
| 10:29 |
|
hthepas joined #evergreen |
| 10:31 |
|
mllewellyn joined #evergreen |
| 10:32 |
berick |
bshum: yeah, 2.6 to 2.7 |
| 10:32 |
bshum |
Okie dokie. |
| 10:32 |
* bshum |
is behind schedule but generally commits (haha) to getting it out today then. |
| 10:32 |
Dyrcona |
bshum++ |
| 10:51 |
Bmagic |
ssd++ |
| 10:54 |
|
jeff_ joined #evergreen |
| 10:57 |
|
gmcharlt joined #evergreen |
| 11:04 |
|
kakes joined #evergreen |
| 11:05 |
Bmagic |
I would like to get a general idea of how a metabib decides to include which source bibs. Is it just the normalized title making the fingerprint and matching on that? |
| 11:05 |
bshum |
Bmagic: So there should be a trigger or function that's called to generate the fingerprint for each bib record |
| 11:05 |
bshum |
I think it's based on title + author |
| 11:06 |
bshum |
But only like part of the title, like 245 subfield a |
| 11:06 |
|
krvmga joined #evergreen |
| 11:07 |
* bshum |
looks in the database |
| 11:08 |
|
bmills1 joined #evergreen |
| 11:10 |
eeevil |
there's a table (in modern EG) that defines fingerprint parts |
| 11:10 |
jboyer_isl |
It’s determined by xpath entries in config.biblio_fingerprint, ordered by format and then id. Our db only has entries for title and author (in that order). |
| 11:10 |
Bmagic |
ah |
| 11:11 |
Bmagic |
we just have the defaults I'm sure |
| 11:12 |
Bmagic |
so it normalizes the title and author, and concat's them, violla: fingerprint |
| 11:12 |
jboyer_isl |
Looks like. |
| 11:13 |
bshum |
Yes, that's it. |
| 11:13 |
jboyer_isl |
eeevil, there’s been some interest in tighting-up how metarecords are grouped, other than a reingest (at least?) is there anyhting that would be effected by adding fingerprinter entries? |
| 11:13 |
jboyer_isl |
(interest locally that is) |
| 11:20 |
|
vlewis joined #evergreen |
| 11:20 |
eeevil |
jboyer_isl: MRs are the only thing using fingerprints today. a we could certainly be devised to update those without a reingest, I think, then you'd just use ye olde quick_metarecord_map.sql |
| 11:21 |
eeevil |
er, "a way", not "a we" |
| 11:22 |
* krvmga |
just thought that was your scots accent coming through |
| 11:25 |
bshum |
eeevil: Interesting. :) |
| 11:25 |
jboyer_isl |
That sounds great. I was worried that we might subtlely (or very much not so) effect other aspects of the catalog by changing the way they’re made. I’ll have to bang on our dev server and see what it looks like. |
| 11:26 |
eeevil |
Gotta save the wee turtles! |
| 11:28 |
tsbere |
A very quick look at things seems to say that all you have to do is update biblio.record_entry, fingerprint generation doesn't depend on reingest or even marc changing. So "update biblio.record_entry set fingerprint = '' where not deleted" or something like that should cause the trigger to override the empty string with the new fingerprint |
| 11:28 |
|
ericar joined #evergreen |
| 11:30 |
* tsbere |
will admit to possibly missing something on that front, though, as he just looked at biblio.record_entry |
| 11:31 |
|
jwoodard joined #evergreen |
| 11:32 |
|
collum|2 joined #evergreen |
| 12:02 |
|
akilsdonk joined #evergreen |
| 12:07 |
bshum |
Hmm |
| 12:08 |
bshum |
Would it make sense to prefix the sample RELEASE_NOTE_TEMPLATE.txt file with a leading _ so that it doesn't get picked up and swept into the Miscellaneous section by the create_release_notes.sh script? |
| 12:08 |
bshum |
Or would it be better to just teach the script to ignore that file? |
| 12:09 |
bshum |
Any strong opinions on that before I just pick one? |
| 12:10 |
kmlussier |
Speaking of release notes, I just remembered that my message still hasn't made it to the DIG list. csharp, should I just try re-sending it? |
| 12:10 |
csharp |
kmlussier: please re-send |
| 12:10 |
kmlussier |
I'm not ignoring your question, bshum, I just don't have a strong opinion. :) |
| 12:10 |
kmlussier |
csharp: OK, will do. |
| 12:10 |
csharp |
bshum: I think fixing the script is the best approach |
| 12:11 |
csharp |
(not that I've ever used that tool ;-)) |
| 12:12 |
kmlussier |
Thanks csharp. Looks like the re-send worked. |
| 12:12 |
* bshum |
contemplates it |
| 12:17 |
* mmorgan |
is still exploring money tables ... |
| 12:17 |
mmorgan |
How does money.billable_xact relate to action.circulation, or action.all_circulation? Do the ids always match? |
| 12:20 |
tsbere |
bshum: I didn't even *notice* that file when I recently added some release notes to my branches. >_> |
| 12:20 |
jboyer_isl |
That’s a parent table to action.circulation, booking.reservation, and money.grocery. So all 4 of those tables share the same sequence for Ids. That means your first circ could be 1, then if you create a grocery bill, that’s 2. (That’s also why action.circulation has an unrecovered field, which never made sense before looking this up.) |
| 12:21 |
bshum |
tsbere: I always use the RELEASE_NOTE_TEMPLATE.txt to help me lazy out the syntax for asciidoc appropriately. |
| 12:21 |
bshum |
Just make a copy to the directory |
| 12:21 |
jboyer_isl |
mmorgan: my previous reply was for you, but I am the slowest. |
| 12:21 |
tsbere |
bshum: I looked at another release note, not having seen the template file. |
| 12:25 |
mmorgan |
jboyer_isl: Thanks! I suspected the grocery was in there, but didn't even think about booking. |
| 12:31 |
|
jboyer_isl joined #evergreen |
| 12:35 |
bshum |
tsbere: Well I'll do that too if there's one in the directory to work off of too :) |
| 12:43 |
dbs |
kmlussier: well dang, I thought the release note for the sitemap builder was pretty much a complete set of documentation |
| 12:54 |
|
ericar joined #evergreen |
| 12:54 |
|
ericar left #evergreen |
| 12:56 |
bshum |
Preview compiled 2.7 notes, thus far: http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_7.html |
| 12:56 |
bshum |
I pushed a new branch http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/bshum/2.7-release-notes-compile which has some of the things I did to tweak things. |
| 12:57 |
bshum |
I'll push that up to master later on |
| 12:57 |
bshum |
Maybe after lunch. |
| 12:57 |
bshum |
Lunch is good. |
| 12:59 |
csharp |
jboyer_isl: "unrecovered" is related to a partially implemented PINES feature from days of yore |
| 12:59 |
csharp |
it refers to "unrecovered debt" that is written off after a specified amount of time |
| 13:03 |
|
jihpringle joined #evergreen |
| 13:07 |
|
wjr joined #evergreen |
| 13:16 |
kmlussier |
dbs: Heh, I think you're right. I'll put myself down for that one and basically just move what you have into the docs while I'm cleaning up the release notes. |
| 13:17 |
|
wjr joined #evergreen |
| 13:30 |
|
hbrennan joined #evergreen |
| 13:46 |
|
sseng joined #evergreen |
| 13:51 |
jboyer_isl |
csharp: I see. I assumed it was money related, but I didn’t know why it would be showing up in action.circulation (I hadn’t really paid attention to the parent/child table layout of those things until I was looking at it today) |
| 14:06 |
pinesol_green |
[evergreen|Ben Shum] Fixes for create_release_notes.sh - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=2b4c4fe> |
| 14:06 |
pinesol_green |
[evergreen|Ben Shum] Pre-2.7 Release notes cleanup - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e6c0559> |
| 14:06 |
pinesol_green |
[evergreen|Ben Shum] Compile release notes for Evergreen 2.7.0 - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e790815> |
| 14:09 |
mmorgan |
... so aged circulations don't appear in money.billable_xact? |
| 14:15 |
|
dkyle joined #evergreen |
| 14:23 |
jboyer_isl |
mmorgan: Looks like no. Data is inserted into action.aged_circulation after deletion, so there’s no way to find an old id from aged_circ and learn more about it. I assume (but haven’t checked) that something prevents you from deleting xacts that haven’t finished. |
| 14:25 |
mmorgan |
jboyer_isl: I can delete a patron that still owes money - with proper permission (not saying it's a good idea, but I can). The transaction id for the money owed is no longer in money.billable_xact. |
| 14:26 |
mmorgan |
but it's still referenced in other billing tables: billing, transaction_billing_summary to name a couple. |
| 14:27 |
mmorgan |
I'm trying to understand how these work for accurate reporting. |
| 14:28 |
jboyer_isl |
I see. In that case you can kind of reconnect it with joins on the xact field in those tables, but if that’s not in hte reporter somewhere it has to be done by hand. |
| 14:28 |
jboyer_isl |
I’ve disliked dealing with money reports long enough that I’m not that familiar with the sources. |
| 14:28 |
csharp |
jboyer_isl: totally with you there |
| 14:29 |
|
bmills1 joined #evergreen |
| 14:32 |
jboyer_isl |
mmorgan: I realize that’s not the most helpful reply. How far back are you planning to age circs away? |
| 14:34 |
mmorgan |
We have not aged circs, yet, and don't have immediate plans, but we have deleted patrons, and that ages their circs. |
| 14:34 |
mmorgan |
We will need to keep all this in mind when we consider aging circulations. |
| 14:35 |
mmorgan |
... and any replies are helpful :) |
| 14:35 |
|
kakes joined #evergreen |
| 14:36 |
mmorgan |
jboyer_isl++ |
| 14:39 |
|
chatley joined #evergreen |
| 14:43 |
kmlussier |
Heads up. The Evergreen for Academics meeting is going to start in about 15 minutes. |
| 14:45 |
|
rgagnon joined #evergreen |
| 14:46 |
yboston |
kmlussier: you beat me to the warning kmlussier++ |
| 14:47 |
kmlussier |
yboston: I actually gave the warning 2 minutes early so that I would beat you to the punch. ;) |
| 14:51 |
|
flewis joined #evergreen |
| 14:53 |
remingtron |
flewis: welcome to the channel! |
| 14:54 |
flewis |
remingtron: thanks. Giving it a try. |
| 14:56 |
|
terran joined #evergreen |
| 14:56 |
|
jforce-berklee joined #evergreen |
| 14:57 |
kmlussier |
It's nice to see so many new names in here. Welcome! |
| 14:58 |
terran |
Hi Kathy! |
| 14:59 |
* kmlussier |
waves at terran |
| 14:59 |
|
Christineb joined #evergreen |
| 14:59 |
Shae |
kmlussier: Kathy, just wanted to say hi. I'm hanging out to see what the academics have to say today :) |
| 15:00 |
kmlussier |
Shae: Excellent! :) |
| 15:00 |
kmlussier |
OK, it's meeting time. |
| 15:00 |
kmlussier |
#startmeeting 2014-08-14 - Evergreen for Academics meeting |
| 15:00 |
pinesol_green |
Meeting started Thu Aug 14 15:00:46 2014 US/Eastern. The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 15:00 |
pinesol_green |
The meeting name has been set to '2014_08_14___evergreen_for_academics_meeting' |
| 15:00 |
kmlussier |
#info Meeting agenda is available at http://wiki.evergreen-ils.org/doku.php?id=academics:2014-08-14 |
| 15:01 |
kmlussier |
#topic Introductions |
| 15:01 |
kmlussier |
Please introduce yourselves with the #info command. |
| 15:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 15:01 |
graced |
#info graced is Grace Dunbar, Equinox |
| 15:01 |
|
Kathy__ joined #evergreen |
| 15:01 |
mdriscoll |
#info mdriscoll is Martha Driscoll, NOBLE |
| 15:02 |
kakes |
#info Kelly Drake, FLO |
| 15:02 |
Shae |
#info Shae is Shae Tetterton, Equinox |
| 15:02 |
mmorgan |
#info mmorgan is Michele Morgan, NOBLE |
| 15:02 |
tspindler |
#info /me is Tim Spindler, C/W MARS |
| 15:02 |
yboston |
#info yboston - Yamil Suarez - Berklee |
| 15:02 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative |
| 15:02 |
Christineb |
#info Christineb is Christine Burns, BC Libraries Cooperative |
| 15:03 |
jforce-berklee |
#info jforce-berklee - Jenée Morgan Force - Berklee |
| 15:04 |
|
Kathy__ joined #evergreen |
| 15:04 |
kmlussier |
OK, people can continue introducing themselves as they come in, but let's move on to the next topic. |
| 15:04 |
kmlussier |
#topic Review the Evergreen for Academics Areas of Interest wiki page |
| 15:05 |
kmlussier |
#link http://wiki.evergreen-ils.org/doku.php?id=evergreen_for_academics |
| 15:06 |
kmlussier |
So yboston and kakes have spent a bit of time pulling this page together. Does it seem to cover the interest areas everyone has? |
| 15:06 |
tspindler |
I think so for us |
| 15:07 |
Kathy__ |
It does for us as well |
| 15:07 |
kakes |
So far, for us |
| 15:07 |
kakes |
Certainly seems like a good list to start with |
| 15:07 |
jihpringle |
one thing we've looked into in the past for our academics that I don't see listed is the booking module |
| 15:08 |
kakes |
By booking module do you mean things like room booking? |
| 15:08 |
kmlussier |
jihpringle: Yeah, I was thinking of booking the other day. Is that something you wanted to add to the list? |
| 15:09 |
jihpringle |
yes please, most of our academics have stopped using the current booking module because it doesn't meet their needs |
| 15:09 |
jihpringle |
kakes: yes, room and equiptment booking |
| 15:09 |
graced |
The booking module was originally development for an academic library that wanted to give professors the ability to "book" materials in advance for use in their classes. |
| 15:10 |
kakes |
What is the current status of the module? |
| 15:10 |
graced |
hasn't been touched since initial development I don't believe |
| 15:10 |
graced |
It works for what it was intended. |
| 15:11 |
graced |
But if I'm wrong about that, someone please correct me! |
| 15:11 |
yboston |
what version did it first apepar in? |
| 15:11 |
yboston |
*appear |
| 15:11 |
kmlussier |
graced: I think you're right about it not being touched since it was initially developed. |
| 15:11 |
jihpringle |
I think 2.0 |
| 15:11 |
graced |
yboston: it's been years... |
| 15:11 |
kmlussier |
I think it could be a nice feature with a little added functionality. |
| 15:12 |
yboston |
thanks jihpringle |
| 15:12 |
|
ElaineHardy joined #evergreen |
| 15:12 |
graced |
kmlussier: yes! It just needs some love. |
| 15:12 |
kmlussier |
I was thinking 1.6. It was a lightning talk at my first EG conference. :) |
| 15:12 |
graced |
I think it was 1.6. |
| 15:12 |
kmlussier |
kakes: Thank you for adding it to the matrix! |
| 15:12 |
gmcharlt |
#info Galen Charlton, ESI |
| 15:12 |
Shae |
it is very basic but allows for the creation of booking resources like rooms or equipment. then you add a reservation to a patron's account, much like a hold. there's a booking pull list and then you can check it out. I don't think it does any consideration of set up or cleanup ti me, which some might want. what other features are you guys looking for with booking? |
| 15:12 |
kakes |
not sure i should add the "love' part |
| 15:13 |
kmlussier |
Heh |
| 15:13 |
graced |
:) |
| 15:13 |
kmlussier |
OK, so building the list is the easy part. I think the difficulty is finding areas to focus on. |
| 15:14 |
jihpringle |
Shae: the main need our libraries identified was a calendar to see current and future bookings |
| 15:14 |
kmlussier |
Maybe we should be start by seeing if there is any work currently being done in any of these areas? |
| 15:14 |
kakes |
Now that it's on the list do we want to identify who is interested? |
| 15:14 |
Shae |
jihpringle: that makes sense |
| 15:15 |
kakes |
The idea of the matrix is to gather all the goals, identify who is interested and the difficulty of development |
| 15:15 |
dbs |
#info Dan Scott, Laurentian University |
| 15:15 |
kakes |
Sounds like BC is very interested |
| 15:15 |
kmlussier |
kakes: Should we go through each of these one by one? |
| 15:16 |
kakes |
I tried to put them in a logical order |
| 15:16 |
kakes |
so that would be a good idea |
| 15:16 |
yboston |
I am OK in going through these one by one, but we should decide who will update the wiki. That way we don't overwrite each other's work |
| 15:17 |
kakes |
yboston: if you want to that's fine |
| 15:17 |
yboston |
OK |
| 15:18 |
kmlussier |
OK. since we're already talking about booking, let's start there and then we'll jump to the top of the list. |
| 15:18 |
kakes |
Booking is a low priority for us |
| 15:19 |
kmlussier |
So it would be good to know who, outside of BC Libraries, is interested in seeing improvements in Booking. I dont know how specific we want to be on the goals at this juncture. |
| 15:19 |
Kathy__ |
UCN - booking is not a high priority for us |
| 15:19 |
tspindler |
Not a high priority at C/W MARS |
| 15:19 |
yboston |
I plan to only add those organizations that have high interest(?) |
| 15:19 |
yboston |
in each topic |
| 15:19 |
kmlussier |
yboston: Sounds like a good idea. |
| 15:20 |
jihpringle |
we're interested, but it's not a high priority for us at this time |
| 15:20 |
kmlussier |
I've heard some questions from academics on bookings, but I think there are other items on this list that might be higher in priority. |
| 15:20 |
yboston |
we can ask for other folks to chime in on the mailing list after the meeting |
| 15:21 |
kmlussier |
It sounds like there is enough level of interest in keeping booking on the list, but not a big priority at this point in time? |
| 15:21 |
yboston |
and I can update the list accordingly |
| 15:21 |
kakes |
yboston: agreed |
| 15:21 |
yboston |
quick suggestion, may I just list BC for booking at this early junction, then move on to the next goal? |
| 15:22 |
jihpringle |
sure |
| 15:22 |
kmlussier |
Does somebody want to take an action item to send a follow-up e-mail to the list to gauge interest in all of these issues? |
| 15:22 |
yboston |
I can do that |
| 15:23 |
kmlussier |
yboston++ |
| 15:23 |
kakes |
Seems like another idea might be to ask folks to prioritize the items in the list |
| 15:23 |
kmlussier |
#action yboston to e-mail list to gauge interest in development areas from people who could not make the meeting. |
| 15:24 |
kmlussier |
kakes: Yes, I think doing it oustide of the meeting gives people time to think about it before committing to priorities. |
| 15:24 |
kmlussier |
A simple prioritization scale where 1 is very important, 2 is somewhat important, and 3 is not important at all? |
| 15:25 |
kakes |
kmlussier++ |
| 15:25 |
jihpringle |
that sounds good to me |
| 15:25 |
yboston |
Like…. Booking | Berklee(3) |
| 15:25 |
yboston |
to make it more obvious each institutions priority |
| 15:26 |
kakes |
one other thing we're trying to gauge is how interested the institutions are in working on the development of the goal |
| 15:26 |
kmlussier |
Should we do it right on the wiki or maybe set up some kind of form. Or maybe a Google spreadsheet. |
| 15:26 |
kakes |
not sure how to get that into the matrix |
| 15:26 |
|
hthepas joined #evergreen |
| 15:26 |
kmlussier |
kakes: By working on the development, do you mean either contributing development time or money? |
| 15:27 |
kakes |
specing, as well as coding |
| 15:27 |
phasefx |
domain expertise |
| 15:27 |
yboston |
We can put the extra info in a seperate section or wiki page, so the main matrix does not get to complicated? |
| 15:27 |
kakes |
yboston: sounds good |
| 15:27 |
yboston |
*too complicated |
| 15:28 |
|
horganl joined #evergreen |
| 15:29 |
kakes |
It sounds like we are agreeing to rate the Goals offline? |
| 15:29 |
kmlussier |
OK, how about this? Whatever we use (wiki or spreadsheet) how about if we have a place where each institution can identify how high of a priority it is, but also add a place saying what they would be willing to contribute to make it happen. |
| 15:29 |
|
horganl_ joined #evergreen |
| 15:29 |
kmlussier |
It could be help in specing out the goals. Coding. And funding may need to come into play too. |
| 15:30 |
kmlussier |
kakes: Yes, I think doing it offline makes sense. |
| 15:31 |
kakes |
Ok. Being new to the community does it sound reasonable that this could be rated by the end of August? |
| 15:31 |
jihpringle |
do we want institutions to be saying what they can contribue? coding, funding, testing etc. |
| 15:31 |
|
hthepas joined #evergreen |
| 15:31 |
kmlussier |
jihpringle: Yes, that's what I was thinking. |
| 15:31 |
yboston |
jihpringle: I would like to see that |
| 15:31 |
kakes |
Before we can decide on coding and funding, don't we have to see what the current state is? |
| 15:31 |
yboston |
we could have the letter that we send out, have a sample format on what answers to provude for each goal |
| 15:31 |
jihpringle |
kakes: it would work better for us if it was sometime in September - quite a few the staff at our academics are on holidays right now |
| 15:31 |
yboston |
or we can use a google online form too |
| 15:32 |
kakes |
jihpringle: Sept should be fine and give us time to set up another meeting |
| 15:33 |
tspindler |
if you say you can support funding, how firm of a commitment is that? |
| 15:33 |
kmlussier |
kakes: I was thinking the "what we can contribute" part was not so much a firm commitment on a particular amount of money or time spent coding. I see it as a way to see if people are willing to contribute resources to making the goal happen. |
| 15:34 |
tspindler |
kmlussier: sounds good |
| 15:34 |
kakes |
We might need to clarify the goal before we could decide commitment |
| 15:34 |
kmlussier |
I'm guessing most people can't make a firm commitment to funding something until there are detailed specs and code in hand, but they might have an idea that it's a project their institution is willing to fund. |
| 15:35 |
kakes |
For instance Authorities management might mean different things to different libraries |
| 15:37 |
kmlussier |
OK, so let me take back what I just said. Instead of "are you willing to contribute resources", we have something that says "are you willing to work to flesh out the goal"? Is that what you had in mind kakes? |
| 15:38 |
kakes |
kmlussier: sounds good |
| 15:38 |
tspindler |
kmlusser ++ |
| 15:39 |
terran |
kmlussier++ |
| 15:39 |
mdriscoll |
kmlussier++ |
| 15:39 |
jihpringle |
kmlussier++ |
| 15:39 |
kmlussier |
OK, who wants to take the action item to set up something to collect this feedback? |
| 15:40 |
kakes |
yboston: could this be added to your form? |
| 15:40 |
yboston |
I think so, but I may want another collaborator just in case |
| 15:40 |
kakes |
I'm in but on vacation next week |
| 15:41 |
kmlussier |
I can help out too. |
| 15:41 |
kmlussier |
yboston: So you're thinking of a form? I think I like that idea better than a wiki page. |
| 15:41 |
yboston |
kmlussier & kakes: thanks |
| 15:41 |
yboston |
yes, I am thinking of a google form |
| 15:41 |
yboston |
then maybe making a recap simplified table on the wiki afterwards? |
| 15:41 |
kakes |
can I ++ google form? |
| 15:42 |
kmlussier |
#action yboston, kakes, kmlussier to work on a form where people can priortize goals on a scale of 1-3 and identify which areas they are willing to spec out further. |
| 15:42 |
kmlussier |
Does that capture what we just discussed? |
| 15:42 |
yboston |
I think so |
| 15:42 |
kmlussier |
kakes: Sure, you can ++ anything you like here. :) |
| 15:43 |
yboston |
authorities++ |
| 15:43 |
tspindler |
authorities ++ |
| 15:43 |
kakes |
authorities++ |
| 15:43 |
kmlussier |
@karma authorities |
| 15:43 |
pinesol_green |
kmlussier: Karma for "authorities" has been increased 2 times and decreased 1 time for a total karma of 1. |
| 15:44 |
kmlussier |
Looking at the agenda, we also had a piece on discussing the current state of any existing development or projects in this area. |
| 15:45 |
yboston |
we can send a letter ont he dev list to get feedback from devs on that |
| 15:45 |
yboston |
but also on the general list |
| 15:45 |
kmlussier |
Looking at the list, I don't see anything that has any ongoing development, but I can say tspindler and I have been working hard at sorting out authority issues in the OPAC. |
| 15:45 |
kmlussier |
And when I say we've been working hard, I mean tspindler. :) |
| 15:46 |
tspindler |
kmlussier @bar |
| 15:46 |
kakes |
Is there somewhere we can see what the status is? or what tsplindler is working on? |
| 15:47 |
kmlussier |
The best place to track it is probably in one of the bug reports. I would need to find it. |
| 15:47 |
yboston |
there is a page dedicated to authoriities that on occasion I try to update http://wiki.evergreen-ils.org/doku.php?id=authorities |
| 15:47 |
tspindler |
kakes: I have been trying to fix issues with our browse search, I am almost to the point where i can put some things out there |
| 15:47 |
kakes |
tsplindler++ |
| 15:47 |
graced |
You can see the current state of authorities on the Equinox 2.6 demo system http://demo.evergreencatalog.com/eg/opac/browse |
| 15:48 |
kmlussier |
kakes: Yeah, I thinnk we're still at a point where we're trying to nail things down. |
| 15:48 |
kakes |
tspindler++ |
| 15:48 |
yboston |
tspindler++ |
| 15:48 |
kakes |
graced: We'll take a look |
| 15:49 |
kmlussier |
We'll keep everyone posted. |
| 15:50 |
kmlussier |
It seems like we have a good plan for going through these goals. Are there any other specific goals we want to discuss before moving on the the next agenda item? |
| 15:50 |
yboston |
BTW, kmlussier, are you the one that will send out the meeting minutes? |
| 15:50 |
kmlussier |
yboston: I can do that. |
| 15:50 |
yboston |
thanks |
| 15:50 |
kmlussier |
#action kmlussier to send out minutes from the meeting |
| 15:51 |
yboston |
should we consider the date of a next meeting here or on the list? |
| 15:51 |
kmlussier |
yboston: I think that's the next agenda item. :) |
| 15:51 |
yboston |
sorry |
| 15:51 |
kmlussier |
#topic Plan for next steps -- meeting schedule, etc. |
| 15:51 |
kakes |
kmlussier: I agree we're ready to move on |
| 15:51 |
kmlussier |
How often do we want to meet? |
| 15:52 |
kakes |
next meeting date should be after the rating is complete |
| 15:52 |
kmlussier |
We talked about completing the rating in September, right? Should we shoot for late September for a meeting? |
| 15:52 |
kmlussier |
We don't want the date to conflict with the hack-a-way. |
| 15:53 |
terran |
kmlussier: although PINES isn't academic, there are some topics here we might be interested in as well - shall we respond to the survey too? |
| 15:53 |
kakes |
Monthly? |
| 15:53 |
yboston |
kmlussier: September works for me |
| 15:53 |
yboston |
monthly works for me |
| 15:53 |
tspindler |
kakes ++ |
| 15:53 |
kmlussier |
When is DIG doing their big doc day? That's before late September, right? |
| 15:53 |
kakes |
terran ++ |
| 15:54 |
jihpringle |
kmlussier: before Sept 18th |
| 15:54 |
yboston |
BTW, to give karma I think you cannot have a space between the name and the plus signs |
| 15:54 |
kmlussier |
terran: I personally don't see a problem with it, especially if you're willing to help out with the specs. :) |
| 15:54 |
yboston |
I can't remember the DIG plans, need to check my notes |
| 15:54 |
kakes |
yboston: |
| 15:54 |
kakes |
thanks |
| 15:55 |
kmlussier |
yboston: That's okay, I think jihpringle is right. Because that's the official release date. |
| 15:55 |
terran |
kmlussier: no promises, but maybe - depends on timing and budget! |
| 15:55 |
jihpringle |
yboston: between Sept 8th and 18th - poll is going out today |
| 15:55 |
yboston |
jihpringle: thanks and sorry I forgot to send you some dates |
| 15:55 |
kmlussier |
So the hack-a-way is scheduled for the week of the 22nd, right? So we might want to shoot for the week after (the 29th) |
| 15:56 |
jihpringle |
the week of the 29th sounds good to me |
| 15:56 |
kakes |
Thursdays seemed good and 3:00 for the west coast is a good time |
| 15:56 |
kakes |
3:00 est is good for west coast |
| 15:56 |
kmlussier |
That would bring us to October 2. Does that work for everyone? |
| 15:56 |
kmlussier |
Or should we do another Doodle poll? |
| 15:57 |
kakes |
How about we set the meeting for the first thursday of the month at 3:00 |
| 15:57 |
Christineb |
kakes++ |
| 15:57 |
kakes |
starting oct 2 |
| 15:57 |
kmlussier |
+1 |
| 15:57 |
jihpringle |
+1 |
| 15:57 |
Christineb |
+1 |
| 15:57 |
Kathy__ |
+1 |
| 15:57 |
mdriscoll |
+1 |
| 15:57 |
tspindler |
+1 |
| 15:58 |
yboston |
+1 |
| 15:58 |
kmlussier |
Also, I 'm one of the people who strongly encouraged kakes to hold this meeting in IRC. I see a lot of people here who don't typically use IRC. |
| 15:58 |
jforce-berklee |
+1 |
| 15:58 |
kmlussier |
Is this meeting format okay with everyone? |
| 15:58 |
kakes |
Is IRC working for those folks? |
| 15:58 |
terran |
kmlussier++ |
| 15:59 |
yboston |
IRC might not be the best place to ask if IRC for some :) |
| 15:59 |
kakes |
Right! |
| 15:59 |
kmlussier |
yboston: Heh, fair enough. |
| 15:59 |
yboston |
I can host another practice sesssion |
| 15:59 |
yboston |
IRC practice session |
| 15:59 |
kakes |
Please email kelly flo.org if you'd like to discuss other meeting options |
| 16:00 |
kmlussier |
kakes++ |
| 16:00 |
terran |
I endorse yboston's practice sessions! |
| 16:00 |
kakes |
We don't want to leave anyone out and could maybe do other formats |
| 16:00 |
kmlussier |
Anything else before we wrap up? |
| 16:00 |
yboston |
also, in the future I can see this group breaking up into sub groups to work on specific goals. then with a smaller crowd other options might be more feasible |
| 16:00 |
yboston |
nothing from me |
| 16:01 |
mdriscoll |
I just thought of another goal to add: Batch Patron Delete |
| 16:01 |
kmlussier |
yboston: Yeah, I think you're right. I don't see that work happening here. |
| 16:01 |
yboston |
mdriscoll++ |
| 16:01 |
kakes |
mdriscoll: I'll add that to the list |
| 16:01 |
kmlussier |
mdriscoll: Or maybe it could be rolled into Batch Patron Loading as batch patron operations? |
| 16:02 |
mdriscoll |
kmlussier: Sure. both functions are important |
| 16:02 |
jihpringle |
do we want to have space on the form for additional goals? |
| 16:02 |
kmlussier |
jihpringle: I think that's a very good idea. |
| 16:02 |
kakes |
jihpringle: Yes |
| 16:02 |
kakes |
This should be a continuous list of development items |
| 16:03 |
kmlussier |
Yes, I would say we should all feel free to continue adding ideas to that wiki page, even after we're done collecting feedback. |
| 16:03 |
kmlussier |
OK, I'm going to wrap up now. Thanks everyone for attending! |
| 16:03 |
kmlussier |
#endmeeting |
| 16:03 |
pinesol_green |
Meeting ended Thu Aug 14 16:03:55 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:03 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-08-14-15.00.html |
| 16:03 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-08-14-15.00.txt |
| 16:03 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-08-14-15.00.log.html |
| 16:03 |
yboston |
kmlussier++ |
| 16:04 |
graced |
kmlussier++ |
| 16:04 |
tspindler |
kmlussier++ |
| 16:04 |
kakes |
kmlussier++ |
| 16:04 |
graced |
kakes++ |
| 16:04 |
kmlussier |
kakes++ #for pulling this group together! |
| 16:04 |
jihpringle |
kakes++ |
| 16:05 |
phasefx |
random aside, I find life so much better after having added ils.org as an alias for git.evergreen-ils.org to my hosts file |
| 16:07 |
phasefx |
gmail tends to break up git URL's on me |
| 16:08 |
yboston |
phasefx++ might do that change myself too |
| 16:16 |
|
bmills1 joined #evergreen |
| 16:23 |
|
jihpringle_ joined #evergreen |
| 16:25 |
kmlussier |
@swill tspindler |
| 16:25 |
* pinesol_green |
grabs a bottle of Extra Dry Champale and sends it sliding down the bar to tspindler |
| 16:25 |
kmlussier |
tspindler: I think that's the command you were looking for earlier. |
| 16:40 |
tspindler |
@bar kmlussier |
| 16:40 |
pinesol_green |
tspindler: Message root @ server God....Universe going down for reboot.... |
| 16:40 |
tspindler |
@swill kmlussier |
| 16:40 |
* pinesol_green |
grabs a can of Sparks Stinger and sends it sliding down the bar to kmlussier |
| 16:41 |
kmlussier |
Or maybe... |
| 16:41 |
kmlussier |
@bartender tspindler |
| 16:41 |
* pinesol_green |
fills a pint glass with Redhook IPA, and sends it sliding down the bar to tspindler (http://beeradvocate.com/beer/profile/1330/70) |
| 16:41 |
kmlussier |
That's the one |
| 16:41 |
tspindler |
yes, that is what i though |
| 16:41 |
tspindler |
@bartender kmlussier |
| 16:41 |
* pinesol_green |
fills a pint glass with Cambridge Brewing Company's Charles River Porter, and sends it sliding down the bar to kmlussier (http://beeradvocate.com/beer/profile/14/515/) |
| 16:41 |
kmlussier |
Nice! I'll drinki it on my long commute home. :) |
| 16:44 |
kmlussier |
Judging by the way I just typed "drink", you would think I was already drinking. |
| 16:46 |
|
tspindler left #evergreen |
| 16:46 |
mmorgan |
Last question (for today) about money tables. bnm_desk_payment looks to be a subset of bnm_payment. What sort of transactions are in bnm_payment that aren't in bnm_desk_payment? |
| 16:51 |
Dyrcona |
mmorgan: It is another case of inheritance, IIRC. |
| 16:51 |
Dyrcona |
money.payment -> money.bnm_payment -> money.bnm_desk_payment. |
| 16:51 |
Dyrcona |
"bnm" == bricks 'n' mortar, IIRC. |
| 16:52 |
mmorgan |
Right. |
| 16:53 |
mmorgan |
Would something like a forgive payment be in bnm_payment, but not in bnm_desk_payment? |
| 16:53 |
Dyrcona |
You could select only from bnm_payment and see what comes out, then looking at the results might give some idea. |
| 16:54 |
Dyrcona |
I am pretty sure the staff client does desk payments for nearly everything. |
| 16:55 |
|
kmlussier left #evergreen |
| 16:57 |
mmorgan |
Dyrcona: thanks, I'll look at that. |
| 16:59 |
Dyrcona |
credit card payments may be there but not in desk payments. but I was only just skimming the code, so might be off on that. |
| 17:00 |
Dyrcona |
Nope. Take that back. |
| 17:01 |
Dyrcona |
credit card payments inherit from bnm_desk_payment, so they'll be there. |
| 17:01 |
Dyrcona |
Anyway, time for me to go home. |
| 17:06 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:06 |
|
mdriscoll left #evergreen |
| 17:09 |
phasefx |
I think another one of those startup race conditions ^ |
| 17:09 |
|
mmorgan left #evergreen |
| 17:10 |
|
_bott_ left #evergreen |
| 17:27 |
|
bmills1 joined #evergreen |
| 17:37 |
|
wjr joined #evergreen |
| 17:41 |
|
gsams joined #evergreen |
| 17:58 |
bshum |
Okay, 2.7.0-beta1 tarballs are up on the site |
| 17:58 |
bshum |
I have to finish updating the downloads page |
| 17:58 |
bshum |
And then I'll write a blog post and email summary |
| 18:01 |
berick |
bshum++ |
| 18:12 |
|
Christineb left #evergreen |
| 19:17 |
jeff |
bshum++ |
| 19:35 |
|
kmlussier joined #evergreen |
| 20:35 |
|
wsmoak joined #evergreen |
| 21:29 |
|
mnsri joined #evergreen |
| 21:41 |
|
mnsri joined #evergreen |
