It is possible that when a view is shared, and a new view is created based on
the original data, if a concern is raised about the data in a particular place,
be it ownership, copy write, data cleanliness, etc. We may need to remove not
only the original view, but all views that data.
For this reason, it is important to store where the data originated. ie, if
view A is created by Bob, and B and C extend the view, and D extends B, if
there are concerns with A, we need to be able to remove all children of that
view, namely B C and D.
To do this, I think that we should log which stored view the resource came
from, then we can see which view came from those resources. We could then
programatically, delete all visualizations derived from some particular data.
For this reason, I think that we kind of need two modes for removing views,
soft removes, where we flag a view as not being available, but still keeping
information about it in the system, and hard removes, where we need to remove
every reference to this data, and its resources in the system. It is also
important to maintain the chain as long as any incoming and outgoing references
occur.
Original issue reported on code.google.com by jrsta...@gmail.com on 7 Dec 2010 at 12:09
Original issue reported on code.google.com by
jrsta...@gmail.comon 7 Dec 2010 at 12:09