Wikivoyage talk:Cooperating with Wikidata/Archive 2013-2018

Wikidata

Swept in from the pub

Has anyone here looked into this Wikidata project and how it might be useful for Wikivoyage? They're concentrating on getting it set up for Wikipedia to start with, but after that it might be very useful for the lists that Wikivoyage uses. So someone updating a phone number on the English Wikivoyage would automatically be updating that phone number for all languages. Might be a good idea for people to start getting involved in figuring out what would need to be done, if that's not being done already. 86.44.163.139 22:53, 16 February 2013 (UTC)

I'm an admin here and on Wikidata, so I'm pretty familiar with both projects :) It's probably good to start thinking about, but it will be a while before it's deployed to non-Wikipedia sites, considering that we don't even have it working on 280 of the Wikipedia sites yet at all. --Rschen7754 23:25, 16 February 2013 (UTC)

I think someone will come up with a usefull way to make use of the data on wikidata in wikivoyage. Wikidata is more powerfull then most users realise. Carsrac (talk) 22:23, 17 February 2013 (UTC)

Can we start with basic stuff like population? That seems like the most primitive use-case for us, and will give us an opportunity to play. It is also something likely to be updates by our friends over at WP, so we can just forget about it, thus saving us time/effort. --Inas (talk) 23:18, 17 February 2013 (UTC)

quite extensive moves are now occurring at WP en of wikilinks - I think it is worth waiting and watching as to how that works. sats (talk) 23:59, 17 February 2013 (UTC)

Wikidata has a large enough volume of work to perform with just basic info on the large Wikipedia language versions, let alone extending Wikidata's capability to other projects and more extensive uses. Maybe we can set up a page like Wikivoyage:Working with Wikidata or Wikivoyage:Wikivoyage and Wikidata where we can collect ideas and, when the time comes, have a place where all ideas and proposals can be found for Wikidata users to view (and start working on) and for us to communicate with them. Since this is a cross-project and cross-language issue, where is the proper location to keep such discussion? Maybe we can discuss this here and when the time comes, start a page on Meta to formally discuss this with other WV projects. AHeneen (talk) 02:17, 18 February 2013 (UTC)

Someone has started a page for Wiktionary at Wikidata. Might be a good idea to get one set up for Wikivoyage. 86.44.163.139 09:29, 18 February 2013 (UTC)

Please, let's use Wikivoyage:Wikidata to brainstorm and coordinate what we might do on Wikivoyage with Wikidata, and possibly, following above Wikidata:Wiktionary example (but I've no other data on how Wikidata is organized) d:Wikidata:Wikivoyage (or d:Wikivoyage?) for what folks might do at Wikidata for or with Wikivoyage. I love names that are so short and obvious that I can type them without looking them up. --Rogerhc (talk) 05:27, 19 February 2013 (UTC)

Here's one nice application that has already been build on top of Wikidata. Not particularly useful for WV, but it show what can eventually be done. —Ruud 10:37, 18 February 2013 (UTC)

I have started a very basic Wikivoyage:Working with Wikidata. --Peter ^Talk 23:30, 20 February 2013 (UTC)

"In the coming year, the [Wikidata] team will be working on the further development and maintenance of Wikidata. This includes, among other things: [...] the possibility of deploying Wikidata in further Wikimedia projects, e.g. Wikimedia Commons or Wikivoyage." (http://blog.wikimedia.de/2013/02/20/the-future-of-wikidata/) —Ruud 12:42, 28 February 2013 (UTC)

Wikidata is coming! ... eventually

Swept in from the pub

According to m:Wikidata/Status updates/2013 06 07, the developers worked on "First steps towards being able to add sitelinks for the first sister-project (WikiVoyage)". --Rschen7754 19:56, 7 June 2013 (UTC)

Get geographical coordinates for listing items

One thing that would be fantastic: be able to have access to the geographical coordinates of any Wikidata item, not only the item related to the current page. For example, for a museum, we would be able to put in the page its coordinates (and Wikipedia link, and official URL…) automatically by giving its Wikidata ID. Unfortunately, this ability is not available (I don't know why, maybe performance). - Fabimaru (talk) 20:53, 20 March 2015 (UTC)

On May 19th we will receive the ability to do this :-) Syced (talk) 04:19, 14 May 2015 (UTC)

Fantastic! Thanks a lot to anybody made that possible. In the French Wikivoyage, we added a parameter "wikidata" to the listings (there is also a parameter "wikipédia"), though it is not used much yet as the current value it provides is quite limited. - Fabimaru (talk) 11:55, 15 May 2015 (UTC)

If you have the Wikipédia link, would there be any way for a robot script to look at la page de Wikipédia, find out which Wikidata item it links, and populate the "wikidata" field? K7L (talk) 14:44, 15 May 2015 (UTC)

It is possible and not really difficult, but it would have to be developed  :-) (I don't have time now to do it) - Fabimaru (talk) 21:30, 16 May 2015 (UTC)

Wikivoyage pages connected to (possible) wrong Wikidata items

Swept in from the pub

Hi, there are these article pages which are connected to disambiguation pages on Wikidata:

• Hepu -> village in Tibet
• Ludlow (Vermont) and St. Albans (Vermont) -> they deal about both a city and a town, which are on separate pages on Wikipedia
• Goring and Streatley and Warth and Schröcken -> they deal about couples of villages/towns, which are on separate pages on Wikipedia

Would you please deal with these apparent wrong connections? Thanks in advance :) --Superchilum (talk) 19:24, 12 April 2015 (UTC)

New York and New England use "town" the way other jurisdictions use "municipal township" - as a container municipality for rural areas, unincorporated suburbs and tiny unincorporated villages which would otherwise have no municipal government. If given a choice between a "town" and a "village", or a "town" and a "city", skip the town and take the village as the main community. K7L (talk) 01:09, 13 April 2015 (UTC)

There are also a few pages in Category:Pages linked to a data item for a disambiguation, where the WP page linked is identified on WD with a "disambiguation" attribute. Texugo (talk) 02:52, 13 April 2015 (UTC)

Goring and Streatley: I recommend creating a Wikidata page rather than using the Wikidata page of either Goring or Streatley. Syced (talk) 06:15, 13 April 2015 (UTC)

Unfortunately, the "other projects" links in the sidebar only give space for one Wikipedia link from the Wikivoyage article, which doesn't work out well if a large rural area has a single page here and multiple articles on WP. K7L (talk) 17:19, 13 April 2015 (UTC)

Which is an issue, that I fear cannot be fixed, can it? Because while Wikipedia might deem a hamlet of 500 people "notable", this here is a site dedicated to travel and unless the hamlet happens to have a big airport right next to it or is of importance for travel by itself it won't (and shouldn't) get an article any time soon, but its (the hamlet's) existence might be worth a word or two in a "go next" section or region article... Hobbitschuster (talk) 21:37, 13 April 2015 (UTC)

If it has a town hall, as an incorporated municipality it's a notable, distinct entity for a WP article. If it's on the US Census, it gets an article. There was an infamously-huge spam incident in which a w:user:Rambot dumped pretty much the entire (now-outdated) US 2000 census, hamlet by hamlet, into WP as a series of village-level stub articles. That spam seems to have stopped by 2005, but the damage has been done. If back in 2000, 0.34% of the 588 people in w:La Fargeville, New York were of Asian descent, Wikipedia has archived that crucial fact for posterity. That's what, two people? K7L (talk) 22:00, 13 April 2015 (UTC)

And at the same time the German Wikipedia deleted articles on subjects such as Darth Vader... Which of course generated a lot of bad press and Internet backlash... But enough of this. How (if at all) can the issue at hand be solved? Hobbitschuster (talk) 22:08, 13 April 2015 (UTC)

Which could be the solution for the articles dealing with pair of destinations? And regarding Hepu, which is the correct item on Wikidata (does it exist?)? --Superchilum (talk) 09:43, 24 April 2015 (UTC)

Page banners and Wikidata

Swept in from the pub

So, I just discovered that Western Finger Lakes has a banner image. Yay! But why didn't I see it added in my watchlist? Oh, because when it was added back in September 2014, it was added to Wikidata. The wikicode in our article still shows the default banner. Now, I do have Wikidata changes on in my watchlist, but I can't tell edits that add or change a banner from edits that add a language link or change the Korean spelling or adjust the geolocation, not without viewing the diff of every single edit. Does anyone else see this as a problem? (Potentially, this loophole could be used to perpetrate undetected image vandalism.) Should we consider a moratorium on Wikidata banners? Powers ^(talk) 01:50, 25 May 2015 (UTC)

I actually stopped using WikiData for banners for this reason. I think the more realistic problem would be someone updating banners with mediocre images rather than vandalism.

Still as we contemplate more integration with WikiData for other things (temperature readings, currency exchange rates, geo-locations etc) then it would be highly desirable to track all WikiData changes related to an article. --Andrewssi2 (talk) 02:02, 25 May 2015 (UTC)

Wikidata is no worse than Commons for this. Do you get a notification when anyone uploads a new (possibly worse) version a banner stored on Commons? Are non-important changes (categories, spelling in the Korean description - no offence to Koreans) filtered out from the notification feed? Syced (talk) 05:14, 25 May 2015 (UTC)

Property-specific Wikidata notifications would be great indeed. This is very feasible (at least as an RSS feed), and I suspect some might have implemented that already, I will have a look. Meanwhile, I don't think there have been many tragic incidents so far, and to me it does not sound like a good reason to abandon the huge benefits of sharing banners between languages. Creating banners is hard-work. Multiplying this work by 17 would be a huge pity (17 languages). Syced (talk) 05:14, 25 May 2015 (UTC)

I agree with Syced on this subject. -- Ryan • (talk) • 05:34, 25 May 2015 (UTC)

This is going to become even harder to monitor if we start using Wikidata to fill fields in individual {{listing}}s. Paris/1st arrondissement is d:Q161741, one Wikidata item to watch if changing it affects the article, but if individual venues with {{listing}}s have corresponding Wikidata items, changing d:Q19675 (musée du Louvre) or other individual-venue records could affect the article in some manner. d:P969 (located at street address) should be the address on "rue de Rivoli" (au moins que je sache) but one stray edit on Wikidata could send the traveller somewhere else (hopefully not to the loo instead of the Louvre?). That sort of thing is hard to catch, as it runs cross-wiki. Indeed, the same issues exist with Commons - blindly tag {{listing|image=museum.jpg}} onto something and expect to wonder why the result becomes nonsensical if someone on Commons replaces the photo of the museum you wanted with some other museum in some other faraway land. I think Wikipedia was taking images that appeared in promotions for featured articles on its front pages, copying them to the local wiki and protecting them as "insurance" against this sort of mishap, but on a limited scale.

It's not a major issue at this point, but any proposals for a technical solution to the problem will need to recognise that a page could be pulling "shared resources" from multiple places, and not just the one matching Wikidata entry. K7L (talk) 13:01, 25 May 2015 (UTC)

Instead of doing the work 17 times, using Wikidata means that 18 communities (each Wikivoyage plus Wikidata) are watching the changes. However, it would be nice to have a feed that shows the changes we're (individually and collectively) interested in. WhatamIdoing (talk) 18:20, 25 May 2015 (UTC)

I agree with wikidata being a huge benefit for the banner effort, but since the implementation I've had concerns about the patrolling of new page banners, mainly regarding the correct size, but also quality. It's really hard to spot wrongly sized banners added locally, but impossible if wikidata item is used. Then it can only be found by a matter of chance. I'd welcome any technical possibility to be able to track newly added wikivoyage banners at wikidata. Danapit (talk) 21:48, 25 May 2015 (UTC)

There is a genuine need to get a watchlist notification whenever something from Commons/Wikidata is modified that actually impacts one of the pages you watch. I think it is time we raise a Phabricator issue about this, I am pretty sure Wikimedia developers will agree it is important. Meanwhile, anyone willing to try and code an RSS-based temporary solution? I a quite busy rigt now with other open source software, but that sounds like a fun project to create :-) Syced (talk) 04:38, 26 May 2015 (UTC)

Phabricator issue for adding relevant Wikidata events to an article's watchlist Very Wikipedia-focussed at the moment so I added a comment to expose our point of vue.

Phabricator issue for adding relevant Commons events to an article's watchlist This issue is marked as solved, so please test it and add a comment asking for reopen if it does not actually work.

Please subscribe to these issues and bring your ideas (diplomatically) thanks! Syced (talk) 06:45, 26 May 2015 (UTC)

I do not understand how to add Commons events to my watchlist. The topic on phabricator does not say anything about that, and I never heard of such a possibility. --Alexander (talk) 16:52, 26 May 2015 (UTC)

A minor note on Commons: images there are not supposed to be replaced with completely different images that fit the same name. There are issues with maps and graphs, where there sometimes are edit wars regarding a file with a generic name (Map_of_Kosovo.jpg & similar), but museum.jpg should not be replaced. It could be moved, with a bot changing the reference on affected projects (and thus insuring we thereafter do not depend on the generic name). I do not know how well images are watched over there, but I have seen only a couple of cases where an image has been replaced in a problematic way. --LPfi (talk) 09:11, 26 May 2015 (UTC)

Certainly, it happens. Image:Santa.jpg used to be a picture of Satan Claus, now it redirects to a team photo of a soccer (football) squad at Image:Santa Eufemia team.jpg - which looks weird if one looks at an old version of a page like https://en.wikipedia.org/w/index.php?title=Area_code_867&oldid=7193002 (as originally created) which expected the other image at that name. The same issues arise if someone monkeys with the template designs. K7L (talk) 12:29, 26 May 2015 (UTC)

That file was deleted as copyvio and later replaced by another, also deleted as copyvio, at least five times. With such a generic name this is hardly very exceptional. The reference to the file should however be removed by a bot quite quickly after deletion. Sure, it is confusing in the history, but it does not affect the current version of pages. (And good images should tend to have good names, avoiding the issue.)

For the current pages the more common problem is probably when an image is overwritten (not deleted) with a similar one, while the caption mentions something specific for the original image. This should not happen for photographs (according to policy), and does not happen too often in my experience.

--LPfi (talk) 15:24, 26 May 2015 (UTC)

Huh? Santa.jpg used to be a picture of "Satan Claus"? XD ϒpsilon (talk) 16:21, 26 May 2015 (UTC)

Yes, and what happens very often is that good images eligible to be used on Wikivoyage under fair use are removed from Commons without any notifications. This is horrible. --Alexander (talk) 16:52, 26 May 2015 (UTC)

While non-free images can be used here under free use provisions, they cannot be stored on Commons. They can be temporarily restored to allow for transferring them to projects allowing fair use images. If you see the bot removing the reference to a deleted image, you can ask for this procedure (Commons:Undeletion requests). --LPfi (talk) 09:42, 27 May 2015 (UTC)

Grat point, LPfi. Back to wikidata, I am quite helpless with it. Is there a way to watch changes in a certain property (wikivoyage banner) for any item, not just those one has on a watchlist? Danapit (talk) 11:28, 27 May 2015 (UTC)

Yes, I can, and nobody will respond because these images are such terrible copyvios, and most of the Commons users consider their obliteration as the most important task of their life. Fortunately, we have one Commons admin in our ruvoy team, so all issues are easily solved on the personal level, but those images that we don't take care of are simply lost for the community. --Alexander (talk) 13:38, 28 May 2015 (UTC)

My request for a way to watch individual Wikidata properties got a reply: "for the watchlist, this should already work exactly as you described. If it does not, please file a separate ticket about that." Syced (talk) 09:03, 28 May 2015 (UTC)

Link articles with Wikidata

Swept in from the pub

Most articles in this Category:Banner missing from Wikidata are not linked properly with Wikidata. Could someone do it? I can't import those banners into Wikidata until this get fixed. See more => [1] Thanks. --Kizar (talk) 18:03, 9 January 2016 (UTC)

Wikidata again

Swept in from the pub

Working with Wikidata is an idea that's been kicked around since 2013, but never quite caught on. So far, it's used widely for pagebanners and interwiki links, but not much else. Retrieving info for individual {{listing}}s or {{quickbar}} fields has been proposed but not implemented; a couple of languages (de, fr) provide a d= or wikidata= field in their listings (which might display a clickable link) but don't seem to use it to run database lookups.

Pity. Ultimately, the idea was that Wikidata could be used to look up listing fields (lat, long, name, address, image...) by some automated means (maybe a 'bot script or a listing editor function; they also might be of use on dynamic maps).

I've made an attempt to update the list at d:Wikidata:Wikivoyage/Resources#Properties for listings to match Wikidata properties to individual {{listing}} fields in various languages. (Some have extra fields we don't use here, like star ratings 'estrellas' in Spanish or wi-fi availability in French. I haven't looked at any of the languages with non-Western character sets. Certainly, now that these are templates instead of WT-style tags, new fields are popping up in many individual-language editions and they don't always match across languages.)

Many of the most common fields already have a corresponding Wikidata property. The rest have been proposed for creation and are stranded at various points in the process. Our hotel/motel/B&B checkin/checkout times are stranded at d:Wikidata:Property proposal/Pending#Awaiting time type with precision second, seemingly for want of a Wikidata data type for a standalone "time of day" with no date attached. Many of the other fields (hours, pricerange...) are languishing at d:Wikidata:Property_proposal/Sister projects#Wikivoyage either for lack of examples or because someone wants to force a structure on an item where the underlying data is widely variable (such as hours= which are different every day of the week, vary seasonally and are different for different pieces of the same establishment (hotel with restaurant and bar might keep pouring drinks long after the kitchen closes for the night).

These need feedback while they're still open for discussion. Could you look at d:Wikidata:Property proposal/Sister projects#Wikivoyage and d:Wikidata:Property proposal/Pending to comment or add any information that's missing from the proposals? K7L (talk) 20:10, 16 May 2016 (UTC)

Migrating quickbars to Wikidata doesn't seem to be that complicated. One of the reasons for the lack of progress is the out-dated Module:Wikibase. I think we should import w:Module:Wikidata and all its dependencies. Does anybody have experiences with mass-importing lua modules? -- T.seppelt (talk) 20:32, 16 May 2016 (UTC)

Some notes:

wikidata= as a field in Template listing - already exists

The interworkings of a Lua Module either standalone or with templates etc. can be very tricky - Lua Modules generally get processed after a page has been processed... In many cases it is necessary to use "safesubst:" which forces the Lua Module to do its work and finalize results before the page gets processed. (The #invoke for the Module essentially no longer exists - just the results)

It is generally possible to build initial template codes we all know and love which in turn would require being edited further by hand.

Lua Modules have been used to create "geo" templates - retrieving lat/long coordinates etc.

Agree that Lua Modules have not been used or implemented in wikivoyage to a great extent.

Wikidata itself is incomplete and its properties wanting -- ie. description property for an article in Wikidata for example is "a city" - hardly enough for a listing or quick box - Larger content descriptions for listings would not exist - many properties one might desire for a quickbox are also missing such as electricity.

Who (bot?) is going to find and add the Wikidata identifier (Qnnn) for each listing's "wikidata=" field.

Lua Modules do have machine processing limits - something else be aware of.

Though many things could probably be accomplished with Lua Modules and Wikidata, I would suggest achieving one goal at a time. Matroc (talk) 17:01, 17 May 2016 (UTC)

The list of Wikidata fields to match the most common WV templates (listing, marker, quickbar, fr:Info Ville, Info Parc, Info Region, geo and mapframe) is d:Wikidata:Wikivoyage/Resources#Properties for listings. Many already exist; fr:'s version of quickbar (Info Pays) already defaults a few fields to the Wikidata record if they're not specified locally. Electricity (as a quickbar field) is missing but has been proposed at d:Wikidata:Property proposal/Sister projects#Wikivoyage, along with many of the other "missing" fields. That still leaves the issue of how to populate all of these fields, if and when they're created; "hours" and "price" are likely to be the problem children as they're currently unstructured free-form text which won't translate easily. Much of the information currently in Wikidata was copied there by 'bots, usually harvesting it from template fields in the corresponding Wikipedia article's info box. Certainly {{listing}} is going to be more difficult, largely because d:wikidata:arbitrary access is "expensive" in server time and much data in our existing listings is in plain-text fields which would need to be translated before they could be re-used elsewhere. It might be possible to add the Wikidata item with some sort of automated script if there's a unique identifier which could be used to match the entries; for instance, a local telephone number matches a number in a listing in the same city in some other-language Wikivoyage, which has wikipedia= linked from its listings, and from that language's WP we can find a d:Q##### record. Not easy, and most of our listings simply don't have (and won't have) Wikidata entries unless and until they get enough notability to get an article in at least one Wikimedia project (likely the WP for that country's home language). That makes using this for quickbars much easier than getting the listings. Then again, many of the same arguments could have been made to state that getting (lat, long) co-ordinates into individual listings is a mammoth task and we're nowhere near having a locator map for every destination. Indeed, but one must start somewhere. K7L (talk) 15:46, 18 May 2016 (UTC)

I'm working on a Wikidata lookup that could be integrated into the listing editor that would work the same as the search typeahead (type a few letters, suggested results show up). As you've noted there is concern about having too many Wikidata items in use on a page as improper usage could result in excessive lookups and parsing, but I would expect lookup performance to improve as Wikidata is more widely used, and we could do some basic testing to see if something like lat/long lookups using {{#property:P625|from=Q3699364}} was currently feasible. -- Ryan • (talk) • 17:07, 18 May 2016 (UTC)

Wonderful! Really looking forward to that Wikidata lookup field in the listing editor :-) Syced (talk) 07:21, 19 May 2016 (UTC)

Sounds great. It would be great to have some progress here. -- T.seppelt (talk) 17:37, 9 October 2016 (UTC)

Deleted listings on Wikidata

Swept in from the pub

Some of our listing were recently deleted from Wikidata and our current featured article got broken listings. I dropped a message on Wikidata, but I assume more discussion will be needed to save our listings on Wikidata and keep them alive over there. -- DerFussi 07:04, 1 March 2017 (UTC)

That is concerning. Although we can technically look at related WD changes in 'Recent Changes', in practice it is very hard to spot if someone wants to change a WV relevant item over there. --Andrewssi2 (talk) 08:51, 1 March 2017 (UTC)

So is there anyway to see from the wikidata page if a wikidata reference is used within a listing? I suspect not. On English Wikivoyage if the wikidata parameter has an entry we create an anchor on that page that has the QID number, can be used for hyperlinking between article on the site and between Wikipedia and WIkivoyage, but you cannot use this on Wikidata entries and not sure you would want that effort. --Traveler100 (talk) 09:27, 1 March 2017 (UTC)

It seems, it can be checked ([2])... Fortunately the items are restored meanwhile. We use WD extensively. The mentioned article Nanxun fetches all data directly from Wikidata. Even the hotel's phone numbers comes from Wikidata. You can not find all the information in the article itself. I want to get in touch with the developers to get some tools that help to see article related changes on Wikidata. -- DerFussi 21:15, 1 March 2017 (UTC)

Articles without Wikidata page

Swept in from the pub

The articles in this Category:Banner missing from Wikidata don't have a page in Wikidata. If anyone has time to fix it will be appreciated. --Kizar (talk) 23:46, 6 January 2017 (UTC)

Hola Kizar, nice to hear from you again! And thanks a lot for running your tool. My answer is late because I was travelling all around Spain :-) Would you mind running your tool again so that I can create the missing Wikidata items? Also, would you mind publishing the source code of your tool? That would allow Wikivoyage to survive even in case you disappear ;-) Thanks a lot! Syced (talk) 10:07, 9 February 2017 (UTC)

I did Syced. About the code, I don't have time now to clean up, but I will publish it soon. --Kizar (talk) 15:05, 5 March 2017 (UTC)

Thanks! :-) I processed one third already. Syced (talk) 14:03, 6 March 2017 (UTC)

Kizar: 100% done :-) Syced (talk) 12:29, 8 March 2017 (UTC)

coordinates ?

Coordinates on wikivoyage sometimes point to the main entrance of a large scale location, whereas Wikidata usually use coordinates of the center of that location. Can there be an option not to use the WD coordinates, or to manually choose whether or not to consolidate WV and WD coordinates? TaBaZzz (talk) 14:45, 10 April 2017 (UTC)

Yes, I agree, while I find the function to update fields from wikidata is really very handy and helps a lot, sometimes I wish there would be way to choose which fields to update. Often also the website linked in wikidata is not the best to use here. Drat70 (talk) 08:25, 11 April 2017 (UTC)

A question on this: When stuff on WD is updated, does it then automatically update on WV? Ceever (talk) 20:16, 11 April 2017 (UTC)

WV pulls data from WD: website, lat/lon, Wiki article, Image. TaBaZzz (talk) 11:55, 12 April 2017 (UTC)

I really don't feel, this is the right way. Meanings and semantics are not always the same, just connecting and inheriting things is dangerous. Who does guarantee, the editors on WD put as much effort into information as editors on WV do. Or who is the one verifying whether the connection is even right. We put too much work into this for it to just being spoiled. I would rather see a soft link here, so whoever wants to see either or both information, can do so with the right tool or script.

Therefore I would not be in favour of this hard connection of WV and WD. Let's rather have a solution like the link to WikiPedia.

Ceever (talk) 18:30, 12 April 2017 (UTC)

Sorry, but I am still a little confused about the simple wipeout of excellent GPS tagging we have done here on WV. Who guarantees the coordinates of WD have undergone the same quality standards?

Is this now consensus that we loose all this valuable work?

Ceever (talk) 20:23, 15 April 2017 (UTC)

Better using Wikidata in the future

Swept in from the pub

I think there are quite some things we might want to use Wikidata for. Unfortunately, I know next to nothing about how wikidata works, but here are three ideas that pop to my head.

1. Currency conversions - up to date exchange rates for currencies; if there is a reason why wikidata can't/doesn't store them we will have to continue doing this locally and manually
2. Climate data - I think there is no reason for our climate data not to be synchronized with what WP and WD know.
3. Visa policy - articles like this one are much more detailed and up to date than our country get in sections - the basic information they contain is visa y/n and sometimes visa under a,b or c conditions and can be displayed as a fairly readable map - having this in one place (and I think that's what WD is for) enables us to benefit from more up to date lists instead of the probably outdated handwritten lists from 2012.

What do you think? Are there other things we could and should ask the people at Wikidata to integrate and implement so we can use them? Hobbitschuster (talk) 21:55, 9 March 2017 (UTC)

@Hobbitschuster: Filling in infoboxes. For what it's worth, I posted to the Project Chat about currency conversion but it went nowhere. —Justin (koavf)❤T☮C☺M☯ 22:17, 9 March 2017 (UTC)

I'm in favour. I haven't been here long enough to know why we don't do this already. Ground Zero (talk) 22:51, 9 March 2017 (UTC)

@Ground Zero: The bottlenecks are mostly time and expertise. And to some extent, creativity. —Justin (koavf)❤T☮C☺M☯ 23:00, 9 March 2017 (UTC)

As well as whether the information to be mined from WD is accurate, complete, up-to-date and properly linked which unfortunately it is not in all cases from my observations. -- Matroc (talk) 03:54, 10 March 2017 (UTC)

If you'd like to know more about Wikidata (with practical examples), then Asaf's recorded workshop is a good place to start. WhatamIdoing (talk) 07:01, 10 March 2017 (UTC)