Midleading

Previous discussion was archived at User talk:Midleading/Archive 1 on 2018-11-06.

I don't think that edits like , are correct. CAS Common Chemistry may give you a 'Get detail failed: Detail not found' error, but this service does not contain all the CAS numbers from CAS Registry, it contains a selection of CAS numbers, about 0,5 million from over 200 million entries.

In other words: CAS number is correct, but CAS Common Chemistry does not have it (but CAS Registry, which is not a free service, do).

Okay, I accessed CAS SciFinderⁿ and confirmed these CAS numbers are on CAS REGISTRY®.

Hi there! I see that you use that script to create properties. I added it to my JS, but couldn't find out how it works. Could you explain how me to use it? Thanks,

When you use this tool, a link named "PropertyCreator helper form" will appear in page tools in a property proposal. Clicking on it will bring you to a form where you fill in information from the property proposal. You may preload the form which helps you fill in the form. Check everything is correct, then click "Create" button. Wait until the property is created by checking out your contributions, and finally update the property proposal, notify the users and edit the new property. I didn't have a user JS. I always load it from the browser console when I need to use it. You will find information printed by this tool in the browser console as well.

Thanks :)

Hi, you marked Wikidata:Property proposal/beforehand-afterward owned by as "ready" but did not created those 2 properties yet. Can you create them and ping me and I will do the rest?

@Jarekt:  Done beforehand owned by (P11811) afterward owned by (P11812)

不能接受通俗的別名嗎。你可以刪掉請不要回退，會提醒我……

E.g. Q117272628. Thanks for your contributions though.

You are doing excellent work with not notable stuff when adding content to our Wikidata:Requests_for_deletions! But it would be extra good if you would notice the creator (e.g. like I did at User talk:Sulejerry). Such notiying would easifying administrators' work considerably

Sure.

I noticed you made this edit, undoing my change to instance of (P31) marking the property as a qualifier. Could you say more about why? JesseW (talk) 15:00, 20 September 2022 (UTC)

I have not seen a property which is not an instance of "Wikidata property (related to ...)"

But

⟨ Wikidata qualifier (Q15720608)    ⟩ instance of (P31) ⟨ Wikidata property (Q18616576)    ⟩

is true. It's a perfectly valid subclass.

The whole "Wikidata property related to X" hierarchy is redundant in a complicated way with other ways of sorting properties; I'm planning (eventually) to write up an RfC suggesting fixes for it. You can see the existing discussion here, if you are interested: Wikidata:Project_chat/Archive/2022/09#We've_got_nearly_200_uncategorized_Properties

I had to revert your edits in rac-salbutamol (Q410358) once again. This item is about a racemate, i.e. a mixture of two enantiomers. Most probably there will never be an illustration suitable for this item. This illustration would be correct for (RS)-salbutamol (Q93346928), such illustrations are not really useful in Wikidata, as it does not represent a specific stereoisomers that can be depicted in 3D, each stereoisomer can have a 3D model of itself. Also, this and this do not illustrate the racemate, but the pharmaceutical products, so the first one is now in Ventolin (Q47522282) (I think there is no item for the second one yet). Wikidata is not a Wikipedia, an illustration must be specific to the concept of the item and not just be related to it in some way.

What about related image (P6802)?

If there is no suitable image in image (P18), chemical structure (P117) or molecular model or crystal lattice model (P8224), then yes, related image (P6802) may be used. I have no objections to the use of this property in chemistry-related items like in this situation, that's what it was created for after all (only personally I find it really strange that it was created at all in a project like Wikidata).

您好，标题能否转换为中文惯用？如淳熙三山志/卷42转换为淳熙三山志·卷四十二。

这些项目基本没用，要不是因为连一个标题都没有我也不会理它，我可以把下一批的改过来，以前的怎么样就怎么样吧。

以后的有可能会在维基百科显示，如果有空建议最后把以前的也改了。

刚好现在维基数据机器人全部暂停了（看最近更改选机器人），我把这一批关闭了。

例子：

https://zh.wikipedia.org/wiki/%E7%8E%8B%E7%BE%B2%E4%B9%8B#%E5%BB%B6%E4%BC%B8%E9%98%85%E8%AF%BB

等維基數據機器人开放後晉書的項目將會被命名，您可查看。特別奇怪的是有很多四庫全書版和四部叢刊版的子頁面也新建了項目，您覺得這些項目怎樣命名好？

都按中文常见的格式“淳熙三山志·卷四十二”如何？标题里不带“四部丛刊本”。邮件联系？

您说的问题实际上背后是一个难题：有些书有过个版本，原文对应的属性main subject (P921)是在哪个版本标注，还是都标注（都标注太麻烦）？百科条目对应的described by source (P1343)标注哪个版本？

我想到的解决方案很简单，那就是在维基文库选一个有扫描对应的版本，覆盖当前的主版本，扫描版本用人工智能标点，这样还能一起解决标点的原创问题。

所以我现在的目标就是创建一个自己的bert训练集，这样就能把page页面都标上标点了。

維基文庫如果已經新建了頁面並保存了主版本，還是用維基文庫現在的頁面吧，畢竟維基文庫又不是只有我們兩人，別人這麼多年的貢獻也不能浪費。現在各個版本都要鏈接edition or translation of (P629)到主條目上，主條目可能有維基百科或者維基文庫頁面，也可能什麼都沒有，但是我反對把版本和主條目混淆起來。

我们应该把提议写成文档放在维基文库。

维基数据帮助页现在基本还是空的，可以写到那里。

請停止使用zh-classical語並把現在有的都移動到lzh語。我建議用zh-hans語和zh-hant語放简体繁體中文，不要都堆在別名裏面，可以減少日後查項目時候出現的問題。

Tracked in Phabricator
Task T257415

您好，zh-classical语对应文言文维基百科。

lzh语才是文言正确的代码，而且在这里也会显示为文言，zh-classical语是在lzh代码出现之前为了维基大典的创立而新建的，但是维基数据出现的时候已经不需要了，这个代码迟早都会被删除。

還有好多“#N/A”，可能需要您的機器人清理一下了，希望以後不要有這種事故了。

谢谢！

您好，能否帮忙写一个脚本，输入名称，查询去世时间（或者没有去世）？

建议分成两个步骤，先查明编号（QXXX），再查询去世时间。查明编号可以去维基百科。然后访问 https://query.wikidata.org/sparql?query=SELECT%20%3Fa%20WHERE%20%7BOPTIONAL%20%7Bwd%3AQXXXX%20wdt%3AP570%20%3Fa%7D%7D 可以查出date of death (P570)的值，或者如果没写就得到空值，其中QXXXX换成具体的编号。注意，需要设置User Agent才能从这个网址获得资料。