| Time |
Nick |
Message |
| 06:33 |
|
book` joined #evergreen |
| 07:46 |
|
graced joined #evergreen |
| 07:47 |
|
collum joined #evergreen |
| 07:48 |
|
akilsdonk joined #evergreen |
| 08:00 |
|
rjackson_isl joined #evergreen |
| 08:01 |
|
mrpeters joined #evergreen |
| 08:14 |
|
Dyrcona joined #evergreen |
| 08:32 |
|
mmorgan joined #evergreen |
| 08:46 |
|
maryj joined #evergreen |
| 08:56 |
|
jwoodard joined #evergreen |
| 09:12 |
|
ericar joined #evergreen |
| 09:20 |
|
sarabee joined #evergreen |
| 09:20 |
|
RoganH joined #evergreen |
| 09:29 |
|
Sato joined #evergreen |
| 09:30 |
|
yboston joined #evergreen |
| 09:34 |
|
tspindler joined #evergreen |
| 09:39 |
|
julialima_ joined #evergreen |
| 09:43 |
|
tspindler left #evergreen |
| 10:04 |
Stompro |
What do you all use for environment monitorying for your server rooms? I'm trying to decided between AVTECH and ITWatchdogs products to monitor one server rack and one telecom closet. |
| 10:15 |
|
maryj joined #evergreen |
| 10:21 |
|
akilsdonk joined #evergreen |
| 10:25 |
jboyer-isl |
Stompro: what kind of monitoring are you interested in? Temp, humidity, etc? |
| 10:25 |
jboyer-isl |
We're not using anything specific here, but I believe our datacenter is monitoring some of that on a more macro scale. |
| 10:26 |
jeff |
temperature, humidity, water on floor, velociraptor presence... the usual. |
| 10:26 |
|
jcamins__ joined #evergreen |
| 10:26 |
Stompro |
jboyer-isl, Temp, Humidity, spot flood, power loss, |
| 10:27 |
jeff |
some of the better ones come with "loud noise" detection also. |
| 10:27 |
|
BigRig joined #evergreen |
| 10:28 |
jeff |
...for when you've moved the "paranoia" and "mission criticality" sliders past the 50% mark. |
| 10:28 |
Stompro |
I like that the itwatchdog devices include humidity sensors in the devices themselves, while avtech requires and external sensor for humidity. |
| 10:28 |
jboyer-isl |
I think APC's NetBots work well enough, but the $$ can be off-putting. We're planning to pick up some HP monitored PDUs so we can track power outages with icinga. (with redundant circuits, of course) |
| 10:29 |
jboyer-isl |
An external humidity sensor can be nice if the cable is long enough. (Though I suppose you can just drop a device on the floor under the cabinet, etc.) |
| 10:50 |
|
collum joined #evergreen |
| 10:56 |
kmlussier |
@dessert add boxes of Saomoa cookies |
| 10:56 |
pinesol_green |
kmlussier: Error: You must be registered to use this command. If you are already registered, you must either identify (using the identify command) or add a hostmask matching your current hostmask (using the "hostmask add" command). |
| 10:56 |
kmlussier |
Sigh...I always forget how to do that. |
| 10:56 |
|
montgoc1 joined #evergreen |
| 10:57 |
kmlussier |
Oh, good think it didn't work. Typo. |
| 10:57 |
kmlussier |
@dessert add boxes of Samoa cookies |
| 10:57 |
pinesol_green |
kmlussier: The operation succeeded. Dessert #30 added. |
| 10:57 |
kmlussier |
@dessert 20 phasefx |
| 10:57 |
* pinesol_green |
grabs some Red Velvet Cake for phasefx |
| 10:57 |
kmlussier |
And I can't read. |
| 10:57 |
kmlussier |
@dessert 30 phasefx |
| 10:57 |
* pinesol_green |
grabs some boxes of Samoa cookies for phasefx |
| 11:05 |
phasefx |
red velvet is my favorite cake, and samoas are my favorite cookies.. oh my |
| 11:05 |
csharp |
phasefx++ |
| 11:09 |
kmlussier |
I don't think I've ever had red velvet cake. |
| 11:09 |
maryj |
*gasp* |
| 11:10 |
csharp |
kmlussier: OH. MY. GOD. |
| 11:10 |
* collum |
wants to pack up some red velvet cake and send it to kmlussier, ASAP. |
| 11:10 |
kmlussier |
But I guess I'll try some soon? |
| 11:11 |
csharp |
I don't know if it's more prevalent in the south, but it was available at pretty much every church picnic or community gathering I ever went to as a kid |
| 11:11 |
berick |
I, for one, don't like fabric in my dessert, no matter how smooth. |
| 11:11 |
csharp |
berick: ewww |
| 11:11 |
kmlussier |
berick++ |
| 11:18 |
Dyrcona |
heh |
| 11:22 |
berick |
eeevil: kmlussier: going to merge working/user/kmlussier/web-client-sprint1-bug-fixing-signoff1 (plus 9804b5c54d12e6f2d1ae7b907a0de80d84ff978f) after light testing. any issues/concerns before I do that? |
| 11:24 |
kmlussier |
I have no concerns |
| 11:25 |
berick |
note for later, we should make the grid less chatty in the console. |
| 11:25 |
berick |
kmlussier: thanks |
| 11:25 |
goood |
berick: just concerns over rebasing the remainder... but that can be a tomorrow problem, I suppose |
| 11:29 |
jeff |
oh and of course the lovely thing about running services on high ephemeral ports... |
| 11:29 |
jeff |
(well, ONE of the things)... sometimes someone else gets there first. :P |
| 11:29 |
berick |
goood: rebasing collab/miker/web-client-sprint1-bug-fixing-rebased-collab ? |
| 11:33 |
berick |
just tried an expirement, rebasing that ^-- to my about-to-merge master branch. i haven't tested it, but it rebased without conflict. |
| 11:33 |
berick |
so there's that |
| 11:42 |
hopkinsju |
Does Evergreen actually use the quality field in biblio.record_entry? I can't think of anything, and we were thinking about reusing that column. |
| 11:44 |
jeff |
hopkinsju: have you considered biblio.record_note? |
| 11:44 |
|
sandbergja joined #evergreen |
| 11:44 |
jeff |
hopkinsju: i don't recommend [re/ab]using existing fields |
| 11:45 |
hopkinsju |
jeff: Well, no, but we are actually wanting to implement a custom scoring algorithm that we developed. |
| 11:45 |
hopkinsju |
What I mean is that it's not really an abuse, I was just thinking we might make use of an unused field. |
| 11:46 |
* berick |
considers adding LP#'s to these commits |
| 11:47 |
jeff |
hopkinsju: I'm pretty sure it's used. What the implications would be for re-using it for your purposes are unclear without knowing more or seeing code. :-) |
| 11:48 |
jeff |
hopkinsju: but our production database has 282 distinct values for bre.quality and I'm pretty sure that vandelay functions make decisions based on it. |
| 11:49 |
csharp |
hopkinsju: hold policies consider quality too |
| 11:49 |
hopkinsju |
jeff: Right on. Thanks for your thoughts. I assumed vandelay *could* make use of it, though currently we aren't because like you there just aren't that many distinct values. |
| 11:50 |
csharp |
hopkinsju: er... maybe I'm thinking of "mint_condition" - nevermind me |
| 11:50 |
* hopkinsju |
nods |
| 11:50 |
bshum |
berick: It's alot of them, but I always like having the LP# entry for reference's sake :D |
| 11:51 |
berick |
bshum: git filter-branch to the rescue |
| 11:51 |
hopkinsju |
We really like our scoring system, and we were thinking about trying to integrate that into the z39.50 multi-target search to create a system like the BookWhere product |
| 11:51 |
bshum |
berick++ git++ :D |
| 11:51 |
hopkinsju |
Also, as we migrate in new libraries we wanted to run the algorithm against their records and compare the average quality to what's already in our system. |
| 11:54 |
* kmlussier |
wonders why some billing OU settings are in the finances category and others are in the circulation category. |
| 11:54 |
bshum |
kmlussier: Whim? |
| 11:54 |
bshum |
And lack of patches |
| 11:55 |
bshum |
:D |
| 11:55 |
mmorgan |
just to confuse those of us who are trying to make sense out of them? :) |
| 11:55 |
bshum |
mmorgan: Now you're getting it! :) |
| 11:55 |
kmlussier |
Yeah, probably. I don't think it matters much. I guess I've just been looking at them far too much over the past year. |
| 11:55 |
berick |
bshum: git filter-branch -f --msg-filter "sed '0,/^/s//LP\#1402797 /1'" origin/master.. |
| 11:56 |
bshum |
If you come up with better categories for things, I'm happy to help test/push that along. One of the things I always wish I had more time to do would be to go back and actually add meaningful descriptions to all YAOUS entries. |
| 11:56 |
berick |
(then had to clean up a few double-tagged commits) |
| 11:56 |
bshum |
berick: Ooooh, fancy! |
| 11:56 |
kmlussier |
bshum: Yeah, adding better descriptions has crossed my mind too. |
| 11:56 |
* berick |
credits gmcharlt with the original suggestion way back when |
| 11:59 |
yboston |
Hello, I can't remember what the rules are for the deadlines we use for having a code change make it to the next release. I see the calendar says that next Friday is the "2.8 Beta Cut-Off" I can't remember what that one is for, I think it is meant for testing and signing off bug fixes? I beleive that the previous "2.8 Feature LP Target Deadline" is for havign signed off changes make it to the beta? |
| 11:59 |
bshum |
kmlussier: "Charge lost on zero" confused me for years. Still does sometime... |
| 12:00 |
berick |
yboston: the 2.8 cut off is for new features only. we *always* accept bug fixes |
| 12:00 |
bshum |
bug_fixes++ |
| 12:00 |
bshum |
:) |
| 12:00 |
yboston |
berick: sorry, that was the one rule I did remember, that bug fixes are always accepted :( |
| 12:00 |
kmlussier |
Is it difficult to update records that are provided in the Concerto set? I keep thinking it would be nice to add prices for all of the copies in there. |
| 12:01 |
kmlussier |
So that when you mark them lost in testing, a bill is added to the patron record. |
| 12:01 |
berick |
yboston: no worries, did I answer your question, though? |
| 12:01 |
bshum |
kmlussier: I'm sure it's not hard to do that. |
| 12:01 |
yboston |
so is there still time to submit (signed off) changes for 2.8? |
| 12:01 |
berick |
yboston: yes! |
| 12:01 |
berick |
we have until next friday for that |
| 12:01 |
yboston |
cool, but what is the earlier deadline for? ( "2.8 Feature LP Target Deadline") |
| 12:04 |
berick |
yboston: documenting / targeting new features in launchpad. the absence of such documention does not prevent new features getting into 2.8, though |
| 12:04 |
berick |
the purpose was to get as much info out as early as possible |
| 12:04 |
yboston |
berick: thank you very much, I had assumed I missed the boat on a new feature |
| 12:06 |
berick |
yboston: speaking of, do you still have any expectation of testing bug #1171984 ? |
| 12:06 |
pinesol_green |
Launchpad bug 1171984 in Evergreen "add support in Vandelay for overlaying authorities during import using match sets" (affected: 5, heat: 22) [Wishlist,Confirmed] https://launchpad.net/bugs/1171984 |
| 12:06 |
yboston |
berick: so sorry |
| 12:07 |
pinesol_green |
Showing latest 5 of 45 commits to Evergreen... |
| 12:07 |
pinesol_green |
[evergreen|Bill Erickson] LP#1402797 PCRUD access for noncat circs in IDL - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8cc0b1c> |
| 12:07 |
pinesol_green |
[evergreen|Bill Erickson] LP#1402797 browser client interval parser - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=75e466e> |
| 12:07 |
pinesol_green |
[evergreen|Bill Erickson] LP#1402797 browser client noncat counts in patron summary - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=158d365> |
| 12:07 |
pinesol_green |
[evergreen|Bill Erickson] LP#1402797 browser client noncat circ display - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c676947> |
| 12:07 |
pinesol_green |
[evergreen|Mike Rylander] LP#1402797 Check for a copy before trying to use it -- fixes non-cat checkout failure - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=34b334f> |
| 12:07 |
yboston |
berick: I totally forgot about it with all of the snow days we have had |
| 12:07 |
yboston |
berick: I will work on it |
| 12:07 |
yboston |
berick: so that it makes it in 2.8 |
| 12:08 |
berick |
yboston: heh, totally understand. I ordered something on line a while back and after a week got an email "snow killed our inet for a week -- we just shipped your order" |
| 12:08 |
berick |
and I thought we were immune down here ;) |
| 12:08 |
berick |
yboston++ |
| 12:09 |
|
bmills joined #evergreen |
| 12:10 |
kmlussier |
berick: If yboston doesn't get to that one, I might be able to. I was just looking at it today. |
| 12:10 |
kmlussier |
Or, I should say, eyeing it as a possible thing to test. |
| 12:11 |
berick |
kmlussier: awesome |
| 12:11 |
* berick |
pushed a rebased-to-master branch |
| 12:11 |
yboston |
kmlussier: I will let you know if I start testing it so you don't have to, then again maybe the more tsts the better |
| 12:13 |
|
sandbergja joined #evergreen |
| 12:13 |
* berick |
needs to come up w/ a conference proposal |
| 12:13 |
|
akilsdonk joined #evergreen |
| 12:16 |
bshum |
berick: So I was reading that request for devs to do a "new features for new Evergreen" and thinking we might work on that together. |
| 12:16 |
kmlussier |
I have two conference proposals in my head. I just need some kind of device to extract my thoughts and organize them into something coherent. |
| 12:16 |
bshum |
It's a pretty general session, maybe we can use that to focus people on thinking about how new features come into being too though, as far as the release process itself. |
| 12:17 |
berick |
bshum: is that from the email thread? |
| 12:17 |
bshum |
berick: yeah, it was in between all the talk about reports |
| 12:17 |
bshum |
http://markmail.org/message/wbtk6mqbpt5fbt4n |
| 12:18 |
kmlussier |
FWIW, I don't thing a presentation like that necessarily needs to be done by devs. Not that I think it's a bad thing for devs to do. |
| 12:18 |
berick |
kmlussier: heh, you may be right |
| 12:18 |
berick |
well, we should do a bit of that in the usual dev roundup |
| 12:18 |
kmlussier |
I do think berick and bshum would do a fine job, though. :) |
| 12:18 |
berick |
;) |
| 12:18 |
bshum |
I was thinking to bring up at the next conference programs committee pow-wow to see about setting aside panel time to talk about the web client though. |
| 12:19 |
bshum |
Kind of like last year. See where things are going now and where we're headed next and all. |
| 12:19 |
yboston |
bshum++ |
| 12:19 |
kmlussier |
bshum: IIRC, we had a higher resolution where some of that "My Account" stuff kicked in. Maybe the change from tabbed sections to a dropdown menu? |
| 12:19 |
* kmlussier |
really needs to look at that again. |
| 12:20 |
bshum |
kmlussier: Ah yes, there's two blocks now. 800px and 600px |
| 12:20 |
bshum |
So maybe it's a matter of defining slightly more details |
| 12:20 |
bshum |
C4L break, brb. |
| 12:20 |
Dyrcona |
What I've been reading online lately suggests designing for mobile first. |
| 12:36 |
geoffsams |
I've been using google webmaster tools to help make sure things are working correctly for our catalog here and there, and they recently implemented a mobile usability features in the service. |
| 12:36 |
geoffsams |
I'd be happy to share some of what is there, but I'm not sure it would be useful honestly |
| 12:36 |
geoffsams |
most of it is speed related, 2.7.3 gets a 98/100 usability apparently |
| 12:37 |
geoffsams |
Of Course I haven't looked at the specific pages that have been brought up either |
| 12:41 |
|
maryj joined #evergreen |
| 12:47 |
kmlussier |
gsams: 98/100 sounds pretty good |
| 12:48 |
gsams |
kmlussier: That's for the advanced search page at least |
| 12:49 |
gsams |
Since I'm 4 days after an upgrade I haven't had time to do more testing |
| 12:49 |
kmlussier |
I'm interepreting that as 98 out of 100. |
| 12:49 |
gsams |
that is correct |
| 12:49 |
gsams |
The only usability changes it suggested were related to tap targets spacing and size |
| 12:51 |
pastebot |
"gsams" at 64.57.241.14 pasted "Google Webmaster Usability" (6 lines) at http://paste.evergreen-ils.org/34 |
| 12:52 |
gsams |
basically, Basic Search and Browse the Catalog are too close, The search input boxes are too close, and we have a link at the bottom that is too close to other things |
| 12:56 |
goood |
hopkinsju: quality is use for lead metarecord selection. can you give some context to your "scoring algorithm"? what are you scoring, how do you interpret a score value, and what questions are answered by the score |
| 13:00 |
|
krvmga joined #evergreen |
| 13:01 |
bshum |
Hmm, c4l lightning talk about "keyboard accessibility" makes me think about how much testing we're doing on the catalog / web client. |
| 13:01 |
bshum |
So much stuff to test. |
| 13:03 |
|
sandbergja left #evergreen |
| 13:05 |
kmlussier |
bshum: Well, there currently isn't much to test in the web client in terms of keyboard accessibility. I don't think the keyboard shortcuts have been included yet. |
| 13:06 |
kmlussier |
yboston: Are you still around? |
| 13:07 |
|
afterl joined #evergreen |
| 13:33 |
yboston |
kmlussier: I am back at my desk |
| 13:34 |
goood |
berick: the removal of dropdown-toggle on the actions in the grid (commit d37e4d0bba) means, for ng 1.2.22 (on webby), that the menu stays open after the launching the action. Is that just an "old ng" problem? |
| 13:34 |
pinesol_green |
[evergreen|Bill Erickson] LP#1402797 Repair browser client dropdown buttons - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d37e4d0> |
| 13:36 |
kmlussier |
yboston++ |
| 13:36 |
berick |
goood: yes, newer versions of ng allow the drop-down to close |
| 13:36 |
goood |
ok |
| 13:37 |
berick |
rather, newer versions of angular-ui-bootstrap IIRC |
| 13:37 |
|
akilsdonk joined #evergreen |
| 13:37 |
goood |
also, there is a more recent fix to the message dialog that use ngOptions to allow display of a null default option. ... just fyi. nobody's signed it off yet, obv |
| 13:38 |
|
b_bonner_ joined #evergreen |
| 13:40 |
* berick |
nods |
| 13:42 |
goood |
but you can see it on webby. also, the "initials" stuff came back |
| 13:43 |
|
b_bonner_ joined #evergreen |
| 13:49 |
* jeff |
plays the "why does this behave differently in two different environments" game |
| 13:53 |
|
Cybrarian joined #evergreen |
| 13:54 |
Cybrarian |
It is ok to sit back and "listen" in on the conversation right? |
| 13:54 |
|
DonB__ joined #evergreen |
| 13:54 |
goood |
Cybrarian: lurking is encouraged :) |
| 13:55 |
kmlussier |
Cybrarian: Yes, absolutely! |
| 13:56 |
kmlussier |
Ooh! The presentation on floating looks like it could be fun! |
| 13:57 |
|
mdriscoll joined #evergreen |
| 13:57 |
kmlussier |
And the proposal from bshum and Dyrcona looks fun too! |
| 13:57 |
yboston |
heads up the Evergreen for academics meeting will start at 2 PM EST |
| 14:00 |
yboston |
#startmeeting 2015-02-12 - Evergreen for academics monthly meeting. |
| 14:00 |
pinesol_green |
Meeting started Thu Feb 12 14:00:27 2015 US/Eastern. The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 14:00 |
pinesol_green |
The meeting name has been set to '2015_02_12___evergreen_for_academics_monthly_meeting_' |
| 14:00 |
yboston |
The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen_for_academics:2015-02-12 |
| 14:01 |
yboston |
#topic Introductions |
| 14:01 |
yboston |
Please feel free to start introducing yourselves... |
| 14:01 |
yboston |
#info yboston is Yamil Suarez @ Berklee College of Music |
| 14:01 |
krvmga |
#info krvmga is Jim Keenan @ CWMARS |
| 14:01 |
mdriscoll |
#info mdriscoll is Martha Driscoll, NOBLE |
| 14:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:01 |
DonB__ |
#info DonB_ is Don Butterworth, Asbury Seminary |
| 14:02 |
yboston |
I will wait another minute before we start |
| 14:03 |
yboston |
OK |
| 14:03 |
yboston |
#topic last meeting's action items |
| 14:03 |
yboston |
1) ck_ and kmlussier to follow up directly with libraries that showed interest in an academic PAC flavor. |
| 14:04 |
kmlussier |
Sorry all. I need to defer that action item to the next meeting. |
| 14:04 |
kmlussier |
I think the other person in it was Joan Kranich from C/W MARS? |
| 14:04 |
yboston |
OK, I will defer it |
| 14:04 |
yboston |
#action ck_ and kmlussier to follow up directly with libraries that showed interest in an academic PAC flavor. |
| 14:04 |
yboston |
moving on |
| 14:05 |
yboston |
2) yboston to share authorities code he has been working on. |
| 14:05 |
yboston |
IN late December I did finally post some code on the Git working repository |
| 14:05 |
yboston |
bug 1403967 |
| 14:05 |
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 |
| 14:05 |
yboston |
#link https://bugs.launchpad.net/evergreen/+bug/1403967 |
| 14:06 |
yboston |
The change is small, and it has given me a chance to get familiar with the "manage authorities" UI |
| 14:06 |
yboston |
here is the exact change http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=89f863b742e8f92c8d5c07df6e541e7576243ae3 |
| 14:07 |
yboston |
I got some feedback on the list, need to find the list link |
| 14:07 |
yboston |
and it looks like there is still time to add this small change to the 2.8 release |
| 14:07 |
kmlussier |
yboston: I think there was somebody here who asked me to load it on a Sandbox. I'll touch base with her to get some feedback. |
| 14:07 |
yboston |
I have until next Friday to finish my code changes AND have someone else "sign off" on my change |
| 14:08 |
yboston |
yesterday I got some feedback from the Canadian Statitical library, they want me to speel out the MARC code full value. Though I still need to figure out how to do that |
| 14:09 |
yboston |
any other comments on this action item before we move on? |
| 14:09 |
yboston |
I did want to mention another atuhority improve,nt that is in the works |
| 14:10 |
kmlussier |
yboston: If, in general, it is an improvement, I would say whatever your finished code does, even if you don't figure that last bit out, could go in for 2.8. |
| 14:10 |
|
jck_ joined #evergreen |
| 14:10 |
kmlussier |
And then you could work on the other bit for the future. |
| 14:10 |
yboston |
kmlussier: that is my "worse case scenario" approach for next week |
| 14:11 |
yboston |
can I mention the other feature while we are talking about authorities? |
| 14:11 |
kmlussier |
yboston++ |
| 14:11 |
yboston |
bug #1171984 |
| 14:11 |
pinesol_green |
Launchpad bug 1171984 in Evergreen "add support in Vandelay for overlaying authorities during import using match sets" (affected: 5, heat: 22) [Wishlist,Confirmed] https://launchpad.net/bugs/1171984 |
| 14:12 |
yboston |
this is a feature that needs to be tested out for inclusion in EG 2.8. Again there is one week left to have someone test it and "sign off" on it |
| 14:12 |
yboston |
Kathy or I will try to do the signing off |
| 14:13 |
yboston |
I am bringing this up partially to showcase how improvements are made to EG |
| 14:13 |
yboston |
that is all for me on authoritites. I can move to the nexr past meeting's action item |
| 14:13 |
|
Cybrarian joined #evergreen |
| 14:14 |
yboston |
moving on |
| 14:14 |
yboston |
3) jeffdavis to put out a call for current patron loading scripts that are already in use. |
| 14:14 |
yboston |
I am not sure if jeffdavis is available now, will wait a bit before defring |
| 14:15 |
yboston |
moving on |
| 14:15 |
yboston |
#action jeffdavis to put out a call for current patron loading scripts that are already in use. |
| 14:15 |
yboston |
at this point there are now more outstanding past meetign action items |
| 14:15 |
yboston |
we can now shift to talk about other issues |
| 14:16 |
yboston |
for example, thoughts on the earlier discussion on call number search |
| 14:16 |
yboston |
or something completely different |
| 14:16 |
Cybrarian |
PAC flavors? |
| 14:16 |
DonB__ |
I sent out a couple of emails to the list regarding call numbers |
| 14:17 |
DonB__ |
It seems there is broad consensus in two areas |
| 14:17 |
yboston |
Lets go in order of reponses |
| 14:17 |
DonB__ |
"Bib Call Number" search can/should be eliminated. |
| 14:17 |
yboston |
#topic PAC Flavors |
| 14:17 |
yboston |
(sorry Don) |
| 14:17 |
DonB__ |
No problem |
| 14:18 |
yboston |
Cybrarian: do you have a specific comment or question? |
| 14:18 |
DonB__ |
Call Number (Shelf Browse) results screen with a “List View” |
| 14:18 |
DonB__ |
Both of these topics received support |
| 14:18 |
Cybrarian |
I'd be grateful for more documentation about how to change specific features in the online catalog. |
| 14:19 |
yboston |
Cybrarian: by features do you also mean the look of the catalog or do you only mean actual functions? |
| 14:19 |
DonB__ |
Another topic that came up regarding PAC flavor was the use of a "more..." feature |
| 14:19 |
DonB__ |
for long texts on MARC records |
| 14:19 |
|
julialima_ left #evergreen |
| 14:19 |
DonB__ |
Not sure where to proceed from here on the Call Number and more... issues |
| 14:20 |
kmlussier |
FWIW, the code to remove the bib call number search has been merged into Evergreen. |
| 14:20 |
|
Cybrarian_ joined #evergreen |
| 14:20 |
DonB__ |
Good! |
| 14:20 |
kmlussier |
Cybrarian: Have you seen http://docs.evergreen-ils.org/2.7/_designing_your_catalog.html? |
| 14:21 |
Cybrarian_ |
Sorry. I keep getting bumped off the network. I should not have tried this. |
| 14:21 |
kmlussier |
Cybrarian: No worries! It's happend to all of us at one time or another. :) |
| 14:21 |
DonB__ |
I have nothing more to report on Call Numbers at this time |
| 14:22 |
yboston |
Cybrarian: you can email me for help with IRC and comments or questions for the academics group if you continue to have issues |
| 14:22 |
Cybrarian_ |
Yes. I saw that document just recently. It is pretty general to get started. |
| 14:22 |
yboston |
Cybrarian: did you see my earlier question? "by features do you also mean the look of the catalog or do you only mean actual functions?" |
| 14:22 |
Cybrarian_ |
I would think it would be nice for new members to see specific examples of really cool catalogs with how to achieve what was done. |
| 14:23 |
yboston |
also, I am pondering submitting a presentation for the next conference to cover tips on how to cusotmize the look of the catalog, maybe I can turn that into new docuemtnation |
| 14:23 |
Cybrarian_ |
I mostly mean look. But also some functions - like locations searching. |
| 14:23 |
yboston |
Cybrarian_: I also want to get representatives of "cool" looking catalogs to share their tricks |
| 14:24 |
Cybrarian_ |
Like how do we set up a search for our Music collection in the catalog and then show it in the OPAC interface? |
| 14:26 |
Cybrarian_ |
I'm a person who likes specifics. :-) |
| 14:26 |
yboston |
Cybrarian_: at first glance that might not be too hard |
| 14:26 |
kmlussier |
Cybrarian_: I guess a lot of that depends on how you identify records in your Music collection. Are they in a specific copy location or identified in some other way? |
| 14:26 |
yboston |
Cybrarian_: contact me by email so I can give you some suggestions on your music question and then share it on the EG list ysuarez berklee.edu |
| 14:26 |
kmlussier |
Cybrarian_: Yeah, yboston is probably the best person to talk to about music collections. :) |
| 14:26 |
Cybrarian_ |
They are in a specific copy location. And I have seen other evergreen catalogs that have a copy location search. But how did they do that? |
| 14:27 |
yboston |
Cybrarian_: this sounds like somethign we might want to work on outside of this meeting, so we can preserve time |
| 14:27 |
yboston |
do you mind if we revisit it later on or by email? |
| 14:28 |
Cybrarian_ |
Thanks. No worries. But it is also related to PAC flavors I would think. I'll move on. |
| 14:28 |
yboston |
Cybrarian_: absolutly it is related to PAC flavors, I am very glad you brought it up, and I hope we can come back to de whole group with tips |
| 14:29 |
yboston |
*absolutely |
| 14:29 |
yboston |
Cybrarian_: any other comment or qeustion before we turn to DonB__ on PAC flavors? |
| 14:30 |
Cybrarian_ |
Nope. I'm good. Don has pressing issues... |
| 14:30 |
kmlussier |
Cybrarian_: I sent you a pm that might get you started. |
| 14:31 |
yboston |
Cybrarian_: you have my email, pelase don't hesitate to reach out. I am glad you ventured out on IRC |
| 14:31 |
yboston |
DonB__: your turn |
| 14:31 |
yboston |
where were we on PAC flavors? |
| 14:32 |
DonB__ |
Oops, looks like I jumped the gun |
| 14:32 |
yboston |
no worries |
| 14:32 |
DonB__ |
Do you want a repeat on what I already entered? |
| 14:32 |
yboston |
"Another topic that came up regarding PAC flavor was the use of a "more..." feature |
| 14:32 |
yboston |
for long texts on MARC records" |
| 14:33 |
yboston |
(I just reposted) |
| 14:33 |
yboston |
I need to find the link for that discussion on the list, have not foudn it yet |
| 14:33 |
kmlussier |
Based on the response to that question, I didn't see that as a pac flavor issue. It sounded like something that lots of people wanted. So more of a new PAC feature. |
| 14:34 |
DonB__ |
Looks like everyone like the idea of using "more..." regardless of the library type |
| 14:34 |
yboston |
I definetly see this happening on occasion, what might seem like an academic only cahnge turns out something others want. |
| 14:35 |
yboston |
I don't mind that this group helps identify things that should be EG defaults moving forward |
| 14:35 |
DonB__ |
Who would be in charge of implementing this feature? |
| 14:36 |
DonB__ |
Did we ever get it on the wish list? |
| 14:36 |
kmlussier |
yboston: I totally agree. But it might be worth a LP wishlist bug. |
| 14:36 |
yboston |
absolutely I agree that it becomes an LP bug |
| 14:37 |
yboston |
is this the right link for the discussion? |
| 14:37 |
kmlussier |
DonB__: As far as who is in charge of implementing, I guess it falls into who ever has the time/ability. |
| 14:37 |
yboston |
http://georgialibraries.markmail.org/thread/3njox5yvjicuapwa |
| 14:38 |
kmlussier |
Is there already an Evergreen site that does this? I thought there was. |
| 14:39 |
yboston |
Michael from Fort Erie Public Library said they had this working on their site |
| 14:39 |
yboston |
#link http://georgialibraries.markmail.org/thread/3njox5yvjicuapwa |
| 14:40 |
kmlussier |
Yes, I was just reading that. But it looks like he was using a jquery plugin, which could be problematic for getting it into core? |
| 14:40 |
kmlussier |
I don't know if any of the devs are paying attention or have thoughts on that. |
| 14:41 |
yboston |
in the meantime we can start with a wish list LP bug |
| 14:41 |
yboston |
DonB__: would you like to team up to create a whish list LP bug for the "see more" feature? |
| 14:42 |
DonB__ |
I'm happy to write up that wishlist item |
| 14:42 |
DonB__ |
Anybody want to look it over before I post it? |
| 14:43 |
kmlussier |
DonB__: Nah. I'm sure it will be fine. :) |
| 14:43 |
DonB__ |
OK |
| 14:43 |
yboston |
#action DonB__ write up a Launcpad wishlist bug to propose "see more" style cuntionality on OPAC record view |
| 14:43 |
yboston |
feel free to run it by me, even if it is to tell you it looks fine as Kathy said |
| 14:44 |
DonB__ |
K |
| 14:44 |
yboston |
you shoudl either reply to the the same thread with the link or write a new eamil to the list to get more feedback or look for volunteers to work on it |
| 14:45 |
DonB__ |
Check |
| 14:45 |
yboston |
any other comments or questions about PAC flovor related stuff? If not we could double back to talk about call number search, |
| 14:45 |
yboston |
DonB__ had started saying some things earlierand I want to make sure we don't miss anything |
| 14:46 |
DonB__ |
Deja vous ... |
| 14:46 |
DonB__ |
It seems that there is broad consensus that the "Bib Call Number" search can/should be eliminated. |
| 14:47 |
DonB__ |
There seems to be broad consensus for a Call Number (Shelf Browse) results screen with a “List View” |
| 14:47 |
DonB__ |
We have already deleted Bib Call Number from out catalog options |
| 14:48 |
yboston |
good recap |
| 14:48 |
DonB__ |
Again, these two items need to be part of the wish list |
| 14:49 |
DonB__ |
End report |
| 14:49 |
yboston |
yes I would create a seperate wishlist item for the call number "list view" |
| 14:50 |
yboston |
BTW, anyone that is also subscribed to the Code4LIb list, did you catch the dsicussion they had in the last few weeks about call number search UI? I glanced at it but I wondered if there were some good ideas there |
| 14:50 |
kmlussier |
I'm subscribed but missed that discussion. |
| 14:50 |
DonB__ |
Sounds like it's above my pay grade |
| 14:51 |
yboston |
I'll try to double back and check it out, and then report back |
| 14:52 |
yboston |
here is the link to the EG list discusion on call number search |
| 14:52 |
yboston |
#link http://georgialibraries.markmail.org/thread/eihp5dmflaleje3f |
| 14:53 |
yboston |
I remember reading that Mike from ESI thought it might not be that hard to make the change that is needed |
| 14:53 |
yboston |
though of course someone one needs to put in the time. |
| 14:53 |
yboston |
I may have enought skills to look into it, but I may not have the time before the conference. |
| 14:54 |
yboston |
maybe this is soemthing that can be a mini project during the upcoming EG conference hack-fest |
| 14:54 |
yboston |
at least to get a prototype |
| 14:55 |
yboston |
any volunteers, specially someone that has not used Launpad before... |
| 14:55 |
DonB__ |
Cool |
| 14:55 |
yboston |
that would like to team up with me to write the wishlist LP bug? |
| 14:56 |
DonB__ |
I would be glad to |
| 14:56 |
yboston |
OK |
| 14:56 |
DonB__ |
Question about the source of the call number |
| 14:56 |
yboston |
go ahead |
| 14:57 |
DonB__ |
Should it come from the copy record or the Bib record? |
| 14:57 |
DonB__ |
I'm guessing it would have to be the copy record, eh? |
| 14:57 |
kmlussier |
A list-based call number browse is something I've considered looking into doing every once in a while. If I do get some time to look at it, I'll post something on the wishlist bug. |
| 14:57 |
kmlussier |
DonB__: Not the bib record. |
| 14:57 |
kmlussier |
It should be the volume call number. |
| 14:58 |
kmlussier |
If it's the bib record, I don't think it helps a majority of the consortia out there. |
| 14:58 |
DonB__ |
OK |
| 14:58 |
yboston |
#action DonB__ and yboston will write out an LP wishlist bug for call number search "list view" |
| 14:58 |
yboston |
we are almost out of time |
| 14:58 |
yboston |
any final comments or questions? |
| 14:59 |
yboston |
specially fromt those that have not had a chance to say anythitng? |
| 15:00 |
yboston |
thanks again to Cybrarian_ for jumping in |
| 15:00 |
yboston |
OK then |
| 15:00 |
yboston |
I think the next meeting would be... |
| 15:01 |
yboston |
Thuesday March 12 |
| 15:01 |
yboston |
Thursday, March 12 |
| 15:01 |
yboston |
thanks for participating |
| 15:01 |
yboston |
#endmeeting |
| 15:01 |
pinesol_green |
Meeting ended Thu Feb 12 15:01:46 2015 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:01 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-02-12-14.00.html |
| 15:01 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-02-12-14.00.txt |
| 15:01 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-02-12-14.00.log.html |
| 15:02 |
|
maryj joined #evergreen |
| 15:03 |
kmlussier |
A question for ESI folks: It looks like http://esilibrary.com/documentation/2-2-copy-location-groups/ never made it into the community docs. Do you know where we might be able to find an AsciiDoc version of it? |
| 15:04 |
kmlussier |
I was looking for it because I thought it might help Cybrarian. |
| 15:12 |
akilsdonk |
kmlussier: I should have the AsciiDoc version. I'll find it and add it to the community docs. |
| 15:12 |
kmlussier |
akilsdonk++ Thank you! |
| 15:22 |
hopkinsju |
jeffdavis: I see that you'd put out a call for patron load scripts... Did I send in a link to our github repo with our migration scripts? |
| 15:23 |
* hopkinsju |
spoke too soon - not sure we actually do that. |
| 15:26 |
|
afterl1 joined #evergreen |
| 15:30 |
kmlussier |
I love how Doodle is always telling us how our polls are bigger than usual. I don't think I've ever participated in a Doodle poll that wasn't bigger than usual. |
| 15:35 |
jboyer-isl |
kmlussier: have you ever had it show you the correct timezone? I'm relatively certain it chooses something silly to try to get you to sign up for an account. |
| 15:36 |
kmlussier |
I'm always logged in, so I might not be a good person to ask. |
| 15:36 |
kmlussier |
Yup! That's how much I use Doodle. I never log out. |
| 15:40 |
jeffdavis |
hopkinsju: hmm, I was *going to* put out a call, but I'm not sure I actually did... |
| 15:45 |
|
chatley joined #evergreen |
| 15:48 |
jeff |
kmlussier: i was just spending some time today looking at copy location groups and search filter groups :-) |
| 15:50 |
|
afterl joined #evergreen |
| 15:54 |
berick |
kmlussier: hah, they could at least use better wording.. "you have impressive meeting requirements. you must be very important!" |
| 15:56 |
kmlussier |
gmcharlt: Are we having a web team meeting next Wednesday? |
| 15:57 |
gmcharlt |
kmlussier: yes |
| 15:57 |
kmlussier |
gmcharlt: OK, I thought maybe not since you listed yourselve as available for the dev meeting at that time. ;) |
| 15:57 |
gmcharlt |
*blinks* |
| 15:58 |
gmcharlt_clone1 |
hey, gmcharlt, are you available next Wednesday? |
| 15:59 |
kmlussier |
lol |
| 16:00 |
hopkinsju |
jeffdavis: I was reading the minutes and saw that as a "past action item" - I was giving you the benefit of the doubt! |
| 16:02 |
berick |
kmlussier: hm, was the web team meeting always on the calendar? |
| 16:02 |
berick |
if so, I looked right past it |
| 16:02 |
berick |
when scheduling the dev meeting |
| 16:02 |
kmlussier |
berick: I think so. I think it was put in as a monthly thing that simply recurs. |
| 16:03 |
gmcharlt |
yeah |
| 16:03 |
berick |
gah, sorry about that. side note: we really need auto-repeating dev meetings |
| 16:04 |
gmcharlt |
berick: +1 to that |
| 16:04 |
gmcharlt |
(and easier since we don't have as many time zones to worry about as Koha does) |
| 16:05 |
berick |
and whenever we do polls, it's practically always the same time.. monday or tuesday ~ 2pm |
| 16:05 |
kmlussier |
We had those a few years ago. But then people started forgetting them. But I'm all for that! |
| 16:05 |
berick |
i'll add it to the agenda |
| 16:05 |
gmcharlt |
it seems to be a cycle :) |
| 16:05 |
berick |
heh |
| 16:07 |
kmlussier |
I think if there is somebody who takes responsibility for sending out reminders, the way yboston does for DIG meetings, I think a regularly-scheduled meeting would work fine. |
| 16:07 |
jboyer-isl |
It might help to send out reminders in place of the meeting date requests, that way it's always fresh in people's minds. |
| 16:07 |
kmlussier |
jboyer-isl: Ha! Beat you! |
| 16:07 |
jboyer-isl |
Great minds, etc. ;) |
| 16:07 |
|
afterl left #evergreen |
| 16:08 |
jboyer-isl |
I guess I need to up my typing game. I used to be a quick typist. |
| 16:08 |
Dyrcona |
A bot could be programmed to send reminders. |
| 16:08 |
Dyrcona |
Or a cron job, take your pick. |
| 16:12 |
gsams |
Okay, fast item add: type in call number, scan barcode, set item attributes, Modify/Create Copies. No item is attached, but the volume is created... |
| 16:16 |
kmlussier |
That sounds familiar |
| 16:16 |
mmorgan |
gsams: No item at all? Did you check and see if the item ended up as a precat? |
| 16:17 |
gsams |
holdings maintenance shows the volume but no item, the item doesn't exist in the database |
| 16:18 |
kmlussier |
gsams: Did you run autogen after upgrading? |
| 16:18 |
kmlussier |
It sounds similar to the problem Bmagic had after his upgrade. http://irc.evergreen-ils.org/evergreen/2014-11-14#i_138914 |
| 16:22 |
gsams |
I'm betting that would fix it from the sound of it |
| 16:22 |
gsams |
I'll get back to you on that |
| 16:28 |
|
RoganH joined #evergreen |
| 16:29 |
RoganH |
@hate reports |
| 16:29 |
pinesol_green |
RoganH: The operation succeeded. RoganH hates reports. |
| 16:30 |
RoganH |
OK. I admit, I very, very rarely use the reporter. Does anyone know why the aggregate filters grey out? I assume I'm not doing some step first. |
| 16:32 |
kmlussier |
RoganH: You need to select a field with an aggregate output type for the aggregate tab to be active. |
| 16:32 |
RoganH |
So, it has to have aggregate output types specified? |
| 16:32 |
RoganH |
per field? |
| 16:33 |
RoganH |
@hate reporter |
| 16:33 |
pinesol_green |
RoganH: The operation succeeded. RoganH hates reporter. |
| 16:35 |
hopkinsju |
RoganH: I was just complaining about views in Drupal. I was comparing it to Evergreen reporter. It's actually more flexible, but if you can believe it, more confusing. |
| 16:36 |
RoganH |
I can believe anything. If it's more bizarre I don't want to see it. |
| 16:37 |
RoganH |
I shouldn't say bizarre, it's just what it is. I just want to sum this and it won't let me. So, where is it defined what fields can aggregate? |
| 16:40 |
|
Sato joined #evergreen |
| 16:41 |
kmlussier |
RoganH: Actually, it isn't the field that has the output type. OK, so as you're choosing the field to add to your report, when you select the field name, if you look at the "Field Transform" box to the right, it shows different ways to use the field. |
| 16:41 |
kmlussier |
In there, it says whethter the output type is aggregate or non-aggregate. |
| 16:41 |
kmlussier |
RoganH: I rarely use reports, so I'm not very good at explaining the little I know. :) |
| 16:41 |
|
sandbergja joined #evergreen |
| 16:42 |
* mmorgan |
has great respect for anyone who is comfortable navigating the reporter |
| 16:42 |
kmlussier |
RoganH: Is that making any sense? |
| 16:42 |
* Dyrcona |
just gives up and uses SQL directly. |
| 16:43 |
RoganH |
kmlussier: a little bit though to me I think "um.... anything can be aggregated" |
| 16:43 |
RoganH |
Dyrcona: that's the problem, they want me to create templates for a datasource I'm adding to the reporter |
| 16:43 |
RoganH |
Dyrcona: the sql took 30 seconds |
| 16:43 |
kmlussier |
RoganH: Yes, and I think if you look at each field, each of them has a transform with both aggregate and non-aggregate types. |
| 16:43 |
RoganH |
kmlussier: I'll look again *grumble grumble* |
| 16:44 |
Dyrcona |
RoganH has my sympathies. |
| 16:44 |
kmlussier |
I don't like the reporter because I'm uncomfortable with it. However, when I talk to some of the people who create a lot of report templates, they really like the power in the reports. |
| 16:44 |
gsams |
RoganH: With the reporter, only certain Data Types have aggregate output types. Money, Timestamp, ID, and int it seems |
| 16:44 |
RoganH |
Back in my day, we just used a magnifying glass, a notepad and went through and counted holes in punch cards, and we liked it! |
| 16:45 |
kmlussier |
They like SQL queries too, but those can't be scheduled to run on an ongoing basis for staff. |
| 16:45 |
jeff |
well. |
| 16:45 |
gsams |
kmlussier: Sure they can! |
| 16:45 |
gsams |
I use a cronjob to run a query and email the results for one of my libraries, because the reporter couldn't do it well enough |
| 16:46 |
jeff |
and we use jasper. |
| 16:46 |
RoganH |
gsams: I'd do this but this is for things they'll want to play with and make on the fly. |
| 16:46 |
jeff |
which lets the users schedule their own reports. |
| 16:46 |
RoganH |
It's an integer and it isn't offering any field transforms. |
| 16:46 |
RoganH |
Unless I'm an idiot. This is not completely discarded as a possibility. |
| 16:46 |
gsams |
RoganH: Oh I understand that completely, I'd rather setup jasper actually but I don't even know where to start with that and we don't have an extra server lying about |
| 16:47 |
gsams |
RoganH: Int values should have Average, Count, Count Distinct, Max, Min, and Sum field transforms |
| 16:48 |
Dyrcona |
kmlussier: SQL queries can be scheduled to run on an ongoing basis, just not within Evergreen. |
| 16:48 |
gsams |
RoganH: At least, in my experience these are the transforms that I usually see for int data types |
| 16:48 |
kmlussier |
gsams / jeff / Dyrcona: Yes, sorry. I knew that. And they do have multiple ways of providing reporting information to their libraries. |
| 16:49 |
Dyrcona |
Oops. Didn't mean to pile on. |
| 16:49 |
kmlussier |
I'm just saying that we have a few people who, after getting comfortable with the interface, really like the information they can get out of the reporter. |
| 16:49 |
Dyrcona |
RoganH: Are the fields of the new source defined properly in the IDL, and did you run autogen.sh? ;) |
| 16:50 |
mmorgan |
I haven't had enough experience with the reporter to be comfortable, but it is very powerful in that it lets end users run very complex sqls without knowing any sql at all. |
| 16:50 |
RoganH |
Dyrcona: I ran autogen, I'm going to look again. I'm wondering if I did something like write integer instead of int. |
| 16:50 |
Dyrcona |
I know some people are comfortable with it and some even like it. |
| 16:50 |
gsams |
I also forgot the text data type has aggregate transforms. |
| 16:51 |
Dyrcona |
I'd double check the element names, too, particularly reporter:datatype |
| 16:52 |
RoganH |
Dyrcona: yep I did datatype="integer" for three of them instead of "int" |
| 16:52 |
* Dyrcona |
typoed Integer as Interger last night. |
| 16:52 |
Dyrcona |
That'll do it. |
| 16:52 |
RoganH |
I did it once before which is why I suddenly thought of it. |
| 16:53 |
RoganH |
I discovered that one before testing though. Ug. |
| 16:57 |
RoganH |
That did it. Thanks for the ideas all. |
| 16:57 |
RoganH |
Dyrcona++ |
| 16:57 |
RoganH |
kmlussier++ |
| 17:03 |
mmorgan |
...and it's snowing again :-(. Goodnight all! |
| 17:04 |
kmlussier |
mmorgan: It's been snowing here off and on all day. |
| 17:04 |
kmlussier |
mmorgan: Have a nice night! |
| 17:04 |
gsams |
kmlussier: autogen for the win |
| 17:04 |
mmorgan |
You also! |
| 17:04 |
|
mmorgan left #evergreen |
| 17:04 |
gsams |
kmlussier++ |
| 17:04 |
kmlussier |
gsams: Awesome! |
| 17:04 |
RoganH |
Good night! |
| 17:07 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:07 |
|
mdriscoll left #evergreen |
| 18:02 |
|
bbqben joined #evergreen |
| 18:12 |
|
mrpeters left #evergreen |
| 19:59 |
|
jcamins joined #evergreen |
| 20:30 |
|
bmills joined #evergreen |
