[kepler-dev] [Bug 2962] - Add metadata to data tokens so that it can be used downstream

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Jul 9 15:01:43 PDT 2008


------- Comment #4 from leinfelder at nceas.ucsb.edu  2008-07-09 15:01 -------
I've done some "proof of concepting" with TokenMetadata.  General gist of it
-add metadata at EMLDataSource (name, description)
-travels along the relationships to downstream actors
-modified most of the Plotter-based actors to use the TokenMetadata names for
axis labeling.

It's pretty slick and minimally invasive, but not clear how to introduce the
metadata into the R environment.

Also to think about:  An ArrayToken has TokenMetadata but it is a list of
Tokens that too can have TokenMetadata.  For instances of ArrayToken that
represent the values of a column of tabular data, having a single TokenMetadata
for the list is all that is necessary (all the Tokens in the list share the
same metadata).  The current implementation adds TokenMetadata to each and
every Token in the ArrayToken list (overkill!).  Are there instances that come
to mind where each Token in an ArrayToken must have its own distinct
TokenMetadata?  My hunch is that there are indeed cases where the the array
contains semantically heterogeneous data Tokens.

More information about the Kepler-dev mailing list