Bug #3039


EML2 Datasource (from search) does not include Documentation

Added by Dan Higgins about 16 years ago. Updated about 16 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


If you search Earthgrid (e.g. for 'Datos') and drag result to work area, the Documentation context menu will not show any information.
If you just drag a EML2 Datasource actor to the workarea, Documentation will show up OK!

Actions #1

Updated by ben leinfelder about 16 years ago

I've been looking at this for a bit.
My plan was to look up the EML actor that is in the component library (it contains a KeplerDocumentation attribute) and copy the documentation from that instance into the documentation for the new instance (created when the search results come in).
I can't seem to find a way to create or look up the "EML 2 Dataset" from the component library!
ANy suggestions are welcome.

Actions #2

Updated by ben leinfelder about 16 years ago

Got it working so that when EML Datasource actors are added to the search results, documentation is added to them based on the existing documentation for the EML 2 Dataset in the actor library.
The EML 2 Dataset from the actor library is looked up from the cache using it's LSID. I'm not sure how static that LSID is, but it is crucial for this to work. (It might be more appropriate to add the lsid to the config file and look it up from there rather than hardcoding it in the class.)

Actions #3

Updated by ben leinfelder about 16 years ago

Spoke with chad b. about this - it would be better if object instantiation did not circumvent the actor library cache. But there are cases (RExpression actor) when the class name is not unique within the actor cache so that retrieving and instantiating from the actor cache by classname alone may not return the intended object.
A naive lookup can be performed such that the first actor found for the given classname will be returned, but that may not be desirable in the long run.

Actions #4

Updated by ben leinfelder about 16 years ago

this is working now. uses the EML200Datasource as a lookup key in the library and uses the documentation found from that instance (not using LSID).

Actions #5

Updated by Redmine Admin almost 11 years ago

Original Bugzilla ID was 3039


Also available in: Atom PDF