Support multiple languages for describing an entity
Summary: Support multiple languages for describing an entity
Description: Currently the registry just supports 1 language for specifying an entity's metadata (Node, Organization, Dataset, Network, ..). In the future we would like to support multiple languages for describing an entity.
Created: 2012-06-01 10:37:06.44
Updated: 2013-12-16 17:50:27.629
Resolved: 2013-12-10 16:54:45.151
Created: 2013-12-10 16:54:45.182
Updated: 2013-12-10 16:54:45.182
Multiple languages for an entity not required.
Created: 2013-12-11 11:13:06.694
Updated: 2013-12-11 11:13:06.694
What do you mean by 'not required'? Has the reported reconsidered?
This year when we start focusing on the mobilization of metadata, we will find that there are several catalogues that are maintained in several languages. The BioCASE catalogue supported several languages, and the derived ones also support different languages. for example, in GBIF Spain:
We should of course talk to this people, but I think we should at least leave that door opened for them.
PS: A comment of the side: how do the 'won't fix' issues appear in summaries? As solved or as pending?
Created: 2013-12-11 12:10:23.898
Updated: 2013-12-11 12:10:23.898
The Registry database layer for example, currently supports metadata for a dataset in a single language.
You raise an important point, that publishers are making their metadata available in multiple languages. Indeed, next year we are making it possible for IPTs to publish dataset metadata (subset of fields) in multiple languages, but GBIF will only index the primary language.
To index and then show multi-language metadata in the Portal, represents a huge undertaking beyond the scope of this issue, which is the registry itself.
Addressing your PS, the won't fix appears as resolved.
Created: 2013-12-11 12:19:09.048
Updated: 2013-12-11 12:19:09.048
Thanks to you, Kyle. It's more clear now.
But wouldn't be then the course of action to link this issue to a wider one about showing multilanguage metadata in the portal as you mention, instead of marking it as 'won't fix', and then losing this requirement?
Created: 2013-12-11 13:25:11.137
Updated: 2013-12-11 13:25:11.137
It definitely would be the right course. I'm not aware of such a wider issue existing though. Are you? Maybe [~firstname.lastname@example.org] knows if a user story exists to show dataset metadata in the portal in multiple languages?