are you aware that this has been dead for 2 years, it is still being edited
About this board
Welcome to Wikidata, ChristianKl!
Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!
Need some help getting started? Here are some pages you can familiarize yourself with:
- Introduction – An introduction to the project.
- Wikidata tours – Interactive tutorials to show you how Wikidata works.
- Community portal – The portal for community members.
- Contents – The main help page for editing and using the site.
- Project chat – Discussions about the project.
If you have any questions, please ask me on my talk page. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.
Previous discussion was archived aton 2016-08-31.
Yahoo! Japan Talent Database ID (P3284)
The fact that the database is dead, doesn't mean that the ID isn't valuable.
so what about the formatter URL, doesn' that need to be changed,and the dead links in en wikipedia
and all the wikidata linked pages.
The links in Wikipedia are Wikipedia's issue and depend on Wikipedia templates instead on Wikidata.
As far as the formatter URL goes, the value is correctly marked as deprecated.
do you also add the archive as a formatter ?
Feel free to add that link.
i was able to do p_3303 before they locked me out for vandalism,
it needs to be marked in some way, deprecated p_31, Q_280943, p_2241, Q_208219
and something that turns off the p_3284 blue link. on pages like Q253882 where the 136 is gone ?
Structured Data feedback - structured licensing and copyright
Structured Data feedback - Depicts statements draft requirements
A slide presentation of the draft requirements for depicts statements on file pages is up on Commons. Please visit this page on Commons to review the slides and discuss the draft. Thank you, see you on the talk page. -- Keegan (WMF) (talk) 21:20, 7 August 2018 (UTC)
I'm reaching out to thank you again for your precious feedback on the soweego project and to ask you whether you know where the Bloomberg database has gone. I couldn't spot it on the Web, and the current formatter URL (P1630) of the Bloomberg person ID (P3052) seems to always redirect to the same page.
Do you have any updated pointers? Thank you in advance. Cheers,
After some digging, I managed to find the correct URL for the Wikidata property example (P1855) of the Bloomberg person ID (P3052), which is https://www.bloomberg.com/research/stocks/private/person.asp?personId=26417606&privcapId=26171912
I'm not sure how to get the
privcapId value, though.
On the other hand, it seems there is another namespace for people, see for instance https://www.bloomberg.com/profiles/people/6470800-andrea-agnelli
There's a namespace for people (Bloomberg person ID (P3052)) (referred with personId in the url) and one for companies (Bloomberg company ID (P3377)) (referred with privacpId). https://www.bloomberg.com/profiles/people/6470800 redirects to https://www.bloomberg.com/profiles/people/6470800-andrea-agnelli, so the name isn't needed.
Wait, https://www.bloomberg.com/profiles/people/26417606 leads to 404, while https://www.bloomberg.com/research/stocks/private/person.asp?personId=26417606&privcapId=26171912 is the correct URL for Bloomberg person ID (P3052)'s Wikidata property example (P1855) value (i.e., Stephen Petranek (Q23301821). I'm confused, maybe the example is just wrong.
I tried that url also with 6470800 and that doesn't work. It seems like there are two separate Bloomberg databases for people. I haven't yet figured out there relationship to each other.
I got the numbers directly from the Url.
Meinung und Hilfe zu Property-Proposal
es gibt ein Web-GIS für historische Kulturlandschaftselemente: no label (Q55589669) Gerne würde ich Wikidata und das KLEKs miteinander verzahnen. Da die Datensätze im KLEKs eine permanente ID besitzen, bietet sich eine Wikidata-Eigenschaft "KLEKs-ID" an. Mich würde Deine Meinung dazu interessieren und ob Du mich eventuell bei der Formulierung eines Property-Vorschlags unterstützen könntest. Viele Grüße, ChristianSW
Kannst du mir ein Beispiel geben? Welche Wikidata Objekte würde z.B. mit welchen KLEK ID's verknüpft sein und gibt es eine existierende Webseite für die ID?
Ja, hier ein Auszug aus meinen Offline-Notizen:
Datentyp: Externer Identifikator
Erwartete Vollständigkeit: Q21873886 dauerhaft unvollständig
Geplante Benutzung: (manuel) link to data about landscape elements
Number of IDs in source: >300 000
Ich hab ein Proposal erstellt: https://www.wikidata.org/wiki/Wikidata:Property_proposal/KLEKs_building_ID
Klasse, vielen Dank! Ich habe das Proposal ein wenig erweitert. Für Fragen etc. bin ich heute Abend wieder erreichbar. Viele Grüße!
What properties does Commons need?
Structured Commons will need properties to make statements about files. The development team is working on making the software ready to support properties; the question is, what properties does Commons need?
You can find more information and examples to help find properties in a workshop on Commons. Please participate and help fill in the list, and let me know if you have any questions. Thanks! -- Keegan (WMF) (talk) 18:53, 28 June 2018 (UTC)
Structured Data on Commons IRC Office Hour, Tuesday 26 June
There will be an IRC office hour for Structured Data on Tuesday, 26 June from 18:00-19:00 UTC in #wikimedia-office. You can find more details, as well as date and time conversion, at the IRC Office Hours page on Meta.
Hi! You was created local version for MediaWiki:Wbqc-violation-message-single-value. In my opinion, this is strongly incorrect way for multilingual site as Wikidata. This is may be done in some cases in the "monolingual" sites like single Wikipedia edition, but in Wikidata, Commons and Meta all changes should be made through Phabricator request and then through TranslateWiki. Otherwise, translators will not be able to maintain the correct display in their language.
In a Wikisystem I don't see why doing changing should require an off-wiki process.
As far as using Translate Wiki in this cases goes, I think that's an issue with the initial setup of the message and not with the edit.
About "issue with the initial setup of the message" - maybe this is true, but it is not a local message and cannot be changed locally.
Wikidata policy is supposed to be done on-wiki. Here the development team made a policy decision about the meaning of of a single value constraint and I reverted that to our existing meaning.
If there's a problem with translation not working for this message in a way that gets picked up by the software that might be a development issue.
If this is local correction - no problem. But in these caces, please, to inform translators and make sure that all translations are also changed locally. Otherwise, it turns out to be extremely incorrect in relation to those who use a non-English interface.
I added the <translate></translate> to the page. Does that do what you want?
Please don't add translate tags to pages in the MediaWiki namespace. That breaks the software and these messages are already translatable. I fixed it.