community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan R Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMDEV-121) Taverna: Databundle viewer for web
Date Sun, 01 Mar 2015 17:54:04 GMT

    [ https://issues.apache.org/jira/browse/COMDEV-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342351#comment-14342351
] 

Alan R Williams commented on COMDEV-121:
----------------------------------------

I suggest that (1) to (5) is changed to:

1) User uploads the databundle file for a workflow run (or provides the URI to one existing
elsewhere) into the presentation system
2) The presentation system shows basic information about the workflow run
3) User navigates to inputs/outputs
4) The presentation system presents a list of inputs or outputs - embedding images etc. where
possible, download links for large files, inline for small text, etc
5) User downloads a selected data file

> Taverna: Databundle viewer for web
> ----------------------------------
>
>                 Key: COMDEV-121
>                 URL: https://issues.apache.org/jira/browse/COMDEV-121
>             Project: Community Development
>          Issue Type: Bug
>            Reporter: Stian Soiland-Reyes
>              Labels: gsoc, gsoc2015, html, mentor, rest, web
>
> Project: Apache Taverna (incubating) http://taverna.incubator.apache.org/
> Mentor: Stian Soiland-Reyes <stain@apache.org>, Ian Dunlop <ianwdunlop@apache.org>
> Taverna Databundle is a file format returned by the Taverna Server containing the results
of a Taverna workflow run and its intermediate values and provenance metadata.
> The databundle is a structured ZIP file with metadata in JSON-LD.
> https://github.com/apache/incubator-taverna-language/tree/master/taverna-databundle
> This GSOC project proposes to create a web-based presentation of a workflow run, e.g.
the following user story:
> 1) User uploads a wfrun  (or provides the URI to one existing elsewhere)
> 2) Server shows basic information about bundle
> 3) User navigates to inputs/outputs
> 4) Server present list of inputs or outputs - embedding images etc. where possible, download
links for large files, inline for small text, etc
> 5) User downloads a selected data file
> Metadata provided can be presented in many different ways, for instance:
> a) Which workflow was executed?
> b) Which steps were executed?
> c) What step produced this value?
> d) What values were produced by this step?
> e) What steps used this value?
> The student is free to choose programming language and web framework, as long as a free
runtime is available (e.g. Ruby on Rails, Java CXF, Node.js, Bootstrap, Ember).
> Your web viewer should aim to be added to the Apache Taverna as a release, so you would
be a part of the Apache Taverna developer community http://taverna.incubator.apache.org/community/
> which will be able to give feedback, testing and guidance for this GSOC project and beyond.
> We can provide virtual servers for hosting the viewer prototypes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message