Changes between Version 8 and Version 9 of MultilingualMetadata
- Timestamp:
- Jul 3, 2009, 5:23:21 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MultilingualMetadata
v8 v9 1 1 = Multilingual editing = 2 2 3 || '''Date''' || 2008/0 8/13 ||3 || '''Date''' || 2008/07/03 || 4 4 || '''Contact(s)''' || fxprunayre || 5 5 || '''Last edited''' || [[Timestamp]] || 6 || '''Status''' || draft||6 || '''Status''' || Motion proposed || 7 7 || '''Assigned to release''' || to be determined || 8 8 || '''Resources''' || Done in geocat.ch sandbox || … … 10 10 == Overview == 11 11 12 Adding the support for multilingual metadatas. For ISO based standards, all the gco:CharacterString elements and their translation can be stored in !GeoNetwork. This also allows editing mulitilingual metadatas. 13 Add multilingual metadata support in view mode and editing 12 Adding the support for multilingual metadata. For ISO based standards, all the gco:CharacterString elements and their translation can be stored in !GeoNetwork. This also allows editing mulitilingual metadatas. Add multilingual metadata support in view mode and editing. Use Google translation service to suggest translation in editing. 14 13 15 14 === Proposal Type === 16 15 * '''Type''': GUI Change, Module Change 17 16 * '''App''': !GeoNetwork 18 * '''Module''': SchemaLoader, Data Manager, Metadata Import, Lucene Index, Search Interface17 * '''Module''': Data Manager, Editor (XSL changes mainly) 19 18 20 19 === Links === … … 24 23 25 24 === Voting History === 26 * Vote proposed by X on Y, result was +/-n (m non-voting members). 27 28 29 == Motivations == 25 * Vote proposed by Francois on Y, result was +/-n (m non-voting members). 30 26 31 27 32 28 == Proposal == 33 29 34 Allow multilingual editing in GeoNetwork. One metadata record define 30 Allow multilingual editing in GeoNetwork. One metadata record define: 35 31 * one main language (using gmd:language element) 36 * n other languages (using gmd:locale element) 32 * n other languages (using gmd:locale elements) 33 34 === Editing mode === 35 A multilingual metadata template is added to default installation. 36 37 In editing mode, each multilingual elements are composed of: 38 * text input 39 * language selection list 40 By default, the selected language is the GUI language if language is defined in the metadata. 37 41 38 42 [[Image(editor-multilingual.png, 400px)]] 39 43 44 Optionnaly, Google translation service is defined. Translation could be suggest to the editor using the small icon right to the language selector. The translation convert the default metadata character string in the current selected language. Google translation service limit to 5000 characters. Other translation service could be pluged in here if needed. 45 46 [[Image(editor-multilingual-google-small.png, 400px)]] 47 48 === View mode === 40 49 In view mode, according to GUI language : 41 50 * if GUI language is available in the metadata, the element is displayed in this language 42 51 * else the elemenet is displayed in metadata default language. 43 52 44 Then multilingual content need to be indexed in lucene. 53 This behaviour is also applied to dublin core output for CSW services. 54 55 === Indexing === 56 By default, full text indexing is applied to all fields. Multilingual content is indexed for the any search criteria. 57 More clever indexing mechanism could be implemented in lucene (see MultilingualIndexMechanism). This is not part of this proposal. 58 45 59 46 60 === Backwards Compatibility Issues === 47 61 * Only ISO compliant 48 49 62 50 63 === Implementation === … … 78 91 79 92 80 In the editor any gco:CharacterString could be multilingual. The gco:CharacterString is in default language, the other PT_FreeText elements has to use a locale declared in the metadata document. 81 82 === Index === 83 One index by language is created and specific language analyzer could be define (eg. FrenchAnalyzer, GermanAnalyzer provided by Lucene). 84 Lucene index is stored in WEB-INF/lucene directory : 85 {{{ 86 lucene 87 +-- nonspatial_eng 88 +-- nonspatial_fra 89 +-- nonspatial_deu 90 }}} 91 92 Metadata indexing is done in default language using index-fields.xsl and multilingual content using language-index-fields.xsl which will extract all fragments to be stored in index. 93 94 More details on indexing mechanism MultilingualIndexMechanism . 95 96 === Search === 97 Search is done using a MultiSearcher (ie. in all index) and the index corresponding to GUI language is "boost" to be on top. 98 A duplicate filter filter search result in order to not to have duplicate in results as one record will appear in more than on index. 93 In the editor any gco:CharacterString could be multilingual but an XSL template is defined to exclude element which should not be multilingual (eg. ISBN, ISSN). The gco:CharacterString is in default language, the other PT_FreeText elements has to use a locale declared in the metadata document. 99 94 100 95 == Risks == 101 96 102 97 == Participants == 103 * List of participants and role (if necessary) in current GIP 104 98 * Francois 99 * Jesse 100 * swisstopo (support)