Return-Path: X-Original-To: apmail-community-commits-archive@minotaur.apache.org Delivered-To: apmail-community-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F27C109C8 for ; Mon, 2 Mar 2015 10:45:11 +0000 (UTC) Received: (qmail 79198 invoked by uid 500); 2 Mar 2015 10:45:04 -0000 Delivered-To: apmail-community-commits-archive@community.apache.org Received: (qmail 79132 invoked by uid 500); 2 Mar 2015 10:45:04 -0000 Mailing-List: contact commits-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list commits@community.apache.org Received: (qmail 78993 invoked by uid 99); 2 Mar 2015 10:45:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2015 10:45:04 +0000 Date: Mon, 2 Mar 2015 10:45:04 +0000 (UTC) From: "Ian Dunlop (JIRA)" To: commits@community.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COMDEV-121) Taverna: Databundle viewer for web MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COMDEV-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343012#comment-14343012 ] Ian Dunlop commented on COMDEV-121: ----------------------------------- Alan's summary is pretty much spot on. What is needed is a system that allows a user to upload a databundle for a workflow run (via file or URI) and then allows viewing and navigation of the steps within the workflow run (and therefore the provenance) and downloading of inputs and outputs. (I would edit but I don't seem to have the permissions!) > 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 , Ian Dunlop > 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)