| Time |
Nick |
Message |
| 08:39 |
|
mmorgan joined #evergreen |
| 09:04 |
|
sandbergja joined #evergreen |
| 10:43 |
|
Dyrcona joined #evergreen |
| 11:05 |
|
sandbergja joined #evergreen |
| 11:07 |
sandbergja |
Regarding translation infrastructure, it looks like archivesspace is another open source library project that uses weblate: https://github.com/archivess​pace/archivesspace/pull/3798 |
| 11:14 |
csharp_ |
sandbergja++ |
| 11:29 |
goood |
csharp_: re your Business::ISBN::Data woes, does updating that package currently fix the issues you've been running across? (fwiw, I think updating the package weekly via cron makes sense, based on the changelog for the module itself: https://metacpan.org/dist/B​usiness-ISBN-Data/changes) |
| 11:30 |
|
jihpringle joined #evergreen |
| 11:32 |
goood |
(though, of course, that would necessitate a service restart if the package actually did change and those changes were relevant) |
| 12:04 |
|
Christineb joined #evergreen |
| 12:08 |
|
jvwoolf joined #evergreen |
| 12:10 |
csharp_ |
goood: installing from CPAN instead of the Debian/Ubuntu version did fix the problem for us - I agree that a cron would make sense - maybe the cron could run a service restart too? *shrug* |
| 12:14 |
goood |
I wouldn't want to restart services at (effectively) random -- A/T processing etc would be interrupted -- but having the cron job check that the version actually changed, and email someone if that happened, should be straight forward in a shell script, say. even just writing to stdout is enough to get email to go out unless cron is configured to not email (note: set your MAILTO! ;) ) |
| 12:23 |
csharp_ |
yeah, we run A/T on its own (non-OPAC-hosting) server, so it wouldn't have the cron |
| 12:23 |
csharp_ |
this is almost a non-EG/purely sys-admin issue - might just need docs/examples IMHO |
| 12:31 |
|
jihpringle joined #evergreen |
| 12:55 |
|
sandbergja joined #evergreen |
| 13:09 |
|
jvwoolf joined #evergreen |
| 13:28 |
|
jihpringle joined #evergreen |
| 14:16 |
jeff |
I may have asked this before, and forgotten the answer: what is the benefit of "validating" the ISBN here, especially in such detail as to require consistently updated ISBN data files? |
| 14:16 |
|
Dyrcona joined #evergreen |
| 14:18 |
jeff |
looks like I missed that bug 2055690 was going to be the focus of collab code review this week. :-\ |
| 14:18 |
pinesol |
Launchpad bug 2055690 in Evergreen 3.16 "Circ events should not update edit info on copies" [Low,Confirmed] https://launchpad.net/bugs/2055690 |
| 14:20 |
jeff |
if people feel so strongly about changing that behavior, we might need to add support for tracking what is lost, since I'm pretty sure our users are going to miss it. |
| 15:00 |
Dyrcona |
jeff: That was added by me at the last minutes. |
| 15:00 |
|
jihpringle joined #evergreen |
| 15:56 |
csharp_ |
jeff: I had the same question as I was troubleshooting that issue - I landed on "it probably doesn't matter but since we can log it, just log it" |
| 16:06 |
|
jvwoolf joined #evergreen |
| 17:14 |
|
mmorgan left #evergreen |
| 17:21 |
|
jvwoolf joined #evergreen |
| 17:34 |
|
jvwoolf joined #evergreen |
| 18:30 |
|
jvwoolf joined #evergreen |
| 19:10 |
|
sandbergja joined #evergreen |
