gui-free class for provenance store settings
It would be nice to have a gui-free class that gives you a new ProvenanceRecorder, created from your currently-in-use provenance settings.
Updated by Bertram Ludaescher over 13 years ago
This sounds interesting, but I'm not sure I fully understand it.
Could this be a bit further expanded?
Can one not use the ProvenanceRecorder without the GUI currently?
And what's the mechanism to turn on/off provenance recording when calling a Kepler wf from the command line?
Updated by Derik Barseghian over 13 years ago
I phrased this awkwardly. When programming I just want an easier way to get a new ProvenanceRecorder for the provenance store that's currently in use by the provenance module, and this feature request is to make a class to do this, and I plan to make it gui-free. I've found myself doing some awkward things to get ahold of a ProvenanceRecorder.
I believe ProvenaceRecorder used to work when running kepler from the command line, but trying it just now I get an error connecting to the database...
As for toggling provenance from the command line, I don't know that you can currently. I believe the current procedure is that you have to create a workflow when using the provenance suite from the gui. Then subsequent runs of this workflow (the moml now contains a reference to the ProvenanceRecorder) from the cmd line when using kepler with the provenance suite will write to the provenance store.
Updated by ben leinfelder over 13 years ago
This is true of the "ReportingListener" as well - it requires that the workflow was authored in the gui (and saved) before being run on the command line. A "vanilla" workflow cannot utilize provenance recording if the only action is to run on the commandline.
This points to needing a better/different way to do module initialization that does not piggyback on GUI classes.
Updated by Daniel Crawl about 13 years ago
The provenance recorder constructors use the connection parameters in the configuration file, and none of the constructors require a gui.
For comment #3: there's no mechanism to automatically add a provenance recorder to a workflow using the command line. In this case, the workflow is parsed and executed entirely in Ptolemy classes, so one of these would need to be changed to allow modification of the workflow prior to execution.