Store visualization reference in case of multiple visualization

[thinkh]

Preconditions

• Visualization component (e.g, scatterplot, LineUp) with registered actions
• Multiple instances of the same visualization component

Problem If an action is reverted all visualization components will be updated at the same time, because we cannot distinguish the target of the action.

Feature Request We need to track/identify the component that triggered the action in the provenance graph, too.

[Tommos0]

Isn't this the responsibility of the application? E.g. it could add a componentID argument for its action and the action could use this information.

Or it could be implemented as a second provenance graph (one per component).

[thinkh]

Storing two provenance graphs is an interesting idea. However, I assume that handling multiple provenance graphs is even more complex, because you need to take care of all timestamps/actions and know which one to execute when. Also the visualization will be more complex.

I like the idea by adding a componentID to the action. That way the application can trigger the action for the correct component.