[kepler-dev] [Bug 3647] - Create Report Assembler

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Thu Nov 13 10:06:32 PST 2008


------- Comment #1 from leinfelder at nceas.ucsb.edu  2008-11-13 10:06 -------
Dynamic ReportItems (i.e. an actor's port) are referenced in the ROML and used
to lookup the value[s] in Provenance.
In the case of an actor port, the Token value[s] that have passed through the
port are used. 

The assembler must handle the layout of multiple values (informed by
configuration in the ROML), and also handle "by reference" tokens (i.e. images
that have "values" that are simply pointers to the resource as it exists in
some accessible system). When we get to the visual rendering stage of the
report instance, those references will need to be available from outside the
particular Provenance system that initially captured them during workflow
execution. Perhaps these resources will be published to the "publication ready
archive" or they will be pushed to an online file store (Metacat instance) and
referenced via an LSID.

Handling the ROML -> RIO step should be in two stages:
-Local execution: Resources are referenced only in Provenance
-RIO export: Referenced items need to be "published" so that they are
accessible for 

More information about the Kepler-dev mailing list