search

codeforamerica / denver-schedules-api

An api for city events & schedules.
MIT License
7 stars 5 forks source link

Consider saving notification data #15

Open gregoryjscott opened 10 years ago

gregoryjscott commented 10 years ago

I think it might be worth it to save data for the notifications that are sent (when reminders are "triggered").

I believe the current plan is to depend on logging for this, but I could make the case that this is important enough that it should be treated like real data and persisted indefinitely. I can envision wanting to query to see how many times users are notified, how often a particular user's notifications fail, etc. I'll bet that there will be some troubleshooting in this area - might as well make it as easy as possible and be sure to have the data you need. Typically logging data is truncated occasionally, not sure that's good enough for this.

I have a Notifications table in mind and a new record would be created for each reminder type and user notified.

boonrs commented 10 years ago

I like the idea of having this data to examine in detail. We can add a dependency to engine light when the table grows to a certain size to re-evaluate saving all the data.