You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description, and links to relevant helpdesk tickets:
DataCite doesn't store our reports and we can't query them, so we want to go ahead and pretend they don't exist and just put our stats into our totals in the database.
Describe the solution you'd like:
Process stats every weekend
We may need to process part of 1 or 2 months, depending on whether the previous week straddles the month's break.
Don't submit to DataCite since it doesn't work.
Save the updated output report JSON files to a known place along with all the other past json report files we've made previously.
Repopulate the database totals from our reports
Since we don't really know the time from that previous totals in the database represent and impossible to match up with reports that keep getting changed, then just remove all totals every week and re-process all of them into the totals.
The rake task for this is called counter:cop_manual, takes the rails environment and json file directory. It will then read through these files and populate stats into the database.
I want to test this out before we do it on production, so I think I need to get the whole python environment set up on stage. Stage is load balanced so it has logs on 2 servers like production (unlike dev). So stage is the best place to test the script.
**Additional context: **
The text was updated successfully, but these errors were encountered:
Problem description, and links to relevant helpdesk tickets:
DataCite doesn't store our reports and we can't query them, so we want to go ahead and pretend they don't exist and just put our stats into our totals in the database.
Describe the solution you'd like:
counter:cop_manual
, takes the rails environment and json file directory. It will then read through these files and populate stats into the database.I want to test this out before we do it on production, so I think I need to get the whole python environment set up on stage. Stage is load balanced so it has logs on 2 servers like production (unlike dev). So stage is the best place to test the script.
**Additional context: **
The text was updated successfully, but these errors were encountered: