myGrid
  1. myGrid
  2. TAV-134

Service panel improvement, service discovery from Taverna

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Taverna GUI
    • Labels:
      None

      Description

      This is a bundle of a set of improvements and new features to make service discovery from within Taverna easier, mainly to improve the "Available services" panel in different ways. Supplements TAV-53.

      Profiles:
      TAV-73 defines how the service panel list can be saved and loaded.

      TAV-74 defines how branches of the service panel can be "updated" to catch changes in services, useful with TAV-73 and web scavengers

      TAV-29 asks for different "service profiles", so that say a micro analyst can choose to only see his relevant services. This is a specialisation of TAV-73, with a central location for those profiles, could probably be the service registry or the portal, or simply a web page.

      Service browsing:
      TAV-78 adds more information about the services in the service panel itself, an extra flip with information on parameters and other stuff that is available from the service provider.

      Search and FETA:
      TAV-97 defines how FETA service search can be integrated in the service panel.

      TAV-77 asks for tabs in the service panel, each search result can be shown in a tab, and a set of tabs can be saved like in TAV-73

      TAV-76 asks for search results to be shown as branches in the tree instead of tabs like in TAV-77.

      API changes:
      TAV-79 asks for a API (more specifically, an SPI) for a general way to plug in service information providers like Feta

      TAV-75 also asks for an API (SPI) for searching services, I can't see that this is much different from TAV-79, except this is more GUI-centric.

      Related:
      TAV-53 is not about the service panel, but about a service portal for more advance browsing, annotation and searching of services. However, once we have a portal we can probably make more fancy service search widgets to include, such as "Newest services", "My services" (TAV-73), "Micro-array services" (TAV-29), "Most reliable services", etc. This doesn't mean that the other requirements will have to wait for a service portal, but that they can later be integrated with this portal.

        Issue Links

          Activity

          Hide
          Stian Soiland-Reyes added a comment -

          I don't think we need full analysis of this, but it's nice to see all these things in connection, like I discussed with June. This will be like the Taverna-side of the portal TAV-53.

          Show
          Stian Soiland-Reyes added a comment - I don't think we need full analysis of this, but it's nice to see all these things in connection, like I discussed with June. This will be like the Taverna-side of the portal TAV-53 .
          Hide
          June Finch (Inactive) added a comment -

          Stian - I'm a bit confused by this one. What is the work to do against for TAV-134 that isn't covered by any of the referenced TAVs?

          Show
          June Finch (Inactive) added a comment - Stian - I'm a bit confused by this one. What is the work to do against for TAV-134 that isn't covered by any of the referenced TAVs?
          Hide
          Stian Soiland-Reyes added a comment -

          Well, what is "really asked for" is not the donkey (the invidual TAV-s) but just that the service panel should be improved (this TAV). The referenced TAV-s are concrete examples of how we might do that. Even if we might not do say TAV-77 (tabs), we would probably need to do TAV-76 (search results in tree).

          So this thing is not an actual task to do, but it is an improvement, hence an Improvement-TAV. Prioritizing this in general will also say something about how we will do work on the sub-improvements if you like.

          Show
          Stian Soiland-Reyes added a comment - Well, what is "really asked for" is not the donkey (the invidual TAV-s) but just that the service panel should be improved (this TAV). The referenced TAV-s are concrete examples of how we might do that. Even if we might not do say TAV-77 (tabs), we would probably need to do TAV-76 (search results in tree). So this thing is not an actual task to do, but it is an improvement, hence an Improvement-TAV. Prioritizing this in general will also say something about how we will do work on the sub-improvements if you like.
          Hide
          June Finch (Inactive) added a comment -

          This is an umbrella requirement - once the individual TAVs referred to have been resolved this will be closed and any future improvements dealt with individually. Service Discovery is a key priority area.

          Show
          June Finch (Inactive) added a comment - This is an umbrella requirement - once the individual TAVs referred to have been resolved this will be closed and any future improvements dealt with individually. Service Discovery is a key priority area.

            People

            • Assignee:
              Tom Oinn
              Reporter:
              Stian Soiland-Reyes
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: