[kepler-users] Updating a local dataset connected to EML2 Dataset Actor

jing tao at nceas.ucsb.edu
Tue Apr 17 11:04:43 PDT 2012


Hi, Mike:

I created a bug at http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5586

You may add comments and keep track on this bug.

Meanwhile, you may delete the cache directory before starting kepler 
when a new version of data file is available.  The cache directory 
locates at /your-home-dir/.kepler. Deleting cache dir will force kepler 
to load the file again.

Thanks,

Jing

On 04/16/2012 09:21 PM, Michael.O'Connor at csiro.au wrote:
> Hi Jing,
>
> Not sure if I should respond on the list. Please advise.
>
> I think it would be helpful if I didn't have to change the file name every
> time I modify the file contents. I typically keep the filename the same
> and use an SVN repository to save versions of the file's content.
>
> So if that check box worked with local files that would help in my
> situation.
>
> Cheers,
>
> Mike
>
> On 17/04/12 1:16 AM, "jing"<tao at nceas.ucsb.edu>  wrote:
>
>> Hi, Mike:
>>
>> Please see my comments under your text.
>>
>> Thanks,
>>
>> Jing
>>
>> On 04/13/2012 07:20 PM, Michael.O'Connor at csiro.au wrote:
>>> Running v2.3 on Mac OSX 10.7.3   Fairly new to Kepler.
>>>
>>> I'm trying to use the EML 2 Dataset Actor to read in a local copy (in a
>>> folder on my laptop drive) of a sample metadata (.xml) file using the
>>> EML 2.1.0 schema and a simple 4-column data (.txt) file.  I have checked
>>> the files using the http://knb.ecoinformatics.org/emlparser/ site, and
>>> both were validated.
>>>
>>> Two problems:
>>> i) If I change either file the Actor doesn't keep up with the changes.
>>> It seems to revert to a cached version of the file as it was when I
>>> first specified it to the Actor (via the EML File: and Data File: fields
>>> in Configure Actor).
>>      Kepler has a cache system to speed the process. Did you change the
>> file name when you modify a file? I believe if you only change the file
>> without changing name, Kepler won't reload the new version and will use
>> the cache. So you have to change the file name when you modify the file
>> content.
>>> ii) I wondered about checking the "Check for latest version" checkbox.
>>> However doing this generates an error dialog with the message "null
>>> Please enter a new value:"  I have to uncheck to stop the error.
>>    This check box is only for packages in a remote repository, e.g. a
>> Metacat server, it wouldn't work for the local file.  We can add this
>> feature for the local files as well.
>>> If I create a new local copy of the metadata and data file after
>>> editing is completed, and connect those to the Actor it works
>>> (presumably a new local cache is made somewhere).
>>>
>>> Couldn't find similar problems on this list; apologies if I missed
>>> something relevant.
>>>
>>> Thanks,
>>> Mike
>>> _______________________________________________
>>> Kepler-users mailing list
>>> Kepler-users at kepler-project.org
>>> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users



More information about the Kepler-users mailing list