#547 closed enhancement (fixed)
Thesaurus language selection improvement
| Reported by: | heikki | Owned by: | heikki |
|---|---|---|---|
| Priority: | minor | Milestone: | v2.6.5 |
| Component: | General | Version: | v2.6.3 |
| Keywords: | thesaurus, editor, SKOS, keywords | Cc: |
Description
If you load an SKOS thesaurus in GeoNetwork, when you want to use it for picking vocabulary items to put in your metadata keywrods, you are presented with those items from the thesaurus that have a language attribute matching the current GUI language.
In some thesauri there may be many concepts with translations to only one even zero languages, though they may contain other elements for names or descriptive items that describe the items.
I think it is more user-friendly to present not only
<skos:prefLabel xml:lang="YOUR CURRENT GUI LANGUAGE">
items, but also newly invented
<skos:prefLabel xml:lang="#default">
items in case no match for the current GUI language was found for the item.
A thesaurus with many items insufficiently translated into <skos:prefLabel> elements can then easily be made more useful by creating <skos:prefLabel xml:lang="#default"> elements from whichever elements are available, before importing into GeoNetwork.
One example of this is the geonames thesaurus.
Change History (2)
comment:1 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 13 years ago
| Milestone: | v2.7.0 → v2.6.5 |
|---|
It turns out that searching for xml:lang="#default" is not possible with our Sesame searches, 0 results are returned. This may be because they check somewhere for valid values for the xml:lang attribute.
New approach is not to use "#default" for this, but "00". This works as expected.
Committed to trunk (rev. 7960) and 2.6.x (rev. 7961).