|API||Add paging and more headers from RFC5988 (http://tools.ietf.org/html/rfc5988).||5|
|-||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|
|-||As a maintainer I want to harvest data from GeoNetwork Opensource http://geonetwork-opensource.org/||6|
|-||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 access open sensor search with my existing open search app, e.g. on Android||4|
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.
|-||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 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 user I want to get suggestions of similar sensors or potentially interesting services (just like in Amazon) > fuzzy search and colocation and keyword search.
|-||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|
|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|
|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|