Why do you have to get lost in them ? Most already have the phrase "ID" or "Identifier" in their naming convention. So perhaps a better approach would be to standardize the naming convention used for External Identifiers and make it a best practice and golden rule during property creation and voting. A further refinement could be to enhance the statement selector with an option for "ID" or "WP ID" or "Descriptor". I think a simple naming convention would suffice (and clean up the existing ones): <blah> ID such as for example: CANTIC ID Freebase ID Munzinger IBA ID NLP ID dmoz ID Oxford Biography Index ID SELIBR ID etc.. Thad +ThadGuidry <https://www.google.com/+ThadGuidry> On Fri, Apr 3, 2015 at 8:17 PM, Denny Vrandečić &lt;vrandecic(a)gmail.com&gt; wrote:

On Fri, Apr 3, 2015 at 7:07 PM, Thad Guidry &lt;thadguidry(a)gmail.com&gt; wrote:> Yes. I could see a simple "Statements" vs. "External identifiers" distinction being useful that's also reflected in the data model so it's easier to treat these property groups in a distinct manner. External identifiers seem as fundamentally different to me from Wikidata-internal and Wikimedia-related properties as external links in a Wikipedia article are from the main content. They (in the common cases) don't tell me anything other than "There's more information about $foo in $bar". Whether I'm a human or a friendly machine, I might want to just look at one set of properties or another, depending on what I'm doing, so having them grouped in some fashion may be beneficial for both user groups. Erik

Citiranje Thad Guidry &lt;thadguidry(a)gmail.com&gt;om>: How would you name ISBN, for example? ISBN ID? :)

Best to have a statement (instance of:wikidata database index property) instead of trying to do this with the English language label as it is easier to localise statement s. On 4 Apr 2015 17:23, "Helder ." &lt;helder.wiki(a)gmail.com&gt; wrote:

Hoi, Reasonator is read only in the sense that the display does not update itself when you make an edit from it through Widar. Even that is not strictly true; the label of the article itself will update when you add a label in your language and once it has been included in Wikidata. I really wonder when you have been last at Widar because there is no wall of ID's. Thanks, GerardM http://ultimategerardm.blogspot.nl/2015/04/wikidata-what-to-do-in-datathon-… On 4 April 2015 at 09:29, Stas Malyshev &lt;smalyshev(a)wikimedia.org&gt; wrote:

Stas Malyshev, 04/04/2015 09:29:>> away from the old layout and that is very welcome. Singling out the Did you mean the opposite? Stas Malyshev, 04/04/2015 10:22: Indeed: https://www.wikidata.org/wiki/Property:P1628 is already used to mark properties ("identifiers") already defined in other ontologies. https://www.wikidata.org/w/index.php?title=Special%3AWhatLinksHere&targ… Looks like we just need to add this property to more properties. Whether this piece of information is used for presentational purposes seems secondary, or at least I don't see a compelling argument for it yet. Nemo

On 4 April 2015 at 10:20, Thomas Douillard &lt;thomas.douillard(a)gmail.com&gt; wrote: The property for an ORCID iD (P 496), for example, is an instance of "Wikidata property for authority control for people" (Q19595382). That, in turn is a sub-class of "Wikidata property for authority control" (Q18614948) -- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk

Hi! I meant when you're looking at the page for Douglas Adams, you can see that his birth name was "Douglas Noël Adams" and this is useful for you as a human reader. But before that, you see that his "LNB identifier" is "000057405" and in 99.9% of cases it is not useful for you since you neither know what "LNB identifier" is nor you need to see one unless you're a Latvian librarian working on integration with Wikidata. Now, I imagine there is a lot of uses for such identifiers, and I am in no way call for diminishing their role or somehow questioning their importance as data, but *presenting* it as the second most important knowledge we have about Douglas Adams right after the fact he is a human looks wrong to me. -- Stas Malyshev smalyshev(a)wikimedia.org

Quick hack: On your user common.js page, add: importScript( 'User:Magnus Manske/ext-props.js' ); This will "move" all statements for external IDs (to be exact, all properties with a "URL formatter" property) to the sidebar. The statements in the main body are just hidden; there is a toggle link in the sidebar to make them visible again, qualifiers and all. This is, of course, just a demo to show what the main body would look like without such statements. On Sun, Apr 5, 2015 at 12:05 AM apohllo(a)o2.pl &lt;apohllo(a)o2.pl&gt; wrote:

On Sun, Apr 5, 2015 at 6:52 PM, Magnus Manske &lt;magnusmanske(a)googlemail.com&gt; wrote: Magnus, as always you're a treasure ;-) I hadn't thought about the toggle option yet. So let me summarize the options I see for identifiers: 1) we give them their own section below statements 2) we give them their own section in the right sidebar and have some compact way of showing and editing references and qualifiers 3) we do both of the above and have a way to toggle between the two I initially was set on 2 but am coming around to 2. 3 seems like the easiest way out right now but it'll feel awkward to new users. On the technical side I see the following options to identify which statements to group into the identifiers section: 1) we make them sitelinks 2) we we give them a special datatype (We should be able to migrate the existing ones in a one-time operation without changing their property IDs) 3) we rely on a statement on the property 4) we have a list in the wiki configuration 1 seems bad because we'd lose references and qualifiers 3 seems problematic from a performance point 4 is ugly and not maintainable So I am coming around to 2. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

If you change the datatype for identifiers from string and the other properties with string datatype are changed to monolingual then we won't have much need for the string datatype On 6 Apr 2015 15:09, "Lydia Pintscher" &lt;lydia.pintscher(a)wikimedia.de&gt; wrote:

Hi Lydia, If a separate section is needed for identifiers, I do not care. when a user tries to add an identifier in the statements section instead of the identifiers section? Besides users are used to add identifier statements to the statements section, it can cause misunderstanding if it is no longer possible to add identifiers to the statements section. I would then recommend (if this is not yet thought of) to allow users to add identifiers to the statement section, and with reloading the page they show up in the right section. (Maybe the other way round as well.) Also when I currently want to add a statement, I press [ end ] on my keyboard, there I click [ add ]. If I must add the a statement to the right section, this would make it much uncomfortable to have to search somewhere between the statements and the identifiers where the [ add ] is for the statements section. If this would happen, it would make adding statements more annoying. (I would like to recommend to make it less annoying and more easier to add statements.) An alternative idea to solve this is to be able to add statements at the top of the statements section. Navigation will be an important issue to have attention for, otherwise splitting it up in identifiers and other statements would make the improvement for users nett less improving but instead worse. If it is wished for to split the identifiers from the other statements, I would more like it see just all the identifiers on the bottom of the statements section. If all statements in the source code ( <div class="wikibase-statementgroupview-property"> ) would get an id="..." based on the property number, it is easy to arrange having all identifier properties on the bottom. At the same time this would be easier for users to put certain properties always on top of the statements section of an item PS: Not all properties with URLs are identifiers, like the official website: https://www.wikidata.org/wiki/Property:P856 PS2: Not all identifiers have or will have an URL available. Romaine 2015-04-06 16:08 GMT+02:00 Lydia Pintscher &lt;lydia.pintscher(a)wikimedia.de&gt;de>: