 to Wikimania. I'm Stefan from Germany. I think some people know me better as Fussi, that's my nickname. Der Rieft from my second name. I want to give you a short introduction to our wiki voyage bubble and how we use wiki data in our project. So as a start, just some information about myself. I started editing in 2005 and then I created with some other friends the wiki voyage project and I led it to the wiki media foundation in 2012 and since then we are part of the family and there are two contacts because I want to introduce some of our modules that use wiki data and if you have a question you can contact these two guys at the bottom, that's me and my colleague Roland and if you have a question you can drop us a line. A very very short look back because maybe somebody, not everybody knows it, that before we became a family member we had an own database created when we run the wiki voyage project for ourselves. It was called location database. It's of course not that big as wiki data is now, but it was quite useful. This database saved the geographical hierarchy, the inter wiki links and the coordinates and that time and of course this database died when we moved our project to the wiki media servers. Why wiki data? Yes of course we were anxiously waiting for the database because we have many information that are just short facts or short values and like addresses, phone numbers, coordinates, opening hours, features of place, crime data and a very special two wiki voyages that we are not urgently need sources or references so we can live with articles without it and one of the big advantages that we are small communities so if somebody adds some information we can see it easily in all language versions so that's a big good support for us. To give you an overview of how we use wiki data there are some statistics we have articles that have 350 database accesses in one article. In the past it happens that we got time outs when our articles were passed but at the moment the performance is quite good. You see two of our articles which use wiki data quite heavily so you can see we have in Vienna 250 templates called wika that all use wiki data and so you have some information how much we use it. This is just a screenshot of one article it's a small article but I have marked all the information that comes from wiki data in one article so you may have a good overview of a visual impression how we use it and maybe you can see that's the half of the information are not directly in the article but that are fetched from wiki data. Yeah of course there are some challenges that we faced in the past or still face so of course stamina is not that's normal people have to fix it it can happen that values are deleted or changed sometimes unintentionally but I think the community and some bots can fix it. The second challenge is the changes of data models we used wiki data from the beginning so it can happen that you write a module that works today and tomorrow it doesn't work properly because the data model and the information change so I wrote an as an example I wrote a module that find to every place on this earth the first level province of a country and meanwhile there are additionally additional properties that I have to process that makes the whole process a little bit more difficult second example is the osm in the past we could save only relations but later on osm entities were possible but just with the prefix but now we have separate properties for every information so wiki data is changing permanently and if you write a module you have to sometimes improve your modules as well so sometimes it can be quite difficult to find the right value we have ranks like preferred normal and deprecated ranks but sometimes the preferred value is not the right value it can happen that's a value this is has a preferred rank but it has an end date there are qualifiers starting date or end date so you have you can have a value that is preferred but actually outdated so what how to handle this there are many decisions to make how you handle these data and yet these qualifier that's just called off but in the meantime it shouldn't be used any longer so sometimes if you want to fetch some information from wiki data you have to run analysis how is it saved in wiki data so that's why we notice that we need several modules depending on the data type we want to get from wiki data so I wrote modules for every data type even simple string values can be difficult as you can see the postal code of the Malaysian province Sabah is saved as a range value just just a normal string and if you look to Chiang Mai you have a big list and this this big list can make your info boxes blasting so we had to create a module that fetches strings and you can in this example you can give a limit of values and if the the count of values is bigger than the limit then this module creates a range value so you can see in our info box on the left side the huge list of Chiang Mai is reduced to such a range value different problems can can happen if you want to have numbers the problem can be especially if you are have information from us they have are not in the value in the unit that you want sometimes values are saved in miles or feet and the german wiki voyage wants to have meters and kilometers and so I have implemented automatic conversion you can say which unit you want and if it's not saved on wiki data and that unit it takes it makes a conversion for you and then it you get your information get displayed in the unit you want to have like the aria and altitude um the next feature are our get item modules so if if you have an item on wiki data is as a value so you you have the option to see just the text like the bonus program of Chiang Mai or if you want you can get a link provided and the link that is provided has a priority the first priority is that the link goes to the german wiki voyage if an article exists if not it uses the german wikipedia and if this one fails it goes over to the local wikipedia so if you have an article about Thailand it would go to the Thai article in that case yeah we have special modules for getting images to be put in the info boxes um if you want these uh flags or coat of arms or seals you can easily just use the first letter if you write in your info box ah okay thanks um so you can just use in the parameters the first letter and then it will show us coat of arms or flags or something and special features are the location maps you can choose for the whole wiki which kind of maps you want to see so there is a priority list of collections and in the german wiki voyagers decided to use the green ones the green autographic maps but just by changing the item in this this one parameter so you can change all articles uh at the same time and display another location map and we have a special module that's climbing up the geographical hierarchy on wiki data and it determines the first level province of every town in in every country so and we have a few modules that are designed just for one purpose because some information are more more complex like uh web links so we add the we add automatically the language of the website and the module tries to fetch the best one for your purpose so in this priority you can fetch the german website or english one and if you don't find it you get a local one and there are of course some very special entities like uh like capitals special example is south africa that has three different capitals so it's formatted and fetched and you get even then the the kind of capital um all our modules um can be used within the text and it has an option to be a part of the info boxes so you can just start an info box with an open opening template and then just add one of these modules and get your content displayed if you use a parameter and uh and leave the value out then it's fetched from wiki data but you can give also a local value which is displayed in that case instead of wiki data but in the background there's a comparison with wiki data so the result of this comparison is is showed in i i made some uh screenshot of the hdml so you can see that the result is shown in in classes and if you use a gadget so you can color the information also it's shown in the tooltip so if you open an article and see it in red or green then you know if it's green the the value on wiki data is the same as a local wiki so you can just remove it in a local wiki or if it's red you can decide um should i fix wiki data or is my local value the wrong one so i can just delete it as well and use wiki data in future and because we use these classes so maybe in the next step could be to develop some gadgets or features that use these classes and make for you a form that uses the api of wiki data to to change the information easily so you don't have to go over to wiki data and it's easier for newbies just to add wiki data from here it could be the next step that's why we have implemented it and i think it's uh quite useful so on the biggest module is our wikard it provides information about all places that are in articles restaurants museums temples whatever this module creates all the information it creates the pin on the cartographers map it it it it creates micro formats for external tools to save automatically the addresses of phone numbers it formats the phone numbers that you can easily call or Skype to this place and there's an info box that you can create with just the button that's quite useful on the mobile version when you when you are in a foreign town and just jump into a taxi it creates for you this this text for the taxi driver so the article recognizes okay i'm an article in thailand so it creates even in Thai language please take me to this place so i think it's quite useful when you are on travel just to show the taxi driver yeah take me there please so wishes of course uh this is our experience we have some wishes meantime sometimes um the the interface is quite difficult especially for newbies is still i have to say quite nerdy so what we originally would need is a coordinate picker you still have to copy it from anywhere in inside the form and even if you see you have different inputs for for date values that result in different values on wiki data so if you try to type gen it it's just created with date if you uh why january yeah it's the german one it's just the months so and the date output is this localization but if you want to type in local values it's not recognized so the german october is showed to you but you cannot input it and sometimes it's quite tricky if you copy it from from other websites there are non-breaking spaces that are not recognized as really spaces so maybe there is still some space for improvement and if you type after every single letter it's a lot of internet traffic if if you have a low internet it can be yeah you need some patience patience to to input your data okay so and of course i think these wishes are from several communities it would be very nice to to edit wiki data from outside or from the local wiki i don't know how the current developments are on that side and of course mobile editing is not i've tried it on my way here and actually it's not really possible isn't it yeah that would be cool if if you can add your data mobile on mobile so the next problem is we have a lot of information that we use regularly so if you if you use a model several times you have an access to internet several times there are many information that are needed all the time in one article so it's like calling codes iso codes and phone area codes at the moment we do we make a sparkle request and then we copy it to an editor format it as a lure table and then save the lure table in our local wiki so i feel easier access to this information it would be cool to have a tool i don't know if some exist i ask around that can do it automatically create a lure table and save it maybe as a cron drop or a bot i don't know if a bot exists at the moment but at the moment it's it's more manual work to copy this information but to reduce the access it's quite useful to have some permanent information your local wiki and one thing that would be useful is some better functions so some lure functions we have at the moment just get the best statement but if if you remember the problem at the beginning the best statement is not the current one always maybe that it would be useful to have a lure function that gets the most recent value and other informations like the last edit date is not available via lure just via apa there are some wishes we have at the moment currently yeah and constraints i saw i i think it it's it's there are more discussions about constraints do we have some more or or should we have some more or not we would like have some more but i know and not not everybody wants and of course more data one one data that we miss is climate data you want we would like to create this climate diagrams but at the moment we have no information about that on wiki data and it would be useful to have some i got the question in the meantime do do you have an idea how for how client communities could coordinate better with the wiki data community regarding data model changes oh at the moment not really it's quite difficult you have to to to browse around many discussion sites on the properties yeah an idea at the moment not i have to admit but there is lydia maybe you know something about it i have some ideas one of the things that came up earlier in a different context also modeling challenges was to do one of those community days that we've been doing in the past around data quality and like geographical data uh to do one for data modeling uh where people like uh you from wiki world could come um and and bring up a challenge and discuss that with the community so that is something that i'm uh gonna bring up with the team and see if we can make that happen thanks and i think yeah i got the sign the time is over and thank you very much too thank you and see you in one of the next sessions around thank you