Property talk:P38

Documentation

LinkedIn personal profile ID
identifier for a person, on the LinkedIn website

Represents	LinkedIn (Q2550)
Associated item	LinkedIn (Q2550)
Applicable "stated in" value	LinkedIn (Q2550)
Data type	External identifier
Allowed values	[\p{Ll}0-9\-&_'\.]+
Example	Chima Joseph Ugo (Q2) → ugochimobi
Formatter URL	https://www.linkedin.com/in/$1/
See also	LinkedIn organisation ID (P24)
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 Gratispaideia 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)> Map Random list
Proposal discussion	[not applicable Proposal discussion]
Search for values

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

Item “instance of (P3): human (Q4)”: Items with this property should also have “instance of (P3): human (Q4)”.

List of this constraint violations: Database reports/Constraint violations/P38#Item, hourly updated report, search, SPARQL

Single value: this property generally contains a single value.

Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P38#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items.

List of this constraint violations: Database reports/Constraint violations/P38#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)

Allowed entity types are Wikibase item datatype (Q799): the property may only be used on a certain entity type

Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P38#allowed entity types

Scope is as main value (Q793), as reference (Q780): the property must be used by specified way only

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

Conflicts with “website account on (P390): LinkedIn (Q2550)”: this property must not be used with the listed properties and values.

Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P38#Conflicts with, search, SPARQL

Format “[\p{L}0-9\-&_'’\.]+”: value must be formatted using this pattern (PCRE syntax).

Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P38#Format, SPARQL

Qualifiers “website username (P68), language of work or name (P35), start time (P174), end time (P175), has quality (P48), number of subscribers (P10), point in time (P80), subject named as (P82), archive URL (P191), archive date (P205), reason for deprecated rank (P344), reason for preferred rank (P345)”: this property should be used only with the listed qualifiers.

Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P38#Allowed qualifiers, SPARQL

Format “[^A-Z]+”: value must be formatted using this pattern (PCRE syntax).

Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P38#Format, SPARQL