| Time |
Nick |
Message |
| 01:37 |
|
sandbergja joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:16 |
|
rjackson_isl_hom joined #evergreen |
| 07:50 |
|
collum joined #evergreen |
| 08:18 |
|
mantis1 joined #evergreen |
| 08:33 |
|
mmorgan joined #evergreen |
| 08:44 |
|
terranm joined #evergreen |
| 09:08 |
|
Dyrcona joined #evergreen |
| 09:10 |
|
jvwoolf joined #evergreen |
| 09:32 |
|
dbwells joined #evergreen |
| 11:48 |
|
jihpringle joined #evergreen |
| 13:48 |
|
mmorgan1 joined #evergreen |
| 14:21 |
|
khuckins joined #evergreen |
| 14:38 |
|
nfBurton joined #evergreen |
| 14:50 |
nfBurton |
Anyone know how the action trigger reports are named? We changed the length and all the data on the trigger but still have old names for the files |
| 15:05 |
csharp |
nfBurton: do you mean reports sources? not quite grokking |
| 15:13 |
nfBurton |
Yeah. Like my 10_day_overdue.txt.pdf should now be 7 day to correctly reflect. But I'm unsure where it gets it's name from because I changed them days ago and they appear as the same name |
| 15:14 |
csharp |
and that file is generated by the Evergreen reporter? |
| 15:16 |
nfBurton |
by the action_trigger |
| 15:17 |
csharp |
oohhh |
| 15:19 |
jeffdavis |
I don't think that is part of standard Evergreen? The GenerateBatchOverduePDF reactor is commented out in the SQL schema files and wouldn't normally exist. |
| 15:24 |
Dyrcona |
In our overdue print set up, the names of the output are determined by shell scripts that gather up the a/t event data. |
| 15:25 |
JBoyer |
nfBurton, somewhere in the crontab on the machine where those are built there's a script that is collecting event output, probably by id. Depending on when it was last changed it may either be using psql or action_trigger_aggregator.pl |
| 15:27 |
csharp |
that makes sense - I'm not able to find anything in the code itself |
| 15:27 |
csharp |
we're still creating our overdue notices super old school because I've never gone to the trouble to move them to A/T |
| 15:28 |
csharp |
wait, I'm lying - we're doing them in A/T except for what we send to UMS |
| 15:28 |
csharp |
that's the only part we haven't moved to A/T |
| 15:29 |
jeff |
heh |
| 15:34 |
berick |
csharp: not sure if you saw this, but I shared our UMS code on my github (and posted here). it's a mix of A/T and external processing, similar to the old scripts. https://github.com/berick/evergreen-xml-notices |
| 15:35 |
|
mantis1 left #evergreen |
| 16:02 |
|
collum_ joined #evergreen |
| 16:29 |
csharp |
berick: I had a memory of you sharing that (or something like it) before - thanks! |
| 16:29 |
csharp |
berick++ |
| 16:53 |
nfBurton |
It's action_trigger.pl but can't figure out which file builds the names of the output. Or if there's a correlation I am missing |
| 16:56 |
Dyrcona |
nfBurton: Did you mean action_trigger_runner.pl? action_trigger.pl is not a standard Evergreen script name. |
| 16:57 |
nfBurton |
yes. Thats what I meant |
| 16:57 |
Dyrcona |
Ours work like this: We have some custom action trigger event defined with custom granularity. A cron job runs every day to run action_trigger_runner.pl with that granularity. |
| 16:57 |
nfBurton |
That's mine too but the Cron and the Event both dont seem to represent the title of the file |
| 16:57 |
Dyrcona |
At the end of the cron script, there's a process to extract the template data for the events in XML format. This is then processed via shell script though fop to produce PDFs. |
| 16:58 |
Dyrcona |
nfBurton: You have a utility server that runs your cron jobs? I'd check on there. Your process is likely similar to ours. |
| 16:58 |
nfBurton |
Yes. |
| 16:59 |
nfBurton |
But how does the file get it's name? |
| 16:59 |
Dyrcona |
`crontab -l` will list the contents of a user's crontab. |
| 16:59 |
Dyrcona |
It's probably the opensrf user. |
| 17:01 |
nfBurton |
The output file I mean. Like 10_day_overdue.pdf |
| 17:01 |
nfBurton |
This doesn't seem to set it either in the job |
| 17:02 |
|
jvwoolf left #evergreen |
| 17:02 |
Dyrcona |
grep -R 10_day_overdue.pdf ./ |
| 17:02 |
nfBurton |
I know where they go |
| 17:03 |
nfBurton |
But how does it set the name. Because that should now be represented as 7_day_overdue |
| 17:03 |
Dyrcona |
That's a grep, not find. It'll look inside files to see if any mention it. |
| 17:05 |
Dyrcona |
I'm assuming it is hardcoded and that it exists somewhere under ~opensrf. |
| 17:16 |
nfBurton |
Oh yes, I found it. I think... It's odd that the Action Trigger Notification Event doesn't just use the title as it's name |
| 17:24 |
Dyrcona |
A/T can't do the things that are required for generating PDFs, so post processing script is needed. You could probably modify that script to use the event label or whatever, but I haven't seen your scripts. |
| 17:25 |
|
sandbergja joined #evergreen |
| 17:26 |
Dyrcona |
Ours split them up into output files by library, event, and date. |
| 17:28 |
|
mmorgan left #evergreen |
| 17:30 |
|
dbwells joined #evergreen |
| 17:43 |
nfBurton |
That is how mine works too. Thanks |
| 17:43 |
nfBurton |
Dyrcona++ |
| 17:51 |
|
sandbergja joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 19:04 |
|
sandbergja joined #evergreen |
| 22:59 |
|
khuckins joined #evergreen |
| 23:53 |
|
sandbergja joined #evergreen |
