Property talk:P1237
Jump to navigation
Jump to search
Documentation
Box Office Mojo film ID (former scheme)
identifier for a movie at the website Box Office Mojo
identifier for a movie at the website Box Office Mojo
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1237#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)Single value: this property generally contains a single value. (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/P1237#Single value, SPARQL
Type “film (Q11424)”: item must contain property “instance of (P31)” with classes “film (Q11424)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1237#Type Q11424, hourly updated report, SPARQLExceptions 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/P1237#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1237#Format, SPARQL
Conflicts with “instance of (P31): human (Q5)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1237#Conflicts with P31, hourly updated report, search, SPARQLConflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836), Wikimedia project page (Q14204246), Wikimedia template (Q11266439)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1237#Conflicts with P31, hourly updated report, SPARQLAllowed 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/P1237#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/P1237#Scope, SPARQL
![]() |
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
Discussion
[edit]BOM uses IMDb IDs now
[edit]It seems Box Office Mojo has been brought closer to the IMDb brand so much so it uses the IMDb ID (P345) now. What does this mean for the future of this property? The pages for names (people) are only available with an IMDb Pro subscription now (also using the IMDb ID instead of Box Office Mojo person ID (P2688)), while franchise and studio pages seem defunct now (along with Box Office Mojo franchise ID (former scheme) (P2530) and Box Office Mojo studio ID (P2531)). – Máté (talk) 09:03, 7 November 2019 (UTC)
- Also pinging @Jura1:. Yeah, noticed this last month, when the change happened. I think we should keep the properties and IDs as is for historical purposes. There are probably various sites and databases out there that still have the old IDs stored and keeping them makes matching and reconciliation of external databases with Wikidata easier. We also don't know if they keep the redirects working forever.
- I've already created a Mix'n'match catalogue for people IDs shortly before the change and created/matched all IDs. I discovered various cases where they used the wrong IMDb profile (mainly confusing people with other people of the same name), so I used Google and Bing caches and the Internet Archive to check old versions of the pages and matched the IDs to the items of the persons they used to represent. I've also created a catalogue for the movies via Bing and Google cache, but currently simply lack the time and energy to match 10,000 films (not to mention comparing it to - now quickly disappearing - cached versions of the pages to make sure they redirect to the correct IMDb IDs/film profiles). If we want to add the remaining IDs for studios and franchises, we should probably do so soon, as I'm not sure how long Google and Bing will have cached versions of the pages and the Internet Archive doesn't seem to have archived all pages of the website.
- And then, we probably have the same problem as with other sites/databases that use just a subset of an existing ID. Either we create new BOM IDs for movies and people that just duplicate the IMDb IDs, or we only add BOM as a third-party formatter URL (P3303) to IMDb ID (P345). --Kam Solusar (talk) 17:59, 7 November 2019 (UTC)
- I had been wondering how long they would keep them separate .. so 11 years is the answer. I guess the formatter url would have to be deprecated. --- Jura 07:39, 8 November 2019 (UTC)
Notified participants of WikiProject Movies Maybe now we must use "https://www.boxofficemojo.com/title/$1/" where $1 is equal to IMDb ID (P345)? --ValterVB (talk) 10:17, 12 December 2021 (UTC)
Categories:
- United States of America-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with unique value constraints
- Properties with single value constraints
- Properties with constraints on type
- Properties with format constraints
- Properties with conflicts with constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties about movies