User talk:Multichill/Archives/2016/August

Notability policy

Wikidata:Notability is not applicable to non-item pages, so "Does not meet the notability policy" is not a reason to delete pages like Wikidata:Wikimania 2016 presentations. Although I don't oppose the deletion, next time you should provide a better reason, and if necessary, reach a consensus to delete such pages.--GZWDer (talk) 12:38, 10 July 2016 (UTC)

@GZWDer: hmm, my intention was to only delete the not notable items. Must have missed have overlooked this one. No point in undeleting it now I guess.... Multichill (talk) 17:58, 12 August 2016 (UTC)

Drag'n'drop update

Hi, could you update the gadget from User:Magnus Manske/dragref.js again? I got a report that API editing is slow, and could reproduce it occasionally, so I'm adding a "in progress" banner, so that people know it's running. Thanks! --Magnus Manske (talk) 14:19, 12 July 2016 (UTC)

@Magnus Manske: took a bit longer, was on a break, but now it's updated. Check out MediaWiki:Gadget-DragNDrop.js. Multichill (talk) 17:57, 12 August 2016 (UTC)

Spongebob

list of SpongeBob SquarePants shorts (Q6351333) is not an episode, but a wikimedia list of episodes. The Anexio: triggered me. Edoderoo (talk) 21:59, 7 August 2016 (UTC)

@Edoderoo: Ja klopt, ik moet nog even door User:Multichill/SpongeBob SquarePants episodes heengaan en de boel wat op orde brengen. Het lastige is dat een episode uit meerdere segmenten bestaat die dan weer allemaal een eigen naam hebben. Dat wordt puzzelen. Multichill (talk) 18:00, 12 August 2016 (UTC)

Inventory number on Q20271014

finaly I got an answerd - see: https://www.wikidata.org/wiki/User_talk:Villy_Fink_Isaksen#Inventory_number_on_Q20271014 --Villy Fink Isaksen (talk) 17:43, 12 August 2016 (UTC)

Single value constraint on p1246

I've reverted your readdition of a single value constraint to patent number (P1246) because it is incorrect for the reasons I explained at Property talk:P1246 yesterday. If you disagree please discuss there. Thryduulf (talk) 19:17, 16 August 2016 (UTC)

I responded over there. I did a big clean up of external-identifier properties which has missing constraints. I expected some properties to pop up that are of the wrong type. Multichill (talk) 19:46, 16 August 2016 (UTC)

as promised, a pie chart :)

• : cat (Q146)  

• : instance of (P31)  

SELECT ?item ?itemLabel 
WHERE 
{
  ?item wdt:P31 wd:Q146.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

[1]

--Yurik (talk) 00:06, 17 August 2016 (UTC)

That's pretty cool Yurik! Some tests:

• : cat (Q146)  

• : instance of (P31)  

SELECT ?item ?itemLabel 
WHERE 
{
  ?item wdt:P31 wd:Q146.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

[2]

• : cat (Q146)  

• : instance of (P31)  

SELECT ?item ?itemLabel 
WHERE 
{
  ?item wdt:P31 wd:Q146.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

[3]

Look at the source. I used urlencode here, but the template should probably take care of that. Would this also work for other types of charts? Multichill (talk) 16:16, 17 August 2016 (UTC)

Single value for Mérimée ID (P380)

Hi,

I'm not sure the single value constraint is a good idea for Mérimée ID (P380). Most monuments have several ids (see what I wrote on the talk page Property talk:P380 beack in 2013).

Cdlt, VIGNERON (talk) 13:06, 17 August 2016 (UTC)

Hey VIGNERON, I went to all the properties of type external-id and added missing contraints because for many properties constraints were missing. When I look at the long list I wonder some things:

• Did two databases ("Monuments historiques" & "Inventaire général du patrimoine culturel") get mixed into one property?
• How come one object has multiple id's? How does that work?

Multichill (talk) 16:27, 17 August 2016 (UTC)

Hey,

• indeed, several similar concepts like (including but not limitated to) "Monuments historiques" (MH) and "Inventaire général du patrimoine culturel" (IGPC) are mixed in the Mérimée database (maybe we should we have three properties for the same database based on the id prefix ?).
• Mérimée Ids are about protection, but an object can be protected multiple times (in time or in space) ; where Mérimée see two objects, Wikidata may have only one item (and vice versa sometime Mérimée has one ID for two objects). Examples: Immeuble, 4 place du Parlement (Q22102118) is only one building but for an unknown reason Mérimée decided that's two MH (maybe because there is two cadastral parcel...), on the other way around, Mérimée has only one id for two groups of stones two kilometers apart (so we have three items : Pierre courcoulée and cordon des Druides (Q17984083), cordon des Druides (Q1132337)} and Pierre courcoulée (Q2093334)). And about MH and IGPC, almost all MH are IGPC too, so technically all MH should/could have at least two ids (but most people don't care about IGPC, beggining with the Mérimée database itself which have only 10 or 20 % of the IGPC). That's why I think we should remove this constraint.

Cdlt, VIGNERON (talk) 08:26, 18 August 2016 (UTC)