Stats are *very* helpful

[bjendres]

I recently added stats to the Twingle profiles:

• usage count: how often was this profile used?
• last used: when was the profile used the last time?
• first used: when was the profile used for the first time?

This makes profile life cycle management (i.e. "can I delete this?") a lot easier, as well as for debugging or just general book keeping.

Potentially we would have to exclude these columns from extended logging, so we don't bloat the DB.

[jensschuppe]

Donation Receipts is doing that by dynamically calculating usages based on other things, i. e. not relying on explicitly stored usage counts. @bjendres would you advocate for providing usage statistics fields in the entity schema (allowing them being empty) or do you think a "pseudo" property inside the JSON data property would be sufficient for implementing extensions?

[bjendres]

@bjendres would you advocate for providing usage statistics fields in the entity schema

Yes. But I would still leave it up to the "user" extension to use these fields or not. Or even go for a different approach, like the DonationReceips.