Property talk:P11460

Documentation

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

Plex media key
24 hex character identifier for media item on Plex; different than watch.plex.tv url slug

Represents	Plex (Q7204887)
Data type	External identifier
Domain	film (Q11424), film series (Q24856), television series season (Q3464665), television series episode (Q21191270), television series (Q5398426), television program (Q15416), podcast (Q24634210) or web series (Q526877)
Allowed values	[a-f0-9]{24}
Example	Apéritif (Q30612280) → 5d9c11154eefaa001f6364e0 Hannibal, season 1 (Q15991276) → 5d9c09bd3c3f87001f361344 Hannibal (Q888841) → 5d9c08544eefaa001f5daa50 Casino Royale (Q151904) → 5d7768686f4521001eaa5cac
Source	https://www.plex.tv/
Formatter URL	https://app.plex.tv/desktop/#!/provider/tv.plex.provider.metadata/details?key=/library/metadata/$1
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 Database reports/Constraint violations/P11460 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 139,767 Main statement 139,752 >99.9% of uses Qualifier 4 <0.1% of uses Reference 11 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “[a-f0-9]{24}”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P11460#Format, hourly updated report, SPARQL

Scope is as main value (Q54828448): 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/P11460#Scope, 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/P11460#Entity types

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/P11460#Unique value, 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/P11460#Single value, 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/P11460#Conflicts with P31, hourly updated report, search, SPARQL

Type “film (Q11424), film series (Q24856), television series season (Q3464665), television series episode (Q21191270), television series (Q5398426), television program (Q15416), podcast (Q24634210), web series (Q526877)”: item must contain property “instance of (P31), subclass of (P279)” with classes “film (Q11424), film series (Q24856), television series season (Q3464665), television series episode (Q21191270), television series (Q5398426), television program (Q15416), podcast (Q24634210), web series (Q526877)” 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/P11460#Type Q11424, Q24856, Q3464665, Q21191270, Q5398426, Q15416, Q24634210, Q526877, SPARQL

Use property for people

I cannot understand: is there a reason why property cannot be used for people? --93.70.150.168 00:43, 6 February 2024 (UTC)

Unfortunately Plex people are stored under their own namespace “/library/people/“. Where this property targets media under the “/library/metadata/“ key namespace. I’d support and help populate a “Plex People GUID” property if it was proposed. Josh404 (talk) 03:28, 6 February 2024 (UTC)

Thanks for the reply, @Josh404. However, there are other properties that have different namespaces depending on the type of content, for example Trakt.tv ID uses the namespaces movies/IDmovie and people/IDpeople. Although it would be necessary to correct all the current records (perhaps this can be done with a bot?) wouldn't it be more appropriate to modify the structure of Plex media key like that of Trakt.tv ID in the example above? --93.70.150.168 08:24, 6 February 2024 (UTC)

Changing the semantics and mass property edits aren’t a good idea once a property has been around for a while. The recommended path is to create a new property, use a bot to copy data over, and mark the old as deprecated. The old becomes hidden in from the UI in that case but still around via API. In any major change, a new property discussion is the right path forward. I can help facilitated that proposal if you need help.

I’m curious what you’re primary use case with the property is?

There’s another point of confusion which is that Plex has multiple metadata catalogs on their site. So for people, there exists both:

- 5d776825880197001ec90392: https://app.plex.tv/desktop/#!/provider/tv.plex.provider.discover/details?key=/library/people/5d776825880197001ec90392

- liam-neeson: https://watch.plex.tv/person/liam-neeson

I’ve considered proposing a new “Plex watch slug” property in that format of “type/name” rooted in the watch.plex.tv domain. The older key format has been around for a long time, is used for local Plex metadata matching, and scrapable via their API. While this watch.plex.tv domain has come around in the past year or so. I haven't found a good way to build an index of that system for my bot. Josh404 (talk) 17:23, 6 February 2024 (UTC)

I satisfy your curiosity: no particular use, mine is just a desire for completeness!
But why do you intend to name the property Plex watch slug? And would you limit it only to the insertion of people? I believe you are much more knowledgeable than I am, perhaps it would be more appropriate for you to create the property request.
And, in addition, a change similar to the one we are talking about happened for trakt.tv (Q84591894) and its Trakt.tv ID (P8013) and Trakt.tv film ID (P12492) properties. --94.34.248.123 07:40, 1 March 2024 (UTC)

Haha, yes, I too would love to see Plex people coverage just for completeness!

Maybe you're right "slug" isn't the best term. But I was trying to describe the fact that it's the word part of the URL rather than an internal ID.

What you're describing about the Trakt IDs is very similar. I do see the value in having both types of properties to cover the different use cases. Trakt.tv ID (P8013) is more of a user and web friendly identifier. While Trakt.tv film ID (P12492) is easier for API clients and bots to use. Internet Game Database game ID (P5794) and Internet Game Database numeric game ID (P9043) are another good example of this pair of properties pattern. Plex media key (P11460) is definitely more intended to be API and bot friendly. Josh404 (talk) 18:30, 1 March 2024 (UTC)