rubyforgood
Investigate whether we can do a backdated snapshot before which we won't allow edits
Summary
This is about checking the behaviour of the users in prod to see what's reasonable.
Things to consider
No response
Criteria for Completion
- [ ] Check it out
- [ ] Report back to the planning team
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I only found 19 things that were edited more than 3 months apart (first number is organization ID, second is eventable ID, last is diff in days)
154: 4692 Purchase,185
64: 74300 Distribution,97
12: 74501 Distribution,145
119: 23352 Donation,98
119: 69176 Distribution,104
119: 76379 Distribution,104
: 4989 Purchase,110
205: 78188 Distribution,92
111: 77932 Distribution,118
247: 23633 Donation,154
247: 76020 Distribution,132
114: 76213 Distribution,147
114: 76219 Distribution,147
114: 76602 Distribution,140
114: 77170 Distribution,130
114: 78480 Distribution,100
114: 78482 Distribution,100
114: 78483 Distribution,100
114: 78695 Distribution,98
: 71452 Distribution,107
212: 4971 Purchase,118
2 of them don't have org IDs because they must have been deleted.
And that would be since whenever we put the events to everybody. Hmm. Let's talk Sunday, and we'll probably want to talk to the stakeholders.
I am wondering if all those ones from 114 for were all the same day or so for the update and plausibly part of some roughly quarterly process.
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.
Nope, this is still with me. I think I have to verify that 6 months should be ok (3 isn't)
There are definitely changes to purchases and distributions more than 6 months out, but not to the inventory levels. Will take this to the Sunday meeting for final discussion of next steps.
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.
The investigation was completed -- we found that 6 months seemed a reasonable point to make a cutoff -- so we will be putting in some restrictions on edits, then instituting a periodic snap-shot 6 months back.