ConsolidatedApril2009

From myExperiment

Jump to: navigation, search

Consolidated myExperiment Task List April 2009

Sources:

Not scheduled

  • Integrate - Automatic collection of metadata when repository items included in packs, supported for EPrints and Fedora (20 days)
  • Integrate - ??? Extension to version-checking for packs ( days)
  • Integrate - Trials with friends and family then release on myexperiment.org ()
  • Discovery - Autogeneration of tags (5 days)
  • Discovery - Ranking (3 days)
  • Discovery - Indexing of packs (1 day)
  • Discovery - Related search and recommendation (20 days)
  • Curation - ??? Support of expert curation, e.g. annotation of content quality ( days)
  • Curation - ??? Improving community curation, including use of external references into content ( days)
  • Workflow monitoring/decay ( days)
  • Be able to play (run) a workflow from a web application which can be deployed anywhere. ( days)


April (12 days)

  • Bulk workflow upload (Don 3 days)
  • API support (Don 5 days)
  • T2 plugin (Sergey 12 days)
  • Community - (2.5 days)
  • Curation - Workflow quality triage (dder)
  • Rails 2 (Don 4 days - 10 total)

May (21 days)

  • Customability (Don 9 days)
  • API (cont) (Don 5 days)
  • T2 plugin (Sergey 21 days)
  • Community (NeISS kickoff, OR 2009) - (7 days)

June (22 days)

  • Discovery - Faceted browsing (cont) (Don 10 days - 15 total)
  • T2 Support:
    • Implement the T2 workflow processor with full image and metadata parsing support.
  • Finish off T2 plugin (Jits)
  • Community - (2.5 days)
  • ISMB June 27 - July 2, 2009

July

  • Rails 2 (cont) (Don 6 days - 10 total)
  • T2 Support:
    • Pull in additional annotations from workflows and store within myExperiment (making them searchable and viewable).
  • Integrate the Annotations plugin (from BioCatalogue) (Jits)
  • Discovery - Support for user-provided controlled vocabularies (Don 10 days)
  • Discovery - Support for tagging and advanced search through other interfaces eg iGoogle, Facebook (summer student 3 days)
  • Integrate - Interconnection of people identifiers between myExperiment & repositories (summer student 10 days)
  • Implement Attachments
    • Example requirements:
      • "You can have a Taverna workflow where the "definition" of it is the workflow file and some external jars (and maybe data) on which it relies. I would still consider that group to be the workflow. I'm not sure where support for this would be done." (Alan Williams)
      • "Will anything be done to support the sharing of provenance? A simple example would be an example workflow run to go with a workflow definition, including the re-playing of the run."(Alan Williams)
  • Community - (2.5 days)

August

  • BioCatalogue Integration: (Jits)
    • Implement BioCatalogue harvesting and caching mechanism.
    • Implement "Services" tab, with Latest Services, Updated Services, etc sub tabs (like on the Workflows tab).
    • Implement a basic service entry view page showing metadata harvested from BioCatalogue, then link through to the main entry in BioCatalogue.
    • Make services searchable from within myExp.
    • Extract the services information from within the processors of Taverna workflows (at the moment we cant parse out enough information to determine the exact services).
    • Link services within workflows to the service entry in myExp (and therefore to the BioCat entry).
    • Implement a search facility to be able to find all the workflows that have a specific service (through API as well) (ie: "retrieve all workflows that use a specific service").
    • Implement a "other workflows using the same services" section on the workflows show page.
    • For non-Taverna workflows, have the ability for users to specify what services their workflow uses.
  • Beanshell Repository:
    • Implement the "beanshell" contribution type and all corresponding views/controller/model.
  • Community - (2.5 days)

September

  • Workflow "basic" (or even "scientific") view - ie: only the essential details of a workflow, without all the social metadata and so on.
    • Exact requirement is: "The ability to view the workflows without all the "boring" bits i.e. to see what it really is doing from a scientific point of view." (Alan Williams)
  • BioCatalogue Integration:
    • Update the T2 myExp plugin to include BioCatalogue functionality (part of BioCatalogue workplan as well).
  • Beanshell Repository:
    • Update the T2 myExp plugin to take into account beanshells.
  • Community - (2.5 days)

October

  • Community - (2.5 days)

November

  • Easier creation of packs and adding items to packs (ie: shopping cart mechanism, selecting multiple items from a list, temporary "scratchpad" for new/existing pack items etc).
  • Bulk editing of metadata, tags, permissions etc.
  • Community - (2.5 days)

December

  • Community - (2.5 days)
Personal tools