| Time |
Nick |
Message |
| 02:54 |
|
JBoyer joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:13 |
|
rjackson_isl joined #evergreen |
| 07:29 |
|
rfrasur joined #evergreen |
| 07:34 |
|
Dyrcona joined #evergreen |
| 08:02 |
|
book` joined #evergreen |
| 08:09 |
Dyrcona |
We seem to get a fair number (1-50) auto-renewal events that get stuck in collected and reacting states from time to time. Does anyone else have this problem? |
| 08:10 |
rfrasur |
rjackson_isl, is this the same issue we have periodically? |
| 08:11 |
rjackson_isl |
yes - we manually clean up the events - rerunning the cron to re-create after they have failed/gotten stuck |
| 08:13 |
Dyrcona |
I do that when I notice them, like this morning, but most of the ones I see now are too old to bother with fixing. |
| 08:13 |
Dyrcona |
So, this should probably be a Launchpad bug. |
| 08:13 |
rjackson_isl |
documented steps in our wiki - have a cron job setup to uery for them and send email if found |
| 08:15 |
rfrasur |
++ to documented steps, cron jobs, and LP bugs. |
| 08:19 |
rjackson_isl |
in our case (Evergreen Indiana Consortium) it may partially be a load issue and not enough computing horsepower! Co-workers are in the process of upgrading hardware... |
| 08:20 |
rjackson_isl |
where "in the process" might take a few months to get scheduled and in production but the hardware is on site! |
| 08:21 |
Dyrcona |
rjackson_isl: I don't think that's the issue. I narrowed some down over a year ago to max_stanza_size, and we set it to 10MB on the utility server. |
| 08:22 |
Dyrcona |
We did O/S updates this morning, and I had to wait for the auto-renewals to finish. Once they were done, there was 1 that was collected. I reran it after completing the updates. |
| 08:22 |
rjackson_isl |
yeah - some could be accounts with tons of items out and too much to gather in space given |
| 08:22 |
Dyrcona |
We only did about 16,800 this morning. |
| 08:23 |
Dyrcona |
I don't think that's our problem this time, since that usually leads to hundreds or thousands of events left pending after the trigger runner "crashes." |
| 08:23 |
rjackson_isl |
for us it is a hit and miss with some remaining at a non-complete state |
| 08:24 |
rjackson_isl |
some end up being checked in during the processing or renewed by patron online |
| 08:26 |
rjackson_isl |
we only had a little over 10K this am |
| 08:26 |
Dyrcona |
Our process starts at 3:05 am, so it's not likely staff are renewing anything while it runs. |
| 08:27 |
rjackson_isl |
yeah it is usually an opac renewal |
| 08:27 |
rjackson_isl |
night owls |
| 08:27 |
Dyrcona |
We run it with a daily granularity, which also handles our 7 day account expiration courtesy notices. |
| 08:28 |
rjackson_isl |
++ |
| 08:28 |
Dyrcona |
I don't think that was the case for this 1 event. When I ran it again, it went to complete. If it had been renewed, it would have gone to invalid. |
| 08:28 |
Dyrcona |
I think something else is going on with the auto-renewal events, but I don't know what. |
| 08:33 |
|
book` joined #evergreen |
| 08:38 |
|
mmorgan joined #evergreen |
| 08:39 |
|
book` joined #evergreen |
| 08:42 |
|
dguarrac joined #evergreen |
| 08:46 |
Dyrcona |
rfrasur | rjackson_isl: Lp 1935971 |
| 08:46 |
pinesol |
Launchpad bug 1935971 in Evergreen "Autorenewal Events Get Stuck in collected and reacting states" [Undecided,New] https://launchpad.net/bugs/1935971 |
| 08:46 |
rfrasur |
Dyrcona++ |
| 08:50 |
rjackson_isl |
Dyrcona++ (and +1 on bug) |
| 08:52 |
Dyrcona |
If either of you would confirm the bug, that would be great, thanks! |
| 08:52 |
rfrasur |
I did. |
| 08:53 |
rfrasur |
Unless you need a more technical confirmation than "this happens in this version." |
| 08:54 |
Dyrcona |
rfrasur++ |
| 08:54 |
Dyrcona |
rjackson_isl++ |
| 09:09 |
|
mantis joined #evergreen |
| 09:59 |
|
rfrasur joined #evergreen |
| 10:25 |
pinesol |
[evergreen|Jason Boyer] LP1895737: Add Curbside Appointments to Bootstrap OPAC - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=5cd1d52> |
| 10:26 |
* gmcharlt |
claims 1269 |
| 10:28 |
|
jonadab joined #evergreen |
| 10:29 |
pinesol |
[evergreen|Jane Sandberg] LP1910891: Add new booking perms to appropriate groups - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=0c414a2> |
| 10:29 |
pinesol |
[evergreen|Galen Charlton] LP#1910891: stamp DB update - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9d4aec8> |
| 10:37 |
pinesol |
[evergreen|Jane Sandberg] LP1857060: Tests for ISBNs with 979 prefix - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=3831d36> |
| 10:40 |
rjackson_isl |
looking at a request for a site specific self check receipt and looking at others notice a 5 second Processing Delay being set. Is there a reason this could not be 0 or 1? |
| 10:44 |
jeff |
is it 5 seconds or 5 minutes? stock selfcheck receipt doesn't specify a delay, so it would probably default to '00:05:00'::interval |
| 10:44 |
jeff |
either way, I don't think the value of the delay column is used for print-on-demand. |
| 10:44 |
rjackson_isl |
we were just discussing that locally after I hit enter :( jeff++ |
| 10:45 |
mmorgan |
rjackson_isl was just testing us :) |
| 10:45 |
rjackson_isl |
and it does appear to default to 5 minutes not seconds which would be one heck of a wait! |
| 10:46 |
rjackson_isl |
rjackson_isl is trying to engage brain transmission... |
| 10:48 |
Dyrcona |
Yeah, what jeff said. I think it just executes immediately. |
| 10:51 |
|
Keith-isl joined #evergreen |
| 10:51 |
|
rfrasur joined #evergreen |
| 10:57 |
|
mmorgan left #evergreen |
| 11:01 |
|
mmorgan joined #evergreen |
| 12:05 |
|
jihpringle joined #evergreen |
| 12:07 |
pinesol |
[evergreen|Bill Erickson] LP1910808 Staff catalog show call number - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=b24ff80> |
| 12:07 |
pinesol |
[evergreen|Bill Erickson] LP1913807 Staff catalog shows preferred lib holdings counts - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6d31774> |
| 12:08 |
* gmcharlt |
claims 1270 |
| 12:08 |
|
nfBurton joined #evergreen |
| 12:15 |
pinesol |
[evergreen|Jane Sandberg] LP1718782: Add the Srce fixed field to the Angular MARC editor - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=953d488> |
| 12:15 |
pinesol |
[evergreen|Galen Charlton] LP#1718782: stamp DB update - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c991003> |
| 12:27 |
mantis |
Is there any way to create a template via reporter on online registration? |
| 12:29 |
jeff |
mantis: staged users are deleted once they are registered, and there's nothing that's added to the user object that indicates it was "from" a staged user. |
| 12:32 |
jeff |
I'm pretty sure you can report on Mailing Address Stage or Billing Address Stage, but that's a bug and may already be fixed in current releases. It also would give you limited info -- you could count distinct staged users over time, but not home_ou, etc. |
| 12:33 |
* jeff |
looks to see if there's a bug on that or if it's already fixed |
| 12:57 |
|
collum joined #evergreen |
| 13:13 |
|
jvwoolf joined #evergreen |
| 13:50 |
|
jvwoolf1 joined #evergreen |
| 13:56 |
|
jihpringle joined #evergreen |
| 13:57 |
|
pastebot joined #evergreen |
| 14:00 |
|
pastebot joined #evergreen |
| 14:01 |
pastebot |
"jeff" at 168.25.130.30 pasted "testing" (1 line) at http://paste.evergreen-ils.org/10000 |
| 14:28 |
mantis |
jeff++ |
| 14:29 |
mantis |
jeff: I was looking around the fields for ILS User and wasn't finding anything. The explanation is very helpful! |
| 14:30 |
JBoyer |
Dev meeting in 30 |
| 14:36 |
|
mantis1 joined #evergreen |
| 14:37 |
|
cabreedl joined #evergreen |
| 14:40 |
|
pastebot joined #evergreen |
| 14:41 |
pastebot |
"jeff" at 168.25.130.30 pasted "testing 14402" (1 line) at http://paste.evergreen-ils.org/14402 |
| 14:52 |
Dyrcona |
jeff++ |
| 14:57 |
|
terranm joined #evergreen |
| 14:58 |
bshum |
jeff++ |
| 14:59 |
gmcharlt |
jeff++ |
| 15:01 |
JBoyer |
OHAI |
| 15:01 |
|
abowling joined #evergreen |
| 15:02 |
Dyrcona |
Ohai? |
| 15:02 |
JBoyer |
#startmeeting 2021-07-13 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-07-13 |
| 15:02 |
pinesol |
Meeting started Tue Jul 13 15:02:05 2021 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:02 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:02 |
pinesol |
The meeting name has been set to '2021_07_13___developer_meeting__agenda_available_at_https___wiki_evergreen_ils_org_doku_php_id_dev_meetings_2021_07_13' |
| 15:02 |
abowling |
#info abowling = Adam Bowling, Emerald Data Networks |
| 15:02 |
JBoyer |
oh, hi, but more annoying. |
| 15:02 |
JBoyer |
#topic Introductions |
| 15:02 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
| 15:03 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:03 |
JBoyer |
abowling is ahead of the game, and I am also behind. |
| 15:03 |
jeff |
#info jeff = Jeff Godin, Traverse Area District Library (TADL) |
| 15:03 |
alynn26 |
#info alynn26 is Lynn Floyd, Evergreen Indiana |
| 15:03 |
phasefx |
#info phasefx = Jason Etheridge, Equinox |
| 15:03 |
JBoyer |
#info JBoyer = Jason Boyer, Equinox |
| 15:03 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:03 |
gmcharlt |
#info gmcharlt = Galen Charlton, Equinox |
| 15:03 |
berick |
#info berick = Bill Erickson, KCLS |
| 15:03 |
Dyrcona |
I know, but Ohai is a place name, and I looked it up this morning because I mistakenly thought that was what the O in OMC stood for. |
| 15:03 |
jeffdavis |
#info jeffdavis = Jeff Davis, BC Libraries Cooperative (Sitka) |
| 15:03 |
collum |
#info collum = Garry Collum, KCPL |
| 15:03 |
Dyrcona |
The O is actually for Otara. |
| 15:03 |
abowling |
JBoyer, broken clock... |
| 15:04 |
JBoyer |
And anyone else joining in later feel free to sprinkle infos at the appropriate time. |
| 15:04 |
JBoyer |
#topic Action Items from Last Meeting |
| 15:05 |
JBoyer |
#info JBoyer will for-really-this-time work with csharp to update mailman settings and make an announcement to the lists ahead of time |
| 15:05 |
JBoyer |
We for-really did it, finally! |
| 15:06 |
berick |
JBoyer++ csharp_++ |
| 15:06 |
JBoyer |
I don't expect it to be a significant change for anyone, but if you ever had DMARC rejections in the past or made a change in the future that would have caused such, you're welcome. |
| 15:06 |
alynn26 |
JBoyer++ csharp_++ |
| 15:06 |
Dyrcona |
JBoyer++ csharp_++ |
| 15:07 |
|
sandbergja joined #evergreen |
| 15:07 |
JBoyer |
Everything under release info is still just placeholders, so I'm going hop on down to new business unless someone is eager to spring a surprise on us. |
| 15:07 |
sandbergja |
#info sandbergja is Jane Sandberg, LBCC (making lunch, so I'll be here and there) |
| 15:08 |
JBoyer |
#topic New Business |
| 15:08 |
JBoyer |
#topic Offer official staff interface support for (modern) Edge? |
| 15:09 |
gmcharlt |
JBoyer: when we're done discussion Edge, I do have a couple 3.8 things to call out |
| 15:09 |
JBoyer |
gmcharlt and I were discussing this earlier today, with current Edge being nothing but Chromium with some MS paint, should we offer official support for it? |
| 15:10 |
alynn26 |
We have had users using it. |
| 15:10 |
berick |
was about to ask |
| 15:10 |
gmcharlt |
alynn26: any of them also happening to be shoehorning Hatch into Edge as well? |
| 15:11 |
alynn26 |
nope, they are not. |
| 15:11 |
miker |
#info miker = Mike Rylander, EOLI |
| 15:11 |
|
jvwoolf joined #evergreen |
| 15:11 |
JBoyer |
I use it to talk to Evergreen also, though Hatch support is likely 1) missing, and 2), not that difficult to add. |
| 15:12 |
|
jvwoolf left #evergreen |
| 15:12 |
gmcharlt |
Microsoft actually publishes .debs of Edge, so assuming that it has a headless mode, theoretically it could be folded into the Angular tests if somebody were sufficiently eager |
| 15:12 |
berick |
gmcharlt: huh, didn't know they made debs |
| 15:13 |
berick |
that simplifies some things |
| 15:13 |
JBoyer |
For Hatch I suspect they learned their lesson with old Edge's ridiculous extension mechanism and won't likely stray far from Chromium, though if we want Hatch on the Edge Extension store that's one more place to publish it. |
| 15:16 |
berick |
maybe we could limit this some and say just the Angular bits? maybe that's implied.. |
| 15:16 |
gmcharlt |
having the starting point be support-but-not-Hatch-yet seems like it would be OK |
| 15:16 |
JBoyer |
I don't mind trying to add Edge support to the Angular testing setup, though it will likely be optional so running <os>-<distro>-developer doesn't end up installing 4, 5, or 6 browsers in future. |
| 15:17 |
gmcharlt |
berick: that is, if I'm understanding your question correctly. If Edge somehow breaks on the Dojo or AngularJS stuff, fixing that may be more than we awnt to tackle |
| 15:17 |
JBoyer |
berick, do you mean no Hatch yet, or even more limited than that somehow? |
| 15:18 |
berick |
i mean what gmcharlt said. fixing stuff that's being actively replaced is not best use of time |
| 15:18 |
JBoyer |
Makes sense. |
| 15:18 |
jeff |
+1 to "no fixing stuff that's being actively replaced" |
| 15:19 |
alynn26 |
+1 |
| 15:19 |
JBoyer |
Unless Chrome 92 breaks dojo overnight, heh. |
| 15:19 |
alynn26 |
yep, if it's broke in Chrome that is another issue. |
| 15:21 |
jeff |
certainly. |
| 15:21 |
* berick |
tries installing hatch |
| 15:21 |
JBoyer |
I think this will be a desirable feature since it means one less thing to install |
| 15:21 |
jeffdavis |
I think if the answer to "Is Edge supported?" is "It's complicated" due to Hatch, Dojo, AngJS etc, we effectively don't support Edge. |
| 15:21 |
gmcharlt |
so it sounds like we're defining a second tier of support |
| 15:21 |
gmcharlt |
i.e., |
| 15:22 |
gmcharlt |
Chrome, Firefox: we fix any breakage around Angular, AngularJS, and Dojo unless impossible |
| 15:23 |
gmcharlt |
Edge: we fix any breakage around Angular for versions supported by Angular (https://angular.io/guide/browser-support), but make no definite guarantee about maintianence for AngularJS and Dojo bits |
| 15:23 |
gmcharlt |
and as far as Hatch goes... TBD based on the ease of using the existing extension and publishing it in the Edge store |
| 15:24 |
jeff |
sounds like a reasonable summary of what I think the concensus so far is. |
| 15:24 |
gmcharlt |
(all of that said, not particularly expecting any Dojo or AngularJS issues) |
| 15:24 |
* jeff |
nods |
| 15:24 |
jeffdavis |
I'd be hesitant to tell a library they can use Edge under those conditions tbh. |
| 15:25 |
jeff |
it sounds like there has been some light testing of the current code in Edge. |
| 15:25 |
gmcharlt |
yeah, and production use |
| 15:25 |
alynn26 |
The staff that use Edge know we do not support it. but use it anyway. Have not found any issues with Edge with the AngularJS or Dojo parts. |
| 15:25 |
JBoyer |
I understand the desire not to allow it to cause us any additional support burden, but as I understand it, neither Google or MS make many changes to the core rendering bits of Chromium, it's mostly the (pardon), chrome and syncing backends that are different. I don't see a situation where we have a compatibililty problem with Edge that we wouldn't have with Chrome within days. |
| 15:25 |
gmcharlt |
if Edge weren't Chromium-plus-stuff, I think it would be a bigger lift |
| 15:26 |
jeff |
I think the hesitency in this discussion to claim full support is mostly stemming from the fact that very few here have tested the staff interfaces in Edge. |
| 15:26 |
* mmorgan |
would be interested to know why Edge is preferred by those who are currently using it. |
| 15:27 |
JBoyer |
It's already there. |
| 15:27 |
JBoyer |
And if you're an IT department, it's more easily controlled with group policy. |
| 15:27 |
gmcharlt |
"exchanging Google telemetry for Microsoft telemetry!" |
| 15:27 |
miker |
mmorgan: central admin of IT resources, probably. less for them to have to support |
| 15:27 |
alynn26 |
That is it. JBoyer hit it on the head. |
| 15:27 |
* mmorgan |
nods Edge is kinda pushy, too. |
| 15:27 |
jeff |
"more easily controlled with group policy" is thankfully becoming less of a valid claim. |
| 15:28 |
JBoyer |
Sure, I believe Chrome(-ium?) and even FF have GP templates these days. |
| 15:28 |
gmcharlt |
indeed |
| 15:28 |
alynn26 |
There are. I've used them in the past |
| 15:29 |
gmcharlt |
but if you're a MS shop with a very strict notion of avoding "foreign" software... hey, at least Edge is lightyears ahead of IE in terms of compatibility issues, at least for now |
| 15:30 |
phasefx |
embrace, extend, ... ignore my zealotry :) |
| 15:31 |
gmcharlt |
it also sounds like there are two potentially data-gathering tasks |
| 15:31 |
gmcharlt |
1. a couple people taking it upon themselves to run through the staff interfaces with Edge |
| 15:32 |
gmcharlt |
2. and a quick feasibility check of the current Hatch extension on Edge |
| 15:32 |
berick |
Hatch is working :) |
| 15:32 |
gmcharlt |
berick++ |
| 15:32 |
JBoyer |
berick++ |
| 15:32 |
berick |
edge + hatch on linux that is |
| 15:33 |
gmcharlt |
berick: OK, you have 123.5 seconds to exercise the staff interface ;) |
| 15:33 |
JBoyer |
I can track down the reg info for Windows in that case. |
| 15:33 |
berick |
this would mean modifying the Hatch windows installer as well to deploy the manifest file |
| 15:34 |
JBoyer |
That's what I meant, I'm not going to try installing on Windows until *after* the meeting. ;) |
| 15:34 |
JBoyer |
(Since I'm on a Mac right now, anyway) |
| 15:35 |
gmcharlt |
alynn26: do you know if anybody has successfully used offline circ with Edge? |
| 15:35 |
JBoyer |
Since berick knocked out #2 already, is anyone interested in taking an action item on exercising the staff client in Edge? Hatch is not necessary, but offline would be. |
| 15:36 |
alynn26 |
No, not offline circ on edge. Testing edge on Windows 10 now. |
| 15:37 |
JBoyer |
To be clear, I don't mean anyone needs to try to knock out a client test right now, I know personally that it works fine for everything I've done in it, but there are a lot of things I don't touch. |
| 15:38 |
JBoyer |
Or I will poke at it. |
| 15:39 |
JBoyer |
#action JBoyer will exercise the staff client in a current release of Edge and report back in August |
| 15:39 |
mmorgan |
JBoyer++ |
| 15:39 |
JBoyer |
#action JBoyer will look at adding Edge on Windows support to the Hatch installer |
| 15:40 |
JBoyer |
Any other Edge discussion before we move on? |
| 15:41 |
jeff |
in summary, until further research is complete: Chrome or Firefox recommended, Edge if you're... Brave. |
| 15:41 |
jeff |
(ducks) |
| 15:41 |
berick |
heh |
| 15:41 |
alynn26 |
+1 |
| 15:41 |
JBoyer |
Hey-o, |
| 15:41 |
JBoyer |
But yeah, Brave users are on their own for now. :P |
| 15:42 |
jeff |
yes. |
| 15:43 |
JBoyer |
Ok, moving on to |
| 15:43 |
JBoyer |
#topic Feedback for New Features Under Development |
| 15:43 |
JBoyer |
gmcharlt, I assume your 3.8 question is about bug 1904036? |
| 15:43 |
pinesol |
Launchpad bug 1904036 in Evergreen "Port patron interfaces to Angular (search, checkout, etc.)" [Wishlist,New] https://launchpad.net/bugs/1904036 |
| 15:43 |
berick |
i added that one |
| 15:44 |
gmcharlt |
JBoyer: yeah, mine was more of a general heads up about a bunch of big features for which we need testing |
| 15:44 |
JBoyer |
:( |
| 15:44 |
berick |
seeking feedback on trying to add it to 3.8 as experimental |
| 15:44 |
gmcharlt |
1904036 is definitely one of them, but there's also |
| 15:44 |
gmcharlt |
- the volume/copy editor Mark Angular |
| 15:44 |
gmcharlt |
- berick's PO/LI/SL stuff |
| 15:45 |
gmcharlt |
- the acquisitions administration work |
| 15:45 |
berick |
if it's disabled, it's essentially not there, but it does add quite a few angular updates (that could potentially be extracted out to their own bugs, of course) |
| 15:45 |
gmcharlt |
- as well as remaining Angular staff catalog regressions |
| 15:45 |
gmcharlt |
and yeah, as berick says, a ton of updates to core Angular components across all of these branches |
| 15:46 |
gmcharlt |
so generally speaking - here's my plea/call for folks to adopt some of these branches and exercise them |
| 15:46 |
gmcharlt |
berick and I will also be coordinating some stuff to make Angular PO/SL/LI + Angular acq admin coexist cleanly |
| 15:46 |
gmcharlt |
(they're already 97% there, but there are a couple mege conflicts to sort out) |
| 15:47 |
gmcharlt |
so, that's my pitch; back to berick for more on Angular patron interfaces |
| 15:47 |
berick |
that's pretty much it, just wanted to propose we include it in the 3.8 pile-o-angular |
| 15:48 |
berick |
gmcharlt: i can def. poke the acq admin branch as part of our merge management |
| 15:48 |
gmcharlt |
berick++ |
| 15:49 |
JBoyer |
I'm +1 to getting the patron interface in, especially since it can be disabled. There will always be something that's not caught until real users see something, if they can go back and forth for a release that's a big help |
| 15:49 |
alynn26 |
+1 for patron interface |
| 15:50 |
mmorgan |
+1 for the ability to go back and forth between new and old interfaces |
| 15:51 |
sandbergja |
I'm curious about getting us up to Angular 12 |
| 15:51 |
sandbergja |
I wonder if we could get the big angular stuff merged early in the cycle, so y'all don't have to go back and update your branches |
| 15:51 |
sandbergja |
and then upgrade angular later in the cycle? |
| 15:52 |
berick |
sandbergja: that would be my pref |
| 15:52 |
berick |
i could also see the argument for updating to ang 12 directly after 3.8 |
| 15:53 |
berick |
but I haven't looked yet to see what's involved in the update. might be simpler |
| 15:53 |
berick |
er, simple |
| 15:53 |
JBoyer |
I was about to ask if there was anything in A12 that would be especially useful for 3.8 or if it could wait |
| 15:53 |
JBoyer |
(Not that "not falling behind" isn't useful, mind.) |
| 15:54 |
gmcharlt |
berick: I played around with Angular 11 or 12 a while back; impression I got is that it's going to be bigger than normal |
| 15:54 |
berick |
gmcharlt: gotcha |
| 15:54 |
gmcharlt |
e.g., lint will drastrically change |
| 15:54 |
gmcharlt |
but to sandbergja's point, I'm all in favor of getting the bigger Angular bits in sooner rather than later |
| 15:55 |
JBoyer |
+1 |
| 15:55 |
berick |
+1 |
| 15:55 |
sandbergja |
+1 |
| 15:57 |
berick |
quick question re: acq po/li/sl angular UI's |
| 15:57 |
berick |
i want to make them optional without affecting the existing search interfaces |
| 15:57 |
berick |
should I just put links on the top of the (e.g.) PO page pointing to its Ang counterpart? |
| 15:57 |
berick |
not sure how else people will find them |
| 15:57 |
berick |
without search |
| 15:58 |
gmcharlt |
berick: my gut reaction: experimental nav menus for the new interfaces + a library or workstation setting to control whether links from the search interface bounce the user from search rsesults to either the old or new interface |
| 15:59 |
mmorgan |
+1 to experimental nav menus |
| 15:59 |
berick |
gmcharlt: not sure what the nav menus would looke like, though, since search is the only real entry point |
| 16:00 |
berick |
maybe if the setting is on, the search UI will present 2 links -- could get crouded |
| 16:00 |
gmcharlt |
we don't have menu nesting (yet?), but maybe something like |
| 16:00 |
jeff |
checkbox next to search input field that determines if the links open in new/old UI? |
| 16:01 |
jeff |
(checkbox, dropdown/select, what-have-you) |
| 16:01 |
gmcharlt |
Acquistions => Experimental => Create Purchase Order (for anything that would be an entry point other than search) |
| 16:02 |
berick |
ah, right, ok i guess there are some top-level pages |
| 16:02 |
gmcharlt |
and maybe a "Acquisitions Preferences" on acq search similar to catalog preferences for the WS setting about where to link search results to |
| 16:02 |
mmorgan |
berick: There is an Acquisitions interest group tomorrow for potential input |
| 16:03 |
jeff |
links in new/old to view in old/new and a setting to determine default might be good also. |
| 16:03 |
gmcharlt |
and possibly all of that wrapped in a library setting or a global flag to let administraors hide the experimental stuff outright |
| 16:03 |
berick |
jeff: i kind of like the checkbox option since it allows access to both |
| 16:04 |
jeff |
I like the idea of being able to use the new UI without having to make a conscious decision of "new UI or old UI?" each time you perform an operation. |
| 16:04 |
berick |
sticky checkbox, just on the search page |
| 16:04 |
berick |
but being able to access the old UI's is critical, i think |
| 16:05 |
JBoyer |
Agreed |
| 16:05 |
jeff |
yes. otherwise the first time you run into an issue, you'll completely stop using the new UI. :-) |
| 16:05 |
berick |
ok, i'll synthesize some of this and post it in the LP |
| 16:05 |
berick |
thanks for all the input |
| 16:05 |
JBoyer |
berick++ |
| 16:06 |
berick |
mmorgan: if you hear anything of note, let me know! |
| 16:06 |
berick |
not sure I can make tomorrow's acq meeting |
| 16:06 |
JBoyer |
Ok, if there are no other questions or comments we can go about the rest of our days (and start testing Angular branches! ;) ) |
| 16:06 |
gmcharlt |
berick: I'll be demoing the acq admin interfaces there tomorrow, and would be happy to relay any questions you care to feed me |
| 16:07 |
mmorgan |
berick: Will share this with my colleague who will be attending that meeting. |
| 16:07 |
berick |
is it 2pm eastern? |
| 16:07 |
gmcharlt |
3 pm |
| 16:07 |
mmorgan |
Yep, 3 |
| 16:07 |
berick |
ok, will try to come, may be late |
| 16:09 |
JBoyer |
ok |
| 16:09 |
JBoyer |
#topic Announcements |
| 16:09 |
JBoyer |
#info Next Meeting is August 10, 2021 |
| 16:09 |
JBoyer |
Looking forward to getting some good stuff in 3.8! |
| 16:09 |
JBoyer |
#endmeeting |
| 16:09 |
pinesol |
Meeting ended Tue Jul 13 16:09:33 2021 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:09 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-07-13-15.02.html |
| 16:09 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-07-13-15.02.txt |
| 16:09 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-07-13-15.02.log.html |
| 16:09 |
berick |
JBoyer++ |
| 16:09 |
gmcharlt |
JBoyer++ |
| 16:09 |
mmorgan |
JBoyer++ |
| 16:09 |
phasefx |
JBoyer++ |
| 16:10 |
miker |
JBoyer++ |
| 16:13 |
jeff |
JBoyer: did the announcement about Mailman config changes go out to the lists? Can you summarize the change here or point me in the direction of the announcement? I didn't find it and wasn't sure I remembered the proposed change. |
| 16:16 |
JBoyer |
jeff, Notice of it went out, but probably nothing terribly detailed. Looking at my email to csharp_ it amounted to: setting from_is_list to Munge and turning on the REMOVE_DKIM_HEADERS setting. |
| 16:18 |
JBoyer |
Though I think the end result is the same as it was pre-change: Reply goes to the list, Reply All to the list and sender. |
| 16:19 |
JBoyer |
Apparently the Mailman wiki was mistaken about how long ago the dmarc_moderation_action was added, so we couldn't use that. |
| 16:19 |
jeff |
ah, found the email in question. |
| 16:19 |
jeff |
I *thought* I had seen it before. |
| 16:40 |
jeff |
we use some liner-free sticky receipt printers for hold slips. the Epson TM-T88 ReStick in particular, and it's been increasingly difficult to source them. Does anyone in #evergreen have a model that they like that's a bit more obtainable? Looking at alternatives like the Star Micronics TSP-654SK. |
| 16:52 |
|
brettgilio joined #evergreen |
| 16:55 |
|
jvwoolf joined #evergreen |
| 17:18 |
|
mmorgan left #evergreen |
| 17:28 |
|
jvwoolf left #evergreen |
| 18:01 |
pinesol |
News from qatests: Failed Running pgTAP tests <http://testing.evergreen-ils.org/~live//archive/2021-07/2021-07-13_16:00:02/test.42.html> |
| 22:27 |
|
mmorgan1 joined #evergreen |
| 22:27 |
|
mmorgan1 left #evergreen |
