| Time |
Nick |
Message |
| 00:41 |
|
cmalm joined #evergreen |
| 00:45 |
|
collum joined #evergreen |
| 00:59 |
|
sandbergja joined #evergreen |
| 01:11 |
|
cmalm joined #evergreen |
| 01:32 |
|
cmalm_ joined #evergreen |
| 01:37 |
|
collum joined #evergreen |
| 01:38 |
|
collum_ joined #evergreen |
| 01:45 |
|
sandbergja joined #evergreen |
| 02:12 |
|
collum joined #evergreen |
| 02:27 |
|
cmalm joined #evergreen |
| 02:43 |
|
collum_ joined #evergreen |
| 02:47 |
|
cmalm_ joined #evergreen |
| 02:52 |
|
cmalm joined #evergreen |
| 03:20 |
|
yboston joined #evergreen |
| 04:43 |
|
collum joined #evergreen |
| 04:49 |
|
yboston joined #evergreen |
| 05:25 |
|
collum joined #evergreen |
| 05:35 |
|
yboston joined #evergreen |
| 05:37 |
|
collum joined #evergreen |
| 06:09 |
|
collum joined #evergreen |
| 06:18 |
|
jeff_ joined #evergreen |
| 06:18 |
|
eeevil joined #evergreen |
| 06:18 |
|
devted joined #evergreen |
| 06:18 |
|
jyorio joined #evergreen |
| 06:18 |
|
phasefx_ joined #evergreen |
| 06:18 |
|
akilsdonk joined #evergreen |
| 06:18 |
|
egbuilder joined #evergreen |
| 06:18 |
|
RBecker joined #evergreen |
| 06:18 |
|
mnsri joined #evergreen |
| 06:18 |
|
rashma joined #evergreen |
| 06:19 |
|
rhamby joined #evergreen |
| 06:19 |
|
jgoodson joined #evergreen |
| 06:19 |
|
lbarry joined #evergreen |
| 06:19 |
|
abneiman joined #evergreen |
| 06:19 |
|
drigney joined #evergreen |
| 06:19 |
|
laurie joined #evergreen |
| 06:19 |
|
remingtron joined #evergreen |
| 06:19 |
|
kip joined #evergreen |
| 06:19 |
|
pastebot joined #evergreen |
| 06:23 |
|
dbs joined #evergreen |
| 06:23 |
|
csharp joined #evergreen |
| 06:23 |
|
gsams joined #evergreen |
| 06:24 |
|
kip joined #evergreen |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 07:15 |
|
collum joined #evergreen |
| 07:36 |
|
collum joined #evergreen |
| 08:18 |
|
Dyrcona joined #evergreen |
| 08:34 |
|
mantis1 joined #evergreen |
| 08:34 |
|
sandbergja joined #evergreen |
| 08:44 |
Dyrcona |
Y'know. It would be useful if the OPAC had some kind of one-time notification feature where an important message could pop up to notify users of something important, such as a change in service, etc. I know there is the maintenance message, but I'm thinking of something more dynamic and possibly location specific. |
| 08:44 |
|
mmorgan joined #evergreen |
| 09:02 |
|
mdriscoll joined #evergreen |
| 09:07 |
rhamby |
I can certainly see the use for that. "Hey folks we may be closing for inclement weather tomorrow, we will post something on the website as soon as we know." etc... |
| 09:17 |
|
jvwoolf joined #evergreen |
| 09:22 |
|
collum joined #evergreen |
| 09:34 |
|
yboston joined #evergreen |
| 09:40 |
bshum |
Dyrcona: I think there was thought to add more messages, like https://bugs.launchpad.net/evergreen/+bug/1801999 |
| 09:40 |
pinesol |
Launchpad bug 1801999 in Evergreen "Additional Alert Message for Public Catalog" [Wishlist,New] |
| 09:41 |
Dyrcona |
bshum: Thanks for the reminder. I agree with Terran's comment on that bug, though I actually was thinking of a new admin interface for this. |
| 09:42 |
bshum |
Right, it is nice to consider |
| 09:42 |
|
cmalm joined #evergreen |
| 09:44 |
Dyrcona |
I also imagined the UI popping up a dialog or something that would go away and not show for that user again. Also would be nice to give the messages start and end dates. |
| 09:47 |
Dyrcona |
Guess that would require new permissions, too.... "This'll run into money." :) |
| 10:08 |
|
mmorgan1 joined #evergreen |
| 10:21 |
|
jvwoolf1 joined #evergreen |
| 10:26 |
|
mmorgan joined #evergreen |
| 10:28 |
|
Christineb joined #evergreen |
| 11:06 |
|
sandbergja joined #evergreen |
| 12:03 |
|
jihpringle joined #evergreen |
| 12:17 |
|
khuckins joined #evergreen |
| 12:54 |
|
sandbergja joined #evergreen |
| 13:50 |
|
jvwoolf joined #evergreen |
| 14:01 |
|
csharp joined #evergreen |
| 14:38 |
|
terranm joined #evergreen |
| 14:59 |
berick |
volunteer to host IRC dev meeting appreciated |
| 15:00 |
|
mmorgan1 joined #evergreen |
| 15:02 |
* csharp |
decides to give it a whirl |
| 15:02 |
berick |
csharp++ |
| 15:02 |
csharp |
#startmeeting 2020-02-04 Developer Meeting |
| 15:02 |
pinesol |
Meeting started Tue Feb 4 15:02:31 2020 US/Eastern. The chair is csharp. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:02 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:02 |
|
Topic for #evergreen is now (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:02 |
pinesol |
The meeting name has been set to '2020_02_04_developer_meeting' |
| 15:03 |
csharp |
#info Agenda: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2020-02-04 |
| 15:03 |
csharp |
#topic Roll Call |
| 15:03 |
|
Topic for #evergreen is now Roll Call (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:03 |
csharp |
#info csharp = Chris Sharp, GPLS |
| 15:03 |
berick |
#info berick Bill Erickson, KCLS |
| 15:04 |
jeff_ |
#info jeff = Jeff Godin, Traverse Area District Library (TADL) |
| 15:04 |
jeffdavis |
#info jeffdavis = Jeff Davis, Sitka (BC Libraries Coop) |
| 15:04 |
sandbergja |
#info sandbergja = Jane Sandberg, Linn-Benton Community College |
| 15:04 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:05 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin University) |
| 15:05 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (Calvin University) |
| 15:05 |
csharp |
#topic Action Items from Last Meeting |
| 15:05 |
|
Topic for #evergreen is now Action Items from Last Meeting (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:05 |
csharp |
#info gmcharlt will apply various code changes and nudges regarding the remaining webstaffblocker bugs |
| 15:06 |
csharp |
anyone have an update on that? |
| 15:06 |
* csharp |
notes the lack of EOLI folk |
| 15:07 |
|
khuckins joined #evergreen |
| 15:07 |
abneiman |
csharp: EOLI people are having an important internal meeting and will not be available to today's meeting; apologies, all |
| 15:08 |
csharp |
abneiman: thanks for letting us know! |
| 15:08 |
csharp |
#info said bugs: https://bit.ly/2vHWljR |
| 15:08 |
csharp |
just two left |
| 15:09 |
csharp |
(one is a security bug, so may not be visible to all) |
| 15:09 |
csharp |
ok, moving on... |
| 15:09 |
csharp |
# topic OpenSRF release info |
| 15:09 |
csharp |
#topic OpenSRF release info |
| 15:09 |
|
Topic for #evergreen is now OpenSRF release info (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:09 |
csharp |
anyone have updates on OpenSRF releases? |
| 15:10 |
csharp |
looks like we haven't had any new commits since 3.2.0 was release |
| 15:10 |
csharp |
d |
| 15:10 |
csharp |
okey doke |
| 15:11 |
csharp |
#topic Evergreen release info |
| 15:11 |
|
Topic for #evergreen is now Evergreen release info (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:11 |
csharp |
we saw point releases for 3.3 and 3.4 two weeks ago |
| 15:12 |
sandbergja |
I have a release-related question |
| 15:12 |
csharp |
eg builder team deserves our thanks, particularly Dyrcona and Bmagic, who performed the builds |
| 15:12 |
sandbergja |
I am wondering how we can incorporate Angular i18n and poeditor.com into the release process. Is this something simple that the build team could do? Or a project for during the conference? Or something longer term? |
| 15:12 |
terranm |
Dyrcona++ and Bmagic++ |
| 15:12 |
sandbergja |
Dyrcona++ |
| 15:12 |
sandbergja |
Bmagic++ |
| 15:12 |
berick |
sandbergja: i was just thinking about that yesterday... needs some revisiting for usre |
| 15:12 |
berick |
release_team++ # big time |
| 15:13 |
sandbergja |
As we get more and more Angular interfaces, fewer and fewer of the interfaces are actually available in localized versions |
| 15:13 |
sandbergja |
:-( |
| 15:14 |
berick |
right. and one month out from 3.5 beta, we need to get the strings exposed for translation |
| 15:14 |
csharp |
#info we need to address i18n and l10n issues with Angular as fewer and fewer interfaces are available in localized versions |
| 15:15 |
berick |
i'll follow up on that. i'm rusty on the poeditor stuff |
| 15:15 |
sandbergja |
berick++ |
| 15:15 |
csharp |
#info 3.3.6 and 3.4.2 were released 1/29/2020 - first releases of the year |
| 15:16 |
berick |
exporting the strings is simple enough. just need to finalize the work flow for translators |
| 15:16 |
csharp |
#action berick will follow up on i18n/l10n issues and report back |
| 15:16 |
sandbergja |
If I can help with that at all, berick, let me know! |
| 15:16 |
berick |
will do, thanks sandbergja |
| 15:16 |
csharp |
#action sandbergja will assist berick as needed |
| 15:16 |
csharp |
ok, so 3.5... |
| 15:17 |
terranm |
I'm also happy to help with that if I have some direction |
| 15:17 |
* dbwells |
tries to remember his poeditor.com password... |
| 15:17 |
alynn26 |
#info alynn26 = Lynn Floyd, Indiana |
| 15:17 |
csharp |
I believe we have 60 or so bugs targeted for 3.5-alpha |
| 15:18 |
csharp |
41 have pullrequests and 8 have signoffs |
| 15:18 |
csharp |
#info about 60 bugs targeted for 3.5-alpha - 41 with pullrequest tags and 8 with signedoff tags |
| 15:19 |
berick |
on that note, calling all code reviewers and committers for feedback fest in 2 weeks. |
| 15:19 |
csharp |
what are the specific dates for that for the minutes/logs? |
| 15:19 |
csharp |
terranm? |
| 15:19 |
berick |
2/17 -> 2/21 |
| 15:19 |
csharp |
ok cool |
| 15:20 |
terranm |
What Bill said |
| 15:20 |
* berick |
notes 2/17 may be a holiday for some |
| 15:20 |
terranm |
If we can get a bunch of those pullrequests on some sandboxes, the New Developers Group should be able to test a good chunk of them |
| 15:20 |
csharp |
# feedback fest scheduled for the week of 2/17 - 2/22 - code reviewers and committers are expected to participate |
| 15:20 |
csharp |
#info feedback fest scheduled for the week of 2/17 - 2/22 - code reviewers and committers are expected to participate |
| 15:20 |
* csharp |
will get the hang of it |
| 15:21 |
sandbergja |
terranm: would it help if we reserved some bugs specifically for the new devs group? |
| 15:21 |
sandbergja |
e.g. some that are simpler, or some that match particular interests of your members? |
| 15:22 |
terranm |
Anything that is testable without having access to the back end / logs is good |
| 15:22 |
terranm |
Actually getting them installed on a sandbox is the main hurdle |
| 15:23 |
csharp |
we can make at least one master server available if that's helpful |
| 15:23 |
terranm |
csharp++ |
| 15:23 |
alynn26 |
csharp++ |
| 15:23 |
csharp |
#action csharp will work with terranm to get at least one sandbox server running master + pullrequest patches |
| 15:24 |
csharp |
any particular 3.5-targeted features that need special attention? |
| 15:25 |
jeffdavis |
filters... let me look at bug #s |
| 15:25 |
csharp |
we have the OpenAthens integration feature running on PINES production and have applied a couple of patches since to address flaws that only showed up post-deployment |
| 15:25 |
csharp |
https://bugs.launchpad.net/evergreen/+bug/1842297 (for the logs) |
| 15:26 |
pinesol |
Launchpad bug 1842297 in Evergreen "OpenAthens integration" [Wishlist,Confirmed] |
| 15:26 |
jeffdavis |
that's great! |
| 15:26 |
csharp |
while we can verify it's running peacefully on PINES, we don't yet know if the core feature of providing auth to other services works |
| 15:27 |
csharp |
libraries are in the process of migration (coordinated by GALILEO, our sibling agency) |
| 15:28 |
csharp |
any other features anyone wants to highlight/mention? |
| 15:28 |
* berick |
checks the roadmap |
| 15:28 |
terranm |
It'd be nice to get Hopeless Holds finished: https://bugs.launchpad.net/evergreen/+bug/1811710 |
| 15:28 |
pinesol |
Launchpad bug 1811710 in Evergreen "wishlist: Improvements to Hopeless Holds" [Wishlist,Confirmed] |
| 15:29 |
csharp |
#info 3.5 roadmap: https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.5 |
| 15:29 |
terranm |
All 5 of the circ ones are really good improvements |
| 15:29 |
jeffdavis |
bug 1846042 could also use some love, although I'd class it as a regression/bugfix rather than a feature request |
| 15:29 |
pinesol |
Launchpad bug 1846042 in Evergreen 3.3 "Angular admin pages need filters" [High,Confirmed] https://launchpad.net/bugs/1846042 |
| 15:31 |
csharp |
#info request for attention for Hopeless Holds (https://bugs.launchpad.net/evergreen/+bug/1811710) and Angular admin page filters (https://launchpad.net/bugs/1846042) |
| 15:31 |
pinesol |
Launchpad bug 1811710 in Evergreen "wishlist: Improvements to Hopeless Holds" [Wishlist,Confirmed] |
| 15:31 |
pinesol |
Launchpad bug 1846042 in Evergreen 3.3 "Angular admin pages need filters" [High,Confirmed] |
| 15:31 |
berick |
jeffdavis: for the grid filters, UX/Usability are the main concerns at this point? |
| 15:32 |
sandbergja |
jeffdavis: I wonder if this commit might help with the cluttering filter issue: https://github.com/evergreen-library-system/Evergreen/commit/9077cbc427d544b25c932b51591126e4a2b2bead |
| 15:32 |
pinesol |
sandbergja: [evergreen|Galen Charlton] LP#1855931: (follow-up) make grid filter control cells wrap as well - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9077cbc> |
| 15:32 |
jeffdavis |
berick: yes, I think so |
| 15:32 |
jeffdavis |
ah, I was trying to find that follow-up bug |
| 15:32 |
sandbergja |
(just musing, I have not tested a rebased version of gmcharlt's branch for 1846042) |
| 15:33 |
terranm |
PINES has this one in production and it seems to be working well: https://bugs.launchpad.net/evergreen/+bug/1570072 - I'm not sure if anyone else from ECDI has seen any issues with testing |
| 15:33 |
pinesol |
Launchpad bug 1570072 in Evergreen "Hold request update notification preferences on change" [Wishlist,Confirmed] |
| 15:34 |
jeffdavis |
terranm: do you want that targeted for 3.5? Currently it's 3.next |
| 15:34 |
csharp |
ECDI = Evergreen Community Development Initiative for those who don't know |
| 15:34 |
Bmagic |
do we have a list of bugs for the feedback fest? |
| 15:35 |
remingtron |
csharp: thanks for translating |
| 15:35 |
terranm |
jeffdavis: Since we already have it in production, I don't have any preference which it's targeted to |
| 15:35 |
csharp |
jeffdavis: makes sense to me |
| 15:35 |
terranm |
Bmagic: not yet - I'll take a look through the pullrequests. Maybe we can put some on your sandbox and some on one of ours. |
| 15:35 |
jeffdavis |
Ha, fair enough. I've retargeted it. |
| 15:36 |
csharp |
jeffdavis++ |
| 15:36 |
terranm |
jeffdavis++ :)\ |
| 15:36 |
terranm |
I mean, :) |
| 15:37 |
csharp |
ok, unless there's more to talk about 3.5, let's move to Hatch |
| 15:37 |
Bmagic |
also - getting into launchpad fu - do we have a guideline for how we target bugs, etc? When the milestone needs to change and whatnot? |
| 15:38 |
csharp |
Bmagic: I don't know of specific documentation on that, but I can see it would be helpful |
| 15:38 |
Bmagic |
word |
| 15:38 |
berick |
Bmagic: any specific questions? |
| 15:39 |
Bmagic |
I thought of it when thinking about a recent patch bug 1849736 |
| 15:39 |
pinesol |
Launchpad bug 1849736 in Evergreen "Add action trigger for email/sms for patron self registration" [Wishlist,In progress] https://launchpad.net/bugs/1849736 |
| 15:39 |
csharp |
#info there is a need for documentation around bug wrangling guidelines - specifically release/milestone/series targeting |
| 15:40 |
remingtron |
Bmagic: There's a wiki page about some of it: https://wiki.evergreen-ils.org/doku.php?id=dev:bug_wrangler:faq |
| 15:40 |
csharp |
remingtron++ |
| 15:40 |
Bmagic |
Not sure I did the right thing with LP |
| 15:40 |
Bmagic |
remingtron++ |
| 15:40 |
csharp |
#info and like a magician, remingtron provided a wiki link: https://wiki.evergreen-ils.org/doku.php?id=dev:bug_wrangler:faq |
| 15:40 |
Bmagic |
magician++ |
| 15:41 |
berick |
Bmagic: bug looks fine. new features should target 3.5-alpha until it's cut |
| 15:41 |
csharp |
RMs and other wranglers will untarget/retarget bugs as needed when the cut comes |
| 15:42 |
csharp |
#topic Hatch |
| 15:42 |
|
Topic for #evergreen is now Hatch (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:42 |
csharp |
any updates on that? - we saw an omnibus bug come through recently |
| 15:42 |
berick |
I opened Hatch bug #1860187 recently |
| 15:42 |
pinesol |
Launchpad bug 1860187 in Evergreen "Hatch Windows installer creates properties files with limited read access" [Undecided,New] https://launchpad.net/bugs/1860187 |
| 15:42 |
berick |
and we're tesing it locally |
| 15:43 |
csharp |
we've seen some trouble in PINES with Hatch running on 32-bit systems, but we've disavowed Windows 7 support and the libraries have Windows 10 64-bit available to them |
| 15:43 |
csharp |
so we didn't dig much on that |
| 15:44 |
Bmagic |
I've seen that with 0.3.2 because it ships it's own jre - 64 only? |
| 15:44 |
berick |
with hatch 0.3.2, 32-bit is not supported... |
| 15:44 |
berick |
right |
| 15:45 |
csharp |
ok - good to know |
| 15:45 |
|
blongwel joined #evergreen |
| 15:45 |
csharp |
again, probably not a real problem since people need to stop using EOL systems :-) |
| 15:45 |
terranm |
There are 32-bit Windows 10 systems out there, though - at the very least, it should be mentioned on the downloads page / installation instructions |
| 15:46 |
csharp |
ok, on to new business... |
| 15:46 |
Bmagic |
csharp: been there as well and I've gone as far as replacing the alrady-installed (C:\Program File (x86)s\Hatch\java-*) folders with the 32 bit counter parts - I don't recommend it :) |
| 15:46 |
csharp |
Bmagic: heh |
| 15:46 |
terranm |
Bmagic: ew! |
| 15:46 |
csharp |
#topic Feedback for New Features Under Development |
| 15:46 |
|
Topic for #evergreen is now Feedback for New Features Under Development (Meeting topic: 2020-02-04 Developer Meeting) |
| 15:47 |
csharp |
looks like berick has at least one item there |
| 15:47 |
sandbergja |
I put the promise-related one there |
| 15:47 |
berick |
i believe sandbergja goes... |
| 15:48 |
sandbergja |
This grew out of conversations about bug 1821094 |
| 15:48 |
pinesol |
Launchpad bug 1821094 in Evergreen 3.3 "Item status refresh after editing can get confusingly slow" [Medium,Confirmed] https://launchpad.net/bugs/1821094 |
| 15:48 |
sandbergja |
gmcharlt suggested that -- in cases where we need to do a bunch of requests -- we batch those requests |
| 15:49 |
sandbergja |
So we don't totally slow down everything for the user with sequential requests |
| 15:49 |
sandbergja |
But don't clobber the server with simultaneous requests |
| 15:49 |
sandbergja |
jeffdavis mentioned that this should be an approach that we take not just in Item Status, but throughout the Web client |
| 15:50 |
berick |
sandbergja: your promise batching code looks sane. i have not kept up with the bug... does that solve the issue in your tests? |
| 15:50 |
sandbergja |
It does |
| 15:50 |
sandbergja |
But all my tests have been on a little VM on my laptop |
| 15:51 |
sandbergja |
So I'd really appreciate more help testing the specific case in bug 1821094 |
| 15:51 |
pinesol |
Launchpad bug 1821094 in Evergreen 3.3 "Item status refresh after editing can get confusingly slow" [Medium,Confirmed] https://launchpad.net/bugs/1821094 |
| 15:51 |
sandbergja |
And also some discussion about whether we want to batch the promise resolving in other places in the AngularJS client |
| 15:51 |
sandbergja |
Here's the specific commit: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=75176bca0ce8051a6dd4ba56f5613bce75901f09 |
| 15:52 |
csharp |
sandbergja: we can test it on a PINES server with realistic data/specs |
| 15:52 |
sandbergja |
charp++ |
| 15:52 |
sandbergja |
That would be really helpful! |
| 15:52 |
csharp |
#action csharp will arrange testing for sandbergja's fix to https://launchpad.net/bugs/1821094 on a realistic test server |
| 15:52 |
pinesol |
Launchpad bug 1821094 in Evergreen 3.3 "Item status refresh after editing can get confusingly slow" [Medium,Confirmed] |
| 15:53 |
berick |
i think that's a good tool to have in our toolbox. I also think devs should consider the option of creating UI specific APIs for new interfaces. |
| 15:53 |
berick |
batching some of the exising angjs stuff seems like it would be helpful |
| 15:53 |
sandbergja |
berick: UI-specific APIs seem like they would be helpful for the AngJS->Angular transition |
| 15:54 |
csharp |
heads up: I have kind of a hard stop at 4:00 - gotta pick up a kid |
| 15:54 |
berick |
sandbergja: indeed |
| 15:54 |
sandbergja |
Okay, I can be done with my item! |
| 15:54 |
sandbergja |
Thanks, all! |
| 15:54 |
berick |
sandbergja: but I also wouldn't want to cause too much disruption to the existing andjs code just to prep for angular. |
| 15:55 |
csharp |
but if someone wants to take over and follow https://wiki.evergreen-ils.org/doku.php?id=community:using-meetbot and the agenda https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2020-02-04 you don't have to rush :-) |
| 15:55 |
sandbergja |
that makes sense |
| 15:56 |
csharp |
okay, so "needsdiscussion" tag was mentioned - anyone want to champion that cause? |
| 15:57 |
* csharp |
can probably let his son wait a bit, so is willing to go past 4:00 EST if needed |
| 15:57 |
berick |
who added that agenda item? |
| 15:58 |
* csharp |
grumbles $deity knows I've waited for him enough |
| 15:58 |
berick |
heh |
| 15:58 |
csharp |
oh - hmm - looks like that comes free with the agenda boilerplate |
| 15:59 |
berick |
ah |
| 15:59 |
csharp |
yeah, so... |
| 15:59 |
csharp |
berick: feel free to move to your topic |
| 15:59 |
berick |
k |
| 15:59 |
berick |
csharp: be free :) |
| 16:00 |
csharp |
berick: thanks - I'll let you take it from here :-) |
| 16:00 |
berick |
my agenda items essentially boil down to angular staff catalog: what do we want to do for 3.5 and looking ahead to 3.6 |
| 16:00 |
berick |
WRT it being a replacement (whole or part) to the embedded tpac |
| 16:01 |
remingtron |
berick: is there a list of missing features? |
| 16:02 |
berick |
https://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:angular_staff_catalog |
| 16:02 |
berick |
quite a few open pullreuquests. a small handlful of not-yet-coded features |
| 16:02 |
csharp |
as a parting comment, I'll mention there's *some* (not sure how widespread/intense) feeling here that staff need/expect the patron opac within the client - I'm not sure I agree, but it was a specific request from The Beginning of Evergreen in PINES |
| 16:02 |
* csharp |
jets |
| 16:04 |
berick |
as with the XUL client, it's one tab over |
| 16:04 |
sandbergja |
Does anybody have a sense for how much the Angular catalog is currently being used in production? |
| 16:05 |
Dyrcona |
I'll add that having the patron in the staff client was one of the selling points of Evergreen at MVLC, because staff could see more or less what patrons saw. |
| 16:05 |
berick |
i haven't heard one way or the other, sandbergja |
| 16:05 |
sandbergja |
My vague sense is that it's not quite ready to be the default catalog, but definitely ready to be less hidden... |
| 16:06 |
berick |
re: what patrons see, there is a tab in the detail page that shows the patron view. you can also open a new tab to the tpac. i'm confused what the issue is on that. |
| 16:07 |
|
mmorgan joined #evergreen |
| 16:07 |
terranm |
I honestly haven't looked at it since Bill did a demo for the catalogers group a few months ago, but Chris enabled it on one of our test servers so I'll make a point to look further with real data |
| 16:07 |
jeffdavis |
We haven't enabled the Angular catalogue in production here, but I've proposed making it visible. We're seeing a lot of slowness in the staff catalogue and I wonder if the Angular version would be an improvement. |
| 16:07 |
berick |
sandbergja: same. until it gets more use in the wild, making it the default is a hard sell. |
| 16:08 |
berick |
and by the same token, if no staff know it exists, no one will use it |
| 16:08 |
berick |
it's a bit complicated, since using it requires extra steps (since all the links lead back to the tpac catalog) |
| 16:09 |
jeff_ |
is there anything architectural preventing a mode/setting where any catalog links (from, say, grids/etc) go to the angular staff catalog? |
| 16:09 |
berick |
jeff: just a whole lot of if/else statements |
| 16:09 |
berick |
or a redirect |
| 16:10 |
sandbergja |
Dyrcona: here is how the patron view of individual bib records is currently showing up in the Angular catalog: http://www.sandbox.lbcc.linnlibraries.org/patron_view_tab.gif |
| 16:10 |
jeff |
maybe a prefix that's set in one place and then used everywhere we link? |
| 16:10 |
* Dyrcona |
forgot about the meeting until his name was mentioned earlier. :) |
| 16:10 |
sandbergja |
Dyrcona: fwiw, the catalogers working group seemed pretty happy with the patron view tab |
| 16:11 |
terranm |
+1 to the patron view tab |
| 16:11 |
jeffdavis |
sandbergja: that's a surprising number of reference copies of that particular title |
| 16:11 |
berick |
jeff: maybe. but it gets complicated with routerLink's, target=_self, etc. depending on the context |
| 16:14 |
jeffdavis |
berick: sounds like more testing is wanted before we make it the default, but maybe we can at least make it more visible (or not call it "Experimental" anymore or whatever) in 3.5? |
| 16:14 |
terranm |
+1 |
| 16:14 |
remingtron |
berick: maybe during feedback fest we could invite EG users to test the staff catalog and give feedback |
| 16:14 |
remingtron |
(and/or during a bug squashing week) |
| 16:14 |
terranm |
+1 |
| 16:15 |
berick |
remingtron: on that note, I'll be posting all of the pending staff catalog pullreqs to a demo server for fests and squashes |
| 16:15 |
remingtron |
cool |
| 16:16 |
berick |
so i'll post a LP about making it visible by default in 3.5, while retaining the option to hide it |
| 16:16 |
sandbergja |
berick++ |
| 16:16 |
berick |
can just keep the same org setting, requiring an explicit 'false' to hide it. and will request feedback on labeling |
| 16:17 |
berick |
#action berick to open LP on showing link to ang staff cat by default in 3.5 |
| 16:17 |
berick |
anything else on that topic? |
| 16:18 |
berick |
#topic QA-related bugs |
| 16:18 |
berick |
did someone add this one or is it another boilerplate entry? |
| 16:19 |
jeff |
berick: you don't appear to be chair, so none of your commands are being picked up by meetbot. fixing. |
| 16:19 |
remingtron |
boilerplate, I think |
| 16:19 |
berick |
jeff: oh bleh |
| 16:19 |
jeff |
added you. |
| 16:19 |
* berick |
notes the LP link produces no results, so... |
| 16:19 |
berick |
thanks jeff |
| 16:19 |
berick |
#action berick to open LP on showing link to ang staff cat by default in 3.5 |
| 16:19 |
jeff |
if you re-do your #info and #topic i think that's all |
| 16:20 |
jeff |
er, action. yeah. |
| 16:20 |
berick |
i'll skip the QA topic since it seems to be a no-go |
| 16:20 |
berick |
ok, any other business to discuss today? |
| 16:21 |
berick |
#idea more cowbell |
| 16:21 |
* berick |
is practicing |
| 16:21 |
berick |
ok |
| 16:21 |
berick |
#endmeeting |
| 16:21 |
|
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 |
| 16:21 |
pinesol |
Meeting ended Tue Feb 4 16:21:53 2020 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:21 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-02-04-15.02.html |
| 16:21 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-02-04-15.02.txt |
| 16:21 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-02-04-15.02.log.html |
| 16:22 |
berick |
thanks everyone |
| 16:22 |
terranm |
berick++ csharp++ |
| 16:22 |
remingtron |
berick++ |
| 16:22 |
remingtron |
csharp++ |
| 16:22 |
sandbergja |
berick++ |
| 16:22 |
sandbergja |
csharp++ |
| 16:27 |
|
tlittle joined #evergreen |
| 16:31 |
dbwells |
csharp++ berick++ ui_specific_apis++ |
| 16:34 |
mdriscoll |
What is the recommended version of Postgres for 3.4 and beyond? The install instructions say that 9.6 is the minimum. I'm running 9.4 on production and test servers. Should I plan on 9.6 or jump to 10, 11? |
| 16:40 |
bshum |
Stick with 9.6 |
| 16:40 |
bshum |
10 was wonky for some people, I remember csharp having issues after their upgrade? |
| 16:41 |
bshum |
So we're still needing some DB refinements I think for some database function changes |
| 16:41 |
Dyrcona |
bshum: I'm not aware of any specific issues with 10 that remain, but it wouldn't surprise me if something else turned up. |
| 16:41 |
bshum |
Dyrcona: I think csharp noted more set top returning function errors |
| 16:41 |
bshum |
He didn't say which functions were broken specifically, but he was mid rolling back his production or something |
| 16:42 |
bshum |
So, I was going to ask more details the next time I saw him |
| 16:42 |
bshum |
For now I'd say stick to PG 9.6 for community support :D |
| 16:42 |
Dyrcona |
I did a grep through the code and didn't see any. |
| 16:42 |
bshum |
And we'll tackle 10/11/12 next time |
| 16:43 |
bshum |
Yeah I wondered if maybe he just had some custom function |
| 16:43 |
* Dyrcona |
has 9.6 through 12 installed on a test server. |
| 16:43 |
bshum |
Or it's some reporter one |
| 16:43 |
bshum |
That would generally also be custom to PINES |
| 16:43 |
bshum |
I thought we nailed down all the ones from concerto clean master for PG 10 |
| 16:44 |
Dyrcona |
mdriscoll: We upgraded to 9.6 in January from 9.5, if that's any help. |
| 16:44 |
bshum |
But then again, we also didn't yet write pgtap tests for every core function |
| 16:44 |
bshum |
Just to be safe |
| 16:44 |
* bshum |
adds to his Hackfest ideas list |
| 16:44 |
Dyrcona |
Yeah, we need more pgtap tests. |
| 16:45 |
Dyrcona |
Not sure that we can really test all of the functions since they rely so heavily on side effects. |
| 16:45 |
bshum |
Right |
| 16:45 |
bshum |
But at least we can put some input and see what expected output ought to be |
| 16:46 |
Dyrcona |
I *think* we can do multistep tests, i.e. run the function and check table values after. |
| 16:46 |
bshum |
Right |
| 16:46 |
bshum |
I'm pretty sure we can |
| 16:47 |
mdriscoll |
bshum++ |
| 16:47 |
mdriscoll |
Dyrcona++ |
| 16:47 |
Dyrcona |
Sounds like something to work on during the hackfest. Guess I know what we're doing. :) |
| 16:47 |
bshum |
Huzzah! |
| 16:50 |
* bshum |
has only been talking about doing it for like the past 2 or 3 conferences now :( |
| 16:51 |
Dyrcona |
It came up at the hack-away in 2018, too. |
| 16:51 |
bshum |
I should say "evergreen events" rather than just conferences :D |
| 17:02 |
|
mmorgan left #evergreen |
| 17:05 |
|
jvwoolf left #evergreen |
| 17:16 |
csharp |
for the logs, Dyrcona is correct about 10 - I went live with 10 on 3.2 and that was not good, but only because I didn't backport the PG 10-specific fixes |
| 17:16 |
csharp |
berick++ # finishing the meeting |
| 17:16 |
csharp |
@band add Tab Crash |
| 17:16 |
pinesol |
csharp: Band 'Tab Crash' added to list |
| 17:17 |
Dyrcona |
Also for the logs, you can backport the Pg 10 fixes to earlier versions and things are OK. I've tested them on both 9.5 and 9.6. |
| 18:03 |
|
sandbergja_ joined #evergreen |
| 20:16 |
|
sandbergja joined #evergreen |
| 20:57 |
|
JBoyer joined #evergreen |
| 21:38 |
|
sandbergja joined #evergreen |
| 22:01 |
|
sandbergja joined #evergreen |
| 22:12 |
|
sandbergja joined #evergreen |
| 22:48 |
|
sandbergja joined #evergreen |
