Difference between revisions of "Fusion Fame Mapper Configure"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:FFM Install]] | [[Category:FFM Install]] | ||
| + | |||
| + | '''New in Regnology Release R1.1.0.00 July 2024<br>''' | ||
| + | |||
| + | The site config file now includes additional lines to enable you to set colours (for example the banner). | ||
| + | |||
| + | { | ||
| + | "ServicesAPI" : "http://localhost:8080/FusionRegistry/ws/fusion/info/product", | ||
| + | "Locales" : ["en", "fr"], | ||
| + | "BrandingStyle": { | ||
| + | "background":"#9fd3c7", | ||
| + | "color":"white" | ||
| + | } | ||
| + | } | ||
| + | Note that you can use a hex code or text. | ||
| + | |||
| + | '''Previous Versions''' | ||
| + | |||
Fusion Fame Mapper (FFM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax. | Fusion Fame Mapper (FFM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax. | ||
| Line 19: | Line 36: | ||
The browser_lang_[locale].json file contains a map of property name to human readable label, for example: | The browser_lang_[locale].json file contains a map of property name to human readable label, for example: | ||
| − | "menu. | + | "menu.famemapper.dataflows" : "Mapped Dataflows", |
The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FFM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata. | The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FFM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata. | ||
Latest revision as of 01:01, 1 July 2024
New in Regnology Release R1.1.0.00 July 2024
The site config file now includes additional lines to enable you to set colours (for example the banner).
{
"ServicesAPI" : "http://localhost:8080/FusionRegistry/ws/fusion/info/product",
"Locales" : ["en", "fr"],
"BrandingStyle": {
"background":"#9fd3c7",
"color":"white"
}
}
Note that you can use a hex code or text.
Previous Versions
Fusion Fame Mapper (FFM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.
siteconfig.json
Defines where the API will find the connected Fusion Registry and defines which Locales are supported and generates a language picker in the User interface. For example:
{
"ServicesAPI" : "http://localhost:8063/FusionRegistry/ws/fusion/info/product",
"Locales" : ["en"]
}
Adding additional locales Add the appropriate code as show below
"Locales" : ["en", "he", "ru"]
browser_lang_en.json
The browser_lang_[locale].json file contains a map of property name to human readable label, for example:
"menu.famemapper.dataflows" : "Mapped Dataflows",
The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FFM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata.
