Hello, I want to use this nice tool to keep provenance over data processing steps inside a Python script (e.g., pandas DataFrames are entities, pandas code is an activity with tool name "Python pandas").
For that I currently record the script's metadata (e.g., its EDAM operation class) in the custom_metadata argument of ProvenanceChain.create(), and any statistics of a step (e.g., row count after deduplication) in custom_properties of .add() using custom ontology term: value pairs with either activity:, input-entity: or output-entity. And I see that dataprov-report CLI tool creates a nice report, but it is missing these extra elements.
Would it be possible for the dataprov-report to also display the custom metadata and custom properties in the HTML report? The custom metadata could be at the top of the report as a collapsible section, while each step would have either a activity custom properties in a separate box and input/output entity metadata in the Inputs or outputs section of the step. Prototype of a step card (newly added elements in red):
Version used: 3.2.0
(Thanks for the useful in-depth documentation in the README!)
Hello, I want to use this nice tool to keep provenance over data processing steps inside a Python script (e.g., pandas DataFrames are entities, pandas code is an activity with tool name "Python pandas").
For that I currently record the script's metadata (e.g., its EDAM operation class) in the
custom_metadataargument ofProvenanceChain.create(), and any statistics of a step (e.g., row count after deduplication) incustom_propertiesof.add()using custom ontology term: value pairs with eitheractivity:,input-entity:oroutput-entity. And I see thatdataprov-reportCLI tool creates a nice report, but it is missing these extra elements.Would it be possible for the
dataprov-reportto also display the custom metadata and custom properties in the HTML report? The custom metadata could be at the top of the report as a collapsible section, while each step would have either a activity custom properties in a separate box and input/output entity metadata in the Inputs or outputs section of the step. Prototype of a step card (newly added elements in red):Version used: 3.2.0
(Thanks for the useful in-depth documentation in the README!)