Docs updates

OPSILab · Oct 15, 2018 · b669ba3 · b669ba3
1 parent e8baf20
commit b669ba3
Showing 1 changed file with 7 additions and 7 deletions.
diff --git a/docs/source/manuals/administration_gui.md b/docs/source/manuals/administration_gui.md
@@ -42,13 +42,13 @@ The default metadata related to a catalogue are:
 
 By selecting the type of a catalogue, the administrator may have to insert additional configuration parameters in order to federate it.
 The available catalogues types that an administrator can create are:
-- CKAN: this type of catalogue does not require any additional configuration parameters; 
-- DCATDUMP: in order to federate this type of catalogue, the administrator has to provide a dump file or a dumpURL together with the specific DCAT Profile (e.g. DCAT-AP or DCAT-AP_IT); 
-- DKAN: this type of catalogue does not require any additional configuration parameters;
-- ORION: in order to federate the Fiware ORION Context Broker, additional configuration parameters are mandatory. If the ORION CB API endpoint requires authentication, the administrator has to insert the *client_id*, *client_secret* and the *oauth2Endpoint* in order to manage the OAUTH2 authentication and authorization flow. Moreover, the administrator has to upload a file with the datasets' metadata definition. Every distribution of each dataset must contain a valid ORION CB query and, optionally, the *Fiware-Service* and *Fiware-ServicePath* headers. 
-- SOCRATA: this type of catalogue does not require any additional configuration parameters;
-- SPARQL: in order to federate this type of catalogue, the administrator has to upload a file with the datasets' metadata definition. Every distribution of each dataset must contain a valid SPARLQ query and, optionally, an array of formats (e.g. csv,json,xml,etc...). 
-- WEB: this type of catalogue retrieves the datasets' metadata by scraping a website. For this reason, it is required that the administrator adds a so called *sitemap* that contains the navigation parameters of the website and the mapping with DCAT-AP fields.
+- **CKAN**: this type of catalogue does not require any additional configuration parameters; 
+- **DCATDUMP**: in order to federate this type of catalogue, the administrator has to provide a dump file or a dumpURL together with the specific DCAT Profile (e.g. DCAT-AP or DCAT-AP_IT); 
+- **DKAN**: this type of catalogue does not require any additional configuration parameters;
+- **ORION**: in order to federate the Fiware ORION Context Broker, additional configuration parameters are mandatory. If the ORION CB API endpoint requires authentication, the administrator has to insert the *client_id*, *client_secret* and the *oauth2Endpoint* in order to manage the OAUTH2 authentication and authorization flow. Moreover, the administrator has to upload a file with the datasets' metadata definition. Every distribution of each dataset must contain a valid ORION CB query and, optionally, the *Fiware-Service* and *Fiware-ServicePath* headers. 
+- **SOCRATA**: this type of catalogue does not require any additional configuration parameters;
+- **SPARQL**: in order to federate this type of catalogue, the administrator has to upload a file with the datasets' metadata definition. Every distribution of each dataset must contain a valid SPARLQ query and, optionally, an array of formats (e.g. csv,json,xml,etc...). 
+- **WEB**: this type of catalogue retrieves the datasets' metadata by scraping a website. For this reason, it is required that the administrator adds a so called *sitemap* that contains the navigation parameters of the website and the mapping with DCAT-AP fields.
 
 ### Edit/Delete a Catalogue