EBMS Tickets

I checked, and it's only available as a manual task. As far as I can tell, there was never a request for it to be automated.

Thanks, Bob. I think we should discuss making this process automated.

How often would you like it to run, and when?

Scheduled job created to run Sunday mornings at 5 am.

That seems reasonable. Thanks, Bob. How should we test this one?

You could find a journal which you know is new or has changed its title recently, and verify that it's correct in the EBMS on Monday morning. If that's impossible (or tedious) you could let me check the logs to verify that the job ran. Another possibility is that you could compare the journal lists on DEV (where the job was run by the cron scheduler) with those on QA or PROD (but not STAGE, where I have run the refresh from the admin menus).

Bob, could you please create an ad-hoc diff report comparing the journal lists on DEV and QA so we can more easily see the differences? Thank you!

Diff report attached. The lines beginning with "<" represent values from the QA database, for which the refresh has not been run in a while. The lines beginning with ">" come from the DEV database, where the refresh job runs on a scheduled basis.

The refresh seems to have gone well on QA - I've checked several journal names that hadn't been updated at the time of the diff report and they now show the correct and current journal name on QA.

When was the refresh last done on PROD? I haven't been able to find any journals that aren't showing the current names already so this may be harder to test once we get to PROD.

Last run on PROD was January 10.

Verified on QA.

~bkline, are you able to confirm that this job is running on Sundays at 5am? If so, then I think we can close this ticket. Thanks.

Yes, I just checked the logs and confirmed that it's been running each week.

Great, thanks!