Admin / Languages and translations #5923
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* web/src/main/webResources/WEB-INF/data/config/index/records.json: Add fields langfre and anyfre with french analyzer.
records.json: Add properties lang... for different languages. copy_to to these properties.
* Remove schema for french only. * Add asciifolding in french for better support of accents * Update doc * Dispatch keywords in proper full text lang field.
* If records are in one language, the record language is used by default (and no options are proposed to users) * if records are in various languages, the following options are available: Languages are ordered by frequency in records. Languages proposed does not take into account templates. Language detection is made on the list of record's languages. The more languages you have, the more the language detection precision decrease. Catalogue administrator can define the language strategy to use by default in UI configuration: * queryBase: to adjust query * searchOptions.language: to display language options * languageStrategy Language strategies: * searchInUILanguage: search in UI languages eg. full text field is any.langfre if French * searchInAllLanguages: search using any.* fields (no analysis is done, more records are returned) * searchInDetectedLanguage: restrict the search to the language detected based on user search. If language detection fails, search in all languages. * forceALanguage: depending on user selection, force a language.
…n in batch editing.
…stead of based on catalogue content).
…re of language config).
Instead of configuring all the settings available for the user configuration,
only define the settings you want to change and apply that to the default configuration.
* Keep configuration as simple as possible
* Correct merge of settings by working on settings path instead of fuzzy merge (which was not combining well arrays or objects)
* Make migration easier
2 tabs are available to:
* configure using the classic form
* or configure directly in the JSON
On the JSON form, user can:
* Reset configuration to the minimum ie. `{}`
* Set the configuration to the complete config with all options (not
recommanded).
* Compare current config and the default and remove all options that are common.
To populate the configuration, user can choose among the set of all options computed from the default config.
JSON form also has basic autocomplete and basic snippets enabled.
* Update ace library
* Underscore replaced by lodash (to manipulate object by full path) https://github.com/lodash/lodash/wiki/Migrating
Those that can be initialized with and SQL scripts. Also fix PUT operation after JPA migration.
For end user, it is recommended to remove unused languages to keep admin form as simple as possible.
|
Just a small thing, this would be a nice icon for it: https://fontawesome.com/v4.7/icon/language (at least if it's available in the Font Awesome version GN is using) |
I don't see it https://fontawesome.com/v3.2/icons/ (we are using old versions of a number of libs ...). If you think something match better in 3.2 ? |
|
No, can't really think of one in |
User configuration / Easier config with overlay mechanism.
…nayre/core-geonetwork into fxprunayre-406-index-perfieldanalyzer
Merged
|
Added with #6188 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a new panel for managing database languages and translations.
For end user, it is recommended to remove unused languages to keep admin form as simple as possible.
Other fix: