• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Filmow ID
identifier at the Filmow database of films and TV shows

Associated item	Filmow (Q5449163)
Applicable "stated in" value	Filmow (Q5449163)
Data type	External identifier
Domain	film (Q11424), human (Q5), television series season (Q3464665) or television series (Q5398426)
Allowed values	[at][1-9]\d*
Example	13 Reasons Why, season 2 (Q53679951) → t233906 Jane Russell (Q217033) → a64948 Selena (Q751130) → t1937 Kate Winslet (Q202765) → a35
Source	https://filmow.com/
Formatter URL	https://filmow.com/wd-$1
Related to country	Brazil (Q155) (See 95 others)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis 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) Usage history (main statement) Chart by item creation date Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Database reports/Constraint violations/P5233 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 2,806 Main statement 2,794 99.6% of uses Qualifier 4 0.1% of uses Reference 8 0.3% of uses
Search for values

Type “film (Q11424), human (Q5), television series season (Q3464665), television series (Q5398426)”: item must contain property “instance of (P31)” with classes “film (Q11424), human (Q5), television series season (Q3464665), television series (Q5398426)” or their subclasses (defined using subclass of (P279)). (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/P5233#Type Q11424, Q5, Q3464665, Q5398426, SPARQL

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/P5233#Single value, 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).
List of violations of this constraint: Database reports/Constraint violations/P5233#Unique value, SPARQL (every item), SPARQL (by value)

Format “[at][1-9]\d*”: 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/P5233#Format, SPARQL

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/P5233#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/P5233#Scope, SPARQL

Label required in languages: pt: Entities using this property should have labels in one of the following languages: pt (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/P5233#Label in 'pt' language, search, SPARQL

Label required in languages: pt-br: Entities using this property should have labels in one of the following languages: pt-br (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/P5233#Label in 'pt-br' language, search, SPARQL

Pattern ^.+\-([at][1-9]\d*)\/?$ will be automatically replaced to \1. Testing: TODO list

Currently, the property uses the slug (part of the URL) as an ID. But after looking around in the HTML source of the page, it seems we could also simply use the numerical ID that is part of that URL, instead. The formatter URL "https://filmow.com/filme/$1/" seems to work, so instead of "13-reasons-why-2a-temporada-t233906", we could just use "233906" instead (= https://filmow.com/filme/233906/). I think generally, using such unique IDs is preferable to using slugs, since slugs are more prone to change over time.

Currently, the property is barely used (only 59 uses), so I think switching to the other kind of ID wouldn't cause much trouble. Pinging @NMaia: as the property proposer. What do you think? --Kam Solusar (talk) 15:27, 11 September 2019 (UTC)[reply]

No problem, go ahead! NMaia (talk) 11:48, 12 September 2019 (UTC)[reply]

So, I was just about to make these changes, but it turns out I should have looked more closely into this earlier. I somehow totally overlooked that this property is not only for films/series but also for persons - sorry about that. As they apparently have two different IDs, one for films and one for persons, we'd also need two separate properties for these. However it seems they don't have the same kind of redirect/short url for persons as they have for films (or at least I can't find it). So just changing this property won't work and a separate property for persons would need to use the current slug-IDs anyway (while the film/series property could use the numerical ID). Not sure that would be a big improvement. --Kam Solusar (talk) 15:11, 20 September 2019 (UTC)[reply]