| Time |
Nick |
Message |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:15 |
|
rlefaive joined #evergreen |
| 07:41 |
|
Callender joined #evergreen |
| 07:46 |
|
Callender joined #evergreen |
| 07:48 |
|
ericar joined #evergreen |
| 08:29 |
|
rlefaive joined #evergreen |
| 08:31 |
|
rlefaive joined #evergreen |
| 08:35 |
|
rlefaive_ joined #evergreen |
| 08:35 |
|
Dyrcona joined #evergreen |
| 08:37 |
|
mrpeters joined #evergreen |
| 08:37 |
|
mmorgan joined #evergreen |
| 08:50 |
Dyrcona |
tsbere upgraded us to 2.9.2 + some bug fixes going into 2.9.3 last night. |
| 08:50 |
Dyrcona |
So, we're up to date again. Yay! |
| 08:52 |
mmorgan |
Dyrcona++ |
| 08:53 |
Dyrcona |
tsbere++ ;) |
| 08:54 |
mmorgan |
tsbere++ :) |
| 08:57 |
|
rhamby joined #evergreen |
| 08:58 |
Dyrcona |
Interesting tidbit from the upgrade.... |
| 08:58 |
Dyrcona |
tsbere also moved our database from regular HDD to SSD storage. |
| 08:58 |
Dyrcona |
It took less than 15 minute to move over 100GB of data. |
| 08:58 |
Dyrcona |
We both thought that would have taken longer. |
| 08:59 |
Dyrcona |
ssd++ |
| 09:27 |
|
jboyer joined #evergreen |
| 09:30 |
jboyer |
berick: did you mention in the last couple of months that you couldn't disable some version of ssl because the XUL client could no longer connect? Google-ing the logs is letting me down if so. |
| 09:32 |
|
mmorgan1 joined #evergreen |
| 09:32 |
Dyrcona |
jboyer: That is true. berick did say that, and I confirmed it with a quick test on my development system. |
| 09:32 |
Dyrcona |
You can, I believe disable SSL, but you can't disable certain versions of TLS. |
| 09:33 |
* Dyrcona |
can't comma right. |
| 09:34 |
jboyer |
Oh. That does sound more familiar. TLS 1.1 or 1.2 maybe. I was trying to look it up while I wait for my car to be repaired, this is how I stay entertained these days, I guess. |
| 09:35 |
Dyrcona |
I believe TLS 1.1, or possibly even 1.0, is the best that the staff client can do. |
| 09:36 |
jboyer |
And there are some reasons to disable those versions, correct? (Not as serious as old ssl, but still reasons I thought.) |
| 09:38 |
jboyer |
Well I can look into that now that I know what I'm actually looking for. Hopefully I'll be out of here soon anyway. Thanks for pointing me in the right direction. |
| 09:40 |
Dyrcona |
jboyer will likely be back before too long. |
| 09:41 |
|
yboston joined #evergreen |
| 09:44 |
Dyrcona |
@later tell jboyer https://bugs.launchpad.net/evergreen/+bug/1547668 |
| 09:44 |
pinesol_green |
Dyrcona: The operation succeeded. |
| 09:44 |
pinesol_green |
Launchpad bug 1547668 in Evergreen "XUL staff client does not support TLS above 1.0" [Undecided,New] |
| 09:48 |
|
mllewellyn joined #evergreen |
| 10:07 |
|
maryj joined #evergreen |
| 10:12 |
|
mmorgan joined #evergreen |
| 10:42 |
|
Christineb joined #evergreen |
| 11:07 |
|
vlewis joined #evergreen |
| 11:08 |
Bmagic |
bug 1437112 - was tested on bug squashing day and received sign offs. I noticed that it may* have introduced issues with the search screen |
| 11:08 |
pinesol_green |
Launchpad bug 1437112 in Evergreen "not possible to set workstation preferences in web staff client" [Undecided,Confirmed] https://launchpad.net/bugs/1437112 |
| 11:08 |
Bmagic |
https://sb1.missourievergreen.org/eg/staff/cat/catalog/index |
| 11:08 |
Bmagic |
gadmin/admin |
| 11:09 |
Bmagic |
maybe it's a mistake on the setup of the box, but I wanted to see if anyone else has this code on their machine? |
| 11:27 |
|
jvwoolf joined #evergreen |
| 11:29 |
|
mmorgan1 joined #evergreen |
| 11:37 |
|
JBoyer joined #evergreen |
| 11:46 |
|
sandbergja joined #evergreen |
| 12:09 |
kmlussier |
Bmagic: I believe Dyrcona loaded it on his dev server at one time along with several other branches. There were some issues, and he removed most of the branches because I had to focus my testing elsewhere. I never identified which branch was causing the problem. |
| 12:10 |
kmlussier |
Bmagic: I'm pretty sure it was the same issue you're seeing now. I would say that branch isn't ready to go. |
| 12:10 |
|
jihpringle joined #evergreen |
| 12:15 |
kmlussier |
Bmagic: Hmmm...It looks like the weird behavior happens only if you don't set your workstation search preferences. Once you set them, the advanced search screens come up okay for m. |
| 12:16 |
kmlussier |
Perhaps the tester started by setting the worsktation preferences and didn't notice that the search screen was messed up when the preferences weren't set. |
| 12:19 |
Bmagic |
kmlussier: I registered my workstation, and I am still getting {{label}} all over that page |
| 12:19 |
kmlussier |
Bmagic: That's the branch where you had to resolve conflicts, right? That should also be noted on the bug. Do you want to add a comment to the bug or should I? |
| 12:19 |
kmlussier |
Bmagic: No, it's not the workstation registration that fixed the display. It was setting the default search preferences. |
| 12:20 |
Bmagic |
I'll comment |
| 12:20 |
kmlussier |
Bmagic++ |
| 12:30 |
|
mmorgan1 left #evergreen |
| 12:31 |
|
meme joined #evergreen |
| 12:43 |
|
mmorgan joined #evergreen |
| 12:43 |
* Dyrcona |
wasn't sure about that one...so many branches.... |
| 12:43 |
|
rlefaive joined #evergreen |
| 12:45 |
Dyrcona |
It has been very quiet for the first day after an upgrade. |
| 12:45 |
kmlussier |
Dyrcona: That's a good thing, right? |
| 12:45 |
Dyrcona |
kmlussier: Yes, it is. |
| 12:45 |
kmlussier |
:) |
| 12:57 |
* mmorgan |
knocks on wood. |
| 13:18 |
|
Arty-chan joined #evergreen |
| 13:21 |
Arty-chan |
morning, does anyone know if incorrect character encoding in z39.50 import has anything to do with the settings on my end, or is it always an issue on the other library's end? |
| 13:24 |
pinesol_green |
[evergreen|Terran McCanna] LP#1551451 Hide OPAC footer when viewed inside staff client - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=0c131c6> |
| 13:43 |
|
meme joined #evergreen |
| 13:43 |
meme |
Just trying this out...Can someone respond to reassure me? |
| 13:44 |
dbwells |
meme: hello! |
| 13:44 |
meme |
Hello....I have a meeting here and I am trying things out.. |
| 13:45 |
meme |
Thanks...Now I am going to sit passively to see what happens.. |
| 13:54 |
|
alynn26 joined #evergreen |
| 13:54 |
Dyrcona |
Arty-chan: Are you asking about lp 1346518? (Comment #6 is of particular note.) |
| 13:54 |
pinesol_green |
Launchpad bug 1346518 in Evergreen "remote z39.50 search returns no results for terms with diacritics" [Undecided,New] https://launchpad.net/bugs/1346518 |
| 13:56 |
* kmlussier |
waves to meme |
| 13:57 |
kmlussier |
meme: While you're waiting for the meeting to start, you can read through the IRC Quick Start guide at http://wiki.evergreen-ils.org/doku.php?id=community:irc-quick-start. |
| 13:57 |
Arty-chan |
Dyrcona: no, I mean more if there are diacritics in the author's name and such in the results... the character encoding has clearly gone wrong somewhere, because they turn into symbols |
| 13:58 |
sandbergja |
Heads up: we'll be talking about Docs Re-org in about 2 minutes |
| 13:58 |
Dyrcona |
Arty-chan: The issues are probably related, but the answer is that I don't know the answer. |
| 13:58 |
Arty-chan |
ah well, thanks for trying |
| 14:00 |
sandbergja |
meme: glad you could join us! |
| 14:00 |
meme |
Me too.. |
| 14:01 |
sandbergja |
#startmeeting docs re-org update meeting |
| 14:01 |
pinesol_green |
Meeting started Mon Mar 7 14:01:16 2016 US/Eastern. The chair is sandbergja. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:01 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:01 |
pinesol_green |
The meeting name has been set to 'docs_re_org_update_meeting' |
| 14:01 |
sandbergja |
#chair yboston |
| 14:01 |
pinesol_green |
Current chairs: sandbergja yboston |
| 14:01 |
sandbergja |
Welcome, everyone! |
| 14:01 |
sandbergja |
Here's the agenda for today's meeting |
| 14:01 |
sandbergja |
#link http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:agenda_2016-03-07 |
| 14:02 |
sandbergja |
Let's get started with introductions |
| 14:02 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
| 14:02 |
alynn26 |
#info alynn26 is Lynn Floyd, Anderson County Library, SCLENDS |
| 14:02 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
| 14:02 |
meme |
#info meme is Meme Marlow, Worch Library Ohio |
| 14:02 |
Christineb |
#info Christineb is Christine Burns - BC Libraries Cooperative / SItka |
| 14:03 |
sandbergja |
Great; glad to have you all here |
| 14:03 |
sandbergja |
#topic Updates from circulation re-org group |
| 14:03 |
sandbergja |
I'm curious to hear about any progress or roadblock y'all have run into! |
| 14:03 |
Bmagic |
#info Bmagic is Blake GH, MOBIUS |
| 14:05 |
sandbergja |
It's also fine if there are no updates; I know we are all busy :-) |
| 14:05 |
meme |
Since I was not at last one, what were we supposed to have done... |
| 14:06 |
meme |
I am assuming you are talking about the updates from the groups? |
| 14:06 |
sandbergja |
Yes, thanks for asking, meme. We were going to start looking at what documentation already exists for front-line circ staff + client sysadmins |
| 14:07 |
sandbergja |
And start putting together some tables of contents for what we'd want to see in a Front-line circ manual or a staff client sysadmin manual |
| 14:07 |
meme |
Ok, thanks for the info... |
| 14:08 |
meme |
I did not do that.. |
| 14:08 |
Christineb |
some links to existing documentation have been added for client sys admins |
| 14:08 |
sandbergja |
Yeah, let's move on to looking at the client sys admin ToC |
| 14:08 |
sandbergja |
#topic Updates from client sysadmin group |
| 14:09 |
sandbergja |
#link http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:system_admin |
| 14:09 |
sandbergja |
Here's what we've come up with so far |
| 14:09 |
sandbergja |
All the links are to existing documentation that provides a basis for what we'd like to see in a client sysadmin manual |
| 14:10 |
|
Arty-chan left #evergreen |
| 14:10 |
sandbergja |
christineb++ jihpringle++ remingtron++ for all your help with this |
| 14:11 |
jihpringle |
I haven't had much time to look at this so far, but looking at it today I wonder if the sys admin manual is the best place for info on building staff clients |
| 14:12 |
sandbergja |
Good point! Where would we like to see that information? |
| 14:13 |
jihpringle |
in a manual aimed at sys admins outside of the staff client (not sure how to best word that) |
| 14:13 |
jihpringle |
I just don't think that most people using the admin functions in the staff client are going to be the ones building the clients |
| 14:14 |
sandbergja |
Good point |
| 14:14 |
remingtron |
jihpringle: "command line" or "shell access" are keywords for server-level admin |
| 14:15 |
sandbergja |
So maybe it should have a crosslink into the "command line" manual that says "if you are a Mac user, the instructions for building the client are here." |
| 14:15 |
sandbergja |
or something along those lines? |
| 14:15 |
alynn26 |
I was thinking more of the lines of Staff Client Administration, and then Server-Level Administration. To me there is the dividing fact of who has command line acess. |
| 14:16 |
jihpringle |
agreed |
| 14:16 |
|
edoceo joined #evergreen |
| 14:16 |
sandbergja |
That makes sense |
| 14:16 |
jihpringle |
I think calling this one Staff Client Administration more clearly describes who it is intended for |
| 14:17 |
sandbergja |
building a mac client does require a bunch of command line work |
| 14:17 |
sandbergja |
although not on a server |
| 14:18 |
jihpringle |
I suspect we will need a manual for everthing that is done outside of the staff client |
| 14:19 |
sandbergja |
That makes sense |
| 14:19 |
meme |
At the server level? |
| 14:19 |
sandbergja |
So a "in-client" book and an "out-of-client" book? |
| 14:19 |
sandbergja |
^an "in-client" |
| 14:19 |
alynn26 |
those would include things like installing the staff Client, Troubleshooting access, and etc. |
| 14:19 |
krvmga |
#info krvmga = Jim Keenan, C/W MARS |
| 14:20 |
krvmga |
sorry to be late :( |
| 14:20 |
jihpringle |
alynn26 would you include those as in or out of client? |
| 14:20 |
sandbergja |
krvmga: no worries |
| 14:21 |
alynn26 |
install staff client - Out |
| 14:21 |
jihpringle |
I'd put installing the staff client as in-client since staff with local system administrator perms can perform that function |
| 14:21 |
alynn26 |
Troubleshooting access - both |
| 14:22 |
meme |
But in some libraries the installation would be handled by a differnet person as the one setting up the permissions.... |
| 14:22 |
alynn26 |
maybe it should be in both locations. |
| 14:22 |
jihpringle |
i'd vote for bothm or in one with a link to the other |
| 14:22 |
krvmga |
it's all 1s and 0s; doesn't cost extra to do it in both places. :) |
| 14:23 |
alynn26 |
Meme that is true. |
| 14:23 |
sandbergja |
here's another complication: the developer tools in the staff client. Yes, they are technically in the staff client, but they are weird stuff like consoles and stuff that most local sysadmins would rarely, if ever, use. |
| 14:23 |
alynn26 |
:) |
| 14:23 |
sandbergja |
would those be in the "in client" book or the "out of client" book? |
| 14:24 |
sandbergja |
or both? |
| 14:24 |
krvmga |
i'd have installed the client in the "out" book and troubleshooting the client in both |
| 14:24 |
alynn26 |
I would mainly focus things on the admin menu items, the developer tools are in a whole different location. |
| 14:24 |
krvmga |
i agree with alynn26 on that. |
| 14:24 |
jihpringle |
agreed |
| 14:24 |
meme |
I think both should be in out of client as in my library anyway, the tasks are handled by differnt people |
| 14:24 |
meme |
Trouble shooting in both though. |
| 14:25 |
krvmga |
three are two troubleshootings: troubleshooting the installation and figuring out problems with the interface while you're working with it. |
| 14:25 |
krvmga |
three=there (fumble fingers) |
| 14:26 |
meme |
I think both should be in both. That way if issues while setting up in staff client can determine if in installation or interface. |
| 14:26 |
alynn26 |
Troubleshooting installation of the server, should be its own book. |
| 14:27 |
krvmga |
alynn26++ |
| 14:27 |
sandbergja |
I guess it would be helpful to know -- as far as the client installs go -- who actually does that work in most libraries? |
| 14:27 |
|
jlundgren joined #evergreen |
| 14:27 |
alynn26 |
troubleshooting installing and connecting the staff client in both. |
| 14:27 |
sandbergja |
Is it someone with shell access, someone who is an admin, or even just a regular person at the circ desk |
| 14:28 |
krvmga |
i don't see a problem with having it in both places |
| 14:28 |
sandbergja |
what about at the start of each book? |
| 14:28 |
krvmga |
an appendix? |
| 14:28 |
alynn26 |
here it is the IT department (Me) as staff don't have that access. In other places I help with it could be anyone. |
| 14:28 |
sandbergja |
Since acq people will also need to know how to get started with the staff client and troubleshoot if it can't connect, as will circ, etc. |
| 14:29 |
krvmga |
a prologue, then (as in something about hobbits) |
| 14:29 |
alynn26 |
it's the registering the Workstation, that is usually done by only done by the local sys admins. |
| 14:30 |
jihpringle |
or maybe we need a getting started book that is linked to at the beginning of all the other books |
| 14:30 |
alynn26 |
That would be a good book. |
| 14:30 |
krvmga |
a getting started book strikes me as a good idea |
| 14:30 |
sandbergja |
good idea, jihpringle! |
| 14:30 |
alynn26 |
jihpringle++ |
| 14:33 |
jihpringle |
I would also vote to move most, if not all, of the acq admin into the acq book (maintaining funds, providers etc.) otherwise you'll have acq staff who have to refer to two books for regular acq functions |
| 14:34 |
krvmga |
+1 |
| 14:34 |
Christineb |
+1 |
| 14:34 |
sandbergja |
+1 |
| 14:34 |
meme |
+1 |
| 14:34 |
|
jlitrell joined #evergreen |
| 14:34 |
alynn26 |
The goal I am thinking is to have it available in both locations. We keep one set of documents, point the various locations to that same set of documents. |
| 14:35 |
jihpringle |
we could have a page for acq admin in the staff client admin book that is just a link to the acq admin docs in the acq manual |
| 14:35 |
alynn26 |
so, when we comple the acq docs the admin functions are there, and when we compile the admin docs they are there also. |
| 14:36 |
sandbergja |
But the tone of the docs are really focused more toward acquisitions staff, not sysadmins? |
| 14:38 |
alynn26 |
that is true, they should be as they would be the primary user of the docs. |
| 14:38 |
jihpringle |
agreed |
| 14:39 |
sandbergja |
Cool! I think we are having a great discussion. |
| 14:39 |
sandbergja |
I think we will probably have a lot of these conversations of which-book-does-it-go-in |
| 14:39 |
sandbergja |
as this project progresses |
| 14:40 |
sandbergja |
I did want to talk a bit about the survey; any more thoughts on the client sysadmin book, or should we move on? |
| 14:40 |
alynn26 |
especially as we move into some of the other areas Circ and Cataloging. |
| 14:40 |
sandbergja |
alynn26, very true! |
| 14:41 |
sandbergja |
I have to say that most of my sysadmin work is troubleshooting circ issues |
| 14:41 |
|
meme joined #evergreen |
| 14:41 |
alynn26 |
Mine too. |
| 14:41 |
jihpringle |
do we have a date by which we'd like the table of contents to be complete (at least in a draft form)? |
| 14:41 |
sandbergja |
but most of our circ supervisor's work is also troubleshooting circ issues... |
| 14:41 |
alynn26 |
MeMe welcome back |
| 14:42 |
sandbergja |
quick poll: does everyone think we could get a draft of the sysadmin book in the next month? |
| 14:43 |
meme |
We can try... |
| 14:43 |
jihpringle |
I think so |
| 14:43 |
krvmga |
i think so |
| 14:44 |
alynn26 |
+1 |
| 14:44 |
krvmga |
i don't think i'm being overly optimistic when i say that |
| 14:44 |
sandbergja |
So, how does everyone feel about an early April deadline for the sysadmin book, and an early May deadline for the circ book? |
| 14:44 |
jihpringle |
sounds good to me |
| 14:44 |
krvmga |
we've got the evergreen conference in april |
| 14:45 |
krvmga |
that will limit my participation a bit |
| 14:45 |
sandbergja |
Oh, yes! Good point. |
| 14:45 |
sandbergja |
We should also figure out a time to meet up then |
| 14:45 |
sandbergja |
Perhaps informally? |
| 14:45 |
sandbergja |
at the EG conference, I mean |
| 14:46 |
krvmga |
how many of us will be at the conference? |
| 14:46 |
krvmga |
me |
| 14:46 |
sandbergja |
I will |
| 14:46 |
alynn26 |
me. |
| 14:46 |
jihpringle |
I will |
| 14:46 |
meme |
I will not be.. There will be others there from our consortium.. |
| 14:46 |
krvmga |
i think it would be great for us to get together |
| 14:46 |
meme |
We are COOL , Consortium of Ohio Libraries |
| 14:47 |
krvmga |
you ARE cool, meme |
| 14:47 |
krvmga |
:) |
| 14:47 |
krvmga |
could we get together informally one time after the official day is done? |
| 14:48 |
alynn26 |
i think that would be a good idea. |
| 14:48 |
jihpringle |
agreed |
| 14:48 |
sandbergja |
I like that; perhaps one of us could research the local bars/etc to find a good (fun) place to meet? |
| 14:49 |
krvmga |
as the time gets closer, we can firm up the details |
| 14:49 |
sandbergja |
sounds good |
| 14:49 |
sandbergja |
let's chat about the survey really quickly |
| 14:49 |
sandbergja |
#topic Survey |
| 14:49 |
jihpringle |
I think the questions look really good |
| 14:49 |
sandbergja |
me too! |
| 14:50 |
krvmga |
me, too. i sent a couple of suggestions separately. |
| 14:50 |
sandbergja |
alynn26: are you still up for putting it on surveymonkey? |
| 14:50 |
sandbergja |
#link http://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg_2014:survey-questions |
| 14:50 |
alynn26 |
Yep, have a draft done already. |
| 14:50 |
sandbergja |
nice! |
| 14:50 |
sandbergja |
alynn26++ |
| 14:50 |
krvmga |
alynn26++ |
| 14:50 |
alynn26 |
https://www.surveymonkey.com/r/GF7FFJT |
| 14:51 |
sandbergja |
It's really pretty! |
| 14:51 |
meme |
Wow..good job. |
| 14:51 |
alynn26 |
Any additional questions, are changes |
| 14:52 |
alynn26 |
or changes |
| 14:52 |
sandbergja |
I think it looks great |
| 14:52 |
Christineb |
looks great!! |
| 14:52 |
Christineb |
alynn26++ |
| 14:52 |
jihpringle |
alynn26++ |
| 14:52 |
* krvmga |
opens survey |
| 14:52 |
krvmga |
this looks really good. |
| 14:52 |
meme |
Did you want to include the follow up comments at the end? |
| 14:53 |
meme |
Anything else you want to say about evergreen documentation? |
| 14:53 |
krvmga |
does #7 take care of that? |
| 14:53 |
krvmga |
maybe it's not enough |
| 14:53 |
sandbergja |
Not necessarily |
| 14:53 |
meme |
I was just comparing to original.. |
| 14:54 |
krvmga |
i'm all in favor of comments |
| 14:54 |
sandbergja |
They might have something really good to say about the docs, which they wouldn't really put in #7 |
| 14:54 |
alynn26 |
That i can add. |
| 14:54 |
sandbergja |
Thanks! |
| 14:54 |
krvmga |
i'd be happy to see an extra unrequired comment at the end. |
| 14:54 |
sandbergja |
How long should we keep the survey open? Until start of April? |
| 14:54 |
* alynn26 |
edits survey quickly. |
| 14:54 |
krvmga |
are we making #7 mandatory? |
| 14:55 |
krvmga |
not against it; just asking |
| 14:55 |
jihpringle |
I don't think #7 should be mandatory |
| 14:55 |
meme |
If you did early april, then you can discuss at conference |
| 14:56 |
sandbergja |
Just spotted one other potential change. On #4, should they be allowed to choose only one answer? |
| 14:56 |
krvmga |
in the event there is not a lot of response, can we be flexible and leave the survey open (i.e. to some promotion at the conference)? |
| 14:57 |
meme |
Good thinking on promoting survey at conference. |
| 14:57 |
jihpringle |
I'd be tempted to leave it open for longer, ie. post conference |
| 14:57 |
krvmga |
since it says "go to first"; can't go to two people first :) |
| 14:57 |
alynn26 |
I was thinking about #4 and looking at it, for me it depends on what I am looking for. |
| 14:57 |
krvmga |
(unless they're sitting right by each other maybe :) ) |
| 14:57 |
alynn26 |
Is it something I know in the docs then the docs I head to first. |
| 14:58 |
* krvmga |
thinks alynn26 makes a good point. |
| 14:58 |
meme |
Can we switch to ratings, first, second and third? |
| 14:58 |
alynn26 |
We can switch it. to ratings if you want. |
| 14:58 |
jihpringle |
I like the idea of ratings |
| 14:58 |
sandbergja |
+1 |
| 14:58 |
alynn26 |
I made #7 not Mandatory. |
| 14:58 |
krvmga |
meme's idea is good, i think |
| 14:58 |
krvmga |
+1 |
| 15:00 |
krvmga |
shall we vote to release the survey into the wild after that change? |
| 15:00 |
sandbergja |
Let's do it! |
| 15:00 |
jihpringle |
if we want to promote it at the conference do we want the end date to be something like June 1st? |
| 15:00 |
meme |
+1 |
| 15:00 |
Christineb |
+1 |
| 15:00 |
alynn26 |
Ol, be looking for it in your email |
| 15:00 |
krvmga |
sandbergja++ |
| 15:00 |
krvmga |
:) |
| 15:00 |
sandbergja |
+1 to June 1st as deadline |
| 15:01 |
meme |
+1 |
| 15:01 |
krvmga |
i'd put the end day in early May maybe |
| 15:01 |
krvmga |
but maybe that's too soon |
| 15:01 |
sandbergja |
Well, we can be sure to pester people to take it, and set it to early May |
| 15:01 |
jihpringle |
if we want to promote it at the conference I think we need to give staff a few weeks after to get it out to libraries, especially in consortiu, |
| 15:01 |
krvmga |
May 20? |
| 15:02 |
krvmga |
that's about 4 weeks after the conference |
| 15:02 |
jihpringle |
May 20 sounds good to me |
| 15:02 |
sandbergja |
Any objections to May 20? |
| 15:02 |
meme |
none.. |
| 15:02 |
sandbergja |
#agreed the survey will be due May 20 |
| 15:02 |
sandbergja |
Cool, thanks everyone for a great meeting! |
| 15:02 |
krvmga |
thanks everyone!! |
| 15:02 |
sandbergja |
and thanks for all your work on this project! |
| 15:02 |
krvmga |
sandbergja++ |
| 15:02 |
krvmga |
meme++ |
| 15:02 |
meme |
Thanks... |
| 15:03 |
krvmga |
jihpringle++ |
| 15:03 |
jihpringle |
sandbergja++ |
| 15:03 |
krvmga |
alynn26++ |
| 15:03 |
sandbergja |
#endmeeting |
| 15:03 |
pinesol_green |
Meeting ended Mon Mar 7 15:03:12 2016 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:03 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-03-07-14.01.html |
| 15:03 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-03-07-14.01.txt |
| 15:03 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-03-07-14.01.log.html |
| 15:03 |
krvmga |
Christineb++ |
| 15:03 |
sandbergja |
krvmga++ ! |
| 15:59 |
|
alt-JBoyer joined #evergreen |
| 16:00 |
Bmagic |
sandbergja++ |
| 16:00 |
|
JBoyer joined #evergreen |
| 16:26 |
Dyrcona |
Do the numbers that acquisitions put in on order barcodes and call numbers mean anything? That is, do they relate to an id somewhere else in the database? |
| 16:35 |
tsbere |
Dyrcona: acq.lineitem_detail ids, I think |
| 16:35 |
tsbere |
I think it does the same thing for the call numbers too |
| 16:37 |
rhamby |
That sounds right to me. I looked at it a while back for a cleanup task. |
| 16:38 |
tsbere |
Looks easier to go the other way. Copy id to the same id in said table. |
| 16:38 |
tsbere |
But meh |
| 16:39 |
* tsbere |
isn't sure what is being looked at, just that Dyrcona's office isn't large enough for him to join in to find out ;) |
| 16:42 |
rhamby |
Is it a broom cupboard office? |
| 16:42 |
|
mrpeters joined #evergreen |
| 16:44 |
Dyrcona |
tsbere: That looks like it, but this lineitem_detail was deleted. |
| 16:44 |
Dyrcona |
rhamby: It used to be a short hallway leading to stairs into another part of the building. |
| 16:46 |
Dyrcona |
If the fund was over encumbered, it probably never created the lineitem_detail in the first place. |
| 16:59 |
|
vlewis_ joined #evergreen |
| 17:11 |
|
mmorgan left #evergreen |
| 17:18 |
|
mrpeters joined #evergreen |
| 17:43 |
|
eady joined #evergreen |
| 17:57 |
|
vlewis joined #evergreen |
| 19:34 |
|
rlefaive joined #evergreen |
| 19:40 |
|
Stompro joined #evergreen |
