Property talk:P345

From Wikidata
Jump to navigation Jump to search


identifier for the IMDb [with prefix 'tt', 'nm', 'co', 'ev', 'ch' or 'ni']
RepresentsInternet Movie Database (Q37312)
Associated itemInternet Movie Database (Q37312)
Applicable "stated in" valueInternet Movie Database (Q37312)
Data typeExternal identifier
Corresponding templateTemplate:IMDb (Q13220022), Template:IMDb title (Q5640735), Template:IMDb name (Q6007932), Template:IMDb company (Q7126128), Template:IMDb event (Q13361743)
Template parameter
According to this template: Creative work, Person, character, company
According to statements in the property:
audiovisual work (Q2431196), human (Q5), group of humans (Q16334295), event (Q1656682), animal actor (Q52688389), fictional character (Q95074), podcast (Q24634210), television series season (Q3464665), trailer (Q622550), award (Q618779), television play (Q7697093), group of video games (Q116741534), animated series (Q581714), episode (Q1983062) or video (Q98069877)
When possible, data should only be stored as statements
Allowed valuesev\d{7}\/(19|20)\d{2}(\/[12])?|tt\d{7,8}\/characters\/nm\d{7,8}|(tt|ni|nm)\d{8}|(ch|co|ev|tt|nm)\d{7}|
ExampleThe Godfather (Q47703)tt0068646
Leonardo da Vinci (Q762)nm1827914
Lucasfilm (Q242446)co0071326
87th Academy Awards (Q16773560)ev0000003/2015
‘Captain Marvel’ Finds Directors in Anna Boden, Ryan Fleck (EXCLUSIVE) (Q29512115)ni61008607
Format and edit filter validationAbuse filter #17
External linksUse in sister projects:
Formatter URL$1$1/$1/$1/$1$1/$1/$1/
Tracking: sameCategory:IMDb ID same as Wikidata (Q32203163)
Tracking: differencesCategory:IMDb ID different from Wikidata (Q26220033)
Tracking: usageCategory:Pages using Wikidata property P345 (Q26997818)
Tracking: local yes, WD noCategory:IMDb ID not in Wikidata, but available on Wikipedia (Q26220045)
Related to country United States of America (Q30) (See 728 others)
See alsoAcademy Awards Database nominee ID (P6150), castingvideos ID (P6476), Equipboard artist ID (P6912), IMVDb artist ID (P6960), Awards & Winners artist ID (P7184), AaRC person ID (P7533), Ratingraph actor ID (P7602), Taiwan Cinema film ID (P7611), OFDb film ID (P3138), OFDb person ID (P9404), TMDB movie ID (P4947), Rate Your Music film ID (P11598), Rate Your Music artist ID (P5404), Rate Your Music release ID (P8392), Rate Your Music film genre ID (P11588), Encyclociné ID (P12059)
  • Top missing properties by number of sitelinks/P345
  • Items with the most statements of this property
  • 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
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history (total)
  • Map of people by place values:
  • January 1st dates
  • Database reports/Complex constraint violations/P345
  • Database reports/Humans with missing claims/P345
  • Database reports/Constraint violations/P345
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Main statement1,010,378 out of 484,123,998 (0% complete)80.5% of uses
    Qualifier102<0.1% of uses
    Reference244,56919.5% of uses
    Search for values
    [create Create a translatable help page (preferably in English) for this property to be included here]
    List of violations of this constraint: Database reports/Constraint violations/P345#Conflicts with P31, hourly updated report, SPARQL
    Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P345#Item P31, search, SPARQL
    Conflicts with “instance of (P31): song (Q7366), television series season (Q3464665): this property must not be used with the listed properties and values. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: The Haunting of Hill House (Q43379503), The Haunting of Bly Manor (Q85807418)
    List of violations of this constraint: Database reports/Constraint violations/P345#Conflicts with P31, SPARQL
    Format “ev\d{7}/(?:19|20)\d{2}(?:/[12])?|tt\d{7,8}/characters/nm\d{7,8}|(tt|ni|nm)\d{8}|(?:ch|co|ev|tt|nm)\d{7}|: value must be formatted using this pattern (PCRE syntax). (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P345#Format, SPARQL
    Distinct values: this property likely contains a value that is different from all other items. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Q460163, Q5094942, Q7499225, Q7532265, Q13114252, Q3773223, Q384930, Q13416804, Q17165527, Q2559332, Q13685096, Q209515, Q1358109, Q2505040, Q2739228, Q14153484, Q319918, Q2348663, Q17422086, Q25408770, Q7489069, Q25095746, Q4526407, Q16252357, Q25217690
    List of violations of this constraint: Database reports/Constraint violations/P345#Unique value, SPARQL (every item), SPARQL (by value)
    Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P345#Entity types
    Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P345#Scope, SPARQL
    Conflicts with “instance of (P31): radio program (Q1555508), radio series (Q14623351): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P345#Conflicts with P31, hourly updated report, SPARQL
    Conflicts with “instance of (P31): podcast (Q20899), audio podcast (Q24633474), video podcast (Q3276244): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P345#Conflicts with P31, hourly updated report, SPARQL
    Conflicts with “instance of (P31): podcast series season (Q69154911): this property must not be used with the listed properties and values. (Help)
    List of violations of this constraint: Database reports/Constraint violations/P345#Conflicts with P31, hourly updated report, search, SPARQL
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P345#Conflicts with P31, SPARQL
    Pattern ^(ch|co|ev|nm|tt|ni)0+([1-9]\d{6,7})$ will be automatically replaced to \1\2.
    Testing: TODO list
    Pattern ^name/(nm)(\d{7,8})/?$ will be automatically replaced to \1\2.
    Testing: TODO list
    Pattern ^(https:\/\/(m\.|www\.|)imdb\.com)?\/?(title\/(tt)|name\/(nm))(\d{7,8})(\/?.*)?$ will be automatically replaced to \4\5\6.
    Testing: TODO list
    Unsuitable IMDb identifier for human
    Person with IMDb identifier but prefix is not nm or ch (Help)
    Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P31 wd:Q5; p:P345/ps:P345 ?imdb. ?item p:P345 ?imdbStatement . ?imdbStatement wikibase:rank ?rank . FILTER(!STRSTARTS(?imdb, 'nm') && !STRSTARTS(?imdb, 'ch') && ?rank != wikibase:DeprecatedRank) }
    List of this constraint violations: Database reports/Complex constraint violations/P345#Unsuitable IMDb identifier for human
    TV series episode without IMDB and without link to other episode
    instance of (P31) -> television series episode (Q21191270), but no IMDb ID (P345) and no link to a previous or next episode (Help)
    Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P31 wd:Q21191270 . MINUS {?item p:P345 [] } . MINUS {?item wdt:P155 [] } . MINUS {?item wdt:P156 [] } . MINUS { ?item wdt:P179 ?series . ?series pq:P155 [] } } ORDER BY xsd:integer(SUBSTR(STR(?item),STRLEN("")+1)) LIMIT 1000
    List of this constraint violations: Database reports/Complex constraint violations/P345#TV series episode without IMDB and without link to other episode
    TV series episode without IMDB and with other episode with link
    instance of (P31) -> television series episode (Q21191270), but no IMDb ID (P345), but does have a link to a previous or next episode with a IMDb ID (P345) link (Help)
    Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P31 wd:Q21191270 . MINUS {?item p:P345 [] } { ?item wdt:P155 ?otheritem . ?otheritem wdt:P345 [] } UNION { ?item wdt:P156 ?otheritem . ?otheritem wdt:P345 [] } } ORDER BY xsd:integer(SUBSTR(STR(?item),STRLEN("")+1)) LIMIT 1000
    List of this constraint violations: Database reports/Complex constraint violations/P345#TV series episode without IMDB and with other episode with link
    TV series episode without IMDB
    instance of (P31) -> television series episode (Q21191270), but no IMDb ID (P345), might need to add some filters later (Help)
    Violations query: SELECT DISTINCT ?item { ?item wdt:P31/wdt:P279* wd:Q21191270. MINUS { ?item p:P345 [] } MINUS { ?item wdt:P527/wdt:P345 [] } }
    List of this constraint violations: Database reports/Complex constraint violations/P345#TV series episode without IMDB
    This property is being used by:

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)


    More than one IMDb identifier[edit]

    What should be done with items that have more than one valid IMDb identifier? For instance, Q91 has two IMDb identifiers, namely nm1118823 and ch0026778. Or Q223132, for that matter. What ought to be the precedent here? Add both, and let the infoboxes and such sort it out when Phase 2 is rolled out? Gabbe (talk) 11:56, 18 April 2013 (UTC)Reply[reply]

    I think items that are about real people (not fictional characters) should only have the nm- ID. As for multi-part episodes, I think the best practice would be to list out all like in Q402401 and wait for qualifiers to roll out to apply "Part 1", "Part 2", etc. to the correct ID. FallingGravity (talk) 20:59, 18 April 2013 (UTC)Reply[reply]

    Constraint item[edit]

    {{Constraint:Item|property=P107|item=Q386724|item2=Q215627|item3=Q43229}} (yes, organization is already there) seems to work OK with Magnus' tool (example), but unfortunately not with constraint violations generator. --Jklamo (talk) 14:25, 23 July 2013 (UTC)Reply[reply]

    constraint report relating to Wikimedia disambiguation page (Q4167410)[edit]

    If instance of (P31) is a Wikimedia disambiguation page (Q4167410) the presence of IMDb ID (P345) is prohibited

    see: Wikimedia disambiguation page (Q4167410) with IMDb identifier (P345) . Usualy there might be two possibilities:
    a) please identify the non - ambiguation page (WD item) where the property IMDb identifier should be moved;
    "normally" no other statements should be left at the disambiguation page;
    it can happen that a set of properties should be moved to another (a second) WD item, another set to a third WD item etc.
    b) verify which language is a disambiguation page and separate it from the rest; please use Gadget-labelLister.js can be activated at preferences#gadgets to remove all faulty descriptions after the disambiguation page is separated (the languages are de, en, fr, es, pt, pt-br, ru, sv and possibly some others).

    Thanks in advance! gangLeri לערי ריינהארט (talk) 19:38, 26 May 2014 (UTC)Reply[reply]


    If I want to connect Taurus World Stunt Awards 2001 (Q2397212) with how should I do that? The identifier ev0000709/2001 does not match the format constraint. --Pasleim (talk) 20:44, 26 April 2015 (UTC)Reply[reply]

    I changed the format constraints to accept also IDs like ev0000709/2001 for a specific year of an event. But there is still a problem with it: The formatted URL can't handle those (e.g. [1]). Is there an alternative for formatting the URL that can handle events with a year? --Floscher (talk) 10:47, 2 June 2015 (UTC)Reply[reply]
    ev0000709/2001 is no identifier for Taurus World Stunt Awards 2001 (Q2397212), but ev0000709 for Taurus World Stunt Awards (Q585872), that is all you can do. Queryzo (talk) 11:04, 8 September 2015 (UTC)Reply[reply]
    @Pasleim: Now it matches: [2].

    Video games[edit]

    I'm just leaving a note hear so that people realize that IMDb also has a database of video games that can be added to items here on Wikidata. Granted it's not the best gaming database out there but I feel this has been largely overlooked by most bots and editors. FallingGravity (talk) 05:31, 19 July 2015 (UTC)Reply[reply]

    short film (Q24862) invalid classification?[edit]

    Why is Flames of Passion (Q1426920) a "Item instance of (P31)" violation? instance of (P31) short film (Q24862) should be a valid classification. Queryzo (talk) 11:07, 8 September 2015 (UTC)Reply[reply]

    Where did you find this to be a violation? Mbch331 (talk) 12:54, 9 September 2015 (UTC)Reply[reply]
    It was listet at P345 Constraint violations, while ValterVB had already fixed it by adding short film (Q24862). Queryzo (talk) 09:30, 11 September 2015 (UTC)Reply[reply]
    Maybe it should go into genre, rather than P31. --- Jura 09:34, 11 September 2015 (UTC)Reply[reply]
    @Jura1: What do you mean? Queryzo (talk) 09:38, 11 September 2015 (UTC)Reply[reply]
    Add instance of (P31) = film and genre (P136) = short film. --- Jura 09:43, 11 September 2015 (UTC)Reply[reply]
    No, add instance of (P31) = short film, that'll work now. Queryzo (talk) 19:19, 1 December 2016 (UTC)Reply[reply]


    Who made them unclickable and why? --Jobu0101 (talk) 08:20, 12 October 2015 (UTC)Reply[reply]

    I think there's a bot, that adds the link at some time. Queryzo (talk) 11:59, 17 November 2015 (UTC)Reply[reply]
    Nope, I think it was a Wikidata software/JS issue with my browser. --Jobu0101 (talk) 09:59, 10 December 2015 (UTC)Reply[reply]

    No value (not only) for siblings[edit]

    There are currently some discussions (1, 2) how to to handle with siblings and twins like Camilla and Rebecca Rosso (Q54863) or Coen brothers (Q56095). No value causes a constraint violation so objects like that might be classified as valid objects. Queryzo (talk) 09:35, 10 December 2015 (UTC)Reply[reply]

    I'd appreciate to have a non-constraints-violating possibility to mark also objects which usally have an IMDb id with novalue to emphysize that there is currently no id in IMDb for them. So we are not only talking about siblings. --Jobu0101 (talk) 09:55, 10 December 2015 (UTC)Reply[reply]
    Either the special snakvalue novalue should be treated as not being a value by constraint reports (but still be displayed) or the whole constraint system should be more flexible (so for example groups can only have the value novalue and nothing else and individuals can have a IMDb ID starting with nm and/or ch etc.). I prefer the latter solution, but that requires recoding and requires a third form of constraint system (currently we have the template based system, plans are to move the constraints to the statements section of the properties). Mbch331 (talk) 10:28, 10 December 2015 (UTC)Reply[reply]
    novalue is also used by other authority control properties like GND ID (P227). The constraint violations can be adjusted. --Kolja21 (talk) 12:49, 10 December 2015 (UTC)Reply[reply]
    There is one small difference. For GND ID (P227) there is no constraint that says it can't be used on groups. For IMDb the only allowed value for groups should be novalue and that constraint isn't possible in the current and planned constraint system. If we allow IMDb ID's for groups where the ID isn't for the group, but for 1 of it's members, there will be no more possibility to check that automatically. That could be solved if the constraint system could check the title of the IMDb page and match the defined displayname for the IMDb claim. (Eg. Boris Tokarev (Q2068051)IMDb ID (P345)nm0006491displaynameBoris Tokarev The displayname should be checked against the meta tag: <meta property='og:title' content="Boris Tokarev" />.) Then it would be possible to remove the constraint on groups. Mbch331 (talk) 13:02, 10 December 2015 (UTC)Reply[reply]

    Problem with URL generation[edit]

    The url for the 87th Academy Awards (Q16773560) doesn't work: [3]. --Jobu0101 (talk) 13:53, 24 December 2015 (UTC)Reply[reply]

    It should link here. I guess this problem occurs at all ids with prefix "ev". --Jobu0101 (talk) 21:22, 16 January 2016 (UTC)Reply[reply]
    IMDb changed the naming scheme of pages before there were event pages. They kept the old naming scheme as a redirect, but since ev didn't exist, there are no redirects for that type of links. That's why they don't work and the others do. Mbch331 (talk) 22:11, 17 January 2016 (UTC)Reply[reply]
    The actual links are defined at MediaWiki:Gadget-AuthorityControl.js. Instead of using redirects, direct links could be defined.
    --- Jura 08:26, 18 January 2016 (UTC)Reply[reply]

    Complex constraint[edit]

    @Pasleim: great idea, but I think you could also exclude ch (character) for people. It should be OK, that, for example, Gert Bastian (Q69251) has ch0525295. --Edgars2007 (talk) 15:17, 28 January 2016 (UTC)Reply[reply]

    @Edgars2007: You contradict yourself. What do you mean? --Jobu0101 (talk) 11:14, 30 January 2016 (UTC)Reply[reply]
    He means that humans can have a name entry (nm) or an character entry (ch) and both shouldn't be returned as an incorrect value. I adjusted the constraint accordingly. Mbch331 (talk) 11:22, 30 January 2016 (UTC)Reply[reply]
    Ah, okay. So with "exclude" he means to exclude/remove the contraint that people should not have a ch id. --Jobu0101 (talk) 11:38, 30 January 2016 (UTC)Reply[reply]
    Yes. Mbch331 (talk) 11:50, 30 January 2016 (UTC)Reply[reply]
    It's good, that at least one person understands, what I wanted to say :) --Edgars2007 (talk) 11:53, 30 January 2016 (UTC)Reply[reply]
    Now I understand, too. And I share your opinion. I actually had the plan a few days ago to discuss this issue here. Now you came first. --Jobu0101 (talk) 11:55, 30 January 2016 (UTC)Reply[reply]

    Tag: Unexpected value for IMDb identifier[edit]

    Why is this edit tagged? It should be matched by the set format as a regular expression (P1793) (ev\d{7}/\d{4})|((tt|nm|ch|co|ev)\d{7}). --Jobu0101 (talk) 20:46, 5 February 2016 (UTC)Reply[reply]

    Yes, filter should get updated. @Matěj Suchánek:. --Edgars2007 (talk) 20:54, 5 February 2016 (UTC)Reply[reply]
    ✓ Done Special:AbuseFilter/history/17/diff/prev/807 Matěj Suchánek (talk) 21:11, 5 February 2016 (UTC)Reply[reply]

    Split this property up[edit]

    Currently this property is used for all concepts available on the IMDB website. That makes this property special and quite complicated. An obvious step to make this easy and straightforward is to split this property up in different related properties. Each of these new properties would be an external identifier with a specific scope. Steps would be:

    • Achieve consensus that this is a good plan
    • Propose new properties and wait for those to be created
    • Copy all statements to the new properties (easy bot job)
    • Mark this property as deprecated and inform downstream users
    • (.... wait .....)
    • Remove this property from all items

    What do you think? Multichill (talk) 14:03, 28 February 2016 (UTC)Reply[reply]

    I agree, properties should be small in scope as that makes them easier to handle (regarding validation, linking, querying, …). Keeping both around for a bit sounds worthwhile to me in order to help users to migrate. - Hoo man (talk) 14:06, 28 February 2016 (UTC)Reply[reply]

    WikiProject Movies has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.. --Jobu0101 (talk) 14:25, 28 February 2016 (UTC)Reply[reply]

    Strong  Support! And I knew :) --Edgars2007 (talk) 14:33, 28 February 2016 (UTC)Reply[reply]
     Support - Makes it easier to use constraints and other movie sites are also split by person/title etc. Mbch331 (talk) 14:43, 28 February 2016 (UTC)Reply[reply]
     Oppose We put a lot of effort in providing stable entities. Replacing a property which is used on many Wikipedia templates and on an unknown number of external projects, data reusers would lose the trust in stable Wikidata entities. --Pasleim (talk) 14:51, 28 February 2016 (UTC)Reply[reply]
     Comment I think development of providing varying urls for a property has already been discussed and should be planned. It wasn't initially thought needed for this one, but it should easily work for this one as well. The effort needed for this is less than to change 100'000s of identifiers.
    --- Jura 17:54, 28 February 2016 (UTC)Reply[reply]
     Comment Perhaps the most useful distinction this would come up with is the difference between names of real people (nm) and fictional characters (ch), because these can overlap on items about real people. Besides that, I don't see that much use in splitting the property. FallingGravity (talk) 21:56, 28 February 2016 (UTC)Reply[reply]
     Comment If it gets split up (which sounds like a huge amount of work for the wikis), please notify Wikipedias using this property. The German one is using it here. --mfb (talk) 22:28, 28 February 2016 (UTC)Reply[reply]
     Oppose What about having an additional property for characters (ch) only? Then the existing property could still handle tt, nm, ev and co and in a way that each item gets at most one IMDb id. In my opinion that's totally sufficient. --Jobu0101 (talk) 23:55, 28 February 2016 (UTC)Reply[reply]
     Support We shouldn't let past mistakes bind us, especially at this relatvely early stage of the poject. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:03, 29 February 2016 (UTC)Reply[reply]
     Support We need to fix nm/ch conflicts. —putnik 02:14, 1 March 2016 (UTC)Reply[reply]
    Depending on how you want to handle them, you can do that with the complex constraints already now and you probably would need to do that even if two properties.
    --- Jura 13:08, 8 March 2016 (UTC)Reply[reply]
     Oppose With 400 000+ items and 40+ templates using this is not a good solution. --Jklamo (talk) 21:36, 9 March 2016 (UTC)Reply[reply]
    Thanks for your thoughts. Opinions seem to differ about this. No consensus, so I'm going to do something else. Multichill (talk) 18:14, 27 March 2016 (UTC)Reply[reply]
    WikiProject Movies has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.  Strong support! @User:Pasleim current external url is provided by Wikimedia labs which guaranty of stability is no provided, as my self a user of Wikimedia labs had stability issues which made me not run bots on their servers beside that it's maintained by Dr. Smith not the community or the organization which is the least stable. BTW we can easily replace it with new properties using a bot, there is no reason for us to add backlinks to our labs. Also this proposal needs more attention, write it on community portal. Mjbmr (talk) 16:28, 26 September 2016 (UTC)Reply[reply]
    Can someone state the exact problem which the splitting of this property is intended to resolve? Danrok (talk) 16:38, 26 September 2016 (UTC)Reply[reply]
    Problem is that IMDb ID cover various concepts (movie, person, award etc.) and in case of person and character these two will overlap and one item will have both of these (like above mentioned Q91 has nm1118823 and ch0026778). --Jklamo (talk) 08:54, 27 September 2016 (UTC)Reply[reply]

    Different solutions[edit]

    Would you mind to tell us your preference?

    1. Leave it as it is (one identifier for everything)
    2. Two properties (P345 for tt, nm, ev, co and an additional new property for ch)
    1.  Support --Jobu0101 (talk) 12:54, 8 March 2016 (UTC). There are only 4017 items which use P345 for a ch IMDb id opposed to 400,000 items which use P345 in general. So we could keep most of the items as they are. --Jobu0101 (talk) 22:05, 9 March 2016 (UTC)Reply[reply]
    2.  SupportFallingGravity (talk) 15:37, 8 March 2016 (UTC)Reply[reply]
    3.  Oppose. I do not think it is a good solution. This method solves only one task, but all becomes extremely illogical to the end user. —putnik 18:19, 9 March 2016 (UTC)Reply[reply]
      I think it's quite logical. One property (this one) is for the real stuff and the other property (the new one) for the fictional stuff. By the way, instead of opposing this proposal, you could support one of the others or create a fourth solution proposal. --Jobu0101 (talk) 19:04, 9 March 2016 (UTC)Reply[reply]
    4.  Support Sounds reasonable. --Jklamo (talk) 21:36, 9 March 2016 (UTC)Reply[reply]
    5.  Support Let us have this workable solution right now. --Nucleos (talk) 10:08, 2 June 2016 (UTC)Reply[reply]
    6.  Oppose per discussion above.
      --- Jura 10:47, 2 June 2016 (UTC)Reply[reply]
    3. Five new properties for tt, nm, ev, co and ch

    RegEx for MediaWiki:Gadget-AuthorityControl.js[edit]

    Can't we also use regular expressions for tools like the Primary Sources Tool, so the URL would be correct instead of sth. like, which gives a 404 error. Queryzo (talk) 09:54, 23 March 2016 (UTC)Reply[reply]

    Yes, the link is currently broken because of that. I'm having trouble seeing when it changed. @Jura1:? Bovlb (talk) 19:08, 23 March 2016 (UTC)Reply[reply]
    It was changed following the problem at Property_talk:P345#Problem_with_URL_generation, but the conversion to external-id datatype might have broken that. @Hoo man: will your proposed change to the gadget correct that or can you undo the datatype conversion?
    --- Jura 06:07, 24 March 2016 (UTC)Reply[reply]
    @Queryzo, Jura1, Bovlb: Thinking about this, I think it might be desirable to undo the data type conversion in case there's consensus to deprecate this Property, as I don't see a problem with legacy identifiers not being actual identifiers. If there's no consensus to do that, we will need to find another way to handle this, but it's probably going to be rather painful.
    About the authority control gadget: It already has special handling for this property and that wasn't affected by the type conversion and also wont be affected by my proposed performance patch. But if a value is saved, the gadget is not being run, thus you'll see the (maybe wrong) link from Wikibase. Reloading the page will then give you the right link. Cheers, Hoo man (talk) 16:56, 24 March 2016 (UTC)Reply[reply]
    Currently the rules in the gadget seem the be ignored. All links just use the first formatter URL (P1630) statement. Mbch331 (talk) 20:53, 24 March 2016 (UTC)Reply[reply]
    I think the development needed to have these work without the gadget will be needed for other properties as well. Lydia probably already has it on her todo list. To avoid that we get incorrect links in one or the other configuration, I'd prefer to undo the conversion. Once the code is finalized, it can be converted again.
    --- Jura 11:40, 25 March 2016 (UTC)Reply[reply]
    @Jura1: There are no current plans for external identifier linking support for properties like these, conceptually this shouldn't be one property. Proper tooling support for this is very hard and I don't think it's worth spending time on. If there's an agreement to phase out this property, we can convert it back, as noted above. Cheers, Hoo man (talk) 15:39, 27 March 2016 (UTC)Reply[reply]
    @Hoo man: Why did you convert it when you were aware that this wont work? It was already mentioned on the list you processed.
    --- Jura 15:44, 27 March 2016 (UTC)Reply[reply]
    Because it should still work by the gadget overwriting it. It is just that the gadget often doesn't load on first load. But we need to solve the underlying issue now: the mixing up of what IMDB seems to be handling as different classes of identifiers. We could probably hack this up but I don't believe this is a good idea for several reasons: 1) we're just fixing it in one place while it is an issue in many others as well like 3rd party applications who we do not want to force to reimplement the special casing 2) it'd take quite some development effort that I believe is better spent on linking the identifiers in our RDF and JSON exports so Wikidata is actually a good citizen of the web of data instead of a dead-end 3) we open the door for a lot of complexity that we can and should avoid at this point. The question which datatype the property has is not really important for the decision if we're going to split up the property because the issues we are running into now are there no matter which datatype. --LydiaPintscher (talk) 18:06, 30 March 2016 (UTC)Reply[reply]
    The current solution didn't seem problematic until the conversion was done. Given that it's easier to add to line of code to do the links correctly, adding complexing to users adding or reusing this identifier seems to burden them in an unnecessary way. I'm not sure though if it's a good idea to wait for the gadget to overwrite it. It's not even sure if the gadget is active at all places. Given that it was mentioned by the community before the conversion, I think good development practice is either to implement the requested feature or to restore the previous solution.
    --- Jura 03:13, 31 March 2016 (UTC)Reply[reply]
    It looks like the links are working fine now except on the property page itself and in the property documentation above. If you go to The Godfather (Q47703), I get a correct link. Mbch331 (talk) 11:02, 6 April 2016 (UTC)Reply[reply]
    Mbch331 - when I load The Godfather (Q47703) the IMDB link shows as - and gives a 404. I think the best solution here might be to have a volunteer set up a some kind of resolving service for complex id's like this somewhere, say at WMF labs, and point the formatter url to that - so you could have the external id reference something like and that would redirect to the proper IMDB link. ArthurPSmith (talk) 15:46, 6 April 2016 (UTC)Reply[reply]
    For me it works fine, @ArthurPSmith: Do you have the authorityControl gadget activated? --Pasleim (talk) 16:14, 6 April 2016 (UTC)Reply[reply]
    The links also need to work without the gadget: For including them in the dumps, for showing them after edit but before the page is reloaded (as the gadget doesn't cover that), for mobile users, for non-JavaScript users, … We should not forget about this just because AuthorityControl can mangle the links in some cases. Cheers, Hoo man (talk) 16:36, 6 April 2016 (UTC)Reply[reply]
    @Pasleim: yes I have it activated, but it sometimes fails (as in this case). Though now it's working - same browser (MacOS Safari). Anyway, I agree with Hoo man, it really isn't optimal that we are link an id to a URL that is not actually functional, however some javascript interface may sometimes make it work ok. ArthurPSmith (talk) 18:57, 6 April 2016 (UTC)Reply[reply]
    Well, if we don't want to rely on a gadget, then there are 2 possible solutions: 1) Change the code so it can handle formatter URL's together with regex as a qualifier to select which formatter URL is needed. 2) Split up P345 in new properties (1 for nm, 1 for ch, 1 for tt, 1 for ev and 1 for co). (You could argue there is a third one: IMDb change the way their site works, but don't know if they're willing to do that). Mbch331 (talk) 20:02, 6 April 2016 (UTC)Reply[reply]
    @T.seppelt: Can't we use sth. you suggested in the filmportal discussion? Queryzo (talk) 21:24, 6 April 2016 (UTC)Reply[reply]

    Items with IMDb ID but without instance[edit]

    Query. Currently 1066 items. --Jobu0101 (talk) 12:52, 23 August 2016 (UTC)Reply[reply]

    It would be great to have a list just for nm-values. Queryzo (talk) 14:26, 23 August 2016 (UTC)Reply[reply]
    query for nm-values without P31 --Pasleim (talk) 14:28, 23 August 2016 (UTC)Reply[reply]
    265 items, this task is not too hard, somebody wants to help? Queryzo (talk) 15:25, 23 August 2016 (UTC)Reply[reply]
    now 113, thanks for helping hands so far ... Queryzo (talk) 21:00, 23 August 2016 (UTC)Reply[reply]
    I updated the P31 links at Wikidata:WikiProject_Movies/Tools#instance_of_.28P31.29 to use PetScan instead of Autolist.
    --- Jura 17:53, 30 August 2016 (UTC)Reply[reply]
    But please remember, that we can't mark items with P31=person, simply because it has nmX. There are some errors in values (adding wrong prefixes). --Edgars2007 (talk) 13:42, 4 September 2016 (UTC)Reply[reply]
    27 to go. Queryzo (talk) 20:59, 3 November 2016 (UTC)Reply[reply]


    The query is currently running and should produce a list at . Multichill (talk) 15:30, 29 October 2016 (UTC)Reply[reply]

    Nice, how we can easily import the data? Queryzo (talk) 20:24, 3 November 2016 (UTC)Reply[reply]
    I could do that. --Jobu0101 (talk) 22:13, 3 November 2016 (UTC)Reply[reply]
    But there are many wrong matches like "Q6619947 tt0488988". --Jobu0101 (talk) 22:17, 3 November 2016 (UTC)Reply[reply]
    is there a wrong match with instance of (P31) = film (Q11424)? Queryzo (talk) 22:26, 3 November 2016 (UTC)Reply[reply]
    @Multichill: ? Queryzo (talk) 19:18, 1 December 2016 (UTC)Reply[reply]
    Right, damn lists. You would need to check that it's instance of film (Q11424) or television series episode (Q21191270) and not a list before adding it. Multichill (talk) 21:04, 1 December 2016 (UTC)Reply[reply]
    @Multichill: I could match that list with [4], but now the list is gone ... ? Queryzo (talk) 07:19, 2 December 2016 (UTC)Reply[reply]
    @Multichill: ? Queryzo (talk) 22:40, 3 December 2016 (UTC)Reply[reply]
    The list is actually still there, but due to the fact the header starts on the same line as the message the other constraint has no results, the header isn't shown as a header. @Pasleim: could you check why your bot doesn't start the second results on a new line? Mbch331 (talk) 17:00, 4 December 2016 (UTC)Reply[reply]
    @Queryzo: I re-generated the list this afternoon, takes 47 minutes. Multichill (talk) 18:40, 4 December 2016 (UTC)Reply[reply]
    @Multichill: I added them for Q11424 and Q21191270. Can you refresh the list without the list-items? Is there useable content left? Queryzo (talk) 14:05, 6 December 2016 (UTC)Reply[reply]
    @Queryzo: I doubt you'll find more useful things in there. Running now, should be done in about an hour. Multichill (talk) 14:17, 6 December 2016 (UTC)Reply[reply]

    @Magnus Manske: Can we do an import including all items that are class/subclass of Q11424 or class Q21191270 (no subclass of "film")? Petscan seems not to support a manual list of Q-items yet. Queryzo (talk) 18:55, 30 November 2016 (UTC)Reply[reply]

    Constraint violations/P345 - "Single value" violations[edit]

    There are some items with one film (part 1 and part 2, same title) that was split in 2 parts at IMDb, but naturally only one article in wikipadia - e.g. see The Mad Woman in the Attic (Q3521720). How to set an exception? -- MovieFex (talk) 03:27, 14 February 2017 (UTC)Reply[reply]

    duo (Q10648343) as constraint exception[edit]

    We should add duo (Q10648343) as constraint exception because no value is a valid value for Coen brothers (Q56095). Together with has part(s) (P527) this can be used to output the child items and their ids with external templates like de:Template:IMDb does it in de:Die Jagd nach dem Tode. Instead I would create an complex constraint query for items that belong to duo (Q10648343) and have an imdb id that is not empty. Can anybody do that? Queryzo (talk) 07:16, 17 April 2017 (UTC)Reply[reply]

    You can add items such as Q56095 as exceptions, but I don't think changing the type constraint is a good idea if it's merely for "novalue". If you add "duo" as a valid type, people just start re-adding incorrect imdbs to duos and cleanup Ivan A. Krestinin did was for nothing.
    --- Jura 07:39, 17 April 2017 (UTC)Reply[reply]
    Then I would delete no value entries. Queryzo (talk) 12:41, 17 April 2017 (UTC)Reply[reply]

    Error in code for news[edit]

    hello, in the exemples, the id ni61008607 do not work (bad url generated). The good url is : . Thanks, --Bergil (talk) 12:49, 5 September 2017 (UTC)Reply[reply]

    more and more problems with length of string...[edit]

    I regularly add/import Imdb to actors, especially persons from not latin languages, since it allows to have acces to their name in English transcription.

    These last weeks, I had a lot of refusals, or constraint violations, even with id directly copied/pasted from the real Imdb page... [ see here.

    It seems that Imdb has gone to longer ids (8 or 9 figures) which are considered as "unexpted value" by constraint violation, and also rejected by Harvest Template, while they are perfectly valid on the site pov. @Pasleim: for HT.

    Would it be possible to check this, and perhaps allow a little more flexibility for the format of the id ?

    Thanks for your views. --Hsarrazin (talk) 18:44, 10 October 2017 (UTC)Reply[reply]

    IMDb Ids have 7 figures, in fact you have to cut the preceeding zero. When IMDb will have numbers up to nm9999999, we will fix the reg ex and set it to 8 figures. The reason for that is that nm0123456 won't be the same as nm00123456, but we need constraint violations for that. Queryzo (talk) 20:31, 12 October 2017 (UTC)Reply[reply]

    Deprecate character identifiers in old format ("ch")?[edit]

    It seems that IMDb is changing the format of character pages. Going forward, there will be one per film, not a general one.

    Supposedly, at some point links on identifiers will stop working. I don't think we should delete existing identifiers, but we could set them to deprecated with some explanatory item in "reason for deprecation".
    --- Jura 00:29, 26 November 2017 (UTC)Reply[reply]

    I added Q44374960 to these pages, I will request the rank to be changed at Wikidata:Bot requests.
    --- Jura 11:15, 2 December 2017 (UTC)Reply[reply]
    Wouldn't withdrawn identifier value (Q21441764) work? I'll rather see some general reason instead of specific ones. Sjoerd de Bruin (talk) 16:05, 2 December 2017 (UTC)Reply[reply]
    It's the entire group of identifiers that has been replaced with some other scheme. We could merely deprecate the values, but the option for reasons was added as people might not understand. Too bad we don't have items for other pages that get discontinued.
    --- Jura 16:14, 2 December 2017 (UTC)Reply[reply]
    The links are not working anymore, guess we should deprecate them now. Sjoerd de Bruin (talk) 17:52, 18 December 2017 (UTC)Reply[reply]
    As said before, the links don't work anymore, so why should we promote the use of it in the description?--CENNOXX (talk) 17:03, 1 July 2018 (UTC)Reply[reply]
    @CennoxX: Agreed, I restored your edit. We shouldn't be promoting a deprecated prefix in the description. Multichill (talk) 18:16, 1 July 2018 (UTC)Reply[reply]
    @Jura1, Sjoerddebruin, CennoxX, Multichill: but if character pages don't exist anymore, why do we keep the links to something which doesn't exist? Why don't we remove them instead of deprecating them? Maybe there's a chance for them to be restored someday, and that's why we are cautious? --Superchilum(talk to me!) 07:06, 11 July 2018 (UTC)Reply[reply]
    • We don't store links, but identifiers for concepts. If these happen to link somewhere, all the better. It's still possible to add more and use them to cross-check other databases. I don't see a problem with mentioning accepted formats in the description. Freebase or P2384 are gone, but we still have identifiers.
      Here, in theory, I think they should have remained with normal rank, but this may not be easily understood.
      --- Jura 12:03, 14 July 2018 (UTC)Reply[reply]
      Yes, it was incorrect for these to be marked as deprecated, because that means the identifier was never correct and if you want to find the Wikidata item when you have an identifier for a character, that the item with the deprecated statement is not the item you want. The deprecated rank and reason for deprecated rank (P2241) should be replaced by normal rank and end cause (P1534). - Nikki (talk) 08:17, 14 September 2018 (UTC)Reply[reply]

    Movie title identifier[edit]

    The "Allowed values" regex is wrong: movie identifiers have only 7 digits, not 8.--Fringio (talk) 23:31, 29 July 2018 (UTC)Reply[reply]

    but persons could now have 8 digits, see Mai Ngô (Q30920002). Queryzo (talk) 17:50, 1 August 2018 (UTC)Reply[reply]
    I've added the 8 identifiers for persons back.--CENNOXX (talk) 13:29, 9 August 2018 (UTC)Reply[reply]

    URL formatter[edit]

    I just changed the main URL formatter for this property; the reason is that the rerouting service at has not worked for at least a couple of days, so all the links from e.g. no:Mal:Filmlenker and other templates using the URL formatter property would fail. Whenever the service is back, the URL formatter could be changed back to that – I understand it was put in place because there are some frince cases where the URL I used ($1) don't work. Jon Harald Søby (talk) 12:34, 18 March 2019 (UTC)Reply[reply]

    Removal of aliases[edit]

    @Mike Novikoff: please stop removing useful aliases. The page you refer to (Help:Aliases#Criteria_for_inclusion_and_exclusion) is for items. This is a property so this doesn't apply here. It's common practice for properties to have quite a few aliases making it easier for editors to find and use it. So please, don't remove it any more. Multichill (talk) 21:40, 4 January 2020 (UTC)Reply[reply]

    @Multichill, can you please clarify what exactly these substrings and alternative capitalizations are useful for, and why? The search engine doesn't use capitalization, be it within items or properties, and it doesn't distinguish hyphens from whitespace, so everything I've removed could still be found. You can easily check that we can find even "iMdB", "iNteRneT-mOViE-dATABasE", or "mOVIE-dATABASE". Why would we need all this redundancy defined explicitly when it works anyway? — Mike Novikoff 23:30, 4 January 2020 (UTC)Reply[reply]
    I was under the impression this would mess up some workflows, but I think you're right. Multichill (talk) 10:59, 5 January 2020 (UTC)Reply[reply]

    Audio podcasts[edit]

    Just to explain my addition of Wikidata property related to podcasts (Q67198839) to instance of (P31): IMDb is now listing audio podcasts. Trivialist (talk) 10:19, 10 March 2020 (UTC)Reply[reply]

    Handling id redirects[edit]

    What's the best practice when updating IMDb IDs point to an old ID that is now a redirect to a new ID? For an example, resolving nm0811487 now results in a "301 Moved Permanently" to nm0118612. Should the old statement be replaced by the new ID? Or should the new ID be added while marking the as a deprecated rank? Josh404 (talk) 04:10, 13 April 2021 (UTC)Reply[reply]

    @Josh404: I would either mark the non-redirect one as preferred or mark the redirect one with an (unknown) end time (P582) or probably both. Technically deprecation isn't correct since it still works and also used to work. BrokenSegue (talk) 02:02, 29 May 2021 (UTC)Reply[reply]
    I saw this proposal since posting that question regarding
    Wikidata:Requests for comment/Handling of stored IDs after they've been deleted or redirected in the external database. One the proposal is to use reason for deprecated rank (P2241) redirect (Q45403344).
    For my own use cases keeping the old ID as still normal rank would make cross reference SPARQL queries a bit cleaner. Though, the single-value constraint (Q19474404) might be an issue with having multiple values.
    Do you think this type of a task could be performed by a bot? Should I write up a proposal? Just did a quick a random sample of IMDb statements, there tends to be 1 in 1000 redirects. It might take quite sometime to scan the entire 700k+ ID space, heh. Josh404 (talk) 03:18, 29 May 2021 (UTC)Reply[reply]
    Yeah, I disagree with that RfC's suggestion. I don't know if there is broad agreement on the right way to handle this case (some people delete, some people deprecate, I use end times). but just adding qualifiers is probably less problematic. It does seem weird to give a reason for deprecation but not to deprecate though. If you wrote up a proposal/bot to do this I would support it. I'd personally worried about getting banned by IMDb though. BrokenSegue (talk) 22:16, 29 May 2021 (UTC)Reply[reply]

    URL redirection service - Why?[edit]

    Is there any reason to still use the URL redirection service at instead of the direct URLs, at least for titles (tt\d{7,8}) and names (nm\d{7,8})? — Vincent Lefèvre (talk) 20:44, 3 February 2022 (UTC)Reply[reply]

    what would the formater be? the base paths for the different kinds of identifiers are different. BrokenSegue (talk) 23:21, 14 October 2022 (UTC)Reply[reply]

    Duplicate ID values[edit]

    Ingrid Cannonier (Q95750443) has two IMDb ID values, she's been recorded under two different names. This is being reported as a constraint violation (single-value). But isn't that an IMDb problem and we're just trying to reflect here at Wikidata what is being used elsewhere?-- 22:01, 14 October 2022 (UTC)Reply[reply]

    Add a subject named as (P1810) qualifier to solve the constraint violation. But the error is on the IMDb side too. They should have 1 entry for 1 person too and just use (as ...) to correct the name.
    I solved it for Ingrid Cannonier (Q95750443). Mbch331 (talk) 06:13, 15 October 2022 (UTC)Reply[reply]
    Thank you very much! Merging the two Ingrid's at IMDb, is that something you triggered? Since I used your suggestion of subject named as with Hansi Thoms-Evelt (Q95878693) myself for the first time: is there an easy way to notify IMDb editors without becoming one myself?-- 16:56, 22 October 2022 (UTC)Reply[reply]

    504 Gateway Time-out[edit]

    Unable to access the page via the link provided in the page https://fr .wikipedia. org/wiki/GHB_(movie). What is the problem? Braaark (talk) 21:17, 15 May 2023 (UTC)Reply[reply]

    works for me BrokenSegue (talk) 01:27, 16 May 2023 (UTC)Reply[reply]

    Abuse Filter false positive[edit]

    @DannyS712, Matěj Suchánek: this edit triggered the abusefilter. Not sure if the filter can be updated to only look at the target value. Multichill (talk) 10:18, 10 June 2023 (UTC)Reply[reply]

    Split (again)[edit]

    I think we should revisit this question asap, because 7 years after the voting - in the current form it is impossible to comprehensively use this property. Third party services constantly hang in timeout with 950k values - hundreds of duplicates, issues that hard to track, restrictions on how you can work with this, etc. At the moment I think the best option would be to flag this property as deprecated, add new tt, nm, ev, co properties with copying the values into the new properties. Then give about 5+ years to rebuild all infoboxes and bots to the new properties and then go back to discussion of the removing the merged one. This is a necessity that we will have to come to anyway. Unless the efficiency of WQS will increase tenfold to handle million of IDs at once (which is doubtful). Solidest (talk) 15:25, 22 August 2023 (UTC)Reply[reply]