There will be a lot of data generated from transactions on pages, with the amount, comment and potentially allocation of the donations as well as dates, including tax relief etc.
We will need an efficient way to pull this data into memory for use when rendering pages and also when showing back office content apps.
The current N3O_Entities table will not be a good fit for this as we don't want a simple key value store. Instead we will need to design some custom tables such as N3O_CrowdFunding_Donations with suitable columns we can index and query against.
We do need to think carefully about which bits of data need to be editable. For example, if there is an inappropriate comment left on a donation, how can backoffice staff correct it or remove it if it is not a node in Umbraco? We may be able to lean on Konstrukt to scaffold some UI for these but need to look at licensing and other implications.
There will be a lot of data generated from transactions on pages, with the amount, comment and potentially allocation of the donations as well as dates, including tax relief etc.
We will need an efficient way to pull this data into memory for use when rendering pages and also when showing back office content apps.
The current
N3O_Entitiestable will not be a good fit for this as we don't want a simple key value store. Instead we will need to design some custom tables such asN3O_CrowdFunding_Donationswith suitable columns we can index and query against.We do need to think carefully about which bits of data need to be editable. For example, if there is an inappropriate comment left on a donation, how can backoffice staff correct it or remove it if it is not a node in Umbraco? We may be able to lean on Konstrukt to scaffold some UI for these but need to look at licensing and other implications.