User: David Lowery | User: Bob Morris | User: Zhimin Wang | User: BertramLudaescher | User: Lei Dou | User:
- UC Davis (Lei and Bertram): Kepler workflow run engine (Web service wrapper): Documentation is available here: https://kepler-project.org/developers/interest-groups/distributed/technical-documentation/the-overview-of-the-workflow-run-engine-component
- Zhimin: Successfully deployed demo on top of GBIF cache. With Lei's help, installed and tested Kepler web service module, which is on top of AXIS2. Work with Bob on the use case analysis.
- Bob: With Zhimin use case analysis for Researcher Seeks DwC Metadata
The Scenario assumes that a researcher has a specimen or occurrence record(s), but it is missing some Darwin Core metadata. She wants to launch a query that will result in the return of any annotations in the network that will contain putative DwC data for her record(s)
The web service code(Kepler run engine) is OK. May need further refactory if new requirement comes. Data one:
Use case with Ebird:
1,observation records of birds with integrity constraints.based which system can identify data quality problem (rareness of some kind of bird). Expert may also validate records
2. ebird review can be taken as annotations in our system(slide3). a specific workflow can be constructed for their review process
==> work towards an extended use case with Steve Kelling where FPush is used as a "tag-based" workflow system
3.Have multiple observations of the same bird (observation fuse). current approach: clustering and suggest, and human verify. Bob:some kind of different from the case in specimen duplicate
==> again work towards an extended use case with Steve Kelling
==> expand eBird curation workflow; study how that might be implemented as a Kepler/Ptolemy model.
Later: - Kepler for simulation workflows, including FPush