| Time |
Nick |
Message |
| 01:18 |
|
jamesrf joined #evergreen |
| 05:01 |
pinesol |
News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~live/test.42.html#2019-04-02T04:57:24,725729014-0400 -0> |
| 06:41 |
|
yar joined #evergreen |
| 06:59 |
|
agoben joined #evergreen |
| 07:12 |
|
rjackson_isl joined #evergreen |
| 07:19 |
|
bos20k joined #evergreen |
| 08:10 |
|
jamesrf joined #evergreen |
| 08:26 |
|
bdljohn joined #evergreen |
| 08:40 |
|
mmorgan joined #evergreen |
| 08:41 |
|
krvmga joined #evergreen |
| 08:53 |
|
Dyrcona joined #evergreen |
| 08:55 |
|
bdljohn joined #evergreen |
| 09:20 |
|
yboston joined #evergreen |
| 09:30 |
|
seymour joined #evergreen |
| 09:34 |
|
sandbergja joined #evergreen |
| 10:17 |
krvmga |
can i construct a search string for basic search that includes keyword, org_unit, and shelving locations within that org_unit? |
| 10:19 |
krvmga |
maybe something like keyword:<keyword> && locg:<ou number> && locations:<number> && locations:<number> |
| 10:19 |
krvmga |
i ask this after already failing with the above string |
| 10:20 |
krvmga |
i'm not sure if i'm missing something or if it's just not possible |
| 10:20 |
berick |
krvmga: if you construct the query in the catalog, submit it, then review the activity logs it should show you exactly what you need |
| 10:41 |
dbwells |
krvmga: I know locations is specified with parentheses, e.g. locations(123). Not sure about locg. Did you figure it out? |
| 10:44 |
Dyrcona |
In our case the activity log is useless. krvmga will want the ap access log, which I've sent him. |
| 10:44 |
jeff |
you're getting close to the territory of bug 1808055, but i don't think you're running into it in this case. |
| 10:45 |
pinesol |
Launchpad bug 1808055 in Evergreen "Search queries containing a filter in a subquery/group may drop the filter" [Undecided,Confirmed] https://launchpad.net/bugs/1808055 - Assigned to Mike Rylander (mrylander) |
| 10:45 |
jeff |
something to be aware of as you're experimenting, though. |
| 10:46 |
berick |
Dyrcona: you don't see lines like this in your activity log? ... EGWeb: [bre search] piano site(BR1) depth(2) |
| 10:46 |
Dyrcona |
I guess I do, but no way to match 'em neatly to a specific search.. |
| 10:51 |
|
Christineb joined #evergreen |
| 11:47 |
|
sandbergja joined #evergreen |
| 11:55 |
|
jamesrf joined #evergreen |
| 11:57 |
|
aabbee joined #evergreen |
| 12:04 |
|
khuckins joined #evergreen |
| 12:09 |
berick |
hm, dev meeting? |
| 12:09 |
berick |
later, i mean, not right now |
| 12:12 |
JBoyer |
berick, was it rescheduled from tomorrow or is my recurrance setup broken? (I see it's today on the community G calendar) |
| 12:12 |
JBoyer |
Uh, looks like my event is out of date. Never mind! |
| 12:13 |
berick |
i believe we changed days after the re-survey |
| 12:13 |
|
jihpringle joined #evergreen |
| 12:24 |
|
yboston joined #evergreen |
| 12:31 |
JBoyer |
I remember that now, but apparently didn't remember then to update Outlook. Agenda is looking sparse, though I don't have anything to add here. |
| 12:40 |
jeff |
I think client-side grid sorting depends on there being an arrayNotifier in use. It looks like at least in the case of pending patrons, there is not and never was one in use. I think that's why bug 1786501 exists. Not ruling out other issues also... |
| 12:40 |
pinesol |
Launchpad bug 1786501 in Evergreen "column sort broken in pending patrons" [Undecided,New] https://launchpad.net/bugs/1786501 |
| 12:52 |
Dyrcona |
yboston: What's up with Berklee and Evergreen? Are you all still planning on migrating away? |
| 12:54 |
yboston |
Dyrcona: ¡Hola! I am still offically on a holding pattern, since we have no funding. So we still run two ILSs, with a dsicovery layer (EDS) to hide that fact. |
| 12:55 |
Dyrcona |
Ah, OK! bshum and I were just chatting privately about academic Evergreen sites and we wondered about Berklee. |
| 12:57 |
bshum |
Yeah I was compiling a list of different kinds of Evergreen academic library catalogs to show to some folks who were looking around and asked me about it |
| 13:07 |
|
sandbergja_ joined #evergreen |
| 13:07 |
yboston |
bshum & Dyrcona: cool, hope all is well with the both of you |
| 13:08 |
Dyrcona |
yboston: Thanks! Yeah, things are good for me. I'm preparing for an upgrade to Evergreen 3.2.5 in about two weeks. |
| 13:08 |
yboston |
Dyrcona: you are welcome and good luck |
| 13:09 |
bshum |
yboston: Thanks! Work is work, but I'll still trying to keep up to date on Evergreen happenings where I can :) |
| 13:29 |
|
terran joined #evergreen |
| 13:34 |
jeff |
git blame... whitespace commit! git blame previous to that... unrelated feature merge! |
| 13:34 |
jeff |
git blame revision previous to THAT... |
| 13:34 |
jeff |
the other Daily Double |
| 13:34 |
jeff |
er, I mean, the Other Whitespace Commit. |
| 13:35 |
Dyrcona |
@blame the whitespace commit |
| 13:35 |
pinesol |
Dyrcona: the whitespace commit HAXORED Dyrcona's SERVERZ!!!! |
| 13:35 |
Dyrcona |
jeff: You know it's eventually going to blame you... git blame always does. :) |
| 13:35 |
jeff |
well of course. |
| 13:35 |
jeff |
Dyrcona: "Jeff Godin claims they have done this and it has produced no issues for them." |
| 13:36 |
Dyrcona |
@blame me |
| 13:36 |
pinesol |
Dyrcona: Dyrcona WILL PERISH UNDER MAXIMUM DELETION! DELETE. DELETE. DELETE! |
| 13:37 |
Dyrcona |
I may not be upgrading to 3.2.5 after all. We may only go to 3.2.4. Seems that the fix for Lp 1721109 is slow with a large number of items on the screen. |
| 13:37 |
pinesol |
Launchpad bug 1721109 in Evergreen 3.2 "Web client: Editing item information from the item status screen does not automatically update item status display" [Medium,Fix released] https://launchpad.net/bugs/1721109 |
| 13:43 |
berick |
@swill [band] |
| 13:43 |
* pinesol |
grabs a bottle of Wild Irish Rose and sends it sliding down the bar to Monkey Knockout Gas |
| 13:51 |
|
medlibrarian joined #evergreen |
| 13:55 |
medlibrarian |
hello, I'm new to the discussion board and would like to know must I be connected to a server to use evergreen? |
| 13:55 |
medlibrarian |
Please reply to hofuller wheelinghospital.org |
| 13:56 |
Dyrcona |
medlibrarian: It doesn't work like that, and you're likely to get more spam, now, since this channel is publicly logged. |
| 13:56 |
berick |
medlibrarian: if you prefer to use email, you can find the community mailing lists at https://evergreen-ils.org/communicate/mailing-lists/ |
| 13:57 |
medlibrarian |
ok, thank you so much. |
| 13:57 |
medlibrarian |
But do I need a server to use evergreen? |
| 13:58 |
berick |
medlibrarian: yes, Evergreen runs as a server |
| 13:58 |
medlibrarian |
ok, thank you so much. I am new to this and appreciate your reply. |
| 13:59 |
Dyrcona |
I can't seem to find the list of public test servers at the moment. |
| 13:59 |
Dyrcona |
And, too late..... |
| 14:00 |
terran |
Dyrcona: https://wiki.evergreen-ils.org/doku.php?id=community_servers |
| 14:02 |
Dyrcona |
terran: Thanks. |
| 14:08 |
|
terran joined #evergreen |
| 14:18 |
Dyrcona |
Whee! Kernel updates...rebooting laptop in a bit. |
| 14:22 |
|
Dyrcona joined #evergreen |
| 14:35 |
|
khuckins joined #evergreen |
| 14:57 |
gmcharlt |
we ostensibly have a dev meeting scheduled to start in a couple minutes |
| 14:57 |
gmcharlt |
while we don't have much of an agenda, https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2019-04-02 |
| 14:57 |
gmcharlt |
if dbwells is available, it might be good to hold it now for at least an official release update |
| 15:02 |
dbwells |
I'm working on a list announcement to send this afternoon/evening, but can give a quick update today or next week if that's better. |
| 15:03 |
gmcharlt |
dbwells: thanks. I'm not necessarily hearing a clamor for a meeting at the moment, but if you've got a quick update to share now, that would be great |
| 15:07 |
berick |
huzzah rel_3_3 branch |
| 15:07 |
dbwells |
To cut to the chase, 3.3.0 is officially out. |
| 15:08 |
dbwells |
We had two RC builds, one of which was posted only to IRC, some issues were further ironed out, and a second RC was posted to the downloads page. |
| 15:08 |
berick |
dbwells++ |
| 15:08 |
JBoyer |
dbwells++ |
| 15:09 |
dbwells |
That RC tested well internally, and I didn't get any negative feedback, so that has now been rebranded as 3.3.0. |
| 15:09 |
gmcharlt |
dbwells++ |
| 15:09 |
dbwells |
And as berick noted, I pushed the rel_3_3 branch moments ago, so please be aware of that for future pushes. |
| 15:12 |
dbwells |
There are a lot of mostly smaller improvements, but probably the biggest shift is in a number of interfaces moving to eg2/Angular 7. Some of that is still optional/experimental, but some is also frontline now. |
| 15:12 |
JBoyer |
berick++ |
| 15:12 |
JBoyer |
sandbergja++ |
| 15:14 |
JBoyer |
When I have time to look around in the A7 stuff I do like it quite a bit, looking forward to more. (And more time to look into it...) |
| 15:17 |
JBoyer |
gmcharlt++ # mini-meeting |
| 15:22 |
dbwells |
One thing I would like folks to think about is 3.1 EOL. It is scheduled to go security only in 3 days, but we've talked of extending that as needed. We have one or two known webstaff blockers in LP, but I think some users are more anxious than that stat might imply. I suggest extending 3.1 full support for 3 months, which means it's security window would end at the 3.4 release, giving us one more release buffer to settle people's nerves. |
| 15:30 |
JBoyer |
I imagine this will come up when we have the dev meeting, but I'm +1 to another 3 months so it lines up with 3.4. Especially since we appear to be down to 1 open webstaffblocker. |
| 15:32 |
gmcharlt |
my memory may be failing me, but I thought we'd already agreed to an initial 6 month extension |
| 15:33 |
berick |
yeah, we agreed to a 6-month extension |
| 15:33 |
abneiman |
relevant link http://libmail.georgialibraries.org/pipermail/open-ils-dev/2018-October/010602.html |
| 15:34 |
berick |
thanks abneiman |
| 15:34 |
sandbergja |
abneiman++ |
| 15:34 |
berick |
heh, or I did anyway ;) |
| 15:35 |
gmcharlt |
and nobody objected at the time |
| 15:35 |
gmcharlt |
so unless there are objections now, I'm happen to update the wiki page RIGHT NOW |
| 15:36 |
gmcharlt |
(and add on 3.2 and 3.3) |
| 15:37 |
abneiman |
+1 to 6 months |
| 15:38 |
Bmagic |
This is really weird. Check this out. The full title of the bib record is NOT shown with this URL: https://jcl.missourievergreen.org/eg/opac/record/2833706?query=2833706;qtype=keyword;locg=259 |
| 15:38 |
Bmagic |
but it is when you remove the URI from the URL: https://jcl.missourievergreen.org/eg/opac/record/2833706 |
| 15:38 |
dbwells |
gmcharlt++ |
| 15:40 |
gmcharlt |
ok, here's the updated version: https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule |
| 15:42 |
gmcharlt |
and upon looking at it, I'm inclined to make a virtue of a typo and just have the security EOL for 3.1 and 3.2 both be on the same day |
| 15:43 |
khuckins |
Bmagic: I noticed that as well while I was working on the read more functionality. It's related to how the tmeplate checks for a highlighted version of the title, and if there isn't, it uses the full title |
| 15:43 |
mmorgan |
Bmagic: This may be of interest: http://irc.evergreen-ils.org/evergreen/2019-02-08 |
| 15:43 |
Bmagic |
mmorgan++ |
| 15:46 |
dbwells |
gmcharlt: One good typo deserves another, so maybe the same day for the bugfix EOL as well :) |
| 15:47 |
gmcharlt |
indeed, I'll normalize it |
| 15:52 |
Bmagic |
mmorgan: am I right in understanding that this issue and many others are detailed on bug 1806724 ? Or is this a different bug? |
| 15:52 |
pinesol |
Launchpad bug 1806724 in Evergreen "Display field strangeness on some 3.1+ systems" [Medium,Confirmed] https://launchpad.net/bugs/1806724 |
| 15:53 |
Bmagic |
khuckins++ |
| 16:00 |
mmorgan |
Bmagic: The issues in 1806724 and the missing 245c are all related to display fields, but the missing 245c is not detailed in that bug. |
| 16:01 |
Bmagic |
So there isn't a bug exactly for this? Is it really worth it if the current OPAC is going away in favor of berick's angular version? |
| 16:01 |
berick |
Bmagic: only plans on the table for now are staff catalog |
| 16:01 |
berick |
!= opac |
| 16:02 |
mmorgan |
The missing 245c we fixed by adding a config.metabib_field entry for it. Perhaps it should be its own bug since it apparently affects a few sites. |
| 16:02 |
|
RBecker joined #evergreen |
| 16:03 |
Bmagic |
there was some talk about changing the OPAC right? I've been holding our OPAC committe over until we see what comes in 3.4 |
| 16:03 |
berick |
Bmagic: talk, yes, but not concrete plans that i'm aware of |
| 16:04 |
Bmagic |
I suppose it's just wishful thinking on my part :) |
| 16:05 |
Bmagic |
I'll make a bug report then |
| 16:09 |
Bmagic |
bug 1822875 |
| 16:09 |
pinesol |
Launchpad bug 1822875 in Evergreen "OPAC titles are truncated when search URI's present" [Undecided,New] https://launchpad.net/bugs/1822875 |
| 16:10 |
|
yboston joined #evergreen |
| 16:10 |
sandbergja |
Regarding the OPAC: I know that nfburton has been working on a really stylin' bootrap version of the TT2 OPAC in bug 1778972 -- I wonder how that could tie together with berick's work on the Bootstrap 4 staff catalog |
| 16:10 |
pinesol |
Launchpad bug 1778972 in Evergreen "Wishlist - OPAC Redesign" [Wishlist,In progress] https://launchpad.net/bugs/1778972 - Assigned to Christopher Burton (cburton) |
| 16:10 |
sandbergja |
...whenever we decide on a direction for the OPAC |
| 16:12 |
Bmagic |
nfburton++ # freestyling it! |
| 16:13 |
|
khuckins_ joined #evergreen |
| 16:14 |
|
RBecker joined #evergreen |
| 16:30 |
Bmagic |
Is there something I can do to cause search results (as a patron logged in) searching the consortium scope locg=1 to move the bibs with the preferred library to the top of the results and those bibs without items from the home OU below? |
| 16:32 |
jeff |
Bmagic: I'm confused by your usage of "URI" above, but don't trust my current brain focus enough to claim that you're using it wrong. :-) |
| 16:32 |
Bmagic |
jeff: I've been under the impression that everything that comes after the question mark is called the "URI string" |
| 16:33 |
Bmagic |
http(s)://domain.com/folder/webpage?URI=this&string=strings |
| 16:34 |
Bmagic |
whereas URL is referring to the entire thing including the uri string. Please correct me if I am not using the correct nomenclature |
| 16:35 |
jeff |
Now I'm pretty sure you're mis-using the term. Sorry. :-) |
| 16:36 |
Bmagic |
:) hit me with the correct thang |
| 16:37 |
Dyrcona |
Bmagic You mean query string. |
| 16:37 |
Bmagic |
query string, yes (the stuff after the ?) |
| 16:37 |
Dyrcona |
Yes. |
| 16:37 |
Dyrcona |
URI is a superset of URL, IIRC. |
| 16:37 |
Bmagic |
https://dev.to/flippedcoding/what-is-the-difference-between-a-uri-and-a-url-4455 |
| 16:38 |
Bmagic |
education++ |
| 16:38 |
Dyrcona |
Right. |
| 16:38 |
Dyrcona |
What that page says. :) |
| 16:38 |
Bmagic |
:) |
| 16:38 |
Bmagic |
I changed the bug's title |
| 16:39 |
Bmagic |
jeff++ |
| 16:54 |
|
nfBurton joined #evergreen |
| 16:54 |
nfBurton |
Hey all |
| 16:54 |
Bmagic |
heya |
| 16:54 |
nfBurton |
I can't seem to get cstore, pcrus or reporter-store osrf services to run. |
| 16:55 |
nfBurton |
I did an upgrade to 3.2.4 the other day and they try to start but then come back with a stale pid |
| 16:55 |
nfBurton |
Any suggestions |
| 16:55 |
nfBurton |
They were working tiol i restarted services |
| 16:56 |
Dyrcona |
nfBurton: Check that you can talk to the database. Then check that the database parameters are correct in opensrf.xml |
| 16:57 |
nfBurton |
Looks like the DB server locked up XD fun times |
| 16:57 |
nfBurton |
I figured |
| 16:57 |
nfBurton |
Dyrcona++ |
| 16:57 |
nfBurton |
Hopefully it comes back after a restart |
| 17:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 17:17 |
|
mmorgan left #evergreen |
| 17:31 |
Bmagic |
dbwells++ # 3.3.0 baby! |
| 17:32 |
dbwells |
:) |
| 18:05 |
|
jamesrf joined #evergreen |
| 19:24 |
|
Christineb joined #evergreen |
| 20:48 |
|
sandbergja_ joined #evergreen |
| 21:12 |
|
rashma_away joined #evergreen |
| 21:13 |
|
Glen joined #evergreen |
| 21:18 |
|
sandbergja_ joined #evergreen |
| 21:26 |
|
khaun joined #evergreen |
