|
This is version 15.
It is not the current version, and thus it cannot be edited.
[Back to current version]
[Restore this version]
- 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
- 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
- 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
- User interface mockup: What should the interface look like for validating connections?
- Everytime a connection is made
- Need six (?) types of connections: datatype valid, invalid, unknown; and semtype valid, invalid, unknown.
- Laura will look at the various ways to do this, and try to find some good approaches
- SMS backend services
- when a relation is connected to an input and ouptut port, a change event will be caught, and an sms method will be called, passing in the output actor-port pair, the input actor-port pair, and the workflow itself.
- the sms method will reply with three states: valid, invalid, and unknown, which the even handler will use to code the relation with (to show these cases). Also, a textual description of why the match is invalid may be useful ... but we may get to this more in the next step, which is helping a user "fix" the connection
- it would be useful to do the same thing with datatypes
public SemtypeValidityCheckResult isSemtypeCompatibleConnection(LSID workflowId, Connection connection); // connection within wf
- one issue is that if we consider the use of constraints (like in units), then one connection may affect other connections (later down in the workflow), in which case, we would need to extend the return type. Also, this is the reason for including the workflow in the call. The Connection object has four components: OutputActorId, OutputPortName, InputActorId, InputPortName.
SMS backend services
User interface mockup
Ontology needs assessment
Tasks and milestones
|
