Difference between revisions of "ICT technical guidelines"
From MyWiki
(→Metadata catalogue services (CS)) |
|||
| Line 1: | Line 1: | ||
| + | = Technical references for services = | ||
| + | This section contains the technical references about interfaces, versions, operations, etc. required at server or client levels. | ||
| + | Indeed, the details of these technical references are based on previous EU projects (e.g. eENVplus, GeoSmartCity) available at the deliverables public access pages. | ||
| + | Technical references are divided in three main sections: | ||
| + | * client: set of requirements related to client software (desktop or web) directly used by human beings to search/discover, view, access energy-related data | ||
| + | * server: set of requirements related to server components, to be made available at partners’ level | ||
| + | * interface: set of requirements related to standard interfaces and protocols to be considered at client and/or server side levels to guarantee interoperability | ||
| + | |||
| + | The detailed list of technical specifications is available in the separate page [[ICT technical guidelines]]. | ||
| + | |||
| + | == Metadata catalogue services (CS) == | ||
| + | |||
| + | |||
| + | '''Table 8 - Technical details for metadata catalog services - client''' | ||
| + | |||
| + | {| class="wikitable" | ||
| + | | style="text-align: center;" | '''DESCRIPTION''' | ||
| + | |- | ||
| + | | style="font-style: center;" | CS clients shall allow users to search the catalogue either through hierarchical browsing, or by expressing queries with a combination of parameters defined by the user through the controls (edit boxes, select boxes, etc.) available in the discovery GUI | ||
| + | |- | ||
| + | | style="font-style: center;" |CS clients shall enable the user to filter search results by selecting / setting a value for the following features: | ||
| + | * INSPIRE themes (e.g., Addresses, Administrative Units, etc.) or other topic categories | ||
| + | * Country | ||
| + | * Resource type (e.g. dataset, layer, service, series) | ||
| + | * Service type (e.g. discovery, view, download, invoke, transformation, other) | ||
| + | * Spatial resolution | ||
| + | * Original language | ||
| + | * Access constraint | ||
| + | * Responsible organization | ||
| + | * Timestamp | ||
| + | * Defined timeframe (decade, year, or month, based on “Creation date”, “Temporal extent”, “Publication Date”, “Revision Date”, or all dates) | ||
| + | * Bounding box (geographical constraint) | ||
| + | * Geographical name (based on gazetteer) | ||
| + | |- | ||
| + | | style="font-style: center;" | CS client shall allow users to sort the results by various criteria such as name and date or geographic ranking, which is based on a similarity function between the area of the rectangle of the found items and the geographical constraint. | ||
| + | |- | ||
| + | | style="font-style: center;" | In the case of discovery of viewable layers, CS client shall allow users to visualise them on a geographic viewer (View Service clients), which enables the user to browse these layers over a background map (pan / zoom) and switch on/off the visibility of the layers. | ||
| + | |- | ||
| + | | style="font-style: center;" | CS clients shall allow users to add and combine layers to the map (geographic viewer) in the following ways: | ||
| + | * from a search of the Geoportal’s Catalogue Service | ||
| + | * from local (cached) resources | ||
| + | |- | ||
| + | | style="font-style: center;" | CS Client shall perform automatic multi-lingual keyword suggestions in the GUI (concept of interactive discovery and auto-completion) given by the internal vocabulary and code-list, using GEMET and additional thesauri (e.g. eENVplus Thesaurus Framework) | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall be able to return a list of identifiers for corresponding features for a request expressed in an OGC query language (aka “Discovery.GetRecords” in CSW specification). | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall be able to return associated meta information instances of features selected by user, managed by the catalogue and returned by a previous query (getRecordById). | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall provide a mean that allows harvesting resources over the network (Manager.Harvest). | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall provide the ability to push information into the catalogue. This operation receives the meta information to be stored and returns information about the update of the catalogue (Manager.Transaction). | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall accept an area of interest (geographic zone definition) and a time period in input parameters | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall accept the lower limit and the maximum number of results by catalogue | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall check metadata inserted, updated, or harvested. | ||
| + | |- | ||
| + | | style="font-style: center;" | CS server shall allow search in distributed catalogues. | ||
| + | |- | ||
| + | |} | ||
Revision as of 13:47, 23 February 2018
Technical references for services
This section contains the technical references about interfaces, versions, operations, etc. required at server or client levels. Indeed, the details of these technical references are based on previous EU projects (e.g. eENVplus, GeoSmartCity) available at the deliverables public access pages.
Technical references are divided in three main sections:
- client: set of requirements related to client software (desktop or web) directly used by human beings to search/discover, view, access energy-related data
- server: set of requirements related to server components, to be made available at partners’ level
- interface: set of requirements related to standard interfaces and protocols to be considered at client and/or server side levels to guarantee interoperability
The detailed list of technical specifications is available in the separate page ICT technical guidelines.
Metadata catalogue services (CS)
Table 8 - Technical details for metadata catalog services - client
| DESCRIPTION |
| CS clients shall allow users to search the catalogue either through hierarchical browsing, or by expressing queries with a combination of parameters defined by the user through the controls (edit boxes, select boxes, etc.) available in the discovery GUI |
CS clients shall enable the user to filter search results by selecting / setting a value for the following features:
|
| CS client shall allow users to sort the results by various criteria such as name and date or geographic ranking, which is based on a similarity function between the area of the rectangle of the found items and the geographical constraint. |
| In the case of discovery of viewable layers, CS client shall allow users to visualise them on a geographic viewer (View Service clients), which enables the user to browse these layers over a background map (pan / zoom) and switch on/off the visibility of the layers. |
CS clients shall allow users to add and combine layers to the map (geographic viewer) in the following ways:
|
| CS Client shall perform automatic multi-lingual keyword suggestions in the GUI (concept of interactive discovery and auto-completion) given by the internal vocabulary and code-list, using GEMET and additional thesauri (e.g. eENVplus Thesaurus Framework) |
| CS server shall be able to return a list of identifiers for corresponding features for a request expressed in an OGC query language (aka “Discovery.GetRecords” in CSW specification). |
| CS server shall be able to return associated meta information instances of features selected by user, managed by the catalogue and returned by a previous query (getRecordById). |
| CS server shall provide a mean that allows harvesting resources over the network (Manager.Harvest). |
| CS server shall provide the ability to push information into the catalogue. This operation receives the meta information to be stored and returns information about the update of the catalogue (Manager.Transaction). |
| CS server shall accept an area of interest (geographic zone definition) and a time period in input parameters |
| CS server shall accept the lower limit and the maximum number of results by catalogue |
| CS server shall check metadata inserted, updated, or harvested. |
| CS server shall allow search in distributed catalogues. |
