[kepler-dev] [Bug 2963] - Add data structure for tabular data and associated metadata
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Mon Aug 17 14:30:13 PDT 2009
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2963
------- Comment #2 from leinfelder at nceas.ucsb.edu 2009-08-17 14:30 -------
I've introduced an OrderedRecordToken to ptolemy - it preserves the original
order of the RecordToken.
Unfortunately this can be blown away when you serialize it as a string
{a={1,2,3, b={4,5,6}} and then deserialize it back to a RecordToken.
In the mean time, the 'wrp' module overrides the ptolemy RecordToken to use the
correct storage class to preserve the original order. I'm not sure how we can
have both implementations without changing the serialization syntax for the
ordered version. Plausible?
***Or just change RecordToken in Ptolemy to keep it's order and give people a
method to sort them if they want that behavior***
More information about the Kepler-dev
mailing list