Task #2240

INSPIRE dashboard prototype

Added by Francois Prunayre almost 6 years ago. Updated over 4 years ago.

Status:ClosedStart date:24 Oct 2014
Priority:NormalDue date:
Assignee:Francois Prunayre% Done:

100%

Category:-
Proposed change or action:

Description

Online demo & resources

Online demo: http://apps.titellus.net/solr
Videos:

Screenshots: https://drive.google.com/open?id=0BwyvNKYgG4ZWbXh1OTJ6emtsZ28&authuser=0

Source code: https://github.com/titellus/daobs

Draft documentation: https://github.com/titellus/daobs#overview

Features

The demo website provides the following features:

  • Dashboard:
    • View predefined dashboards on INSPIRE reporting 2013 and 2014
    • View predefined dashboards on harvested records from MS discovery services
    • Create, Save and Share new dashboards online
  • Reporting
    • View report configuration
    • Generate and export in different formats reports based on harvested records
  • Harvester : view harvester configuration

Data

The demo website data are:

  • INSPIRE reporting 2014 - ref year 2013 (provided in XML format)
  • INSPIRE reporting 2013 - ref year 2012 (provided in XML format)
  • Discovery service from each MS harvested the 23rd October

Limitations & remarks

Harvested data may be incomplete and will require improvements (eg. bad URL, wrong/no CSW GetRecords filters, errors during harvesting or indexing).

Report does not provide information which requires ancillary information (not yet available).

There is no security layer, so please do not remove default dashboards.

History

#1 Updated by Alex Ramage almost 6 years ago

Dashboard requires HTML5 - not all Browsers support this.

#2 Updated by Nico Bonora almost 6 years ago

Dear all,
some comments on the dashboard below.
- I think we are in the right direction to ultimate the tool development; it seems to me it reflects what we have discussed and I’m happy with this.
Potential criticality identified:
- Search: I did not have any chances to get results, even using the suggested syntax (????).
- There are some “drag here to move” (Facet, Hits,…) I do not understand what they mean. I tried to drag something, but nothing happens. Do we really need to include them in the D-B?
- (Marginal issue) Is it only harvesting activity considered for accessing metadata? Cannot we go through indicator calculation leaving metadata where they are?
- When clicking on the maps (through the right side menu, e.g. inspire reporting 2013) a java script (Script: http://apps.titellus.net/solr/dashboard/app/app.js?r=5eeaf7b:4) do not allow to proceed unless it is stopped.
- Why in the right side menu of the main page of the application (http://apps.titellus.net/solr) is used the reporting formulation when it relates more to monitoring?
- (marginal issue) It would be good to link dynamically the legend to the graph/diagram, so that when users move the mouse-pointer on the legend, the correspondent information on the graph/diagram is highlighted.
- search your geospatial information: (http://apps.titellus.net/solr/dashboard/#/dashboard/solr/Search%20your%20geospatial%20information) the difference between row and json (click on a resource to display “View: Table / JSON / Raw”) reflects just a change of color…do we really need to keep both?
- Search your geospatial information: does not work for all the countries (e.g. DE works, AT and LU do not).
- Filters do not behave in the same way for the different countries (try to apply DE and NO).
- "%20" has to be replaced with “empty character” in the filter's small windows (e.g Soil%20use).

I think I had a look more or less everywhere…if I missed something, please, let me know!
Kind regards
Nico

Francois Prunayre wrote:

Online demo & resources

Online demo: http://apps.titellus.net/solr
Videos:

Screenshots: https://drive.google.com/open?id=0BwyvNKYgG4ZWbXh1OTJ6emtsZ28&authuser=0

Source code: https://github.com/titellus/daobs

Draft documentation: https://github.com/titellus/daobs#overview

Features

The demo website provides the following features:
  • Dashboard:
    • View predefined dashboards on INSPIRE reporting 2013 and 2014
    • View predefined dashboards on harvested records from MS discovery services
    • Create, Save and Share new dashboards online
  • Reporting
    • View report configuration
    • Generate and export in different formats reports based on harvested records
  • Harvester : view harvester configuration

Data

The demo website data are:
  • INSPIRE reporting 2014 - ref year 2013 (provided in XML format)
  • INSPIRE reporting 2013 - ref year 2012 (provided in XML format)
  • Discovery service from each MS harvested the 23rd October

Limitations & remarks

Harvested data may be incomplete and will require improvements (eg. bad URL, wrong/no CSW GetRecords filters, errors during harvesting or indexing).

Report does not provide information which requires ancillary information (not yet available).

There is no security layer, so please do not remove default dashboards.

#3 Updated by Ilkka Rinne almost 6 years ago

I've done a quick browse-through of the current prototype functionality, some comments below. I've been looking at this like version 0.5 (0.9?) of the final application, and not a technical prototype, as this was my understanding of the project reality (budget & finishing deadline wise).

Design / usability:

  • Generally the current UI seems to me more like a tool for creating different dashboards and visualisation views than a simple UI for following the INSPIRE implementation status in member states. It seems to me that the current UI might be a bit intimidating for a occasional user. The visual UI components look good, but it's not easy to see what to click and how to navigate in the application. This is not really the developers fault because we could not provide a UI design specification to follow in the implementation.
  • I don't understand what the users are supposed to do with the search component on some Dashboards (like the "INSPIRE Dashboard"
  • The technical implementation platform (SOLR) shows too much to the end-user: Example: When clicking on the info button of a graph, it shows the SOLR query used for retrieving the displayed data, which is very rarely of interest to the users and like to scare them: q=*%3A*&fq=%2BdocumentType:indicator %2BreportingYear:2013&wt=json&rows=0&&stats=true&stats.facet=territory&stats.field=indicatorValue
  • I don't see a good use case for showing the "show/hide row" buttons in dashboards. The same is true for drag-and-drop relocation of the components: We should provide a UI than is good enough for the intended users and show all the info we know they need to solve their tasks. Now we are showing them a build-your-own-dashboard UI.
  • The UI does not seem to guide MS user towards comparing the development of her/his own state's INSPIRE implementation in time, but rather to comparing the indicator values from different member states. I thought we had agreed that comparison between different states was not to be the main goal of the Dashboard, but showing the the national progress in time (implementation is in the early stages, growing strongly, mature, stalled, deteriorating etc.)
  • The Save functionality creates JSON files which seem to me like serialisations (descriptions) for the UI components of the visible dashboard. I would have assumed I could have saved the shown data instead. This is bound to very confusing and not at all interesting for the users. The same applies to Load functionality. This could be a solution for the use cases for creating and managing national dashboards, but not for the casual end user.

Bugs / technical issues:

  • When I click at a country in any of the map components, or bar in the graph, the whole page becomes unresponsive (100% of the CPU). I have to close the whole tab/browser to use the browser again. I'm experiencing the same both with latest Chrome and Firefox on OS X Yosemite.

Missing/incomplete functionality (just as a reminder):

  • Import / export the harvested dashboard information in format suitable for submitting to the official INSPIRE reporting
  • An API for submitting the ancillary information by external applications (maybe something like an HTTP post endpoint with Dashboard user configurable api-key authentication and JSON data structure for submitting the values for given identified service, indicator and time period).
  • Support for the MS use cases for using the Dashboard as an easy-to-use tool for creating the yearly official INSPIRE reporting.

#4 Updated by Anders Rydén almost 6 years ago

Dear all,

I basically agree to most of the comments given by Ilkka. The prototype dashboard is not yet as user friendly as I would like it to be (not the developers fault, I must also emphasise). I have problems navigating within the dashboard even though I consider myself familiar with this type of applications. I also haven’t been able to extract all information I would like from the dashboard in its current state of development. Among other things to discuss, I think we also seriously have to discuss the UI as well as provide the developer with necessary input for further development of the UI. With this in mind, I am looking forward to some very interesting discussions these two days to come.

Regards
Anders

#5 Updated by Ilkka Rinne almost 6 years ago

I will do a quick draft for ancillary information update API to be discussed at the Copenhagen meeting. I'm reflecting the requirements from the perspective an application developer creating support for updating the usage analytics data (like the requests made for each service), but the end result should be usable for automatically updating the time series indicator data for any indicator we choose to be externally updatable.

A couple of questions immediately comes in my mind:

  • How does the external application identify the service for which it provides indicator data? Using it's INSPIRE ID from it's metadata record?
  • What should be the time granularity of the provided indicators? It the external application can provide the usage data on a monthly basis, should it upload the last month's data every month (add) or just update the total yearly value of the given indicator (replace)?
  • Is there any reason the require the update as a XML document instead of JSON? JSON would be simpler for the external application developers but a strict data format maybe the easier to formulate for an XML document.

#6 Updated by Ine de Visser almost 6 years ago

Dear all,

General;
I think we have with this tooling the basic functionality we want; a dashbord and tooling to generate the official monitoring report.
I agree with others that on this moment it's a bit userfrendly, but in potential it is there if you start fi with the INSPIRE dasbord for the last reference year 2013. Also the comparision between different years is there if the indicator trends are be extended with all indicators. Perhaps we should hide all funcionality to generate your own dashboard for "normal" users.

Questions;
-I am wondering how flexible it can be with "certain different dates" as we mentioned in several functional requirements.

(Technical) issues;
- Naming of the fieldnames should be the same as the metadata elements where possible
- The shades of green in the maps are not always to distinguish

Bugs;
-Search is working on the fieldnames as used in the table in the bottom.
The error message on a wrong field name still exists after a correct search. It has to be removed on each graph manualy.
-INSPIRE dashbord, reporting 2014 shows minimaps in IE 11 in chrome it's OK

Kind regards,
Ine

#7 Updated by Ilkka Rinne almost 6 years ago

See Gist page for the proposed ancillary information API in Github: https://gist.github.com/ilkkarinne/b5ba75a94787e66aa868

#8 Updated by Paul Hasenohr over 4 years ago

  • Description updated (diff)
  • Status changed from Proposed to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF