Time |
Nick |
Message |
04:50 |
|
geoffsams joined #evergreen |
05:33 |
|
vanya joined #evergreen |
05:46 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
08:10 |
|
eeevil joined #evergreen |
08:10 |
|
mtate joined #evergreen |
08:11 |
|
phasefx joined #evergreen |
08:11 |
|
Callender joined #evergreen |
08:12 |
|
graced joined #evergreen |
08:20 |
|
akilsdonk joined #evergreen |
08:28 |
|
Shae joined #evergreen |
08:32 |
|
mrpeters joined #evergreen |
08:39 |
|
mmorgan joined #evergreen |
08:46 |
|
kmlussier joined #evergreen |
08:53 |
|
Dyrcona joined #evergreen |
08:56 |
|
ericar joined #evergreen |
08:57 |
|
jwoodard joined #evergreen |
08:57 |
mmorgan |
Is there a way to set a hold policy such that items won't capture and go in transit to the pickup library, but WILL capture if they are checked in at the pickup library? |
08:58 |
eeevil |
mmorgan: you should be able to use a transit distance limit of 0 to make that happen ... but, working from memory, so not /certain/ |
09:01 |
* tsbere |
isn't aware of any way to accomplish that, but could be wrong |
09:01 |
tsbere |
eeevil: Isn't transit based on the item's circ or owning library, not the checkin library? |
09:02 |
eeevil |
tsbere: it is, you're correct |
09:02 |
* eeevil |
will think harder, later :) |
09:04 |
mmorgan |
Yeah, a little early for such a thinky question. :) |
09:04 |
tsbere |
mmorgan: Perhaps a longer description of what you are trying to accomplish might help? |
09:06 |
mmorgan |
Trying to stop the flow of transits for a library that's closing for a temporary move. We want to stop remote capture just for a couple of days, but I think we'll go with making everything not holdable at their pickup location at this point. |
09:09 |
tsbere |
mmorgan: Suspend the holds for pickup there with an activation date of after the couple of days, extending any that were already suspended to after that date if they aren't already? |
09:13 |
mmorgan |
We still want them to trap if they're checked in at the pickup point. We just don't want them to transit from somewhere else to fill a hold at the pickup point. After a couple of days they will essentially be "closed for holds". |
09:14 |
mmorgan |
...until after they move to the temporary location. |
09:15 |
* Dyrcona |
points to eeevil's comment on lp 1342227 and says "And, people wonder why I dislike ruby...." |
09:15 |
pinesol_green |
Launchpad bug 1342227 in Evergreen "Setting up EDI Fails with Ruby version > 1.8" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1342227 |
09:17 |
eeevil |
Dyrcona: I said basically that last night, and was asked "do you mean the language or the ruby community". to which I answered, "yes" ;) |
09:17 |
tsbere |
mmorgan: Well, at a minimum I would recommend turning on "capture local holds as transits" at the pickup point, so that they aren't sending out notices that holds are ready for pickup during the move. |
09:17 |
Dyrcona |
eeevil++ |
09:19 |
kmlussier |
mmorgan: I don't know if it's helpful, but there was a bit of discussion here - http://irc.evergreen-ils.org/evergreen/2013-10-28#i_43175. In this case, though, it was a library that was closing, so a little different. |
09:20 |
mmorgan |
tsbere: Hmm, need to think about that, I don't think they want to capture any holds after a certain point. |
09:21 |
mmorgan |
kmlussier: Thanks, I'll have a look. |
09:33 |
|
yboston joined #evergreen |
09:33 |
|
tspindler joined #evergreen |
09:34 |
|
RoganH joined #evergreen |
10:00 |
|
mllewellyn joined #evergreen |
10:06 |
|
collum joined #evergreen |
10:45 |
|
vanya joined #evergreen |
10:45 |
kmlussier |
yboston: I'm going to add an agenda item for general feedback on Snigdha's ideas. |
10:47 |
yboston |
OK |
10:48 |
RoganH |
kmlussier: I think that to streamline the feedback process, all discussions have to now be held in grammatically correct Latin. |
10:51 |
kmlussier |
RoganH: I haven't had any caffeine yet today, and expect me to use Latin? |
10:52 |
kmlussier |
Heh, I can't even type gramatically correct English. :) |
10:52 |
RoganH |
kmlussier: actually no, I just figure if no one can participate it'll streamline things a lot more |
10:55 |
kmlussier |
I actually took a year of Latin once, but I was in Venezuela at the time and was having enough difficulty following the teacher's Spanish explanations of what he was teaching us. Needless to say, it didn't stick. |
10:56 |
RoganH |
I took many years of latin but it was a very very long time ago. It was enough though that the Brian being punished by the Centurion scene in Life of Brian is still one of the funniest things ever to me. |
10:56 |
RoganH |
Apparently John Cleese used to be a Latin teacher (according to the Criterion edition commentary of said movie). |
10:57 |
kmlussier |
Really? I imagine it would be great fun to have John Cleese as a teacher. |
10:59 |
berick |
kmlussier: you took latin in spanish? |
11:00 |
kmlussier |
berick: Yup. I took french in spanish too. |
11:00 |
|
vlewis joined #evergreen |
11:00 |
berick |
kmlussier: i can't even... ;) |
11:00 |
berick |
that deserves a badge of some sort |
11:00 |
RoganH |
Latin in spanish isn't bad, same vowel structure, lots of root words, etc..... Same for French I would think. |
11:01 |
RoganH |
The conjugation in Latin is what drives most people nuts. |
11:01 |
kmlussier |
berick: I also took English (as a second language) in spanish. The funny thing is I didn't get a perfect score in my last term. :) |
11:04 |
berick |
kmlussier: too many ain't's and ya'll's, I assume ;) |
11:05 |
kmlussier |
berick: Ha! Given where I'm from, it's more likely that I wasn't using my r's. |
11:07 |
berick |
donde esta el coche? WHERE'S THE CAAAHHH |
11:07 |
* kmlussier |
chuckles |
11:07 |
kmlussier |
It's funny how much you learn about the existing client when testing the new client. I keep finding things that are missing, just to discover they never existed. |
11:08 |
* kmlussier |
should submit those reports anyway just to drive graced crazy. |
11:08 |
berick |
heh |
11:09 |
|
snigdha26 joined #evergreen |
11:34 |
* jeff |
grins |
11:37 |
* eeevil |
sets up .forward for berickxx... |
11:39 |
berick |
oh no, mail loop |
11:43 |
pinesol_green |
[evergreen|Angela Kilsdonk] Documentation bug: corrected image file - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4ab439f> |
11:45 |
|
sandbergja joined #evergreen |
11:48 |
|
Em joined #evergreen |
11:53 |
|
nhilton joined #evergreen |
11:58 |
berick |
looking like mon. 2pm east. is best day for the dev mtg |
11:59 |
RoganH |
berick: oct 6th? |
11:59 |
berick |
RoganH: yes |
12:00 |
|
jihpringle joined #evergreen |
12:02 |
* kmlussier |
forgot to fill out the poll. |
12:02 |
berick |
there's still time |
12:05 |
kmlussier |
Done. Of course, I don't need to be there either. :) |
12:06 |
berick |
question about the draft agenda.. wiki says to edit the placeholder directly. i assume there's a backup? |
12:06 |
|
nhilton joined #evergreen |
12:06 |
berick |
or do you just clone the template? |
12:07 |
kmlussier |
berick: Once the meeting date was selected, I always just moved the placeholder to the new wiki page that becomes the real agenda. |
12:07 |
berick |
kmlussier: then how do you recover the placeholder? |
12:07 |
berick |
create a new one? |
12:08 |
bshum |
berick: kmlussier probably means clone the sample to the actual dated agenda page. |
12:08 |
kmlussier |
berick: Sorry, I mistated that. I copied what was in the placeholder and put it in the new agenda page. |
12:08 |
berick |
ah, ok, good, that's what I just did. |
12:09 |
bshum |
The existing template, you can always look back in the history of the page as well to bring it back to placeholder, generic mode. |
12:09 |
berick |
ah yes |
12:09 |
berick |
thanks kmlussier, bshum |
12:09 |
berick |
i'll give a little more time on the poll |
12:09 |
bshum |
I think sometimes people leave topics for discussion on the page so that they don't forget. |
12:09 |
bshum |
Not always. |
12:14 |
Bmagic |
csharp: We are having an issue checking in items that are marked long overdue. It seems that a permission is required. The UI says "COPY_STATUS_LONGOVERDUE.override" which is granted to the staff account in question. What am I missing? |
12:18 |
Dyrcona |
Bmagic: Maybe the depth on the permission isn't right. |
12:19 |
Bmagic |
Dyrcona: Acctually, now that I am looking at it really close, the UI is asking for "COPY_STATUS_LONG_OVERDUE.override" and I gave "COPY_STATUS_LONGOVERDUE.override" A typo in the permission table? |
12:19 |
berick |
kmlussier: do you anticipate any OPW discussion for the dev mtg? |
12:19 |
|
nhilton joined #evergreen |
12:20 |
Dyrcona |
Could be. Maybe there is a launchpad bug. |
12:20 |
|
Sato joined #evergreen |
12:21 |
kmlussier |
berick: I don't think so, but it might not be a bad idea for mentors on coding projects to let people know about the dev meeting as a way to get to know the community. |
12:21 |
berick |
kmlussier: good idea, thanks |
12:21 |
kmlussier |
We've only had one coding candidate who has sought feedback from the community, but I think she got a lot of good e-mail feedback, so I wouldn't think an agenda item is warranted. |
12:22 |
* kmlussier |
will also send out an e-mail for any mentors who may not be paying attention right now. |
12:22 |
Dyrcona |
I should fill out the poll for the meeting, too. |
12:25 |
Dyrcona |
Amazing! As of right now, my calendar is empty for next week. |
12:25 |
kmlussier |
Dyrcona: It is? |
12:25 |
Dyrcona |
<vizzini>Inconceivable!</vizzini> |
12:27 |
berick |
I read that as <vizzini>Uninvoiceable!</vizzini> |
12:28 |
Dyrcona |
Nothing is uninvoiceable.... ;) |
12:28 |
kmlussier |
berick: You've spent way too much time working on acquisitions. |
12:28 |
Dyrcona |
heh. |
12:45 |
kmlussier |
I'm puzzled by deep links into the web client. Sometimes a link to something like https://webby.evergreencatalog.com/eg/staff/circ/patron/3580/items_out works right away. Other times, it requires a refresh. |
12:45 |
kmlussier |
It always seems to require a refresh in Firefox. |
12:51 |
mmorgan |
Hmm. Interesting. I followed your link, and needed to authenticate. After authenticating, the page never loaded. I refreshed and it loaded right away. |
12:53 |
kmlussier |
mmorgan: Yes, it does that for me, even when I'm already authenticated. But sometimes it loads on the first try. Of course, the deep links are a happy side effect to going to the web client. But I was just curious why it doesn't always load on the first try. |
12:53 |
kmlussier |
A very happy side effect. :) |
12:53 |
RoganH |
Just curious, I don't see a way but thought I'd ask, anyone know of a way to suppress the credit card payment option for the internal transactions? |
12:55 |
kmlussier |
RoganH: You mean in the payment type dropdown of the bills UI? |
12:58 |
RoganH |
kmlussier: after that |
12:59 |
RoganH |
kmlussier: select credit card, put in amount, hit apply payment |
12:59 |
RoganH |
kmlussier: then it has a dropdown that asks "Process where?" and it defaults to "Process payment through Evergreen" and you can select "Record externally processed payment" |
12:59 |
kmlussier |
RoganH: Ah, I see. |
13:00 |
RoganH |
kmlussier: we want to either make the external process default or get rid of the internal entirely |
13:00 |
kmlussier |
RoganH: No, I can't help you. |
13:00 |
RoganH |
kmlussier: I don't think there is a way but I've been surprised before so it's always worth asking I figure. |
13:01 |
Bmagic |
Dyrcona: csharp: I didn't realize before I implemented it that long overdue basically does the same thing as lost. Does it make sense for a system to use both long overdue and lost at different intervals. AKA: long overdue at 28 days and lost at 42 days. From my DB queries, I find that the Lost trigger doesn't mark items lost when they are already long overdue |
13:02 |
kmlussier |
RoganH: It would be nice if the default depended on whether your library has enabled the "Allow Credit Card Payments" OU setting or not. |
13:03 |
* kmlussier |
may not be able to help, but is great at giving unsolicited opinions. :) |
13:03 |
RoganH |
kmlussier: I agree. |
13:03 |
mmorgan |
Bmagic: I don't think the two can work together. As things are now, I think you need to choose one or the other. |
13:04 |
mmorgan |
we wanted to do the same thing. |
13:04 |
mmorgan |
Have a look at lp 1331174 |
13:04 |
pinesol_green |
Launchpad bug 1331174 in Evergreen "Long Overdue processing needs org unit settings separate from Lost Processing" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1331174 |
13:06 |
Bmagic |
mmorgan++ |
13:06 |
|
ldwhalen joined #evergreen |
13:12 |
|
mdriscoll1 joined #evergreen |
13:15 |
jeff |
RoganH: pretty sure we made the "external" option default in our staff client with a minor tweak to the XUL |
13:16 |
jeff |
RoganH: http://git.evergreen-ils.org/?p=evergreen/tadl.git;a=commit;h=47a0c636b6c6fe9dbf3e65c220d0f0aecd965c3c |
13:16 |
jeff |
RoganH: i believe that's working for us, though i haven't seen that screen in a while. |
13:16 |
jeff |
RoganH: i would support an org unit setting to completely disable the end user UI bits when there's no processor enabled/defined. |
13:20 |
|
Christineb joined #evergreen |
13:42 |
bshum |
gmcharlt: I just posted the announcement for Evergreen 2.7.0 and included a caveat about needing to use OpenSRF 2.4 series code. |
13:43 |
gmcharlt |
bshum++ |
13:43 |
bshum |
When we have some time, I'd like to review what we need to do to finish up OpenSRF 2.4.0 |
13:43 |
bshum |
Maybe the next dev meeting |
13:43 |
bshum |
*before |
13:43 |
bshum |
Or I guess part of it, during the OpenSRF section of it |
13:43 |
* bshum |
will figure it out sometime |
13:43 |
gmcharlt |
yeah - though I'm hoping to mold 2.4.0 into shape sooner than that |
13:46 |
bshum |
gmcharlt: So far as I can tell it seems fine :) |
13:46 |
dbwells |
bshum++ |
13:46 |
gmcharlt |
bshum: oh, for sure |
13:46 |
gmcharlt |
mabye applying the chrome plating would have been a better metaphor ;) |
13:49 |
bshum |
Shiny :) |
13:50 |
yboston |
heads up the DIG monthy meeting starts at 2 PM EST |
13:51 |
csharp |
Bmagic: the concept behind "Longoverdue" was to have an automatic "age to lost" feature that was clearly system-created, FYI - our libs didn't want L |
13:51 |
csharp |
"Lost" to mean anything system-created |
13:52 |
Bmagic |
csharp: I don't get it. "age to lost" means lost right? |
13:54 |
|
rsoulliere joined #evergreen |
13:54 |
tsbere |
Bmagic: The issue I think stems from "You can manually mark Lost OR automatically mark Lost, and you can't tell which was done at a glance" |
13:55 |
tsbere |
Bmagic: As such "Longoverdue" takes the place of "automatically mark Lost" for those that want it to |
13:55 |
Bmagic |
tsbere: I see, system vs. human |
13:56 |
berick |
hm, i still think of them as two separate things |
13:56 |
csharp |
exactly |
13:56 |
RoganH |
jeff: good to know, thanks! |
13:56 |
berick |
a LO item can still be manually marked as lost, no? |
13:56 |
|
kbutler joined #evergreen |
13:56 |
Bmagic |
berick: good question |
13:56 |
berick |
iow, one doesn't necessarilyreplace the other |
13:56 |
csharp |
berick: I'm pretty sure it can |
13:57 |
tsbere |
berick: I said "for those that want it to" - For those of us who want automatic still I think "Longoverdue" can be an intermediate step. "This is long overdue, but we aren't going to call it lost for another month or until the patron admits they lost it" and such. |
13:57 |
csharp |
PINES will be using it as a replacement for auto-lost |
13:58 |
berick |
tsbere: ah, I misinterpreted what you said |
13:58 |
Bmagic |
tsbere: csharp: our libraries would like the system to mark things longoverdue and just apply the penalty sans billing until lost happens. I think im going to take a crack at the LP bug |
13:58 |
csharp |
ok |
14:00 |
jcamins |
You know what would be a useful feature to go with longoverdue? A process to automatically mark longoverdue books that are returned as "long lost" and send a message to the local paper with a pre-written fluff piece about the descendents of the original borrower being forgiven ten thousand dollars in fines. |
14:00 |
yboston |
#startmeeting 2014-10-02 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting. |
14:00 |
pinesol_green |
Meeting started Thu Oct 2 14:00:24 2014 US/Eastern. The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
14:00 |
pinesol_green |
The meeting name has been set to '2014_10_02___dig_monthly_meeting_evergreen_documentation_interest_group__dig__monthly_meeting_' |
14:00 |
yboston |
The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20141002-agenda |
14:00 |
yboston |
#topic Introductions |
14:00 |
yboston |
Please feel free to start introducing yourselves... |
14:01 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin College) |
14:01 |
yboston |
#info yboston is Yamil Suarez @ Berklee College of Music - DIG meeting facilitator |
14:01 |
Christineb |
#info Christineb is Christine Burns @ BC Libraries Cooperative |
14:01 |
kbutler |
#info kbutler is Kate Butler, Rodgers Library (Hudson NH) |
14:01 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn Benton Community College (Albany, OR) |
14:01 |
rsoulliere |
#info rsoulliere is Robert Soulliere, Mohawk College |
14:01 |
jihpringle |
#info jihpringle is Jennifer Pringle @ BC Libraries Cooperative |
14:02 |
stompro |
#info stompro is Josh Stompro @ Lake Agassiz Regional Library System (MN) |
14:02 |
snigdha26 |
#info snigdha26 is Snigdha Dagar, OPW candidate |
14:02 |
bshum |
#info bshum is Ben Shum, Bibliomation |
14:02 |
yboston |
heads up there is another meeting that start at 3:00 PM EST |
14:02 |
yboston |
today |
14:03 |
yboston |
#topic old business |
14:03 |
yboston |
sorry, we shoudl do content coordinator reports |
14:03 |
yboston |
#topic coordinator reports (if any) |
14:03 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
14:03 |
|
mrpeters joined #evergreen |
14:03 |
ericar |
#info ericar is Erica Rohlfs @ Equinox |
14:04 |
kmlussier |
#topic Release Coordinator report |
14:04 |
kmlussier |
#info The Release Notes for 2.7.0 are done |
14:04 |
remingtron |
kmlussier++ |
14:04 |
kmlussier |
#info I do plan to add links from the release notes to the documentation for the new feature, but we're still waiting on some 2.7 documentation. |
14:04 |
kmlussier |
End of report. |
14:05 |
yboston |
kmlussier++ |
14:05 |
yboston |
kmlussier: do you know what is missing? |
14:05 |
kmlussier |
Also, I just wanted to mention that there were very few features missing from the release notes on my first pass, so the developers did a good job of adding the release notes as they submitted code. |
14:05 |
kmlussier |
developers++ |
14:06 |
yboston |
developers++ |
14:06 |
kmlussier |
yboston: Just a few things missing, I think. http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:2.7_needs |
14:07 |
yboston |
should we check in on each other between now and the next meeting to make sure we are done with 2.7? |
14:08 |
|
zaimma joined #evergreen |
14:08 |
remingtron |
yes, good idea |
14:09 |
kmlussier |
I have updates for a couple of the items. I asked krvmga to send me his Content Cafe docs so that I could review them and put them in a working branch. |
14:09 |
|
kakes joined #evergreen |
14:09 |
remingtron |
kmlussier: do you have them now? or still waiting? |
14:09 |
yboston |
kmlussier: do you mind sending out another emial to check in in a couple of weeks? if not we can wait for the next meeting, by putting an item in the agenda again for 27 |
14:10 |
kmlussier |
And I have on outstanding item for MARC Stream Importer. I have a colleague who did some rough documentation a while back that I was going to use. But I won'g get to it for at least another week. |
14:10 |
kmlussier |
remingtron: Still waiting. I'll see him Monday and can remind him again. |
14:10 |
kmlussier |
yboston: Sure |
14:10 |
remingtron |
kmlussier: sounds fine. if you need a hand reviewing or pushing things in, let me know |
14:11 |
kmlussier |
remingtron: Thanks! I'll probably take you up on that offer. |
14:11 |
yboston |
#action kmlussier will check in on list to help move along pending 2.7 docs |
14:11 |
yboston |
#action yboston will add agenda entry to November DIG meeting to check in on pending 2.7 docs |
14:12 |
yboston |
if neccessary, in a couple of weeks we can just find another volunteer to finsish was was started on stream importer (I could volunteer then) |
14:13 |
yboston |
should we move on to see if Robert wants to report soemthing? |
14:13 |
remingtron |
yes |
14:13 |
rsoulliere |
#topic Conversion Coordinator Report |
14:13 |
rsoulliere |
#info 2.7 docs should be built in the next couple of days from the new rel_2_7 branch. One faulty image is causing a delay but should be an easy fix. |
14:14 |
remingtron |
rsoulliere: I'll try to backport that fix right now |
14:14 |
rsoulliere |
remingtron++ |
14:14 |
rsoulliere |
That is all I had. |
14:14 |
yboston |
rsoulliere++ |
14:15 |
yboston |
in the interest of time, I would like to start with new business |
14:15 |
kmlussier |
rsoulliere++ |
14:15 |
|
nhilton_ joined #evergreen |
14:15 |
remingtron |
rsoulliere++ |
14:15 |
yboston |
#topic new business |
14:15 |
yboston |
#topic Review of EG Upgrading Instructions (Robert) |
14:16 |
remingtron |
I was discussing this with rsoulliere earlier today |
14:16 |
rsoulliere |
Remingtron addressed the issue nicely by adding a note in the docs. |
14:17 |
yboston |
do you have a link or commit has for what he added? |
14:17 |
remingtron |
it was July 10 or so |
14:18 |
remingtron |
I'll look for a link |
14:18 |
yboston |
the date is fine for now |
14:18 |
remingtron |
#link http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=28a5085fd645c9470b852c9700661dbe4cbddf18 |
14:18 |
pinesol_green |
[evergreen|Remington Steed] Documentation: Upgrade instructions examples - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=28a5085> |
14:19 |
yboston |
I have never done an upgrade so I have not been able to help with testing those instructions so far. thanks rsoulliere and remingtron for working on this |
14:19 |
rsoulliere |
And here it is in the docs: http://docs.evergreen-ils.org/2.6/_upgrade_the_evergreen_database_schema.html |
14:19 |
yboston |
anything else to add or any questions from others? |
14:21 |
yboston |
OK, I will move on |
14:21 |
yboston |
#topic 2014 DIG hack-a-way post-mortem (Yamil) |
14:21 |
yboston |
(I am skipping the topic on 2.7 since we spoke about it already) |
14:21 |
|
vlewis_ joined #evergreen |
14:22 |
yboston |
I am personally drwaing a blank on anything that I had pending from the hack-a-way |
14:22 |
kmlussier |
yboston: It was a great day. Fun was had by all! |
14:22 |
yboston |
is anyone waiting for me to push any code to the repo for them? |
14:22 |
kbutler |
yboston: it felt like it was really productive |
14:22 |
yboston |
is this the first time we speak of the DIG hack-a-way since it happened? |
14:23 |
remingtron |
yboston: I think this is the first time |
14:23 |
kmlussier |
Yes |
14:23 |
yboston |
I thought it was the best one so far |
14:23 |
yboston |
I am glad that since the last one we we severla small adjustments to our practices to improve our success |
14:24 |
yboston |
like just focusing on 2.7 |
14:24 |
yboston |
it was helpful how many more peopel are usign git or Github one way or another |
14:25 |
remingtron |
it's exciting to see people participating so much! |
14:25 |
yboston |
the next time we plan to be together physically again will be at the next conference in May |
14:25 |
|
buzzy joined #evergreen |
14:25 |
remingtron |
should we try for at least a digital hackaway before the next release, whenever that is? |
14:25 |
yboston |
unless we want to try another one earlynext year |
14:26 |
remingtron |
might be before the conf |
14:26 |
yboston |
I am open to another event, even if it is remotely or just half a day befoer the next release |
14:27 |
yboston |
we can just wait to see what the developers decide in the next couple of months |
14:27 |
yboston |
they might want to stick to a February/March release date liek they have been doing lately |
14:27 |
remingtron |
agreed. we'll address it when 2.8 release is scheduled |
14:27 |
|
DonB_ joined #evergreen |
14:28 |
kmlussier |
Unless we wanted to spend a day focusing on web client docs |
14:28 |
yboston |
kmlussier: very true |
14:28 |
remingtron |
oooooo, good point |
14:28 |
remingtron |
well, let's discuss that on the list |
14:29 |
kmlussier |
I know I'll be doing some documentation while testing, but I don't know how far I'll get. |
14:29 |
remingtron |
jihpringle volunteered to help with preview web client docs |
14:29 |
yboston |
who would like to follow up on the list to get ideas for how to tackle web client docs |
14:29 |
yboston |
? |
14:29 |
remingtron |
kmlussier: let's coordinate |
14:30 |
kmlussier |
remingtron: Sure, sounds good. |
14:30 |
remingtron |
yboston: I'll take the lead |
14:30 |
yboston |
OK |
14:30 |
jihpringle |
are we going to have a separate set of docs for the web client or a section in 2.7or 2.8? |
14:30 |
yboston |
#action remingtron will start a thread on DIG list on documenting the web client |
14:31 |
remingtron |
jihpringle: I think in 2.7 and 2.8, etc. |
14:31 |
remingtron |
but that could change |
14:31 |
jihpringle |
I just wonder at how long that will get as more module are done |
14:31 |
bshum |
I think a section makes the most sense. |
14:31 |
yboston |
good question, though I doubt we can answer it today |
14:32 |
jihpringle |
do we want to discuss it on the list and then decide in November? |
14:32 |
jihpringle |
we can contribute docs to it until we know where to put them |
14:32 |
yboston |
BTW, we are just past the 30 minute mark |
14:32 |
jihpringle |
can = can't |
14:32 |
remingtron |
jihpringle: yeah, let's discuss on the list and revisit at next mtg |
14:32 |
* kmlussier |
agrees that a section makes the most sense. |
14:33 |
remingtron |
sounds like we'll start with a section in 2.7 |
14:33 |
kmlussier |
It will get long, but we'll eventually be getting rid of the old docs once the old client is deprecated. |
14:33 |
yboston |
or a section in master? |
14:33 |
remingtron |
thanks all for the input! |
14:33 |
kmlussier |
If the preview is available in 2.7, then it probably should be in 2.7 |
14:33 |
remingtron |
yboston: yeah, 2.7 and master both |
14:33 |
yboston |
should we move on? or we can continue too |
14:34 |
remingtron |
master will change as the new version changes |
14:34 |
remingtron |
I'm happy to move on |
14:34 |
kmlussier |
+1 |
14:34 |
yboston |
#idea hack a DIG hack-a-way just for the new web client |
14:35 |
yboston |
#idea consider having another DIG hack-a-way nefore the next major EG release in 2015 |
14:35 |
yboston |
#topic Feedback to OPW candidate's doc site ideas (Kathy, Snigdha) |
14:35 |
kmlussier |
#link http://markmail.org/thread/kjddts4zod2uwbe6 |
14:36 |
yboston |
first of all I would like to welcome our OPW intern candidate snigdha26 |
14:36 |
remingtron |
snigdha26: welcome! |
14:36 |
yboston |
and perhaps other OPW candidates that might be lurking |
14:36 |
kbutler |
I really liked snigdha26's ideas, especially the collapsible TOC over on the left. |
14:36 |
snigdha26 |
yboston: remingtron: thanks :) |
14:37 |
remingtron |
kbutler: +1 to that idea |
14:37 |
yboston |
kbutler: +1 |
14:37 |
stompro |
I also like the collapsible TOC idea. |
14:37 |
kmlussier |
I know snigdha26 received some feedback on her ideas in the e-mail thread, but I thought it might be good to see if others have feedback. It will help her has she pulls together her OPW application. |
14:37 |
yboston |
it is ice to get a fresh perspective from someone from the outside |
14:37 |
yboston |
*nice |
14:38 |
kmlussier |
Also, if people have other suggestions, now is a perfect time to bring them up. :) |
14:38 |
stompro |
I've posted to the list about changing how the search scoping works.. no responses though. |
14:38 |
remingtron |
I love the idea for adding a "Get Help" box at the top |
14:39 |
kbutler |
stompro: I liked that idea as well. It would make so much more sense than searching everything by default. |
14:39 |
remingtron |
stompro: I like the idea, but will depend on how easy it is to accomplish via Google custom search |
14:39 |
kmlussier |
stompro: I like the idea of choosing whether to search this release or all docs. |
14:39 |
snigdha26 |
stompro: I did respond on the thread, but I think google marked that as spam |
14:39 |
stompro |
I think Google custom search can do it, with the pro version. |
14:39 |
remingtron |
stompro: and how much time rsoulliere can put into it. If you figure out the details, send it to the DIG list |
14:40 |
kmlussier |
I wasn't sure about the "search the entire site" option since it would replicate what's on the Evergreen home page. |
14:40 |
yboston |
stompro: I liked the ides too, but I also have remingtron's reservation. though we just need a little research to find out what can be done |
14:40 |
stompro |
I'll look into it some more and post to the list. |
14:41 |
remingtron |
stompro++ |
14:41 |
remingtron |
Not sure about adding user comments to the docs |
14:42 |
kbutler |
I'm also in favor of taking a look at the documentation organization. As it's grown, we may find there are some topics better grouped together that are not together now. |
14:42 |
stompro |
I also like the FAQ idea, but populating it might be hard, we need to know which questions are frequently asked. And there are other FAQ's on the evergreen site that maybe already cover some things. |
14:42 |
kmlussier |
In the realm of other suggestions, one thing I like about PostgreSQL's doc site is that it clearly identifies which release the docs apply to (in case you arrived through a Google search) and has links along the top to quickly jump to the same section for other releases. |
14:43 |
remingtron |
kmlussier: +1 to that! |
14:43 |
|
vrani_ joined #evergreen |
14:43 |
kmlussier |
stompro: One thing I was thinking is we could maybe tie it closely together with the Evergreen site. I think there is a FAQ plug-in for WordPress (can't recall if we're using it). |
14:43 |
yboston |
I agree with kbutler , we might want to rethink the overall organization, but it might require having another docs server set up to test out new re-orgs of the content for us to see, wihtout impacting the main docs server |
14:43 |
stompro |
kbutler, I've wondered why there are 3 sections on tpac and several sections on Acquisitions. A reorg would be good. |
14:44 |
jihpringle |
+1 to a reorg |
14:44 |
kmlussier |
stompro: That's partially due to the Evergreen in Action docs being added without replacing the existing docs. I think if those were more explicitly called out as being "Evergreen in Action" docs, it would make more sense to the user. |
14:44 |
remingtron |
would someone like to give a try at reorganizing the docs? Even baby steps are good. Let's start a wiki page with Table of Contents |
14:45 |
kmlussier |
In terms of a docs server, I e-mailed with rsoulliere a few weeks ago about trying to replicate his set up on one of the MassLNC VM's |
14:45 |
kbutler |
+1 to that idea |
14:45 |
kbutler |
(wiki with table of contents) |
14:45 |
yboston |
+1 to wiki table of contents page to list ideas |
14:45 |
kmlussier |
I don't know if it could serve that purpose permanantly, but I think it will be needed if the doc project is one that's selected for OPW |
14:46 |
vrani |
hi I'm 2n year Student of MCA in NIT Durgapur. I'm interseted in ccontributing in Docccumentation part of Evergreen. Could anybody help in this regard? |
14:46 |
remingtron |
vrani: welcome! |
14:46 |
yboston |
kmlussier: csharp told me to contact gmcharlt about formally requesting a permanent VM for EG community purpoes to be used by DIG |
14:47 |
yboston |
to be hosted by PINES |
14:47 |
kmlussier |
Welcome vrani! You arrived at a good time. We're holding a documentation meeting right now. :) |
14:47 |
vrani |
awesome :) |
14:47 |
* gmcharlt |
perks up |
14:47 |
yboston |
vrani: I will send you a private message right now to ask for more info |
14:47 |
yboston |
vrani: I am one of the mentors for OPW |
14:47 |
vrani |
sounds good :) |
14:47 |
snigdha26 |
In case the wiki page with TOC is implemented, I could help out with it too and based on the ideas, see how the documentation could be re-organized |
14:47 |
vrani |
hi yboston |
14:48 |
gmcharlt |
yboston: I'm listening re VM - or feel free to email me |
14:48 |
remingtron |
snigdha26: sounds good. I will start the wiki page for reorganization ideas |
14:48 |
yboston |
I'll send you the email I started at the hack-a-way that I never sent :) |
14:48 |
yboston |
BTW, we have 12 minutes left in this meeting |
14:49 |
snigdha26 |
remingtron: I'll work with you on that then |
14:49 |
remingtron |
snigdha26++ |
14:49 |
kmlussier |
vrani: You may want to read up in the discussion we've just had about doc site ideas. http://irc.evergreen-ils.org/evergreen/2014-10-02 |
14:50 |
remingtron |
vrani: on that chat log, you can start at about 14:00 |
14:50 |
vrani |
ok thanks alot :) |
14:51 |
yboston |
how do we want to proceed at this point? |
14:51 |
yboston |
we talked about brinstorming on a re-orf |
14:52 |
yboston |
*re-org |
14:52 |
yboston |
with a wiki |
14:52 |
snigdha26 |
Thanks for the feedback everyone :) |
14:52 |
yboston |
remingtron: can I put you down for that action of creating the wiki? |
14:52 |
remingtron |
yboston: yes |
14:52 |
yboston |
#action remingtron will create a wiki page to collect ideas for a docs re-org |
14:52 |
remingtron |
I think we should keep discussing snigdha26's ideas on that email thread |
14:53 |
yboston |
we talked about setting up a test server to be used for OPW purposes, and a few other experiments |
14:53 |
kmlussier |
snigdha26++ Thanks for the ideas! |
14:53 |
yboston |
I can assign that task to me and kmlussier ? is that OK? |
14:54 |
kmlussier |
Does it need to be assigned? snigdha26 already started the thread. People should feel free to continue offering feedback and ideas, I think. |
14:54 |
|
kakes_ joined #evergreen |
14:54 |
yboston |
did we want to focus on a couple of the ideas first liek the search changes or testing the addition of a (collapsible) TOC tot he pages? |
14:54 |
yboston |
kmlussier: I meant about following up with a docs test server |
14:55 |
kmlussier |
Oh, sorry. |
14:55 |
* kmlussier |
was confused. |
14:55 |
yboston |
BTW, the next meeting, Academics for Evergeen, will start in 5 minutes |
14:55 |
kmlussier |
Yes, you should assign it to the two of us. And wrap up this meeting to make way for the academics. :) |
14:56 |
yboston |
#action yboston kmlussier will work to allocate a VM for use by DIG memebres and OPW intern for DIG work |
14:56 |
snigdha26 |
yboston: regarding the collapsible TOC - Im not sure if it can be done in asciidoc, but I can definitely do that in HTML |
14:56 |
remingtron |
kmlussier++ #VM |
14:56 |
yboston |
we need to stop, but if anyone has other questions or comments, bring them up on the DIG list for now |
14:56 |
yboston |
#stopmeeting |
14:56 |
kmlussier |
remingtron: No karma until I actually figure out how to do it. : \ |
14:57 |
kmlussier |
end |
14:57 |
yboston |
#endmeeting |
14:57 |
pinesol_green |
Meeting ended Thu Oct 2 14:57:01 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
14:57 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-14.00.html |
14:57 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-14.00.txt |
14:57 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-14.00.log.html |
14:57 |
jeff |
"oh, this was fixed in Dojo 5 years ago... surely..." nope. fixed in Dojo 1.4. |
14:57 |
remingtron |
yboston++ #leading DIG |
14:57 |
yboston |
those that have arrived for the Academics for Evergreen, we will start shortly |
14:58 |
remingtron |
snigdha26: right, start with HTML/css/javascript for the TOC |
14:58 |
remingtron |
snigdha26: you shouldn't need to worry about AsciiDoc for that |
14:58 |
|
jck_ joined #evergreen |
14:59 |
|
Em joined #evergreen |
14:59 |
snigdha26 |
remingtron: I'll get working on that |
14:59 |
remingtron |
snigdha26: glad to have your help! |
15:00 |
kmlussier |
#startmeeting 2014-10-02 - Evergreen for Academics meeting |
15:00 |
pinesol_green |
Meeting started Thu Oct 2 15:00:50 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_10_02___evergreen_for_academics_meeting' |
15:01 |
kmlussier |
#info Meeting agenda is available at http://wiki.evergreen-ils.org/doku.php?id=evergreen_for_academics:2014-10-02 |
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 |
mdriscoll1 |
#info mdriscoll is Martha Driscoll, NOBLE |
15:02 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative |
15:02 |
kakes_ |
#info kakes is Kelly Drake, FLO |
15:02 |
mmorgan |
#info mmorgan is Michele Morgan, NOBLE |
15:02 |
Em |
#info Em is Gail Blayney at Emily Carr |
15:02 |
DonB_ |
#info DonB is Don Butterworth, Asbury Seminary |
15:03 |
Christineb |
#info Christineb is Christine Burns @ BC Libraries Cooperative |
15:03 |
ericar |
#info ericar is Erica Rohlfs, Equinox Software |
15:03 |
kmlussier |
OK, people can keep introducing themselves as they join in. I'll move on to the next agenda topic. |
15:03 |
yboston |
#info yboston is Yamil Suarez @ Berklee College of Music |
15:04 |
kmlussier |
#topic Action Items from Last Meeting |
15:04 |
tspindler |
#info tspindler is Tim Spindler, C/W MARS |
15:04 |
jck_ |
#info jck is Joan Kranich, C/W MARS |
15:04 |
kmlussier |
yboston to e-mail list to gauge interest in development areas from people who could not make the meeting. |
15:05 |
kmlussier |
yboston: Is that something you did or is that something that didn't need to be done since the poll was sent out? |
15:05 |
yboston |
Sorry, I did not do that |
15:06 |
kmlussier |
I was thinking it probably didn't need to be done since people who didn't attend the meeting had the opportunity to participate in the poll. |
15:06 |
yboston |
though I hope we gleam a bit of that info form the survey |
15:06 |
yboston |
exactly |
15:06 |
kmlussier |
Yeah. I think we can cross it off the list. |
15:07 |
kmlussier |
#info yboston, kakes, kmlussier completed the action item to work on a form where people can prioritize goals on a scale of 1-3 and identify which areas they are willing tospec out further. |
15:07 |
kmlussier |
Though I will say it was mostly yboston and kakes. |
15:07 |
kmlussier |
#info kmlussier completed action item to send out minutes from the meeting |
15:08 |
kakes_ |
The scale ended up being 1 -5 |
15:08 |
kmlussier |
Is there anything we need to discuss from the action items before we look at the results of the poll? |
15:08 |
kakes_ |
nope. Lets go to the poll |
15:08 |
kmlussier |
#topic Results of Poll and Next Steps |
15:09 |
kakes_ |
Demographics and preliminary poll Results are at the bottom of the meeting page at: http://wiki.evergreen-ils.org/doku.php?id=evergreen_for_academics:2014-10-02 |
15:09 |
kmlussier |
#link http://wiki.evergreen-ils.org/lib/exe/fetch.php?media=evergreen_for_academics:academics_for_evergreen_poll_1_responses_.pdf |
15:09 |
kmlussier |
kakes: I'm going to turn it over to you. Anything of note that you want to highlight? |
15:10 |
kakes_ |
Thanks. well to start Data collected for the Goal priorities is inconsistent. |
15:10 |
kakes_ |
Some folks ranked every entry on the basis of 1 to 5, some selected only their top 5 and then ranked them from 1 to five. |
15:10 |
kakes_ |
Goals section therefore is listed first, and actually seems pretty clear. |
15:11 |
kakes_ |
The most popular item was the Academic Flavor PAC |
15:12 |
kakes_ |
and by popular I mean most interest and also the one folks volunteered most to work on in some capacity |
15:12 |
kakes_ |
But before we get into specifics does anyone have any questions on how this works, or what they are seeing? |
15:13 |
DonB_ |
Hi all ... What's a Flesh Specs? |
15:14 |
kmlussier |
Help with writing up specifications for the project. |
15:14 |
DonB_ |
OK |
15:14 |
DonB_ |
New term for me |
15:14 |
kakes_ |
Flesh specs= flesh out the spec. ie help write up what we want the system to do |
15:14 |
kakes_ |
Also, given your previous experience with Evergreen, does this list and the ranking fit with your expectations? |
15:15 |
yboston |
I am surprised how popular the PAC flavor was, but the rest makes sense |
15:16 |
kakes_ |
bueller? |
15:16 |
kmlussier |
I don't think I knew what to expect, but I think I was somewhat surprised course reserves didn't rank higher. Maybe because people are generally happy with the solutions they came up with? |
15:16 |
kmlussier |
Yes, the PAC flavor surprised me too. I would be interested in seeing what we come up with specs for that. Some may be things that are of value to multiple audiences, but it's hard to say. |
15:16 |
DonB_ |
We are moving to mostly electronic reserves |
15:17 |
yboston |
I did get a comment from a co-worker that they wished we had links explainign what each goal was, liek they did not know what LDAP was |
15:17 |
kmlussier |
DonB_: That makes sense. |
15:17 |
tspindler |
PAC flavor surprised me also |
15:17 |
kmlussier |
I also tend to think RDA support is a general wishlist item, not something specific to academics. But I digress. |
15:17 |
yboston |
or maybe PAC flavor means soemthing different to some people |
15:18 |
DonB_ |
I'm one pushing the PAC flavor |
15:18 |
kakes_ |
I too am curious as to what the PAC Flavor would be? |
15:18 |
|
adam__ joined #evergreen |
15:18 |
Christineb |
+1 to links explaining what each goal is |
15:18 |
kakes_ |
especially in light of the authority goals, and searching rating lower |
15:19 |
DonB_ |
I sent an email to the list outlining some of my concerns about PAC |
15:19 |
kmlussier |
Also, for LDAP, I think we already have a certain level of LDAP authentication. I wonder how much of it is dissemination more information about LDAP authentication or if there is something more that's needed there. |
15:19 |
yboston |
DonB_: I rmemmber reading your emails, though I am drawong a blank now |
15:19 |
yboston |
*drawing |
15:19 |
DonB_ |
As a cataloger I spend a lot of time making sure that the bib records have lots of data available for researchers. |
15:20 |
DonB_ |
I think there is room for improvement in how the bib records are displayer |
15:20 |
|
gsams joined #evergreen |
15:20 |
yboston |
BTW, I plan to set up LDAP in the next month or two, I can report back on my succes |
15:20 |
kmlussier |
http://georgialibraries.markmail.org/thread/rwta4qh2u5j5syjf |
15:20 |
|
flewis joined #evergreen |
15:20 |
DonB_ |
And the number of fields that are included for display in the default Evergreen PAC |
15:21 |
kakes_ |
Several other's indicated interest also - what are others looking for? |
15:21 |
DonB_ |
I created a concept drawing that is an attachment |
15:21 |
DonB_ |
on my earlier email |
15:23 |
Em |
We would like to be able to toggle between really limited results lists and the fuller record. Some instructors are looking for DVD titles we have, for instance. |
15:23 |
bshum |
yboston: When you poke at LDAP setup, I know that dbwells helped me through some of it when I had to set it up for a school library Biblio consulted with. Perhaps there's stuff that needs to be better spelled out in the setup process. But generally it works. |
15:23 |
kmlussier |
If it's adding additional fields, I think it could be easily added as an additional template. But I think I would call it "expanded bib view" rather than academic. |
15:24 |
yboston |
bshum++ |
15:26 |
kmlussier |
I guess the question is what we want to do for next steps. |
15:26 |
kmlussier |
Should we pick the top few and see if we can get a group of volunteers to flesh out the specs? Or do we want to have more discussion here on what people were looking for? |
15:27 |
kakes_ |
kmlussier: correct. but i was also wondering if the top 4 were related or separate? |
15:27 |
kakes_ |
ie are they all considered part of the Academic Pac, or are they seen as different? |
15:27 |
kmlussier |
Reports is definitely separate. |
15:27 |
kmlussier |
And federated searching is bigger than Academic PAC. |
15:28 |
yboston |
kmlussier: I agreee on reports; at least functionally |
15:28 |
kmlussier |
What were people looking for on reports. Canned reports specific to academics? |
15:28 |
jck_ |
is the thought one Academic PAC flavor or customized PACS more specific to academics? |
15:28 |
yboston |
I would argue it is bigger than EG |
15:28 |
yboston |
federation would be a departure from current functionality of EG |
15:29 |
kmlussier |
Does the current batch of Evergren canned reports (the ones presumably more geared towards public libraries) still work for recent releases? |
15:29 |
tspindler |
i agree, I think federated search is a lot bigger |
15:29 |
DonB_ |
We are neck deep preparing for accreditation visits. We need reports that deal specifically with what is required by these agencies |
15:30 |
tspindler |
for reports, i'm not sure its really a question of functionality but the canned reports that need to be developed |
15:30 |
jck_ |
I think Evergreen reports by call number can be difficult |
15:30 |
kmlussier |
Speaking personally, and not for all of MassLNC, one concern I have is that we might be overlooking real development needs with things that can be customized locally. Specifically the PAC academic flavor and the reports. |
15:30 |
kakes_ |
I think we found that some of the reports we needed might not be possible |
15:30 |
DonB_ |
Perhaps we need a Reports Repository somewhere |
15:31 |
tspindler |
one area that would help a lot in accreditation might be being able to quickly add batches fo stat cats for reporting purproses |
15:31 |
kakes_ |
like jck_ says |
15:31 |
dbwells |
yboston: The LDAP code has gotten gradually more robust as more people have used it. Feel free to ask if you get stuck. We'll get it to work one way or another. |
15:31 |
yboston |
dbwells: thanks! |
15:32 |
kmlussier |
Didn't there used to be an area of the Evergreen wiki where people could share SQL reports? |
15:32 |
kakes_ |
Is RDA possible, or like Federated searching outside EG |
15:32 |
yboston |
I agree with Kathy that the goals of Academic PAC and Academic reports could be msotly achived by making a small gorup of people to put together documentation or sampel PAC templates |
15:33 |
kmlussier |
kakes_: RDA is possible. I think it goes beyond academics, but it's something the developers have been incorporating a bit at a time. |
15:33 |
jihpringle |
we're creating the reports our libraries need for reporting yearly stats ourselves as they are for a BC organization and so probably not relevant for others |
15:33 |
yboston |
I volunteer to lead a sub-group exploring changes to PAC templates |
15:33 |
DonB_ |
Budget reports are another area that are important to us. We need a snapshot of Available/Spent/Encumbered by various categories |
15:34 |
kmlussier |
If there's consensus on an academic PAC flavor, I can help with the coding something that can be added as an additional template in Evergreen. |
15:34 |
jihpringle |
those are good reports to have but would be useful for any acq library (not just academic) |
15:34 |
|
gsams joined #evergreen |
15:35 |
yboston |
lest set a time to flesh out these two most popular goals either at a different IRC meeting and/or on the mailing list. I would probaly make a sub wiki page for these two topics too |
15:35 |
kmlussier |
+1 |
15:36 |
DonB_ |
+1 |
15:36 |
kmlussier |
Does that sound like a good idea to everyone else? |
15:36 |
tspindler |
+1 |
15:36 |
yboston |
I would start with getting on the same page of what the goals mean |
15:36 |
Em |
1+ |
15:36 |
mdriscoll1 |
+1 |
15:36 |
kmlussier |
I'm willing to help with yboston on PAC flavor. |
15:36 |
DonB_ |
I'd like to be involved with PAC flavor also |
15:36 |
tspindler |
ybost: yes, it is unclear to me what an academic PAC flavor would be |
15:36 |
kmlussier |
Is there anyone who would like to lead the reports effort? |
15:37 |
yboston |
perhpas once we have a path for the first two, which might not need much expensive development, we can more easily look at the other goals |
15:37 |
kmlussier |
Are there other items on this list that somebody would like to make a pitch for moving forward on now rather than waiting? |
15:38 |
yboston |
I need to work on authorites stuff as much as possible, and will be submitting some rudementary code at some point |
15:38 |
kmlussier |
Also, we do need somebody to volunteer to get the ball rolling on reports to make it happen. |
15:38 |
DonB_ |
Improved call number sorting is important for Academics |
15:38 |
DonB_ |
The vast majority of Academics us LC |
15:39 |
DonB_ |
Tangentially the bug when printing an LC call number is very painful for us |
15:39 |
mdriscoll1 |
Batch patron functions is important to me. I do lots of patron loading and many academic want to purge as well. |
15:39 |
tspindler |
i think for us any improvement on authorities management would be most valuable |
15:40 |
kmlussier |
I know several libraries that have been concerned about authorities. Have other academics been experiencing the same problems DonB_ notes with LC call number sorting? |
15:41 |
yboston |
i have had soem issues with call number sorting |
15:41 |
mdriscoll1 |
NOBLE has over 1,000 report templates. Maybe i can convince our report guru to lead the effort? |
15:41 |
tspindler |
as jck pointed out, it is a problem in reporting sometimes, you can get around it some but it is klunky |
15:41 |
Em |
We have issues with call number sorting |
15:41 |
yboston |
will be looking into call number sorting this semster at some point |
15:41 |
kakes_ |
We noted the Call number issue in our trial, and it is an issue, especially in regards to reporting |
15:41 |
tspindler |
LC sorting that is |
15:42 |
yboston |
I have been affected by call number sorting when using the "shelf browser", have not used cal number sorting in reports |
15:42 |
kmlussier |
But it seemed to rank fairly low in the results |
15:43 |
Em |
Call number sorting in reports is a real issue for us. |
15:43 |
DonB_ |
We need to be able to report quantities by call number range |
15:43 |
jck_ |
It may rank low for PAC searching but very much needed for reports and pull lists for Holds. |
15:43 |
DonB_ |
How many in BX, or BR etc |
15:44 |
tspindler |
DonB: one way we have been faciliting that is by using stat cats, its preliminary at this point |
15:44 |
kakes_ |
and unfortuanetly that was the one 'goal' that the data wasn't collected for. - LC Call numbewr |
15:44 |
kmlussier |
For the pull list, I knwo we do have a recent fix to LC call number sorting in staff client interfaces, including the holds interfaces. So I think that may already be good. |
15:44 |
yboston |
the call number sorting might be something that will require development |
15:45 |
yboston |
does someone want to lead a group to list the current complaints and the fucntionality that would be preffered |
15:45 |
kmlussier |
So if we add the three items that people pitched, that would be a total of five projects to possibly flesh out specs on. Is that too much or should we just start with the two? |
15:45 |
kmlussier |
Excuse my typos. I'm typing too fast. :) |
15:45 |
yboston |
then that group could solicit a bib for a developer to address those specific issues |
15:45 |
tspindler |
could you repeat the 5 projects? |
15:45 |
kakes_ |
What are the five? |
15:45 |
kmlussier |
Unless the group included somebody who could work on the code. |
15:46 |
kmlussier |
academic flavor, reports, authorities management, patron loading, and lc call number sorting. |
15:46 |
kmlussier |
It seems like authorities and patron loading would be larger projects to tackle. |
15:46 |
tspindler |
i can't work on code but I would be willing to help in any with with yboston on authorities |
15:47 |
kmlussier |
It seems like we would keep ourselves very busy with that list. :) |
15:47 |
mdriscoll1 |
DonB_: select count(*) from asset.call_number where label ilike 'BX%' |
15:47 |
yboston |
we can start with the PAC flavor becuase we have one person that would lead that gorup (me) |
15:47 |
yboston |
don't think we can start without a group leader(s) |
15:47 |
kmlussier |
mdriscoll1: Can I ask you to lead something for patron loading. I know it's something you've wanted to see for a very long time. |
15:48 |
mdriscoll1 |
Sure. |
15:48 |
kmlussier |
mdriscoll++ |
15:48 |
yboston |
we can definelty start threads on the mailing list to flesh out ideas of each goal, and we can store ideas on the wiki, until a leader emerges. |
15:48 |
kmlussier |
mdriscoll1 was also going to see if she could recruit somebody for reports, but if somebody else here would like to work on it, feel free to speak up. |
15:49 |
kmlussier |
Is there anyone who would like to lead on authorities or on LC call number sorting? |
15:49 |
* kmlussier |
will turn these things into action items shortly. |
15:49 |
yboston |
I can lead authoritites |
15:49 |
tspindler |
i can lead on authorities |
15:49 |
tspindler |
or yboston ;) |
15:49 |
yboston |
I'll do call number |
15:49 |
yboston |
though soemone else might want to lead call numbers |
15:49 |
DonB_ |
I'm still so new at Evergreen that I don't feel qualified to lead anything. But I'm willing to be involved with Reports and PAC flavor |
15:50 |
kmlussier |
Newbies can lead too! Look what kakes has done! :) |
15:50 |
yboston |
DonB_: contact me so I can give you wiki access, that is one way to help with a group(s) |
15:51 |
kmlussier |
ok, I'm going to write up some action items. |
15:51 |
kmlussier |
#action yboston and kmlussier to lead Academic PAC flavor group |
15:51 |
kmlussier |
#action mdriscoll to lead patron loading group |
15:51 |
yboston |
anybody else that wants to help fill up wiki pages with relevant bug reports or wishlist items, just contact me |
15:52 |
kmlussier |
#action tspindler to lead authorities group |
15:52 |
yboston |
kmlussier: put me down to create wiki sub pages |
15:52 |
kmlussier |
I took yboston off that one since he volunteered for call number sorting |
15:52 |
kmlussier |
#action yboston to lead Call Number Sorting group |
15:52 |
kmlussier |
yboston: I think the group leaders should create their own wiki pages. |
15:52 |
Christineb |
I am available to test, etc... I cannot do code |
15:53 |
kmlussier |
Christineb: We're starting with building of specs, so that might be something to help with too. |
15:53 |
kakes_ |
lots of the survey respondents indicated they would help with specing and testing |
15:53 |
kmlussier |
Did I miss anything? |
15:53 |
Christineb |
kmlussier: ok I would like to help where I can |
15:54 |
kmlussier |
So the group leaders will be responsible for soliciting volunteers and starting to pull together needs/specs? Does that sound right? |
15:54 |
kmlussier |
And we report back at the next meeting? |
15:54 |
kakes_ |
sounds good |
15:55 |
jihpringle |
+1 |
15:55 |
Em |
1+ |
15:55 |
tspindler |
+1 |
15:55 |
kmlussier |
Speaking of the next meeting, any objections to me moving on to a topic not on the agenda related to the next meeting date? |
15:55 |
mdriscoll1 |
+1 |
15:55 |
yboston |
kmlussier++ |
15:55 |
yboston |
+1 |
15:55 |
yboston |
go ahead kathy |
15:55 |
kmlussier |
#topic Next meeting date |
15:56 |
kmlussier |
I know we agreed to meet on the first Thursday of the month, but I dont' think I realized at the time that the meeting time is right after the DIG meeting. |
15:56 |
kmlussier |
Which isn't totally undoable, but there are a couple of us who participate in both. |
15:57 |
kmlussier |
I was just wondering if people would be amenable to scheduling it for another Thursday in the month. |
15:57 |
kmlussier |
But not the 3rd Thursday, because then we have EOB. |
15:57 |
yboston |
what about the second Thursday of the month as an alternatively |
15:57 |
DonB_ |
Works for me |
15:57 |
yboston |
I have EG board meeting the third thursday of the month |
15:58 |
kakes_ |
fine for us |
15:58 |
jihpringle |
works for me |
15:58 |
kmlussier |
OK, anything else before we end the meeting? |
15:58 |
tspindler |
works forme |
15:58 |
mdriscoll1 |
ok with me |
15:58 |
kmlussier |
Going one, going twice... |
15:58 |
jihpringle |
since we're not going to be right after DIG could we do an hour earlier? |
15:59 |
jck_ |
sounds good |
15:59 |
DonB_ |
Also fine with me |
15:59 |
yboston |
fine with me |
15:59 |
mdriscoll1 |
fine with me too |
15:59 |
kmlussier |
Works for me. |
16:00 |
kmlussier |
kakes: How does it look for you? |
16:00 |
kakes_ |
that's fine tooo! |
16:00 |
kmlussier |
OK. We'll meet again at 2 p.m. Eastern November 13 then. |
16:00 |
kmlussier |
#endmeeting |
16:00 |
pinesol_green |
Meeting ended Thu Oct 2 16:00:54 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
16:00 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-15.00.html |
16:00 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-15.00.txt |
16:00 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-10-02-15.00.log.html |
16:01 |
yboston |
kmlussier: will you besending out minutes for this meeting on the list? |
16:01 |
kmlussier |
eeevil: I was just thinking, if the Academic PAC flavor is mostly about displaying more fields in the record summary, would the Display fields code help with it? |
16:01 |
kmlussier |
yboston: Yes. |
16:02 |
eeevil |
kmlussier: it certainly could. it would make config simpler, certainly. no template full of xpath, etc |
16:02 |
eeevil |
just "here's your fields, put them where you like" |
16:02 |
kmlussier |
eeevil: And you have a new branch available for testing, right? |
16:03 |
eeevil |
I do. I confirmed that it rebases to master cleanly (as of the hackaway) |
16:03 |
eeevil |
sec... |
16:03 |
kmlussier |
eeevil: But it sounds like it still needs work? |
16:03 |
eeevil |
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp1251394-metabib-display-fields |
16:04 |
kmlussier |
eeevil: I'll try to take some time to look at it once I'm done with web client testing. |
16:04 |
kmlussier |
If I ever finish with web client testing, that is. |
16:04 |
eeevil |
well, it started before browse, and both display and facet fields could probably benefit from being folded into the same underlying storage |
16:05 |
eeevil |
to cut down on duplicate data, at least |
16:06 |
eeevil |
kmlussier: note, that branch /only/ provides the backend. the tpac loader (and friends) would need to be taught to pull the data and pass it to the templates |
16:06 |
eeevil |
that's a smaller job than the backend, though |
16:07 |
eeevil |
there are already plenty of APIs for grabbing piles of data quickly (anon pcrud, fielder, flatfielder, maybe others) |
16:07 |
kmlussier |
eeevil: Ah, I see. Still, it may be a better approach than providing a new template with an expanded bib record view. |
16:07 |
eeevil |
so, could be a 10 line addition to EGWeb |
16:08 |
kmlussier |
eeevil: Sure, for somebody who knows what they're doing. :) |
16:08 |
eeevil |
heh |
16:08 |
eeevil |
there are several ways to attack the template level code |
16:08 |
eeevil |
a template that just uses all of what it's given, or |
16:09 |
eeevil |
a config table that specifies a layout, or |
16:09 |
eeevil |
a "stock overlay" that one enables by adding one apache directive to get more data on the screen |
16:09 |
eeevil |
or, or... :) |
16:09 |
eeevil |
it depends on where we want to invest the "save the time of the user" elbow grease |
16:10 |
eeevil |
and, which mechanism is /actually/ easier to use for your average systems librarian |
16:10 |
* kmlussier |
will just keep nodding her head as if she's following along. |
16:11 |
eeevil |
while TT2 is certainly easier to use than BibTemplate, it's more verbose. it's also not any more "safe" than BibTemplate was |
16:11 |
kmlussier |
Actually, I am following along to some extent. |
16:11 |
eeevil |
so, do we want to make configuring the screen "safe", "easy", or "powerful" |
16:11 |
eeevil |
or, what combo of those do we want |
16:12 |
eeevil |
we /can/ choose all three, but that might be trying to boil the ocean in v1 |
16:13 |
eeevil |
and now, I must disappear for a while ... **poof** |
16:13 |
kmlussier |
eeevil: Thanks for your thoughts. Have a nice night! |
16:14 |
|
crayonsnatcher joined #evergreen |
16:14 |
|
crayonsnatcher left #evergreen |
16:14 |
|
crayonsnatcher joined #evergreen |
16:18 |
|
nhilton joined #evergreen |
16:18 |
|
crayonsnatcher joined #evergreen |
16:20 |
|
crayonsnatcher left #evergreen |
16:21 |
|
buzzy joined #evergreen |
16:30 |
|
tspindler left #evergreen |
16:44 |
|
mdriscoll1 left #evergreen |
16:54 |
kmlussier |
hmmm...has something happened to webby? Im not longer getting results for searches that previously worked. Like "concerto" or "harry potter" |
16:55 |
kmlussier |
Maybe webby is telling me to stop working. |
16:56 |
Dyrcona |
Yes, I think so. |
16:56 |
Dyrcona |
I know I am stopping for the day. |
16:56 |
* kmlussier |
thinks she'll do just that. :) |
16:57 |
mmorgan |
yes, looks to me like webby has called it a day, too. |
16:58 |
* csharp |
keeps picturing Webby™ the Evergreen Mascot |
16:59 |
* bshum |
would buy one |
16:59 |
csharp |
something along the lines of Tux the penguin |
16:59 |
csharp |
@blame search tux |
16:59 |
pinesol_green |
csharp: 1 found: #8: "$who stole bradl's tux doll!" |
16:59 |
* mmorgan |
tries to imagine what creature it would be, keeps getting platypus for some reason. |
16:59 |
kmlussier |
Good night #evergreen! |
16:59 |
csharp |
@blame 8 webby |
16:59 |
pinesol_green |
csharp: webby stole bradl's tux doll! |
16:59 |
kmlussier |
mmorgan: I was thinking duck. |
17:00 |
* csharp |
likes the platypus idea |
17:00 |
mmorgan |
some combination of the three? |
17:00 |
jeff |
in some ways, we missed an opportunity to call the web staff client "Dana" |
17:00 |
mmorgan |
If it were earlier, I might be able to make that into a word |
17:00 |
kmlussier |
A web-footed gecko? |
17:01 |
kmlussier |
Dana? |
17:01 |
csharp |
but, jeff, there is no Dana ONLY XUL |
17:01 |
kmlussier |
Ah, ok. |
17:01 |
* kmlussier |
apparently hasn't watch Ghostbusters enough times to get the reference. |
17:01 |
csharp |
OMG - 30 years |
17:02 |
mmorgan |
Yikes, really?? |
17:02 |
csharp |
yeppers |
17:02 |
kmlussier |
csharp: Yup. How old do you feel now? ;) |
17:02 |
csharp |
older |
17:02 |
kmlussier |
Weren't they planning to re-release it for the anniversary? |
17:02 |
csharp |
yep, I think it's in theaters now |
17:02 |
csharp |
and Krispy Kreme has GB themed donuts |
17:03 |
kmlussier |
Oh, maybe I'll bring the kids. They've already seen it, but it's always more fun in the theater. |
17:03 |
jeff |
(or some other anti-XUL or anti-Zuul reference) |
17:03 |
csharp |
my son (11 years old) really liked it |
17:04 |
csharp |
"Go get her, Ray!" |
17:05 |
kmlussier |
I think it's already left the theaters in our area. Missed out. |
17:05 |
jeff |
failed SU attempts on the home firewall many many (wow, many) years ago resulted in either "Are you a god?" or "Ray, when someone asks if you're a god you say YES!" |
17:06 |
jeff |
it also made a "ping" noise when you pinged it. |
17:06 |
jeff |
netwinders were cool. |
17:06 |
* kmlussier |
leaves for real this time. Good night! |
17:07 |
csharp |
jeff++ # hahah |
17:15 |
|
sandbergja joined #evergreen |
17:19 |
|
mmorgan left #evergreen |
17:28 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
17:32 |
|
cherri joined #evergreen |
17:39 |
|
jeff_ joined #evergreen |
19:53 |
|
ldwhalen joined #evergreen |
21:03 |
|
vanya joined #evergreen |
21:05 |
vanya |
jeff : Are you there? |
21:26 |
|
ningalls joined #evergreen |
22:08 |
vanya |
I've been trying to look at Bug #978040 , and I was wondering if someone could tell me what files to look at regarding that. |
22:08 |
pinesol_green |
Launchpad bug 978040 in Evergreen "No result found search for patron by database id results in return to wrong interface" (affected: 1, heat: 6) [Low,Confirmed] https://launchpad.net/bugs/978040 |
22:50 |
|
remingtron joined #evergreen |
23:03 |
|
remingtron joined #evergreen |
23:12 |
|
nhilton joined #evergreen |
23:20 |
|
cherri joined #evergreen |