| Issue Number | 426 |
|---|---|
| Summary | [Full Citation] Add New Tag to Unreviewed Citations After Two Years |
| Created | 2017-04-13 09:41:15 |
| Issue Type | Improvement |
| Submitted By | Juthe, Robin (NIH/NCI) [E] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-06-05 11:32:22 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.206478 |
We would like to add a new tag - "Not Reviewed" - to citations that have been sitting in a packet for review and have not received any responses or received any further action (Board manager action, On Agenda, Editorial Board Decision) for more than two years.
This would allow us the ability to search for these citations and determine how many are falling into this category (unreviewed and probably won't get reviewed).
We would like to have this tag added automatically. Perhaps we could have a scheduled sweep of the database performed on the first day of each month to add this tag to applicable citations? Please note that the tag will need to be added at the topic level, NOT the citation level.
This automated job should only touch citations that have been in EBMS packets - NOT legacy packets from the old system.
Implemented on DEV. Only some (a little under 300) of the old unreviewed articles have been marked with the new tag, because right now I've got a throttle in the script so that I have plenty of data for testing the cron job, which is running nightly right now. In a few days I'll remove the throttle and flip the job over to running on the first of the month.
All of the tags have been added on DEV (2,080 of them) and the job is scheduled to run at 3 am on the first of each month.
I've spot-checked several citations on DEV and the tag has been added appropriately. We'll continue testing on QA.
Has this cron job been run on QA? If not, would it be possible to run it? I don't think we want to wait until the first of the month to test it. Thanks.
I have tweaked the crontab entry to have it run tomorrow morning at 3 a.m. instead of on the 1st. I'll try to remember to switch it back some time tomorrow after you've reviewed the results.
Verified on QA.
Has the scheduled job been reset to run at 3am on the 1st of the month?
Yes, I modified that this morning.
Verified on PROD.
Elapsed: 0:00:00.000718