[07:28:17] <ESM^>	 something is wrong when using quickstatements to add P217 (inventory number) + value + reference + qualifier
[07:28:20] <ESM^>	 screenshot: https://ibb.co/kEYgav
[07:28:37] <ESM^>	 and nothing has been added to the item, actually
[07:28:40] <ESM^>	 thoughts? thanks!
[07:44:57] <ESM^>	 gah, it seems it's something about my browser, nevermind
[12:34:35] <wontfixit>	 Hi, folks! I played around with wikidata dumps a little bit and notice data inconsistency, for example for spouses. Is it known issue?
[13:07:38] <sjoerddebruin>	 Lydia_WMDE: the new PDF print feature of MediaWiki seems to be deployed, it doesn't work for Wikidata items though. Should I hide it with CSS?
[13:27:06] <Lydia_WMDE>	 sjoerddebruin: i thought we had done that in the past -.-  yes please
[13:33:31] <sjoerddebruin>	 Lydia_WMDE: maybe a better solution should be found, but until then: https://www.wikidata.org/w/index.php?title=MediaWiki%3ACommon.css&type=revision&diff=498208509&oldid=466494383
[13:34:51] <nikki>	 wontfixit: what sort of data inconsistency?
[13:40:01] <wontfixit>	 nikki: Marriage start and end time may be different for participants of same marriage. For example Brad Pitt and Angelina Jolie.
[13:40:22] <Lydia_WMDE>	 sjoerddebruin: thanks :)
[13:47:22] <nikki>	 wontfixit: ah... it is known that the data can get out of sync (that's apparently by design). we have constraints on the property talk pages (e.g. https://www.wikidata.org/wiki/Property_talk:P26 has a "symmetrical" one) but I don't think it checks whether the qualifiers are the same
[13:48:34] <sjoerddebruin>	 good idea for a query (@WikidataFacts ^)
[13:48:51] <nikki>	 it sounds like a good idea for an improvement to the constraints too :P
[13:50:50] <nikki>	 I wonder if there are cases where a property should be symmetric but the qualifiers could be different
[13:51:04] <nikki>	 or if symmetrical implies the qualifiers are the same too
[14:04:47] <nikki>	 I came up with http://tinyurl.com/yblyvfxg for p26
[14:05:09] <nikki>	 I tried a slightly simpler query without the ?p and ?ps variables but that just times out o_O
[14:14:54] <nikki>	 ah, P1038 is symmetrical with different qualifiers
[14:15:02] <nikki>	 well, same qualifier, different value
[14:22:16] <Harmonia_Boulot>	 hmm
[14:22:55] <Harmonia_Boulot>	 can we precise authorized value for property constraint? Like "all subclasses of this Qid *except* this subclass"?
[14:28:26] <nikki>	 it might work with "conflicts with" but I'm not sure if it uses subclasses or not
[14:29:22] <Harmonia_Boulot>	 well no
[14:29:39] <Harmonia_Boulot>	 conflict with is about other properties used on the same item
[14:29:48] <Harmonia_Boulot>	 not the same thing at all
[14:30:48] <nikki>	 you can pick which properties/values are considered conflicts though
[14:31:12] <nikki>	 do you have an example? that might help
[14:31:29] <Harmonia_Boulot>	 so i could say that P735:Roman given name is in conflict with the use of P735?
[14:31:34] <Harmonia_Boulot>	 that seems really strange
[14:32:17] <Harmonia_Boulot>	 well, Roman given names should never be used as values for P735, because they are to be used with the property "Roman given name"
[14:32:50] <Harmonia_Boulot>	 but they are regularly considered as a subclass of given name, so as acceptable values (which they aren't)
[14:34:30] <nikki>	 hm... I think what I had in mind wouldn't work there
[14:34:48] <Harmonia_Boulot>	 doesn't matter
[14:34:55] <Harmonia_Boulot>	 I don"t have errors so frequently
[14:35:04] <Harmonia_Boulot>	 so it's not a problem
[14:35:07] <Harmonia_Boulot>	 thanks
[14:35:11] <nikki>	 a complex constraint would probably work though
[14:35:24] <nikki>	 :/
[15:56:32] <DanielK_WMDE>	 frimellem Lydia_WMDE: https://pdfs.semanticscholar.org/e625/9db8c6f0db9cd1601a960b4abc4653cc5bec.pdf