To keep track of the number of users and requests we get each day, there has to be a database where this information is logged. This will be used for regular transparency reports, to monitor our growth and estimate the potential of RoataWăy.
The database will use SQLAlchemy with an SQLite backend (for now), and contain the following information:
Events table
event_id
timestamp
action, one of {add, feedback, prognosis} as a numeric code
chat_id (not sure about this one yet)
Metadata table
event_id (foreign key)
metadata (depending on the action, feedback -> feedback text, prognosis -> route number)
We refrain from storing metadata about users (names and nicknames), because the chat_id is sufficient to uniquely identify a user.
To keep track of the number of users and requests we get each day, there has to be a database where this information is logged. This will be used for regular transparency reports, to monitor our growth and estimate the potential of RoataWăy.
The database will use
SQLAlchemywith an SQLite backend (for now), and contain the following information:Events table
event_idtimestampaction, one of {add,feedback,prognosis} as a numeric codechat_id(not sure about this one yet)Metadata table
event_id(foreign key)metadata(depending on the action, feedback -> feedback text, prognosis -> route number)We refrain from storing metadata about users (names and nicknames), because the
chat_idis sufficient to uniquely identify a user.