One of the pain points we have with using the Virtual Datasets tool in Governance Toolkit is that jobs are not editable, and if the federation fails, you have to recreate the job. So the first thing we need is for jobs to be editable.
The second thing we need is for jobs to be able compare the name of the dataset in the federating instance with the name of the dataset in the receiving instance so that if the name of the dataset changes in the federating instance, the toolkit will update the name in the receiving instance to match. This would be configurable on a dataset-by-dataset basis and we should be able to set the default to either checked or not checked.
The third thing we need is a setting that will make it so that the Virtual Datasets tool will not let you federate a dataset that has already been federated to the receiving instance and still exists in that instance. Currently, because the default behavior is to allow you to federate the same dataset as many times as you want to, there is no easy way to check to make sure it hasn't already been federated before federating it again. Especially since someone can change the name of the dataset in either instance, people may think the dataset they need hasn't been federated and request that it be federated. Which means we have to resort to joining the federation logs to other datasets in order to determine whether the dataset has already been federated or not, and if so, point them to the right place.
The fourth thing is we need to be able to un-federate a dataset using the Virtual Datasets tool. Domo Publish has the ability to un-publish and delete the content from the subscriber instance, so the Virtual Datasets tool needs to be able to do that too.
