Property talk:P2087

Latest comment: 3 years ago by Okhjon in topic Non-ascii characteres in ID

Documentation

Crunchbase person ID
Identifier for a person, in the Crunchbase database of companies and start-ups, operated by TechCrunch
Associated itemCrunchbase (Q10846831)
Applicable "stated in" valueCrunchbase (Q10846831)
Data typeExternal identifier
Domainpeople (note: this should be moved to the property statements)
Allowed values
According to this template: Valid CrunchBase URL slugs
According to statements in the property:
(?![a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12})[^A-Z /]+
When possible, data should only be stored as statements
ExampleMatt Cohler (Q4208540)matt-cohler
Angelina Jolie (Q13909)angelina-jolie
Chamillionaire (Q299132)kakim-chamillionaire-seriki
SourceWikipedia external links (note: this information should be moved to a property statement; use property source website for the property (P1896))
Formatter URLhttps://www.crunchbase.com/person/$1
See alsoCrunchbase organization ID (P2088)
Lists
Proposal discussionProposal discussion
Current uses
Total2,979
Main statement2,710 out of 1,796,286 (0% complete)91% of uses
Qualifier80.3% of uses
Reference2618.8% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P2087#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2087#Single value, hourly updated report, SPARQL
Conflicts with “Crunchbase organization ID (P2088): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2087#Conflicts with P2088, hourly updated report, search, SPARQL
Format “(?![a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12})[^A-Z /]+: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P2087#Format, hourly updated report, SPARQL
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2087#Item P31, hourly updated report, search, SPARQL
Item “occupation (P106): Items with this property should also have “occupation (P106)”. (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/P2087#Item P106, search, 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/P2087#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/P2087#Scope, SPARQL
 

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

Non-ascii characteres in ID edit

Crunchbase ID's requires non-ascii characteres. See the example at [1]https://www.wikidata.org/wiki/Q65553716 which links to

juantomás-garcía-molina but not to juantomas-garcia-molina.

FYI.

Olea (talk) 17:28, 14 October 2019 (UTC)Reply

Yes, I think we should fix this rule. Q33102150 uses guillaume-olivier-doré (note the é) as well. -- Okhjon (talk) 18:10, 24 January 2021 (UTC)Reply
Return to "P2087" page.