-
Notifications
You must be signed in to change notification settings - Fork 7
Home
The ckanext-multilang CKAN's extension provides a way to localize your CKAN's title and description contents for: Dataset, Resources, Organizations and Groups. This extension creates some new DB tables for this purpose containing localized contents in base of the configured CKAN's locales in configuration (the production.ini file). So, accessing the CKAN's GUI in 'en', for example, the User can create a new Dataset and automatically new localized records for that language will be created in the multilang tables. In the same way, changing the GUI's language, from the CKAN's language dropdown, the User will be able to edit again the same Dataset in order to specify 'title' and 'description' of the Dataset for the new selected language. In this way Dataset's title and description will automatically changed simply switching the language from the CKAN's dropdonw.
The ckanext-multilang provides also an harvester built on the ckanext-spatial extension, and inherits all of its functionalities.
Some extra functionalities are added, such as:
-
Title and Description of: Dataset, Resources, Organizations and Group can be localized simply editing or creating a new of these elements from the CKAN's Admin GUI.
-
The ckanext-multilang provides also an harvester built on the ckanext-spatial extension, and inherits all of its functionalities. With this harvester, localized content for Dataset in CKAN can be retrieved form metadata that contains the gmd:PT_FreeText XML element. For example the XML fragment below:
<gmd:PT_FreeText> <gmd:textGroup> <gmd:LocalisedCharacterString locale="#GER">Autonome Provinz Bozen</gmd:LocalisedCharacterString> </gmd:textGroup> </gmd:PT_FreeText>
provides a localized text for the GERMAN locale. The 'locale' xml attribute must respect the following sintax: {# + 'locale string'}. A mapping between CKAN and the harvested locales must be provided from the harvest configuration in order to respect CKAN's strings locales.
You will have to provide to the harvester the harvesting URL, which will be the same as the CSW endpoint: e.g.:
http://yourdomainname/yourservice/csw
Below a sample configuration to use for the purpose multilanguage purpose:
{
"ckan_locales_mapping":{
"ita": "it",
"eng": "en"
}
}