Kepler

Wade Sheldon from GCE-LTER brought an question if the eml actor can handle mutiple physical representations in an entity.

I took a look at code and found kepler can't handle this correctly. In org.ecoinformatics.seek.datasource.eml.eml2.Eml200Parser class, we always use

physical/dataFormat/textFormat/simpleDelimited/collapseDelimiters, physical/distribution/online/url/@function and et al directly. And also we only get the value from the node which index is 0.

This will handle entity with one physical representation correctly. But it will failed when an entity has more than one physical representation.

For example, a dataTable has two physicals. The first one isn't textFormat and has a downloadable url. The second one is textFormat and has a downloadable url.

Kepler will download the first non-text data object and ignore the second text data object. And the worst case is that kepler will mismatch the non-text data object with the text format information from the second text data object.