Property talk:P213

From Wikidata
Jump to navigation Jump to search


International Standard Name Identifier for an identity. Format: 4 blocks of 4 digits separated by a space, first block is 0000
RepresentsInternational Standard Name Identifier (Q423048)
Has qualityVIAF component (Q26921380)
Data typeExternal identifier
Template parameteren:Template:Authority control: "ISNI" - Template:Authority control (Q3907614)
Domainpersons, places, organizations... (note: this should be moved to the property statements)
Allowed values[0-9]{4} [0-9]{4} [0-9]{4} [0-9]{3}[0-9X]
Usage notesOnly when displayed preceded by the letters ISNI and a space; the digits are displayed as 4 blocks of 4 digits
ExampleNorway (Q20)0000 0001 2197 5163
Nero (Q1413)0000 0001 2141 6409
Intel (Q248)0000 0001 0354 5207
Pink Floyd (Q2306)0000 0001 0939 7559
Ernst Cassirer (Q57188)0000 0001 2146 438X
Formatter URL$1
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: usageCategory:Pages using Wikidata property P213 (Q13280236)
See alsoRinggold ID (P3500), Crossref funder ID (P3153)
  • Items with the most statements
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • Items with no other external identifier
  • Items with no other statements
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history
  • Mix'n'match (Report), Mix'n'match (Report) and Mix'n'match (Report)
  • Database reports/Constraint violations/P213
  • Proposal discussionProposal discussion
    Current uses1,063,458 out of 9,860,000 (11% complete)
    Search for values
    [create] Create a translatable help page (preferably in English) for this property to be included here
    Distinct values: this property likely contains a value that is different from all other items. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P213#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
    Format “(0000 000[0-4] [0-9]{4} [0-9]{3}[0-9X]|): value must be formatted using this pattern (PCRE syntax). (Help)
    List of this constraint violations: Database reports/Constraint violations/P213#Format, hourly updated report, SPARQL, SPARQL (new)
    Qualifiers “reason for deprecation (P2241), named as (P1810), alternate names (P4970): this property should be used only with the listed qualifiers. (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P213#Allowed qualifiers, SPARQL, SPARQL (new)
    Pattern ^(0000)(000[0-4])(\d\d\d\d)(\d\d\d[\dX])$ will be automatically replaced to \1 \2 \3 \4.
    Testing: TODO list

    ISNI format[edit]


    I don't know much about identifiers, but according to en:ISNI, ISNIs are 16 characters, not 20. Could somebody more knowledgeable on the matter than I please explain the discrepancy? — PinkAmpers&(Je vous invite à me parler) 23:49, 6 March 2013 (UTC)

    Yes, I am fixing this to their preferred format, that is

    16 digits dumb identifier. When displayed it is preceded by the letters ISNI, separated from the identifier by a space, and the 16 digits are displayed as four blocks of four digits, with each block separated from the next by a space. EXAMPLE ISNI 1422 4586 3573 0476

    Maximilianklein (talk) 18:39, 25 March 2013 (UTC)
    So what should we add: "0000 0001 2095 5689" (like Vincent van Gogh) or "0000000120955689" (like the example in Wikidata:List of properties)? For human readers the spaces are helpful. Are they machine-readable? If yes we should use them. --Kolja21 (talk) 00:36, 4 April 2013 (UTC)
    The thing is that the outbound links will eventually look like , which is without spaces. So the question is, whether using template logic the spaces can be removed? If so, we should use the human readable form for display. If it's impossible to build the template like{{#removespaces|$1}} then it's more important we have clickable links. Maximilianklein (talk) 16:31, 4 April 2013 (UTC)
    It's difficult to remove spaces with parser functions but not with Lua and I think that authority templates will soon be move to Lua (at the same time as the migration to Wikidata). So, I believe that we can use spaces as we have remove the "/" for LCCN ids. Tpt (talk) 14:13, 5 April 2013 (UTC)

    parameter value normalization[edit]

    This is not a broken links issue. Magnus Manske's authority control.js tool detects the ISNI / ISNI (ISO 27729) parameter in WMF project pages with Authority control templates. In most cases the values for the ISNI parameter at enwikipeia, commons etc. is a string containg three spaces for better readability.
    At this moment the tool does not state that the value "000035411562" is an instance of the value "35411562".
    note: scanning the source code page for lines using "new Node" helps identifying the national identifiers
    see: viaf:24590642 for Q153905 Paul Celan

    new new Node("ISNI|0000000122837889", "ISNI", "ISNI"); relates to this

    VIAFbot made this changes

    [1] VIAFbot (talk | contribs) (‎Created claim: Property:P213, 0000 0003 6865 2462)
    property / ISNI (ISO 27729)
    + 0000 0003 6865 2462
    [2] VIAFbot (talk | contribs) (‎Created claim: Property:P213, 0000 0001 2283 7889)
    property / ISNI (ISO 27729)
    + 0000 0001 2283 7889


    1. In urls as no spaces are used
    2. at viaf:24590642 in the header one can see ISNI: 0000 0001 1022 7004 where multiple spaces are used

    pro and contra about using spaces in the internal representation:
    "copy and paste" of s single numerical string is much easier then reformating it manually. The perameter string may wrap around or eaven worse might wrap according to BiDirectional script rendering.
    One should use one internal representation only. Onece agreed the problem might be fixed with regex. Bothe MediaWiki talk:Gadget-AuthorityControl.js and the WMF AC templates should support both value formats. Thanks for any help!
    see also MediaWiki talk:Gadget-AuthorityControl.js
    additional note: At Q153905 Paul Celan one can find additional issues

    1. viaf:27062193 is a deprecated VIAF id showing This VIAF Cluster has been deleted. It is no longer part of VIAF.
    2. the tool shows at thle lines tool en.wikipedia and ja.wikipedia contains the "wrong" VIAF id
      1. probably also more the WMF projects
        theoratically one needs to verify at least the projects supporting Template:Authority control (Q3907614)
        The list / table is ( 'als', 'ar', 'arz', 'as', 'bar', 'be' 'bn', 'bs', 'ca', cs', 'cv', 'da', 'de', 'en', 'eo', 'ee', 'fa', 'fr', 'hu', 'id', 'ilo', 'it', 'ja', 'km', 'ko', 'mk', 'nds', 'ne', 'nn', ', 'no', 'or', 'pl', ', 'pt', 'ro', 'ru', 'sl', 'st', 'th', 'uk', 'ur', 'vi', 'yi', 'zh', 'commons' )

    לערי ריינהארט (talk) 08:22, 10 October 2013 (UTC)

    This is still an open issue. לערי ריינהארט (talk) 12:26, 30 October 2013 (UTC)

    Spaces are wrong[edit]

    Spaces are wrong. There are no spaces in the ISNI. It is a 16 character ID:

    No other ID maintained by TC 46/SC 9

    like ISBN, ISCI, ISSN, ISRC, ISMN, ISWC has spaces, nor does this one have.

    John B. Sullivan (talk) 12:19, 7 December 2014 (UTC)

    • Some thinks:
    1. Often identifiers has internal presentation and standard display presentation. For example globally unique identifier (Q254972) is 128-bit number. But it is presented not as 123456789023456789456789 but as {21EC2020-3AEA-4069-A2DD-08002B30309D}.
    2. Wikidata used display presentation, not internal. For example the most numeric identifiers are presented using string datatype, not numeric.
    3. Standard display presentation for ISNI is 0000 0000 0000 000X as I see. For example see [3], [4].
    4. 0000 0000 0000 000X is more readable than 000000000000000X.
    So, I think 0000 0000 0000 000X format is more preferred than 000000000000000X. Anyway changing format in 250000+ items is global operation. It need to be discussed before implementing. Please do not touch Constraint template too until the discussion complete because the template is used by bots and inaccurate changes breaks normal work. — Ivan A. Krestinin (talk) 14:03, 7 December 2014 (UTC)
    This conversation was advertised at the village pump. I restored the description pending this conversation. Multichill (talk) 14:39, 7 December 2014 (UTC)
    Dear John, please be polite and don't change things before consensus has been reached. Accusing me and Ivan of vandalism is not polite. I tend to agree with Ivan. Could you please respond to this? I have to warn you, if you revert us again you'll get blocked for edit warring. Multichill (talk) 15:48, 7 December 2014 (UTC)
    John kept on replacing the regex reverting Jura1, Ivan and me. I asked him nicely to please not do that. He did it again so I blocked him for a day. Multichill (talk) 16:13, 7 December 2014 (UTC)
    See also en:Template talk:Authority control#Valus in Wikidata are false and adjacent sections. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:29, 16 December 2014 (UTC)

    Storing in a display format breaks usability in tools like Reasonator[edit]

    There has been discussion before about storing the data in the display format or in the actual format. Storing in a display format breaks usability in other tools. Showing it in a format is just a matter of having some code at our end if that is what you want.

    The current wrong practice defeats the purpose of linking to ISNI and needs to be remedied. Thanks, GerardM (talk) 06:10, 8 January 2016 (UTC)

    • Current format was introduces two years ago. All tools and bots use this format now. The format is more readable. I do not think that we need to start migration process in this stage. Reasonator is looked as the only tool that does not support this format. I think better way is fixing Reasonator code. — Ivan A. Krestinin (talk) 08:10, 8 January 2016 (UTC)
    • There are several other identifiers that currently don't link correctly with Reasonator. Is there anything special about this one?
      --- Jura 09:41, 8 January 2016 (UTC)

    This is the only one using spaces. It heavily breaks usability. GerardM, thanks for bringing this up. 04:47, 19 November 2016 (UTC)

    Value constraints[edit]

    "Item type principal (GND) (P107) = personne (Q215627)" violations[edit]

    There is a problem with this constraint, since ISNI (and VIAF) also comprise "Organizations" (moral persons) and even "Locations" like Switzerland or Paris - could it be possible to check if one of the 3 is used, instead of a long list of Organization here that won't ever be removed from the list if the constraint stays as it is… (same thing on Property:P214 (VIAF) and probably all AC used in VIAF. --Hsarrazin (talk) 03:19, 28 May 2013 (UTC)

    Yes, the constraint should also comprise organisation. For "Locations", this is more complicated: the ISNI for Paris is in fact the identifier of the Paris as organisation (the Marie de Paris) and not Paris as place. But, as the distinction is not done in Wikidata. So, waiting for a good solution, I think that we should remove the "Item type principal (GND) (P107) = personne (Q215627)" contraint. Tpt (talk) 05:47, 28 May 2013 (UTC)
    If you remove simply Q215627, it will list those without the main type property. OTH, if 95% are persons, it might still be worth checking for that. --  Docu  at 06:44, 28 May 2013 (UTC)
    instead of removing the constraint, would it be possible to "extend" it to "organizations", so that all the "treated" values, on top of the list of "violations", can be removed… it is very disappointing to try and treat a list of errors, and all the first 20 or 50 values you try, should simply not be on the list… ;) --Hsarrazin (talk) 09:15, 31 May 2013 (UTC)
    removed the constraint. add it again if you find a solution for organizations. --Akkakk 17:17, 19 June 2013 (UTC)

    Multiple values[edit]

    People with multiple identities (e.g. those using pseudonyms) generally have several records in ISNI database. Since this is not just an exception, I assume, the unique value constraint check should not be applied here.--Shlomo (talk) 08:37, 1 October 2013 (UTC)

    Yes, I did... My mistake, sorry for troubling and thanks for correcting me.--Shlomo (talk) 19:30, 1 October 2013 (UTC)

    Restricting regex to ASCII[edit]

    OLD \d\d\d\d \d\d\d\d \d\d\d\d \d\d\d[\dX]
    NEW [0-9]{4} [0-9]{4} [0-9]{4} [0-9]{3}[0-9X]

    Further reading 21:23, 27 April 2018 (UTC)

    Why not (\d{4} ){3}\d{3}[\dX]? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:55, 1 June 2018 (UTC)
    In most regex implementations, [0-9] is more specific than \d since the latter also matches digits in non-latin scripts (example: \d matches ۸ = 8 in Persian (Q9168)). I guess ISNI allows only latin-script digits. The rest is probably personal flavor: the longer version is easier to understand, while the compact one looks more sophisticated. It does not really matter which one is used here. —MisterSynergy (talk) 12:13, 1 June 2018 (UTC)

    Link to ISNI Registration Authority[edit]


    (noted by user:Reptilien.19831209BE1 at WD:Bistro) Most ISNI database entries appear to be available at 2 URLs: either [5] or [6]. Currently the link is set to format the first one, but in some cases, only the second one appears to work ([7] / [8]). So, can I change MediaWiki:Gadget-AuthorityControl.js to format 2 ? -Zolo (talk) 16:30, 11 July 2014 (UTC)


    I notice that there are some items with "ISNI-test" on, e.g., Vibeke Klint (Q19590089) [9]. I added the ISNI in this case, but the link Reasonator constructs for the ISNI does not resolve: "Page not found". What does this mean? Should ISNI of be avoided? — Finn Årup Nielsen (fnielsen) (talk) 20:13, 14 March 2015 (UTC)

    Update: When searching with I can find 0000 0001 1499 485X. — Finn Årup Nielsen (fnielsen) (talk) 20:15, 14 March 2015 (UTC) resolves fine for me. Eldizzino (talk) 15:12, 31 May 2015 (UTC)


    The link to Isni item leading to error. Look like the link format was changed.Geagea (talk) 02:27, 9 December 2016 (UTC)

    It still works for me. Can you provide a link which doesn't work? --Pasleim (talk) 09:53, 9 December 2016 (UTC)
    • Q12411778 --> ISNI leads to this
    • Q20 --> ISNI leads to this
    Geagea (talk) 23:15, 9 December 2016 (UTC)
    I'm getting an error as well - "Your data limit has been reached". Manually searching on the ISNI site returns valid results, though. Looks like it's rejecting the direct links for some reason. Andrew Gray (talk) 16:19, 11 December 2016 (UTC)

    Property example[edit]

    Property Example[edit]

    Why does the current Property Example here point to the country Norway? The ISNI used there is "0000 0001 2298 9524" with a reference of Imported from VIAF. However, the corresponding link goes to a page containing Creation class: "Musical sound recording" and Creation role: "author, musician", which seems to indicate that this value is not a country. -- Perhaps the item for USA would be a better example. On the face of it, it seems to have a P213 pointing to an ISNI page which might be correct: On the other hand, I can't see any particular semantic information on that page to verify that this is indeed the correct item/entity. (There is no "Creation class" on that page, for one.) I tried to use the search form on the ISNI page to search for potential conflicts, but the search form does not work, at least not for me. How should these property values be verified? Fred Johansen (talk) 14:53, 15 July 2015 (UTC)

    Property example including X[edit]

    Changed one human example to one where the ISNI includes an X. Example taken from English Wikipedia. 10:44, 18 August 2018 (UTC)

    Data type[edit]

    Shouldn't the data type be External identifier not String? Pinging user:Tpt as creator. -- Netoholic (talk) 07:08, 14 April 2016 (UTC)

    Yes definitely. It is an ID on the same level as ISBN-13 (P212) or ISO 639-1 code (P218). Tpt (talk) 08:19, 14 April 2016 (UTC)
    Hello, I agree. How can we change that ? --Daehan (talk) 08:17, 13 June 2016 (UTC)
    Double-check procedure (and previous decisions) at Wikidata:Identifier migration. -- LaddΩ chat ;) 11:23, 13 June 2016 (UTC)
    Follow-up at: Wikidata:Identifier_migration/0#ISNI. -- LaddΩ chat ;) 11:35, 13 June 2016 (UTC)

    Adding values to items[edit]

    Importing ISNI ids from GRID[edit]

    I am going to import ISNI identifiers from the GRID dataset: all items that have a GRID ID (P2427) and no ISNI (P213) will receive a ISNI (P213) if there is a unique ISNI for that GRID id in the latest dump. − Pintoch (talk) 19:49, 1 February 2017 (UTC)

    Still that links do not work, same problem as above. --MovieFex (talk) 23:36, 2 February 2017 (UTC)
    The fact that the resolver blocks direct links is not a reason to remove the statements using that property. Can you please stop reverting my edits? Thank you! − Pintoch (talk) 23:43, 2 February 2017 (UTC)

    Adding ISNI that exist in VIAF[edit]

    I just added an ISNI that exists in VIAF since 2014-05-14 [10]. Added several more long existing ISNI today. Isn't there some automatisation available? Ca 4.2 mio humans in Wikidata, 1,018,671 have VIAF in WD, only 476,549 have ISNI in WD. 12:07, 22 April 2018 (UTC)

    Adding duplicate claims[edit]

    @Magnus Manske: That seems to be a bug in the ORCID tool, maybe? − Pintoch (talk) 12:54, 26 April 2018 (UTC)
    @Pintoch, GerardM, Pigsonthewing, לערי ריינהארט:, once again a bug related to spacing. All external DBs I know of, do not store the ISNI in spaced format. 13:14, 26 April 2018 (UTC)

    Vandal additions[edit]

    Found via 11:21, 18 August 2018 (UTC)


    Great news: ISNI now provides ORCID corresponding ID for researchers. Enjoy! Nomen ad hoc (talk) 16:08, 14 January 2018 (UTC).


    SPARQL - show ISNI with highest number[edit]

    #show ISNI with highest number
    SELECT ?item ?isni
    WHERE {
      ?item wdt:P31 wd:Q5 .
      ?item wdt:P213 ?isni 
    } ORDER by DESC (?isni)
    LIMIT 100

    Try it!

    Result list often broken because users add ISNI in 16-digit format and not in spaced format. 13:06, 26 April 2018 (UTC)

    SPARQL - show ISNI with lowest number[edit]

    #show ISNI with lowest number
    SELECT ?item ?isni
    WHERE {
      ?item wdt:P31 wd:Q5 .
      ?item wdt:P213 ?isni 
    } ORDER by ASC (?isni)
    LIMIT 100

    Try it!

    • As of 2018-04-26 : Number 1: 0000000000000095 , Number 100: 0000000000019554 13:12, 26 April 2018 (UTC)
    • As of 2018-06-17 : Number 1: 0000000000000095 , Number 100: 0000000000016337 16:39, 17 June 2018 (UTC)

    SPARQL - show duplicates[edit]

    Thanks a lot to User:TweetsFactsAndQueries who wrote the query based on a request at Topic:Ufprnhx29r8zv4wh.

    SELECT ?isni ?item1 ?item1Label ?item1DateOfBirth ?item2 ?item2Label ?item2DateOfBirth WITH {
      SELECT * WHERE {
        ?item1 wdt:P213 ?isni;
               wdt:P569 ?item1DateOfBirth.
        ?item2 wdt:P213 ?isni;
               wdt:P569 ?item2DateOfBirth.
        FILTER(STR(?item1) < STR(?item2))
    } AS %results WHERE {
      INCLUDE %results.
      SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }

    Try it! 11:00, 27 June 2018 (UTC)

    SPARQL - instance of subclass of human[edit]

    Instances of human should not be instances of anything else.

    SELECT ?item ?itemLabel ?type ?typeLabel
    WHERE {
    	?item wdt:P31/wdt:P279+ wd:Q5 .
        ?item wdt:P31 ?type .
        ?item wdt:P213 []
        SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }.

    Try it! 11:35, 18 August 2018 (UTC)

    Lowest 100 ISNI from[edit] 13:42, 26 April 2018 (UTC)

    YouTube and ISNI[edit]

    YouTube has become an ISNI registry, and will begin creating ISNI IDs for the musicians whose videos it features [11]. They anticipate the number of ISNI IDs "going up by perhaps 3-5 million over the next couple of years" as a result [12]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:48, 1 June 2018 (UTC)

    formatter URL[edit]


    I do not know for before, but today the url$1 (see works well, so we can modify the formater Url to remove wmflabs, agree ? — eru [Talk] [french wiki] 19:44, 16 March 2019 (UTC)