 |
|
You are here: Wiki>SensorWeb Web>SensorInstanceRegistry>SensorInstanceRegistryBacklog (14 Oct 2013, DanielNuest)Edit Attach
SensorInstanceRegistry Backlog
Vision
Become what mapmatters (http://www.mapmatters.org/) is for WMS, but for SOS and SES.Backlog
The new backlog is available online on easybacklog.com > please contact Daniel to get access to it.Old Backlog
Legend
Priorities: 1 = highest priority, n = lower priorities Costs: "Felt" development costs, relative, no actual estimation neccessary, going from
= "low" to = "very high"
Statuses: 
= open task, 
= somebody is working on the task, 
the task is "done". We have a very loose definition of done: "Contributor did some tests and it worked."
Group: Can be used freely to associate items together, but is optional..
Backlog Items
| Group | Item | Priority |
Costs | Contributor/Status |
|---|---|---|---|---|
| As a user I want to access open sensor search with my existing open search app, e.g. on Android | 4 | |
|
|
| - | As a user I want to search for data that has a maximum age, e.g. "water temperature in Hamburg within the last 2 hours", potentially with a special user interface element (time slider), potentially based on time extension (http://www.opensearch.org/Specifications/OpenSearch/Extensions/Time/1.0/Draft_1). Cumbersome because data must be available somehow. | 4 | |
|
| - | As a user I want to exploit all functionality of OpenSearch where reasonable (indicating errors, email property for contact in description document, multiple URI elements). | 5 | |
|
| - | As a user I want to tag search results (very easy Javascript/HTML 5 user interaction, just click on the list of tags and you can add one) | 5 | |
|
| API | Add paging and more headers from RFC5988 (http://tools.ietf.org/html/rfc5988). | 5 | |
|
| - | As a user I want to differentiate between "hits" and "results" and give direct feedback (e.g. voting up or down of search results, similar to StackExchange), and ideas based on TED Talk by Tim Berners-Lee > http://www.youtube.com/watch?v=OM6XIICm_qo.
|
6 | |
|
| - | As a maintainer I want to harvest data from GeoNetwork Opensource http://geonetwork-opensource.org/ | 6 | |
|
| Concept | Design interfaces to integrate the SIR into a universal service bus, see http://www.galdosinc.com/archives/1304 | 6 | |
|
| General | Evaluate relation to CKAN - is it a possible backend, should OSS be build upon CKAN, can CKAN be integrated (harvesting one way or the orher) - http://ckan.org/features/ and http://docs.ckan.org/en/latest/geospatial.html, see also discussion here: http://article.gmane.org/gmane.comp.gis.geowanking/5986 | 6 | |
|
| - | As a user I want to get suggestions of similar sensors or potentially interesting services (just like in Amazon) > fuzzy search and colocation and keyword search.
|
7 | |
|
| - | As a user I want a landing page that is as beautiful as this one: http://cal-adapt.org/. We could also add some big square buttons below the search field for "search on globe", "search on map", and "upload data". The next/previous background image is great. | 8 | |
|
| - | As a user I want to flattr a sensor provider (if he allows to do so). Extension: support micropayments / business model: this sensor costs X microdollars, "using this sensor data costs X microdollars per query", or "support the maintainer of this sensor" | 8 | |
|
| - | As a catalog maintainer I only want to push the sensor metadata to the catalogue that was actually changed since the last push (Implemented in the push task, but this requires a new database field in table catalog and corresponding DAO). | 10 | |
|
| General | As an administrator I want to run the SIR alongside a SOS to replace the procedure handling of the SOS with the SIR and provide sensor discovery functionality for that service. The SIR should run as a module within the SOS and be configurable from the SOS administrative interface and must use the same encoding and decoding dependencies as the SOS where possible. | 10 | |
|
Edit | Attach | Print version | History: r29 < r28 < r27 < r26 | Backlinks | View wiki text | Edit wiki text | More topic actions
Topic revision: r28 - 14 Oct 2013, DanielNuest
AI_GEOSTATSLegal Notice | Privacy Statement
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding Wiki? Send feedback