So im thinking of a webshop scenario, based on Umbraco and TeaCommerce, but first question is, on the live server, could I schedule a run so it would clean up data every x days.
Can i then make uMunge hook into custom data, or is there some events i could this to. It dosnt matter that is TeaCommerce, its just if it is possible to handle custom data.
Thanks for your message. We have built uMunge with the ability to extend in mind, for example the next feature we want to implement is munging the data stored in Umbraco Forms, and applying this to TeaCommerce would be a similar pattern. We were waiting to see where the demand is.
Regarding scheduling, what scenario do you have in mind? I don't understand about cleaning up data on the live server?
uMunge is designed to work on a development copy of data, not on a live server. The theory is your live server is secured, but any uncontrolled copies of data should be made safe to prevent privacy leaks.
We have considered a system which could be called from a API or command line to execute the data munging on a schedule. This would need to be part of a bigger DevOps process that moves database backups from live to a different environment for processing before distribution to developers. Internally, we do this at the SQL level on non-Umbraco projects so we know it's a useful process.
It is also interesting to think how this could work with Umbraco Cloud - but that's a different story!
I was thinking in more GDPR terms, to be GDPR compliant, your company should be able to handle requests like, a customer calls and wants all their personal data removed from your site, and in my case its a webshop.
So I wanted to use, or thought I could, uMunge here, to replace the users data with dummy data, so that I still have alle the orders and such, but just replaced the personal data(shipping/payment info etc.)
Yes, that's a whole other thing. But a very interesting use case. One idea we had was filters to preserve some sets of data (based on content folder location) but this would be the opposite - selectively zapping some nodes.
I think this may be better done as a custom action on specific items of content / user / forms information - "Munge this data" as an alternative to deletion.
It's not in our plan, but if there is demand we'll build it!
Can this be used for for external data
Hey there :)
So im thinking of a webshop scenario, based on Umbraco and TeaCommerce, but first question is, on the live server, could I schedule a run so it would clean up data every x days.
Can i then make uMunge hook into custom data, or is there some events i could this to. It dosnt matter that is TeaCommerce, its just if it is possible to handle custom data.
Hi Ramus!
Thanks for your message. We have built uMunge with the ability to extend in mind, for example the next feature we want to implement is munging the data stored in Umbraco Forms, and applying this to TeaCommerce would be a similar pattern. We were waiting to see where the demand is.
Regarding scheduling, what scenario do you have in mind? I don't understand about cleaning up data on the live server?
uMunge is designed to work on a development copy of data, not on a live server. The theory is your live server is secured, but any uncontrolled copies of data should be made safe to prevent privacy leaks.
We have considered a system which could be called from a API or command line to execute the data munging on a schedule. This would need to be part of a bigger DevOps process that moves database backups from live to a different environment for processing before distribution to developers. Internally, we do this at the SQL level on non-Umbraco projects so we know it's a useful process.
It is also interesting to think how this could work with Umbraco Cloud - but that's a different story!
Hello Alan
I was thinking in more GDPR terms, to be GDPR compliant, your company should be able to handle requests like, a customer calls and wants all their personal data removed from your site, and in my case its a webshop.
So I wanted to use, or thought I could, uMunge here, to replace the users data with dummy data, so that I still have alle the orders and such, but just replaced the personal data(shipping/payment info etc.)
Dunno if this is a whole other thing.
Ah I see,
Yes, that's a whole other thing. But a very interesting use case. One idea we had was filters to preserve some sets of data (based on content folder location) but this would be the opposite - selectively zapping some nodes.
I think this may be better done as a custom action on specific items of content / user / forms information - "Munge this data" as an alternative to deletion.
It's not in our plan, but if there is demand we'll build it!
Thanks for contributing!
is working on a reply...