Time |
Nick |
Message |
03:07 |
|
Christineb joined #evergreen |
03:07 |
|
jeffdavis joined #evergreen |
07:13 |
|
serflog joined #evergreen |
07:13 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
07:13 |
|
pinesol joined #evergreen |
07:15 |
|
pastebot joined #evergreen |
07:22 |
|
csharp joined #evergreen |
07:26 |
|
rjackson_isl joined #evergreen |
07:34 |
|
bdljohn joined #evergreen |
07:34 |
|
csharp joined #evergreen |
07:58 |
|
_bott_ left #evergreen |
08:01 |
|
_bott_ joined #evergreen |
08:13 |
|
bos20k joined #evergreen |
08:39 |
|
mmorgan joined #evergreen |
08:40 |
|
kmlussier joined #evergreen |
08:41 |
kmlussier |
Good morning #evergreen! |
08:42 |
kmlussier |
@coffee [someone] |
08:42 |
* pinesol |
brews and pours a cup of Sulawesi Toraja, and sends it sliding down the bar to _bott_ |
08:42 |
kmlussier |
@tea [someone] |
08:42 |
* pinesol |
brews and pours a pot of Wuyi Mountain Big Red Robe, and sends it sliding down the bar to gsams_ (http://ratetea.com/tea/verdant/wuyi-mountain-big-red-robe/7311/) |
08:42 |
kmlussier |
@dessert [someone] |
08:42 |
* pinesol |
grabs some Non-Vanilla Ice Cream for jonadab |
08:43 |
kmlussier |
Because early-morning ice cream is good for the soul. |
08:44 |
mmorgan |
Good morning! |
08:44 |
|
Dyrcona joined #evergreen |
08:45 |
* mmorgan |
believes there is no wrong time for ice cream. |
08:45 |
* kmlussier |
agrees with mmorgan |
08:46 |
* kmlussier |
will create a starter agenda for today's dev meeting. |
08:51 |
|
bos20k joined #evergreen |
09:00 |
csharp |
@who screams for eyes cream? |
09:00 |
pinesol |
dluch screams for eyes cream. |
09:01 |
csharp |
I wake up regularly with corneal abrasions, so I often scream for eyes cream :-( |
09:05 |
kmlussier |
Draft agenda is available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2018-10-10. Feel free to add any discussion items. |
09:05 |
kmlussier |
In addition to the usual topics, I added a topic for 3.3 RM. |
09:14 |
|
yboston joined #evergreen |
09:14 |
* Dyrcona |
fixed some dates on the agenda. |
09:18 |
kmlussier |
Heh. The dangers of copying and pasting. I also fixed the UTC time. |
09:22 |
Dyrcona |
DST-- |
09:23 |
JBoyer |
In old comedy act, daylight saves you! |
09:23 |
Dyrcona |
:) |
09:51 |
|
jvwoolf joined #evergreen |
09:57 |
kmlussier |
Has anyone recently seen problems where the login page redirects you to the workstation registration, even when you selected a workstation that was already in the database. |
09:58 |
kmlussier |
I'm seeing this on a 3.1.6 system, but I'm pretty sure it's been happening to me for a few weeks now. I kept assuming that I hadn't registered my workstation yet. |
09:58 |
Dyrcona |
No, I haven't. That has only happened to me if the workstation is not in the database. |
09:58 |
berick |
kmlussier: i've seen that a couple of times. |
10:00 |
kmlussier |
berick: OK, maybe I'll file a bug report then. I'm first going to see if I can replicate it consistently. |
10:05 |
kmlussier |
Weird. I registered a new workstation, confirmed that I could log into it a couple of times, and then closed Chrome. When I went back into Chrome, that new workstation wasn't in my local storage settings anymore. |
10:06 |
kmlussier |
But I'm now able to log in with the default workstation that wasn't working before. |
10:08 |
kmlussier |
Oh, never mind. Different Chrome profile. |
10:08 |
berick |
*phew* |
10:19 |
kmlussier |
OK, so the workstation masslnc-BR1 works in Chrome one I log in under one Chrome profile, but not the other. I also see that a different id is used for this workstation in local storage. I also registered for BR4-masslnc under both profiles, but, in this instance, I am seeing the same id in local storage. |
10:19 |
kmlussier |
I think the wrong workstation id is probably the cause of the problem, but I'm not quite sure why it's given the wrong id in some instances but not others. |
10:21 |
* kmlussier |
confirms that fixing the id in local storage fixes the problem. |
10:26 |
berick |
wrong WS id would definitely do it |
10:26 |
Dyrcona |
The different ids could come from it having been registered in the past, the database being reloaded, and it needing to be recreated. The old id in local storage may not have been updated. |
10:26 |
berick |
we compare local-storage workstation IDs to the wsid() value on the authenticated user |
10:27 |
Dyrcona |
Right, but kmlussier is using different profiles, so if she registered with profile X, then had to register again with profile y (creating a new db entry), then goes back to profile x? |
10:28 |
kmlussier |
Dyrcona: Yes, I think you're right. |
10:28 |
|
beanjammin joined #evergreen |
10:29 |
berick |
hm, it should re-use the existing WS if the owning_lib is not change |
10:29 |
berick |
at least on the API side |
10:30 |
Dyrcona |
Right, but assuming a database reload in between, the workstation will be gone. |
10:30 |
kmlussier |
berick: So this is what happens. I have the workstation in my local storage, but I rebuild my VM, wiping out the database, I then log into the rebuilt VM using the other Chrome profile, and use the same workstation name when I register. |
10:30 |
kmlussier |
I later go back to my old profile and try to log in, but it still has the old information in local storage. |
10:30 |
berick |
ahh! |
10:30 |
berick |
ok, that makes sense |
10:31 |
kmlussier |
I used to only use one Chrome profile, which is why it was never an issue. before. |
10:31 |
kmlussier |
Sorry for all the noise! |
10:51 |
|
stephengwills joined #evergreen |
11:03 |
|
yboston joined #evergreen |
11:03 |
|
Dyrcona joined #evergreen |
11:06 |
Dyrcona |
Charter-- |
11:06 |
* Dyrcona |
will never get Internet from a cable company. |
11:09 |
kmlussier |
Dyrcona: What do you use for Internet now? |
11:09 |
|
khuckins joined #evergreen |
11:09 |
* kmlussier |
has no high-speed options other than the cable company. :( |
11:10 |
Dyrcona |
At home, I use Verizon FIOS. Work has Charter and we just had an outage, but I think it is resovled. |
11:10 |
Dyrcona |
I'm tethering my laptop via my cell phone and probably will for the rest of the day. It's more reliable. :) |
11:10 |
rhamby |
kmlussier: I'm in the same boat, local monopoly, I'm just barely outside the area of any competitors (like one street over) |
11:13 |
* Dyrcona |
thought this was 'Murica where we don't 'llow no monopolies.... :P |
11:20 |
kmlussier |
I've added an item to today's agenda to float the idea of doing one more maintenance release for 3.0, which is supposed to be EOL. Bug 1796978 and bug 1796971 are serious regressions, IMO, and I don't think we should end the release with those bugs still there. |
11:20 |
pinesol |
Launchpad bug 1796978 in Evergreen 3.2 "Web client cannot create two or more copies at the same time" [High,Confirmed] https://launchpad.net/bugs/1796978 |
11:20 |
pinesol |
Launchpad bug 1796971 in Evergreen 3.1 "Web Client: Unable to Add Items from Item Status or Holdings View" [High,Confirmed] https://launchpad.net/bugs/1796971 |
11:21 |
miker |
kmlussier: I'm for it. I commented just now on the bug based on your pasted error. |
11:21 |
kmlussier |
miker++ |
11:22 |
miker |
smells like another race condition (addressed in master, apparently) |
11:23 |
Dyrcona |
Well, I saw the second bug on the latest master last night. |
11:23 |
Dyrcona |
The field labels appear, no text boxes to fill in. |
11:24 |
kmlussier |
miker: I'm not entirely confident about it not being in master. Dyrcona saw similar behavior. I just wasn't able to confirm it on the community demo server. |
11:25 |
miker |
Dyrcona: seeing anything in the console similar to kmlussier's error? |
11:25 |
Dyrcona |
I'd have to look again, and I'm looking into something else at the moment. |
11:26 |
miker |
kk |
11:36 |
|
bos20k joined #evergreen |
11:50 |
Dyrcona |
miker: Yes, I do get the same error in the console as kmlussier. |
12:07 |
|
jihpringle joined #evergreen |
12:15 |
|
nfburton joined #evergreen |
12:58 |
|
nfburton joined #evergreen |
12:59 |
|
lsach joined #evergreen |
13:09 |
|
beanjammin joined #evergreen |
13:10 |
jeff |
Neat. null titles in metabib.wide_display_entry. |
13:10 |
* jeff |
digs |
13:19 |
jeff |
select * from config.metabib_field where field_class = 'title' and display_field = true; |
13:19 |
jeff |
(0 rows) |
13:19 |
jeff |
that seems likely to be a contributing factor. |
13:26 |
jeff |
and/or/also: |
13:26 |
jeff |
SELECT cdfm.*, cmf.field_class, cmf.name FROM config.display_field_map AS cdfm JOIN config.metabib_field AS cmf ON cdfm.field = cmf.id WHERE cdfm.name = 'title'; |
13:26 |
jeff |
name | field | multi | field_class | name |
13:26 |
jeff |
-------+-------+-------+-------------+----------- |
13:26 |
jeff |
title | 6 | f | author | corporate |
13:26 |
JBoyer |
That database seems... sickly. |
13:27 |
jeff |
looks like the upgrade script may have relied upon assertions that do not hold true with our database. |
13:29 |
JBoyer |
I do remember undertaking a "Great Realignment" here at some point years ago. Without that I suspect we'd be in the same boat. |
13:30 |
JBoyer |
(though I did just go check our 3.2 test db just to be sure we're not actually knee deep in said boat.) |
13:42 |
jeff |
during your "Great Realignment", did you dig into how you had diverged? |
13:43 |
jeff |
And, did you encounter any serious gotchas? |
13:49 |
JBoyer |
I suspect that one or more new fields were added manually without necessarily using the same ids as the upgrade scripts (or worse, the upgrade scripts disagree(d) with the seed data) but it was long enough ago and I was fresh enough at the job that I didn't go very far down that road. |
13:49 |
JBoyer |
And the only serious gotcha would be that things behave increasingly strange the more things you have to move around until the full reingest is completed. |
13:52 |
JBoyer |
And by 'behave' I really just mean 'appear' |
13:53 |
JBoyer |
And I would note that there are more FKeys on that table these days, so verifying that index normalizers do what you expect and so on is more work. :/ (the _entry tables obviously are no problem, but still...) |
13:57 |
kmlussier |
We're looking at a great realignment here, and the underlying cause is that the current behavior to give an id of 1000 or higher to custom indexes was not always the behavior. |
13:58 |
kmlussier |
We had a bunch of custom indexes with ids that eventually were used for stock indexes. |
14:27 |
jeff |
This also answers the question "why is keyword/keyword a display field?" |
14:33 |
|
yboston joined #evergreen |
14:40 |
|
bdljohn joined #evergreen |
14:40 |
|
ningalls joined #evergreen |
14:55 |
kmlussier |
Five minutes until dev meeting time. Does anyone want to volunteer to run the meeting? |
15:01 |
|
BAMkubasa joined #evergreen |
15:02 |
kmlussier |
Meetbot controls are listed here if anyone is interested in running the meeting! https://wiki.evergreen-ils.org/doku.php?id=community:using-meetbot |
15:05 |
* JBoyer |
feels like that's a hint... |
15:06 |
kmlussier |
JBoyer: Is that your way of volunteering? ;) |
15:06 |
JBoyer |
I'm only here until 3:30 so either someone jumps up or we have a short meeting. |
15:06 |
JBoyer |
Tick |
15:06 |
JBoyer |
Tick |
15:06 |
JBoyer |
Tick |
15:06 |
kmlussier |
I can do it. |
15:06 |
JBoyer |
Aw, that wasn't my intent. :/ |
15:07 |
kmlussier |
JBoyer: I was just about to start the meeting when you spoke. :) |
15:07 |
kmlussier |
So, no worries! I won't have many more chance to do this. |
15:07 |
Dyrcona |
Do we have a quorum? Do we need a quorum? |
15:07 |
kmlussier |
#startmeeting 2018-10-10 Evergreen developers meeting |
15:07 |
pinesol |
Meeting started Wed Oct 10 15:07:38 2018 US/Eastern. The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot. |
15:07 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
15:07 |
|
Topic for #evergreen is now (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:07 |
pinesol |
The meeting name has been set to '2018_10_10_evergreen_developers_meeting' |
15:07 |
JBoyer |
kmlussier++ |
15:08 |
kmlussier |
#info Meeting agenda is available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2018-10-10 |
15:08 |
kmlussier |
#topic Introductions |
15:08 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:08 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
15:08 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
15:08 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin College) |
15:08 |
JBoyer |
#info JBoyer is Jason Boyer, IN State Lib |
15:08 |
miker |
#info miker = Mike Rylander, EOLI (now having to miss the meeting ... arg, sorry) |
15:09 |
gmcharlt |
#info gmcharlt = Galen Charlton, Equinox |
15:09 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
15:09 |
abneiman |
#info abneiman, Andrea Neiman, Equinox |
15:09 |
berick |
#info berick Bill Erickson, KCLS |
15:09 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (Calvin College) |
15:09 |
jeff |
#info jeff is Jeff Godin, Traverse Area District Library (TADL) |
15:09 |
cesardv_ |
#info cesardv, cesar velez, EOLI |
15:10 |
kmlussier |
#topic Action Items from Last Meeting |
15:10 |
|
Topic for #evergreen is now Action Items from Last Meeting (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:10 |
kmlussier |
gmcharlt will open and work on bugs for documentation changes for better ejabberd configuration during installation of OpenSRF |
15:10 |
gmcharlt |
still on my plate; now that 3.2.0 is out the door, I will turn my attention to OpenSRF releases |
15:11 |
kmlussier |
OK, I'll add that action item for next month's meeting then. |
15:11 |
kmlussier |
#action gmcharlt will open and work on bugs for documentation changes for better ejabberd configuration during installation of OpenSRF |
15:12 |
kmlussier |
#info berick has reviewed miker's ejabberd changes for bug 1703411 |
15:12 |
pinesol |
Launchpad bug 1703411 in OpenSRF "OpenSRF: XMPP Non-SASL auth is being phased out" [Medium,Confirmed] https://launchpad.net/bugs/1703411 |
15:12 |
kmlussier |
#info gmcharlt and Dyrcona to tested the ang6 branch |
15:12 |
kmlussier |
Is there anything else to say about the action items from the previous meeting? |
15:13 |
kmlussier |
#topic OpenSRF 3.1 beta release |
15:13 |
|
Topic for #evergreen is now OpenSRF 3.1 beta release (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:13 |
kmlussier |
gmcharlt? |
15:13 |
Dyrcona |
I think that bug 1703411 should actually be bug 1793356. |
15:13 |
pinesol |
Launchpad bug 1703411 in OpenSRF "OpenSRF: XMPP Non-SASL auth is being phased out" [Medium,Confirmed] https://launchpad.net/bugs/1703411 |
15:13 |
pinesol |
Launchpad bug 1793356 in OpenSRF "Ejabberd strips custom XML attributes" [Medium,Fix committed] https://launchpad.net/bugs/1793356 |
15:13 |
gmcharlt |
#info OpenSRF 3.1 beta will be released before the hack-a-way; hopefully sooner rather than later |
15:14 |
kmlussier |
Dyrcona: Did I misidentify it in the original action? |
15:14 |
Dyrcona |
kmlussier: The code moved to a different bug, so I guess so. |
15:14 |
berick |
the bug later migrated |
15:15 |
gmcharlt |
*insert spider vs. bug migration joke here* |
15:15 |
* Dyrcona |
didn't think of that when reviewing the agenda earlier. |
15:15 |
kmlussier |
#info Correction: berick reviewed miker's ejabberd changes for bug 1793356 |
15:15 |
pinesol |
Launchpad bug 1793356 in OpenSRF "Ejabberd strips custom XML attributes" [Medium,Fix committed] https://launchpad.net/bugs/1793356 |
15:16 |
kmlussier |
gmcharlt: Are there any OpenSRF bugs that need to be reviewed to help with the release? |
15:18 |
gmcharlt |
for the beta, as many eyes as possible on the websocketd patch woudl be great |
15:18 |
JBoyer |
I'm hoping to throw some tuits in that direction soon. |
15:18 |
* berick |
is running it on a large test cluster as of 2 weeks ago |
15:19 |
JBoyer |
berick++ |
15:19 |
kmlussier |
#help websocketd patch needs review from as many people as possible. |
15:19 |
Dyrcona |
I'm running websocketd in production with OpenSRF 3.0.1 if that means anything. |
15:19 |
stephengwills |
#info stephengwills Maine Balsam Libraries |
15:20 |
JBoyer |
Dyrcona, that sounds promising, none of the old pegged /dead processes, etc.? |
15:20 |
Dyrcona |
No problems at all so far. |
15:20 |
JBoyer |
Nice. |
15:20 |
Dyrcona |
Seems to be less load on the servers, too. |
15:21 |
kmlussier |
Is there anything else we need to discuss for the OpenSRF release before we move on to Evergreen updates? |
15:21 |
berick |
i'm planning to post a LP patch for removal of apache2-websockets, but presumably that will not be in 3.1 |
15:22 |
gmcharlt |
berick: yeah, I'd go so far as a deprecation in 3.1, but not a removal |
15:22 |
berick |
gmcharlt: what I figured, thanks |
15:22 |
kmlussier |
#info apache2-websockets to be deprecated in 3.1, with removal planned for 3.2. |
15:23 |
Dyrcona |
Well,it just steps in the README. |
15:23 |
Dyrcona |
I say get rid of them. |
15:24 |
gmcharlt |
we'll use a smaller font ;) |
15:24 |
kmlussier |
#topic Evergreen 3.2 updates |
15:24 |
|
Topic for #evergreen is now Evergreen 3.2 updates (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:24 |
kmlussier |
berick: Do you have any 3.2 updates for us? |
15:24 |
Dyrcona |
<marquee> Don't install this! It's garbage! </marquee> |
15:24 |
berick |
kmlussier: not really. i have not heard a lot, I think people are easing into it |
15:25 |
berick |
we'll be settling in to the usual release schedule now |
15:25 |
kmlussier |
Well, we have had a release since the last meeting. :) |
15:25 |
berick |
haha |
15:25 |
kmlussier |
#info 3.2.0 was released on October 3 |
15:26 |
kmlussier |
Just so that we get it into the minutes. |
15:26 |
berick |
kmlussier++ |
15:26 |
dbwells |
berick++ |
15:26 |
kmlussier |
berick++ # Managing the release schedule. |
15:27 |
kmlussier |
#topic Possible extension of 3.0 to one more maintenance release |
15:27 |
|
Topic for #evergreen is now Possible extension of 3.0 to one more maintenance release (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:28 |
kmlussier |
I added this topic to the agenda because we found some regressions when CW MARS updated to the latest 3.0 maintenance release over the weekend. |
15:28 |
kmlussier |
I would like to suggest that we do one more 3.0 maintenance release that's limited to addressing regressions only. |
15:28 |
gmcharlt |
I'm amenable to that extension, but I think we should nix any other backports |
15:28 |
gmcharlt |
IOW, what kmlussier said |
15:29 |
berick |
+1 |
15:29 |
berick |
keep it stable |
15:29 |
Dyrcona |
I concur, and I could volunteer to release it/manage it. |
15:29 |
JBoyer |
Since it was backports that caused the problem, we could just strip out the couple of commits, release 3.0.13 tomorrow and call it fixed? |
15:30 |
kmlussier |
Do we know exactly which commits caused the problems? |
15:30 |
JBoyer |
(I say that because I thought the issue had been narrowed down to something specific, the hover tags or something similar?) |
15:30 |
kmlussier |
JBoyer: No, that's another issue. |
15:30 |
JBoyer |
Then don't mind me. :( |
15:30 |
Dyrcona |
Well, those tootips do cause problems. |
15:30 |
kmlussier |
I don't think the tooltips were backported, were they? |
15:30 |
Dyrcona |
They were. I did it. |
15:30 |
dbwells |
JBoyer: I thought the same thing at first. |
15:31 |
kmlussier |
bug 1796971 and bug 1796978 are the two issues. |
15:31 |
pinesol |
Launchpad bug 1796971 in Evergreen 3.1 "Web Client: Unable to Add Items from Item Status or Holdings View" [High,Confirmed] https://launchpad.net/bugs/1796971 |
15:31 |
pinesol |
Launchpad bug 1796978 in Evergreen 3.2 "Web client cannot create two or more copies at the same time" [High,Confirmed] https://launchpad.net/bugs/1796978 |
15:31 |
kmlussier |
But if the tooltips were backported, I think that one should be addressed to. |
15:31 |
dbwells |
Also, +1 to another release to fix those bugs, and maybe the hover one, too. |
15:31 |
kmlussier |
s/to/too |
15:31 |
JBoyer |
I'm also +1 for one more fix release, no more backports, and we can figure out what happened another day. :) |
15:32 |
Dyrcona |
Well, we could always have a formal vote for the release, but I don't hear any opposition so far. |
15:32 |
kmlussier |
Are there any objections? Also, are there any objections to Dyrcona managing the release? |
15:32 |
gmcharlt |
as far as the tooltips are concerned, I'm inclined to suggest an outright reversion for rel_3_0; leaving an eventually proper fix for rel_3_1 and later |
15:32 |
kmlussier |
+1 |
15:32 |
JBoyer |
+1 to gmcharlt's suggestion also. |
15:32 |
gmcharlt |
anyway, no objection to Dyrcona managing another 3.0.x |
15:33 |
jeff |
+1 overall to the above |
15:33 |
dbwells |
Dyrcona: startvote: Who wants to have a vote on another release? ;) |
15:33 |
kmlussier |
heh |
15:33 |
* JBoyer |
vanishes. |
15:33 |
* kmlussier |
waves to a disappearing JBoyer |
15:33 |
Dyrcona |
No need to vote at this point. |
15:33 |
gmcharlt |
I never met a metavote I didn't like |
15:33 |
Dyrcona |
:) |
15:33 |
gmcharlt |
^ not truth |
15:33 |
gmcharlt |
er, ^^^ |
15:33 |
Dyrcona |
heh |
15:33 |
kmlussier |
Dyrcona: Do you have a date by which you want to have the last 3.0 release out? |
15:34 |
kmlussier |
Actually, the next maintenance release is next week already, isn't it? It goes by so quickly. |
15:35 |
berick |
last one was delayed, iirc |
15:35 |
Dyrcona |
Next week works if there are fixes for the two bugs above, though it could wait for the next monthly releases. |
15:36 |
* Dyrcona |
suspects the dates will move again. |
15:36 |
kmlussier |
#action Dyrcona to manage one last maintenance release for 3.0 that will be limited to fixing three specific regressions: bug 1796978, bug 1796971 and bug 1797007. |
15:36 |
Dyrcona |
I will go ahead and revert the tooltips from rel_3_0 after the meeting. |
15:36 |
pinesol |
Launchpad bug 1796978 in Evergreen 3.2 "Web client cannot create two or more copies at the same time" [High,Confirmed] https://launchpad.net/bugs/1796978 |
15:36 |
pinesol |
Launchpad bug 1796971 in Evergreen 3.1 "Web Client: Unable to Add Items from Item Status or Holdings View" [High,Confirmed] https://launchpad.net/bugs/1796971 |
15:36 |
pinesol |
Launchpad bug 1797007 in Evergreen 3.2 "Tooltips cause grid slowness" [Undecided,Confirmed] https://launchpad.net/bugs/1797007 |
15:36 |
kmlussier |
Dyrcona++ |
15:37 |
kmlussier |
#topic Evergreen 3.3 Release Manager |
15:37 |
|
Topic for #evergreen is now Evergreen 3.3 Release Manager (Meeting topic: 2018-10-10 Evergreen developers meeting) |
15:38 |
kmlussier |
We probably should be putting out a call for RM for the next Evergreen Release. |
15:38 |
gmcharlt |
so... we have enough time to do the usual call for noms + vote in time to finsih up by the hack-a-way |
15:38 |
gmcharlt |
shall we do that? I'm happy to do the legwork |
15:38 |
berick |
+1 |
15:38 |
berick |
gmcharlt++ |
15:38 |
kmlussier |
+1 |
15:39 |
kmlussier |
gmcharlt++ |
15:39 |
jeff |
+1 / gmcharlt++ |
15:40 |
kmlussier |
OK, then, that brings us to the end of the agenda. Does anyone have anything else they want to discuss? |
15:40 |
gmcharlt |
#action gmcharlt will issue a call for 3.3 release manager using the usual procedure |
15:41 |
kmlussier |
heh, I thought I had already done the action item. Thanks gmcharlt! |
15:42 |
kmlussier |
OK, I have one small announcement for those who don't know yet. I'm going to be leaving MassLNC at the end of November. My new job is going to be taking me out of the Evergreen community, so this is probably my penultimate dev meeting. |
15:42 |
Dyrcona |
kmlussier++ |
15:42 |
berick |
kmlussier++ # can't say it enough |
15:43 |
dbwells |
kmlussier++ |
15:43 |
kmlussier |
But I've had a blast hanging out with all of you in the #evergreen channel. I'm hoping our paths cross again sometime in the future. |
15:43 |
gmcharlt |
kmlussier++ # and don't be a stranger! |
15:43 |
remingtron |
kmlussier++ #thanks a million! |
15:43 |
abneiman |
kmlussier++ |
15:43 |
kmlussier |
But, really, I just wanted to gather some last-minute karma before I left. ;) |
15:44 |
kmlussier |
#endmeeting |
15:44 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
15:44 |
pinesol |
Meeting ended Wed Oct 10 15:44:03 2018 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
15:44 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-10-10-15.07.html |
15:44 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-10-10-15.07.txt |
15:44 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-10-10-15.07.log.html |
15:44 |
mmorgan |
kmlussier++ |
15:44 |
kmlussier |
Thanks everyone! |
16:02 |
Dyrcona |
I created a 3.0.13 milestone and targeted the 3 bugs at it. I then set it to inactive so other bugs cannot be targeted at it. |
16:03 |
kmlussier |
Dyrcona++ |
16:08 |
Bmagic |
Dyrcona++ |
16:12 |
Dyrcona |
dbwells++ |
16:12 |
|
khuckins joined #evergreen |
16:17 |
nfburton |
kmlussier++ |
16:17 |
nfburton |
good luck on your new ventures |
16:17 |
kmlussier |
nfburton: Thanks! |
16:41 |
kmlussier |
dbwells++ |
16:47 |
|
stephengwills left #evergreen |
16:51 |
nfburton |
Quick question as I don't have excessive MARC knowledge. How does Evergreen figure out which format to show? I have some records displaying the incorrect format and would like to change them. Does it save the format type in the database or is it exclusively pulled from LDR/007/008. I removed 007 and it took away the format that should stay and the format I wanted gone just won't leave |
16:53 |
|
montgoc1 joined #evergreen |
16:53 |
abneiman |
nfburton: http://docs.evergreen-ils.org/reorg/3.2/staff_client_admin/_multi_valued_fields_and_composite_record_attributes.html#_search_and_icon_formats |
16:54 |
nfburton |
I saw that |
16:54 |
nfburton |
I guess I'm still slightly confused |
16:55 |
abneiman |
ok. Sometimes it's just a caching thing -- the icon won't update right away |
16:55 |
nfburton |
It has been changing |
16:56 |
nfburton |
The record has no 006 and when I remove 007 the remaining format is there |
16:57 |
nfburton |
I think I found it in the 008. |
16:58 |
abneiman |
hm, not sure what to tell you, it's been a while since I've taken a deep dive into LDR/007/008 |
17:02 |
|
jvwoolf left #evergreen |
17:07 |
|
mmorgan left #evergreen |
17:28 |
|
stephengwills joined #evergreen |
18:53 |
csharp |
@band add Monkey Knockout Gas |
18:53 |
pinesol |
csharp: Band 'Monkey Knockout Gas' added to list |
19:04 |
|
Christineb joined #evergreen |
19:27 |
|
sandbergja joined #evergreen |
19:35 |
|
JBoyer_alt joined #evergreen |
19:35 |
|
dbwells_ joined #evergreen |
19:36 |
|
gsams joined #evergreen |
20:09 |
|
JBoyer_alt_bin joined #evergreen |
20:10 |
|
ningalls_ joined #evergreen |
20:15 |
|
RBecker joined #evergreen |
21:24 |
jeff |
Hrm. Due to the changed default on display_field which is present in the baseline but not in the upgrade script, a fresh 3.1 install has a lot more config.metabib_field rows with display_field = true than a system which has been upgraded to 3.1. |
21:25 |
jeff |
In 3.1 baseline, cmf 45 (keyword/blob) is a display field. |
21:26 |
jeff |
I'm not sure if that's intentional. |
21:40 |
pinesol |
[evergreen|Jane Sandberg] Docs: correcting inaccurate statement in action trigger docs - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1319a3a> |
21:46 |
jeff |
"oops" :-) |
21:53 |
jeff |
sounds like that doc update came from practical experience. |
21:53 |
* jeff |
looks to see if cmf 45 (keyword/blob) is a display field for highlighting purposes. |