| Time |
Nick |
Message |
| 07:27 |
|
BDorsey joined #evergreen |
| 07:46 |
|
collum joined #evergreen |
| 08:08 |
|
rfrasur joined #evergreen |
| 08:21 |
|
kworstell-isl joined #evergreen |
| 08:41 |
|
mmorgan joined #evergreen |
| 08:50 |
|
jvwoolf joined #evergreen |
| 09:01 |
|
dguarrac joined #evergreen |
| 09:03 |
|
Dyrcona joined #evergreen |
| 09:57 |
|
sleary joined #evergreen |
| 10:56 |
Dyrcona |
You know, it's kind of difficult to come up with a grep to find all of the WITH queries, particularly some of those that get built via Perl. |
| 11:05 |
|
kworstell-isl joined #evergreen |
| 11:16 |
|
kworstell_isl joined #evergreen |
| 12:00 |
|
sleary joined #evergreen |
| 12:02 |
|
Christineb joined #evergreen |
| 12:12 |
Stompro |
For an upgrade to 3.10, should I be sticking with the Ruby EDI... or try to move to the new EDI generation code? Bug 1901900 |
| 12:12 |
pinesol |
Launchpad bug 1901900 in Evergreen 3.6 "EDI Webrick Installer Needs Update for Ubuntu 18.04" [Medium,Fix released] https://launchpad.net/bugs/1901900 |
| 12:19 |
Stompro |
The "Setting Up EDI Acquisitions" second of the manual is for the Ruby translator. I'm trying to find a setup or install guide for the new method. |
| 12:25 |
Stompro |
Wrong bug, bug 1373690 |
| 12:25 |
pinesol |
Launchpad bug 1373690 in Evergreen "Direct EDI generation for ACQ orders -- AKA kill ruby webrick" [Wishlist,Fix released] https://launchpad.net/bugs/1373690 |
| 12:26 |
Dyrcona |
I would make the move to the new method if time permits. You can do it piecemeal, moving a few libraries at a time. |
| 12:27 |
Stompro |
Dyrcona, we are centralized, we only have one system doing EDI ordering, so only one to move. |
| 12:30 |
Dyrcona |
That makes it easy. We have a dozen or members doing EDI. |
| 12:30 |
Dyrcona |
...or more... |
| 12:35 |
Dyrcona |
Stompro: Have a look at this https://docs.evergreen-ils.org/eg/docs/latest/admin/acquisitions_admin.html#acq_edi |
| 12:36 |
|
jihpringle joined #evergreen |
| 12:38 |
Dyrcona |
I think we switched to the new EDI in 2019 when we upgraded to 3.2. |
| 12:38 |
Dyrcona |
Someone else did the attribute configuration. |
| 12:39 |
|
kworstell_isl_ joined #evergreen |
| 12:48 |
|
Christineb_ joined #evergreen |
| 12:52 |
|
ejk_ joined #evergreen |
| 12:57 |
Stompro |
Ah, I found the release notes entry for it, in the 3_0 release notes. So instead of edi_pusher.pl, edi_order_pusher.pl is used... Now what about for fetching... |
| 12:58 |
Dyrcona |
Fetching is edi_fetcher.pl. |
| 13:00 |
Stompro |
Ah, and edi_fetcher.pl doesn't use the ruby translator, so nothing changes there. |
| 13:07 |
Dyrcona |
No more need for openils-mapper, either. |
| 13:14 |
Stompro |
I have no idea what that is... not having luck finding it either. |
| 13:14 |
Stompro |
Could you give me a clue of what to search for? |
| 13:14 |
Dyrcona |
https://github.com/berick/openils-mapper |
| 13:15 |
Stompro |
Thanks |
| 13:17 |
Dyrcona |
I believe it may have been optional |
| 13:20 |
Dyrcona |
Ah, no, not optional. It's part of the old install script for the edit_translator. |
| 13:35 |
Stompro |
Thanks, I see it now in the install file. |
| 13:47 |
|
mantis1 joined #evergreen |
| 13:48 |
mantis1 |
Question on contributing translations. Do you need to download a po file, make the translations there, then upload it? |
| 13:48 |
mantis1 |
Wasn't sure on the procedure. |
| 13:48 |
mantis1 |
https://translations.launchpad.net/evergreen/master/+pots/tpac/es |
| 14:13 |
|
kworstell-isl joined #evergreen |
| 14:39 |
|
sleary joined #evergreen |
| 14:41 |
|
JBoyer_direct joined #evergreen |
| 14:41 |
|
shulabear joined #evergreen |
| 14:50 |
JBoyer_direct |
So, I'm connecting directly rather than through my bouncer; but verily, this is me. |
| 14:50 |
JBoyer_direct |
and there's a meeting in 10 mins. |
| 14:51 |
JBoyer_direct |
It would be *superb* if someone else had time to run it, but because I did not think to ask until now, I'll be available. |
| 14:57 |
Dyrcona |
I can run the meeting if no one else volunteers. |
| 14:58 |
mmorgan |
Dyrcona++ |
| 14:58 |
rhamby |
Dyrcona++ |
| 14:58 |
JBoyer_direct |
Dyrcona, you are a gentleman and a scholar, etc. |
| 14:59 |
JBoyer_direct |
Dyrcona++ |
| 14:59 |
Dyrcona |
JBoyer_direct: Do you just copy and paste the bug info? |
| 14:59 |
shulabear |
Dyrcona++ |
| 14:59 |
|
sleary joined #evergreen |
| 14:59 |
JBoyer_direct |
yeah, I usually put together a google doc to c/p from and then toss at the end of the meeting, but it's not much more than hte agenda with the start / end meeting commands. |
| 15:00 |
JBoyer_direct |
(I just use a doc so it's easier to c/p with the keyboard, really) |
| 15:00 |
Dyrcona |
Ok, you use #info for that? |
| 15:01 |
* Dyrcona |
should pay more attention during meetings. :) |
| 15:01 |
Dyrcona |
Speaking of.... |
| 15:01 |
Dyrcona |
#starmeeting 2022-12-13 Developers' Meeting |
| 15:01 |
Dyrcona |
#topic Introductions |
| 15:01 |
Dyrcona |
oops. let's try that again. |
| 15:02 |
mmorgan |
typos-- |
| 15:02 |
Dyrcona |
#startmeeting 2022-12-13 Developer Meeting |
| 15:02 |
pinesol |
Meeting started Tue Dec 13 15:02:08 2022 US/Eastern. The chair is Dyrcona. 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 '2022_12_13_developer_meeting' |
| 15:02 |
Dyrcona |
#topic Introductions |
| 15:02 |
phasefx |
#info phasefx = Jason Etheridge, EOLI |
| 15:02 |
rhamby |
#info rhamby = Rogan Hamby, EOLI |
| 15:02 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:02 |
Dyrcona |
#info Dyrcona = Jason Stephenson CW MARS |
| 15:03 |
sleary |
#info sleary = Stephanie Leary, EOLI |
| 15:03 |
shulabear |
#info shulabear = Shula Link, GCHRL in PINES |
| 15:03 |
collum |
#info collum = Garry Collum, KCPL |
| 15:03 |
|
smorrison joined #evergreen |
| 15:03 |
Stompro |
#info stompro = Josh Stompro, LARL |
| 15:04 |
|
smorrison joined #evergreen |
| 15:04 |
Dyrcona |
So, feel free to continue introducing yourselves as the meeting progresses. |
| 15:04 |
Dyrcona |
#topic Action Items from Last Meeting |
| 15:04 |
Dyrcona |
#info jeffdavis will gather more specific examples of recurring QA problems to present for discussion at the next dev meeting |
| 15:05 |
Dyrcona |
Is jeffdavis around? |
| 15:06 |
Dyrcona |
Ok, not hearing anything from jeffdavis, we'll punt that item to the next meeting in January. |
| 15:06 |
Dyrcona |
#action jeffdavis will gather more specific examples of recurring QA problems to present for discussion at the next dev meeting |
| 15:07 |
Dyrcona |
#topic OpenSRF Release Updates |
| 15:07 |
Dyrcona |
#info gmcharlt isn't able to be here today but said that the OpenSRF release is still on and should drop next week |
| 15:08 |
Dyrcona |
Does anyone have anything to add about next week's OpenSRF release? |
| 15:09 |
Dyrcona |
#topic Evergreen Release Updates |
| 15:09 |
Dyrcona |
#info Contribution of LibraryIQ export code. Github? Contrib repo? It will be similar to collectionHQ, which is inside of a contrib repo. (Bmagic) |
| 15:09 |
Bmagic |
oh hey, that's me |
| 15:09 |
Dyrcona |
Bmagic: I assume you're looking for suggestions on how to share the code with the community? |
| 15:10 |
Bmagic |
Right. It seems we all have little side projects here and there. This one seems like it could be useful for anyone subscribing to LibraryIQ's service |
| 15:11 |
Dyrcona |
How generic is the export? Would it require a lot of customization to make it work for different sites? |
| 15:11 |
Bmagic |
We've utilized similar code (collectionHQ) from the community. This is the same thing, different channel |
| 15:12 |
rhamby |
I'd say it should probably be in a contrib repo though we should have a wiki page tracking these things if we don't already |
| 15:12 |
Bmagic |
I'm writing it with the community in mind. The end result should be: edit a config, setup cron, eat a sandwich |
| 15:14 |
|
Stompro joined #evergreen |
| 15:14 |
Dyrcona |
OK. A crontrib repo requires some intervention on the part of the gitadmins, which means gmcharlt or myself. Wold a working branch aslo work? |
| 15:15 |
Bmagic |
a working branch could work, but that would be against the Evergreen repo? I'm not sure it belongs in Evergreen proper |
| 15:15 |
Dyrcona |
I guess long term, it might be useful to add things like this to the main Evergreen repo, perhaps in a contrib directory or possibly right in support-scripts. |
| 15:15 |
Bmagic |
I've got a branch for another project that made a sub-folder in support-scripts |
| 15:16 |
Bmagic |
I could keep doing it like that. Everyone here think that Evergreen exports to vendors might be useful enough to just be in Evergreen? |
| 15:16 |
Dyrcona |
Well, if you think it warrants a separate repo, we could set up a crontrib repor or it could go on github. I was also thinking of exposure/advertising for these kinds of tools by adding them into a contrib/ hierarchy. |
| 15:17 |
Bmagic |
It's certainly not "big" enough to be a whole repo... maybe a repo for "all things export" ? |
| 15:17 |
Dyrcona |
I think they could be. As it is, the exports that exist can be hard to locate, and there are different versions of each. |
| 15:18 |
Bmagic |
That's why I thought it might be a good topic for today |
| 15:18 |
Dyrcona |
Well, there's the random repo which functions as a kind of contrib repo already. |
| 15:19 |
Dyrcona |
I don't think it is named very well, and as one of the gitadmins I would (selfishly) like to avoid a proliferation of repositories. |
| 15:20 |
Bmagic |
I want to do the right thing. If it's random repo, that's fine. A wiki page with links to all the places to find things like this would be awesome too. So random repo? |
| 15:21 |
Dyrcona |
Well, I'm not sure what the right thing is, really. I think it would be useful if we could come up with a place to pool a lot of the various tools. |
| 15:21 |
jeffdavis |
Bundling these kinds of tools in some way makes sense to me, but I don't have any specific ideas on the best way to do it |
| 15:22 |
Dyrcona |
Maybe we should move this discussion to the development mailing list since there are not many people here today? |
| 15:22 |
Bmagic |
yeah, I was about to say the same |
| 15:22 |
Bmagic |
I'll put out an email |
| 15:22 |
Dyrcona |
OK. I was going to volunteer but Bmagic++ beat me to it. |
| 15:23 |
Bmagic |
Thanks for your time, we can move on |
| 15:23 |
Dyrcona |
#action Bmagic to email the development list about a way to share common Evergreen tools with the community. |
| 15:23 |
Dyrcona |
Bmagic, you're also up next. |
| 15:23 |
Dyrcona |
#info Enhanced Concerto dataset. LP 1901932 (Bmagic) |
| 15:23 |
pinesol |
Launchpad bug 1901932 in Evergreen "Wish List - Enhanced Concerto dataset" [Wishlist,New] https://launchpad.net/bugs/1901932 |
| 15:23 |
Bmagic |
And, I'm back |
| 15:24 |
Bmagic |
I just wanted to bring this up to let everyone know that the enhanced concerto dataset is in a working branch |
| 15:24 |
Dyrcona |
Is it ready to go and should anyone in particular look at it? |
| 15:25 |
Bmagic |
It "works for me" using the standard perl Open-ILS/src/support-scripts/eg_db_config ..... --load-concerto-enhanced |
| 15:26 |
Bmagic |
Though, I'm not ready to pullrequest it yet. I'm going to loop back to it and enhance the code such that it can upgrade itself to match the database structure through upgrades |
| 15:26 |
mmorgan |
Any reason not to tag it with a pullrequest? |
| 15:26 |
mmorgan |
:) |
| 15:27 |
Dyrcona |
I think you could add the pullrequest tag. Upgrading could be a different bug. You could also wait and attempt it all at once. |
| 15:27 |
Dyrcona |
How useful do we think upgrading concerto data is? |
| 15:27 |
Bmagic |
It would be interesting to hear back on my approach. Essentially, it generates the SQL files based upon a live DB. It needs a "schema only" database and another DB containing the enhanced dataset. The code gathers up each table and removes the "stock" stuff that appears in the 950-seed-data |
| 15:28 |
Bmagic |
the result is a perfect dataset that will load itself onto a database that matches where it came from. If Evergreen receives new columns/tables over time, this dataset could still work but it could also break |
| 15:29 |
Bmagic |
So, the next step in my plan is to automate that upgrade with one command. Sort of a "from" .. "to" git commit check, which could be dropped into the make build procedure for releases |
| 15:29 |
Dyrcona |
Hmm. I thought this would just be extra data, or are you talking about upgrades in that previous comment? |
| 15:30 |
Bmagic |
it's extra data for sure. So much extra that the ID's need to come over to make it all coherent |
| 15:31 |
Dyrcona |
I'll have a look at it in my practically non-existent free time. |
| 15:31 |
Dyrcona |
#action Dyrcona to review Lp 1901932 |
| 15:31 |
pinesol |
Launchpad bug 1901932 in Evergreen "Wish List - Enhanced Concerto dataset" [Wishlist,New] https://launchpad.net/bugs/1901932 |
| 15:31 |
Bmagic |
haha, well, that's more detail than I wanted to get into for this meeting. The take away is: try it out and see what you think |
| 15:32 |
Dyrcona |
Ok, before we move on, jeffdavis we tabled your QA action item earlier. Do you want to pick it up now or wait for next meeting? |
| 15:33 |
jeffdavis |
I don't have anything to add, so yes, let's table it please. (Sorry for missing thestart of the meeting) |
| 15:34 |
Dyrcona |
OK. |
| 15:35 |
Dyrcona |
#topic Documentation Updates |
| 15:35 |
Dyrcona |
#info Where's our technical documentation? For a newbie: how to use $e (editor), what is $ctx, etc.I know there's docs/TechRef but I don't know if it is included in the online antora docs or if it's been updated any time recently. |
| 15:35 |
Dyrcona |
I'm not sure who added this one. I haven't looked at the agenda edit history, but it's a big one, too. |
| 15:36 |
scottangel |
This one is mine. I'm new. |
| 15:37 |
jeffdavis |
There's some additional technical documentation on the wiki (https://wiki.evergreen-ils.org) but it's very incomplete and dispersed. |
| 15:38 |
jeffdavis |
It might make a good hackfest project to assemble some better technical documentation for onboarding new devs? |
| 15:38 |
Dyrcona |
Yes, I was going to repeat what jeffdavis said. I also have some lintks to some older things that got me started as well. |
| 15:38 |
jeffdavis |
Similar to the "Evergreen in Action" doc that was assembled a while ago (and which also ought to be resurrected) |
| 15:39 |
scottangel |
I can use all the help I can get. |
| 15:39 |
Dyrcona |
I was just thinking that we could start a development documentation project, possibly in the mainline docs. |
| 15:40 |
Bmagic |
This one looks "full" https://docs.evergreen-ils.org/eg/docs/latest/development/intro_opensrf.html |
| 15:40 |
Dyrcona |
I think we should save specific resources for after the meeting, but it seems to me there's an action item lurking here. |
| 15:41 |
|
rfrasur joined #evergreen |
| 15:41 |
Bmagic |
This is similar to the "where's the code for that" discussion above. There's a need for a jumping-off page for folks to use |
| 15:42 |
Dyrcona |
Something like that, yes. I think a development section of the documentation would be useful. |
| 15:42 |
Dyrcona |
There used to be one, but it was rather sparse. I haven't checked if it is still there. |
| 15:43 |
shulabear |
That might be something for terranm and the new developer group to work on, if that's still a thing? |
| 15:43 |
mmorgan |
seems like a lot of good documentation is in people's brains. :) |
| 15:44 |
Bmagic |
mmorgan: lol |
| 15:44 |
Dyrcona |
shulabear: That is a good idea. Do you know how to get that onto their agenda? |
| 15:45 |
shulabear |
I do not! But I could shoot Terran an email about it. |
| 15:45 |
Dyrcona |
Awesome sauce. I won't assign you an action item unless you really want one. :) |
| 15:46 |
mmorgan |
New Devs wiki page: https://wiki.evergreen-ils.org/doku.php?id=newdevs:start |
| 15:46 |
shulabear |
Assign me nothing, not this close to the holidays. I think there might already be something Terran made that can act as a starting point. |
| 15:46 |
shulabear |
Like that. mmorgan++ |
| 15:47 |
Dyrcona |
shulabear++ mmorgan++ |
| 15:47 |
Dyrcona |
#info New Devs wiki page: https://wiki.evergreen-ils.org/doku.php?id=newdevs:start |
| 15:47 |
mmorgan |
terranm is masterful at organizing the group and often asks for input on topics. Emailing her is a good start. |
| 15:48 |
Dyrcona |
scottangel: I'll share a link or two after the meeting, but we'll see how things work out with the new devs group. |
| 15:49 |
Dyrcona |
Moving on.... |
| 15:50 |
shulabear |
Terran emailed. |
| 15:50 |
Dyrcona |
#topic Launchpad Status |
| 15:50 |
Dyrcona |
#info Snapshot |
| 15:50 |
Dyrcona |
#info Open Bugs - 2847 |
| 15:50 |
Dyrcona |
#info Pullrequests - 91 |
| 15:50 |
Dyrcona |
#info Signedoff - 38 |
| 15:50 |
Dyrcona |
#info Updates Since Last Meeting |
| 15:50 |
Dyrcona |
#info Bugs Added - 53 |
| 15:50 |
Dyrcona |
#info Pullrequest tag Added - 25 |
| 15:50 |
Dyrcona |
#info Signedoff tag Added - 4 |
| 15:50 |
Dyrcona |
#info Fix Committed - 8 |
| 15:50 |
Dyrcona |
Not much to add to the raw numbers there. |
| 15:51 |
Dyrcona |
#topic New Busines |
| 15:51 |
Dyrcona |
#info Recommended PostgreSQL version now that Pg 10 is out of support. |
| 15:52 |
Dyrcona |
This one is me, and I'm not sure that the most interested parties are here to discuss it. |
| 15:52 |
Bmagic |
fork PG into Evergreen |
| 15:52 |
Dyrcona |
No. :) |
| 15:52 |
Bmagic |
:) |
| 15:53 |
jeffdavis |
I need to sign off, but any reason not to go with PG11 until that bug with 12+ is resolved? |
| 15:53 |
Dyrcona |
I want to give a shout out to csharp_ and miker for working on some search performance issues with PG 12+ |
| 15:53 |
Dyrcona |
jeffdavis: Pg 11 looks safe. |
| 15:54 |
Bmagic |
done, PG 11 :) |
| 15:54 |
Dyrcona |
#info Open bugs related to newer PostgreSQL versions: Lp 1999274 and Lp 1997098. |
| 15:54 |
pinesol |
Launchpad bug 1999274 in Evergreen 3.10 "Performance of Search on PostgreSQL Versions 12+" [Medium,Confirmed] https://launchpad.net/bugs/1999274 |
| 15:54 |
pinesol |
Launchpad bug 1997098 in Evergreen "Add Support for PostgreSQL 15" [Medium,Confirmed] https://launchpad.net/bugs/1997098 |
| 15:55 |
Dyrcona |
I'd much rather be able to recommend Pg 15, but anyway.... :) |
| 15:55 |
Dyrcona |
Let's move on. |
| 15:55 |
Dyrcona |
#topic Announcements |
| 15:56 |
Dyrcona |
Does anyone have anything that they would like to announce? |
| 15:56 |
Bmagic |
Happy new year? |
| 15:57 |
mmorgan |
s/?/!! |
| 15:58 |
Dyrcona |
Given recent occurrences, I think the question mark is warranted. :P |
| 15:58 |
Bmagic |
mmorgan++ # loving the enthusiasm |
| 15:58 |
* mmorgan |
is hopeful. |
| 15:59 |
Bmagic |
the question mark was more slanted towards the context of "anything you want to announce" - wasn't sure if it's an announcement |
| 15:59 |
Dyrcona |
:) |
| 15:59 |
Dyrcona |
OK. I guess we can adjourn. |
| 15:59 |
Dyrcona |
#info Next Meeting is January 10th, 2023 |
| 15:59 |
Dyrcona |
#endmeeting |
| 15:59 |
pinesol |
Meeting ended Tue Dec 13 15:59:37 2022 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:59 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-12-13-15.02.html |
| 15:59 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-12-13-15.02.txt |
| 15:59 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-12-13-15.02.log.html |
| 15:59 |
collum |
Dyrcona++ |
| 16:00 |
shulabear |
Dyrcona++ |
| 16:00 |
|
jvwoolf left #evergreen |
| 16:00 |
Bmagic |
Dyrcona++ # great meeting |
| 16:00 |
Dyrcona |
Dyrcona++ # I don't usually give myself karma, but I think I did all right considering it has been a couple of years since I last ran a meeting. |
| 16:00 |
phasefx |
Dyrcona++ |
| 16:01 |
mmorgan |
Dyrcona++ |
| 16:01 |
Dyrcona |
scottangel: If you're interested in look at the Evergreen backend, you might want to have a look at this: https://htmlpreview.github.io/?https://github.com/Dyrcona/evergreen2019-preconference/blob/master/presentation.html |
| 16:02 |
scottangel |
ty! |
| 16:03 |
Bmagic |
dr_strangelove++ |
| 16:04 |
Bmagic |
peter_sellers++ |
| 16:04 |
Bmagic |
"Madrake! Get over here and feed me this belt" |
| 16:04 |
Bmagic |
Mandrake even |
| 16:07 |
Dyrcona |
Heh, |
| 16:07 |
Dyrcona |
"You're going to have to answer to the Coca-Cola company." |
| 16:08 |
shulabear |
"We cannot allow a mineshaft gap!" |
| 16:08 |
Bmagic |
lol |
| 16:10 |
Dyrcona |
:) |
| 16:11 |
mmorgan |
scottangel: I did a preconference presentation last year about finding your way around the Evergreen project. In case it's useful, slides are here: https://drive.google.com/file/d/1r_eJkPJo1b9tKOBmcJhvvLMRVifb9_I3/view?usp=sharing |
| 16:12 |
scottangel |
YES! Thank you, I'm trying to consume as much info as I can. Trust me, I'll have a million questions for you guys in time. |
| 16:13 |
mmorgan |
Lots of good info and links to presentations on the Conference pages: https://evergreen-ils.org/conference/ |
| 16:27 |
JBoyer_direct |
Dyrcona++ |
| 16:31 |
Dyrcona |
jeffdavis++ I like the idea of using prefixes in git commit messages for customization code. |
| 16:32 |
Dyrcona |
JBoyer++ for sharing his meeting "cheat sheet" with me. |
| 17:03 |
|
mmorgan left #evergreen |
| 19:28 |
csharp_ |
@dunno add You're going to have to answer to the Coca-Cola company. |
| 19:28 |
pinesol |
csharp_: The operation succeeded. Dunno #76 added. |
| 19:43 |
|
JBoyer_ joined #evergreen |
| 19:46 |
pinesol |
News from commits: LP1999446 Localize "Record Summary" card heading <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=82fcd07434d0bd30ec740d4217456c8db7bfeef4> |
