DEEP

DEEP is developed as a simple Restful service, providing the list of available datalets (i.e., listing service) and the mapping among the visualization names and their relevant URL within the WC repositories. The system is online and is the base of the architecture of SPOD (http://deep.routetopa.eu/). Both the DEEP and the WC repository have been designed to be extensible: they can collect all the visualization requests so, as planned future work, they could also provide aggregated statistics on both users preferences and on data and their visualizations. For instance, the most popular datalet visualizations, most used datasets, most popular visualizations for a particular dataset, most visualised fields for a particular dataset, and so on. The DEEP main task are the listing services which provides a list of available dataset and the mapping between the visualization names and their relevant URL within the “datalets repositories”.

DEEP work cycle

The DEEP work cycle (see Figure 6) to include a WC in a Web page, comprises three main actors:

• The Client page that exploits DEEP-Client functionality;
• The DEEP (DatalEts-Ecosystem Provider);
• The Web-Component.

First, (1) the Client page send a request to DEEP for a specific WC. Then, (2) the DEEP responds with the information needed to inject the datalet into the page. Finally, (3) the Client retrieves the WC from the DEEP repository and include it into the page.