EML 2 Dataset actor needs to access local data files
The EML 2 Dataset actor currently allows the user to specify a local EML file. Once that file is specified, Kepler immediately parses the metadata and tries to improt the data files using the metadata in the distribution tag. Sinec the distribution tag always contains ecogrid:// addresses (unless the user manually edits them), Kepler always tries to download data files from the KNB at this point. This effectively prevents users from using local copies of EML data sets, as usually the data as well as the metadata will be offline.
#1 Updated by Will Tyburczy about 13 years ago
Suggested fix from the Kepler breakout meeting (Will, Dan, and Mark Sch.):
Add an extra parameter for the EML 2 Dataset actor that allows the user to specify the proper location of the data file, in a similar fashion to how the EML metadata file is selected. If this is left blank (default), the data file would be located using the distribution url element in the EML file as before. If it is specified, however, the actor would use the file specified by the user as the data file. Notably, this would require delaying when the data file was imported into Kepler to when the user hits the "Commit" button for configuring the parameters, rather than when the user selects the EML file (as is currently done).
#2 Updated by Matt Jones about 13 years ago
I agree this needs to be fixed, but its more a problem with how to reference local files within EML than how Kepler handles those identifiers. We need a mroe universal system for locating a local file via a semi-indirect pointer that can be shared across software systems.