Talk:Linguistic Literature GEO Search

From MPDLMediaWiki
Jump to navigation Jump to search

Linking of ISO language codes to geographical coordinates[edit]

database service[edit]

How should this database service look like? Is it enough only to publish the table online? --Kristina 09:42, 15 January 2010 (UTC)
Yes, a basic table is sufficient. However, the table should be accessible for an automatic query. --MCysouw 20:38, 7 February 2010 (UTC)
*** Bitte noch auf die Hauptseite einarbeiten und hier löschen ***

table with geographical coordinates for all ISO 639-3 codes (Cysouw)[edit]

Michael Cysouw has a large table with geographical coordinates for all ISO 639-3 codes. It is available here File:Geo.zip. This table consists of the following columns:

  • NAME_OLD: nur ein String zur identifikation, kan ignoriert werden
  • NAME_NEW: ich weiß nicht, was der Unterschied zu NAME_OLD ist
  • ETHNOLOGUE: der alte drei-Buchstaben code des Ethnologue, in Kapitalen
  • ISO 639-3: die neuene ISO codes, hier scheinen ein par zu Fehlen
  • LAT: latitude
  • LONG: longitude

To be checked:

  • are all ISO 639-3 codes available? --> Kirstin
  • what is going on with the missing ISO 639-3 fields in this table?
could we imagine this as a CoNE extension?--Natasa 11:12, 10 March 2010 (UTC)

CoNE

just a note: like some of the other data sets already in cone, iso-639-3 is also not a static resource, i.e. code points can (and do) change. the same is true for the coordinates, and in this case even worse, because there is no defined change process associated with it. anyway, when we do put more and more data like this in cone, we'd have to come up with a concept of how to maintain this data.--Robert 11:45, 10 March 2010 (UTC)
as of next CoNe (and PubMan) version - CoNE allows vocabulary moderation and editing for particular users. What is usually done in such cases: iso-639-3 vocabulary is static to CoNE in sense that these are modified when official iso-639-3 vocabulary is modified. GeO Codes will be additional vocabulary (related to iso-639-3) but fully owned by LDH Administrator for example. In this case LDH Administrator only modifies LDH specific data - and not iso-639-3 vocabulary data. --Natasa 12:34, 11 March 2010 (UTC)
i'm less concerned about the technical feasibility of vocabulary maintainance than about who is actually going to do it.--Robert 12:48, 11 March 2010 (UTC)

Special search page to search geographically[edit]

That is interesting as it means that this service can not be part of the blog, as it should also work with other databases that provide ISO 639-3 codes. --Kristina 09:42, 15 January 2010 (UTC)
Indeed: this page is technically not part of the LDH. It is a separate service that uses the information from the LDH. --MCysouw 20:53, 7 February 2010 (UTC)
*** Bitte noch auf die Hauptseite einarbeiten und hier löschen ***
How could a search look like? First the user has to choose two databases (one providing the ISO 639-3 codes and one providing the geo-locations. Then there must be an entry mask where the user can define different sorts of search queries. E.g. A) can be defined via a point (coordinates) and a radius (distance in km). When you sort this results based on the distance, B) is answered, etc. --Kristina 09:42, 15 January 2010 (UTC)
User chooses database with literature (currently only LDH is available) and a database with geo-locations (currently only our own table is available). Then the user enters a location, either as coordinates, or through clicking on a map. Results offered as list of nearby literature or view on a map.
*** Bitte noch auf die Hauptseite einarbeiten und hier löschen ***

International Organization for Standardization

Coordinated Universal Time

Control of Named Entities

Publication Management

Language Description Heritage

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Talk:Linguistic_Literature_GEO_Search&oldid=52343"