Sensor Web Client Roadmap

ALERT! This site is in a raw state and has to be refined

Work in progress

Role Story Task Status Effort Priority Comment
System Provider As a system provider I want to make the client better integratable into other systems/UIs Compare traffic throughput between raw data transmission and image data transmission target-red led-aqua arrowbup REST API.
User As a user/developer I want to have a quick and nice-to-read overview of data available Synchronize map clustered content/zooming with parameters/stations in list target-red led-aqualed-aqua arrowbright  

Things to check: TODO
  • Clear xml-apis compatibility
    • fop has transitive dependency on xml-apis-1.3.04
    • hibernate-core-3.5.0-Final has transitive dependency xml-apis-1.0.b2
  • Discuss how to offer OpenData minimum information principles:
    • License clear for raw data/metadata?
    • Show SOS endpoints
      • arrowright let info window include SOS URL and license (parsed from capabilities)
      • arrowright Small info-button next to data provider (e.g. PEGELONLINE, or Wupperverband)
    • Downloadable metadata arrowright include in PDF (w/o contents section)

Ongoing Tasks: TODO
  • optimize and cleanup pom.xml files
  • refactor internal data model (station concept)
    • refactor interface for parsing components to handle several SOS types providing different data profiles
    • reflect station concept in UI (map rendering)
  • Split code into more domain centric Maven modules (Separation of Concerns)
  • cleanup SOS and SES UI
  • create a more abstract level for events
  • optimize initializing UI and server
  • consolidate configurations (+centralizing config, controllable via Maven)

Features

Feature Ideas

Role Story Task Status Effort Priority Comment
System Provider As a system provider I want usage statistics logged to a file add file logging to Statistics timer target-red led-aqua arrowbright  
User As a user I want to have a simple user interface Remove controls from overview map target-red led-aqua arrowbdown Pro: The overview map is quite small and should not be overloaded with controls.
Con: The user should be able to pan/zoom out to get a better idea of the spatial context.
System Provider As an system provider/domain expert I want to create "event products" Add "new subscription section" in admin interface. target-red led-aqualed-aqualed-aqua arrowbdown  
System Provider Create logic in CreateSubscription window to check/render new subscription types target-red led-aqualed-aqualed-aqua arrowbdown  
System Provider Create workflow to handle subscriptions if subscription type will be deleted by admin target-red led-aqualed-aqualed-aqua arrowbdown  
User As a user I want to get a quick impression of the event Send nicely formatted HTML email target-red led-aqualed-aqua arrowbdown  
User Add the diagram of the timeseries to the email content showing the current situation target-red led-aqualed-aqua arrowbdown  
User Add a permalink to the email content target-red led-aqualed-aqua arrowbdown  
User As a user I want to review the current situation of subscribed timeseries Add a backlink to each subscription in user's profile which loads the current timeseries diagram target-red led-aqualed-aqua arrowbup  
User As a user I want to be kept logged while I am interacting with the client Login sessions have to be extended for each valid client-server request target-red led-aqua arrowbup  
Administrator As an administrator I do not want to allow that sessions can be stolen Hash client specific information and add it to the session object. When information changes (like IP) session gets destroyed (principle of "do not trust the client" target-red led-aqualed-aqua arrowbup  
User As a user I want to have a quick overview why I have to register and what data will be stored and processed Add user help/information nearby the registration/login target-red led-aqua arrowbup  
System Provider As a system provider I only want only SOS instances to be subscribable which offer dynamic data Add parameter to sos-instances config to make eventing configurable for each instance target-red led-aqua arrowbdown  
User As a user I want to enter values for units which I am used to create interface and add unit converter implementations (e.g. for \xB0F arrowright \xB0C target-red led-aqualed-aqua arrowbdown  
User As a user I want to edit threshold values for my subscriptions create edit button in subscriptions list and jump to initialized CreateSubscription window target-red led-aqua arrowbright  
User As a user I want to add further SOS instances create workflow so that registered users can configure new SOS instances meeting led-aqualed-aqualed-aqua arrowbdown
• Is this even wanted by a system provider?
User make login mechanism part of core UI (independent to SES) target-red led-aqualed-aqualed-aqua arrowbdown
User integrate an existing (proofed!) security framework target-red led-aqualed-aqualed-aqua arrowbdown
User As a user I want to see markers on the map that cluster, so that there is as less mess than possible tbd target-red led-aqualed-aqua arrowbup Evaluate if current open layers implementation. Check if Leaflet is promising enough to replace current implementation
User As a user I want to see work with a nice map view tbd target-red led-aqualed-aqua arrowbup Check if leafletjs (gwt version is available) is a valuable replacement of openlayers.

Still Raw Ideas

  • Refactor use management from SES module to have it on the whole client. This would lead to some kind of admin tools, where new services could be added, or the metadata cache could be reloaded for one or all services
  • Use a leightweight database implementation (e.g. H2, SQLite) for straight development and quick installation
  • create different kinds of selection mechanisms, make different interaction strategies somehow configurable (at least within the build process)
  • define/create common concepts used by SensorWebClient and SensorInstanceRegistry to harvest SOS instances to build up stations with their parameter constellations to request data from SOS
  • Cell background colouring for visual analytics of data: allow to show different variables as columns and time as rows (or vice versa) and colour the background of cells depending on the value in the cell. This quickly allows to see patterns that one would not see when just looking at the numeric values. Possible extension: aggregation into time of day, days of the week, month of the year for temporal "axis" to see reoccuring patterns. -- DanielNuest - 2013-01-22

Metadata

Topic revision: r23 - 27 Jun 2016 09:02:40, UnknownUser
This site is powered by FoswikiCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback