Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



SMS_KR Developers Meeting Notes May 2005

This is version 13. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]


Kepler Architecture Notes (Monday, May 2nd, 2005)

  • The problems:
    • Versioning
      • Conflicts in Dependency Chains (underlying classes and their dependencies)
      • instead of class names, use lsids
    • no way to uniformly manage objects (workflows, data, libraries/dependencies, etc.)
    • no way to "seamlessly" transport objects
      • both publish and download
    • no way to manage local versus remote objects
      • lsids plus object cache ("intelligent" object cache)
      • dynamically load classes into current Java Classloader
      • no central repository(ies)
        • periodic indexing of HDD in background
    • no good way to create functional groups
      • e.g., the core group, plus packages for geospatial, rexpression, etc.
      • a lighter weight kepler

Search/Discovery Kepler Notes (Tuesday, May 3rd, 2005)

  • Topics
    • Actor browsing/searching
    • Data browsing/searching
    • Unify them
    • Helping understand why a result was included

  • Ideas
    • go with the tree approach for actors and data
    • introduce a "shopping cart"
    • experiment (via mockups) of different approaches -- laura et al
      • advanced search function
      • separate window for searching / results

Annotation Interfaces (Tuesday, May 3rd, 2005)

  • For actors and datasets, we are planning on the following
    • hyjack the port configuration dialog by adding a new column called "semantic type"
    • keep the unit column
    • add a (...) button for the semtype column, which will open up a new annotation dialog
    • the new dialog will open a list of the ontology "variables", which will let one select a "class" and then show the direct relationships of that class, e.g., subclasses, superclasses, and properties

Workflow Validation (Wednesday, May 4th, 2005)

  • What should the interface look like for validating connections?
  • Architecture



Go to top   More info...   Attach file...
This particular version was published on 04-May-2005 09:23:18 PDT by SDSC.bowers.