Ticket #996 (new task)

Opened 12 years ago

Last modified 11 years ago

Client (and visualisation) stack needs to be standalone

Reported by: domlowe Owned by: spascoe
Priority: critical Milestone: NDG3
Component: COWS Version:
Keywords: Cc: domlowe


Current state is that we have the work that Calum did running on a server not much plumbed in anywhere. We need to improve this and the client stack needs to be refactored to be standalone. It should include the WMS client, WCS client, the old browse client, the new browse client and a discovery client, and it should be deployed at BADC and existing NDG sites.

Change History

comment:1 Changed 12 years ago by spascoe

  • Cc domlowe added

This ticket contain a lot in it. Questions for discussion follow:

  1. What is meant by standalone? Do we mean not tied to NDG discovery/browse?
  2. What is meant by the "new" and "old" browse clients?
  3. By "WCS client" do we mean web-browser client or command-line client or both?
  4. Once refactored to make it "standalone". How would we go about re-integrating the code to make a "deployable" system.

On the deployment side:

  1. By "deployed at BADC" what do we mean?
  2. What datasets can we deliver through this "deployed" system?
  3. What dependencies are there on other work being done?
  4. "deployed at existing NDG sites" sounds out of scope unless we can define it much more narrowly.

I will discuss this with Dom and redefine this ticket accordingly.

comment:2 Changed 11 years ago by domlowe

WMS client is now standalone in 'cowsclient' egg.

Note: See TracTickets for help on using tickets.